[Touch-packages] [Bug 1840359] Re: systemd-networkd-wait-online & two ethernet on board
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1840359 Title: systemd-networkd-wait-online & two ethernet on board Status in systemd package in Ubuntu: Expired Bug description: Since I've upgraded to 19.04 my boot was 3 minutes longer due to wait for network. I've tried many tricks, but today I have finally found the source = the bug. My PC has motherboard AsRock Z370M-ITX/ac which has 2 Ethernet ports. When I connect Ethernet cable just to the "first" device "enp3s0" boot is quick, when I connect Ethernet cable just to the "second" device "enp0s31f6" boot is about 3 minutes longer. It simply waits for the "enp3s0" device. Since there is no mark on the board or on the rear panel which port is "first" and which is "second" it's clear that the failure is on Ubuntu 19.04 side. Ubuntu 18.04 LTS has no such problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5.3 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Aug 15 21:55:12 2019 InstallationDate: Installed on 2017-12-22 (600 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=d383d414-f179-4df7-a8f3-890dacf8ca33 ro modprobe.blacklist=nouveau intel_iommu=on SourcePackage: systemd UpgradeStatus: Upgraded to disco on 2019-06-22 (54 days ago) dmi.bios.date: 03/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z370M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd03/21/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ370M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838464] Re: NFS volume not mounting with systemd
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
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/1838464
Title:
NFS volume not mounting with systemd
Status in systemd package in Ubuntu:
Expired
Bug description:
Hello,
I'm unable to mount NFS volume at boot time with systemd. Using Ubuntu
18.04.2 LTS.
I commented out /etc/fstab entry:
#192.168.1.103:/Multimedia/Music /mnt/nas/music/ nfs
_netdev,auto,user,vers=30 0
I created "/etc/systemd/system/mnt-nas-music.mount":
[Unit]
Description=NAS volume - Music
After=network.target
[Mount]
What=192.168.1.103:/Multimedia/Music
Where=/mnt/nas/music/
Type=nfs
Options=_netdev,auto,user,nfsvers=3
TimeoutSec=10
[Install]
WantedBy=multi-user.target
I enabled it with "systemctl enable mnt-nas-music.mount" so that when I run
"systemctl is-enabled mnt-nas-music.mount" I obtain:
enable
But I keep obtaining this error ("systemctl status mnt-nas-
music.mount"):
mnt-nas-music.mount - NAS volume - Music
Loaded: loaded (/etc/systemd/system/mnt-nas-music.mount; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-07-30 21:23:42 CEST;
29min ago
Where: /mnt/nas/music
What: 192.168.1.103:/Multimedia/Music
Process: 1530 ExecMount=/bin/mount 192.168.1.103:/Multimedia/Music
/mnt/nas/music -t nfs -o _netdev,user,nfsvers=3 (code=exited, status=32)
lug 30 21:23:42 ubuntu-desktop systemd[1]: Mounting NAS volume - Music...
lug 30 21:23:42 ubuntu-desktop mount[1530]: mount.nfs: Network is unreachable
lug 30 21:23:42 ubuntu-desktop systemd[1]: mnt-nas-music.mount: Mount process
exited, code=exited status=32
lug 30 21:23:42 ubuntu-desktop systemd[1]: mnt-nas-music.mount: Failed with
result 'exit-code'.
lug 30 21:23:42 ubuntu-desktop systemd[1]: Failed to mount NAS volume - Music.
If I run "journalctl -b" I notice that the attempt to mount NFS volume
happens before network is ready:
lug 30 21:23:42 ubuntu-desktop systemd[1]: Failed to mount NAS volume - Music.
lug 30 21:23:48 ubuntu-desktop NetworkManager[978]: [1564514628.2750]
device (enp2s0): Activation: successful, device activated.
I think this is a bug.
Thanks in advance
Michele
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1838464/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848360] Re: Screen alway returns to full brightness after wake up
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Screen alway returns to full brightness after wake up + [amdgpu] Screen alway returns to full brightness after wake up ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [amdgpu] Screen alway returns to full brightness after wake up + [amdgpu] [Lenovo ideapad 720S-13ARR] Screen always returns to full brightness after wake up -- 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/1848360 Title: [amdgpu] [Lenovo ideapad 720S-13ARR] Screen always returns to full brightness after wake up Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Every time when I open up my lid of my laptop, and wake up my system from sleeping,the screen will return to full brightness.Either I press the brightness - or + button,the brightness will back to normal immediately. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 00:05:56 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical 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:380c] InstallationDate: Installed on 2019-09-28 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: LENOVO 81BR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=d149e099-9234-443a-8b59-fa39ca1a8631 ro idle=nomwait ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6KCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 720S-13ARR dmi.modalias: dmi:bvnLENOVO:bvr6KCN30WW:bd07/04/2018:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR: dmi.product.family: ideapad 720S-13ARR dmi.product.name: 81BR dmi.product.sku: LENOVO_MT_81BR_BU_idea_FM_ideapad 720S-13ARR dmi.product.version: Lenovo ideapad 720S-13ARR 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/gnome-shell/+bug/1848360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Thanks for the confirmation! -- 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/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Invalid Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work
** Summary changed: - Lightdm is just a black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it + Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work -- 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/1847980 Title: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan Ermine (development branch). If i boot with linux-image-5.0.0-31-generic the Xorg works well. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 14 11:15:23 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.42 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.36 dmi.chassis.asset.tag: CZC64082W1 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: X3J10ET#ABZ dmi.sys.vendor: HP 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro nomodeset resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Tags: eoan ubuntu Uname: Linux 5.3.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/19/2019 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.42
[Touch-packages] [Bug 1848374] Re: apt remove of gstreamer also tries to remove ubuntu-desktop
As a point of order, how does one remove gstreamer and all of it's plugins so that a new one can be compiled and then installed? -- 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/1848374 Title: apt remove of gstreamer also tries to remove ubuntu-desktop Status in apt package in Ubuntu: Invalid Bug description: Ubuntu 18.04 after a fresh install i've noticed that there are several packages, that although seem innocuous, if removed will remove the entire desktop with it. The following example contains an attempt to remove gstreamer as it was install unintentionally with the extra software checkmark on install. However, attempting to remove gstreamer will also remove the desktop? That doesn't seem correct. sudo apt remove gstreamer1.0-alsa gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 Reading package lists... Done Building dependency tree Reading state information... Done Package 'gstreamer1.0-plugins-bad' is not installed, so not removed The following packages were automatically installed and are no longer required: liba52-0.7.4 libaacs0 libavfilter6 libavformat57 libavresample3 libbdplus0 libbluray2 libbrotli1 libbs2b0 libchromaprint1 libdvdnav4 libdvdread4 libflite1 libgme0 libmpeg2-4 libmysofa0 libnorm1 libopencore-amrnb0 libopencore-amrwb0 libopenmpt0 libpgm-5.2-0 libpostproc54 librubberband2 libsidplay1v5 libssh-gcrypt-4 libwoff1 libzmq5 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: policykit-1-gnome The following packages will be REMOVED: apturl cheese deja-dup evince gdm3 gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0 gir1.2-rb-3.0 gir1.2-totem-1.0 gir1.2-webkit2-4.0 gnome-calendar gnome-control-center gnome-getting-started-docs gnome-initial-setup gnome-online-accounts gnome-shell gnome-software gnome-software-plugin-snap gnome-todo gnome-user-docs gnome-user-guide gnome-video-effects gstreamer1.0-alsa gstreamer1.0-clutter-3.0 gstreamer1.0-fluendo-mp3 gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-libav gstreamer1.0-packagekit gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio gstreamer1.0-tools gstreamer1.0-vaapi gstreamer1.0-x libcheese-gtk25 libcheese8 libclutter-gst-3.0-0 libdmapsharing-3.0-2 libedataserverui-1.2-2 libevview3-3 libfreerdp-client2-2 libgoa-backend-1.0-1 libgstreamer-gl1.0-0 libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libreoffice-avmedia-backend-gstreamer librhythmbox-core10 libtotem0 libwebkit2gtk-4.0-37 libyelp0 mutter nautilus-share packagekit packagekit-tools remmina-plugin-rdp rhythmbox rhythmbox-plugin-alternative-toolbar rhythmbox-plugins shotwell totem totem-plugins ubuntu-desktop ubuntu-docs ubuntu-release-upgrader-gtk ubuntu-session ubuntu-software update-manager update-notifier yelp zenity The following NEW packages will be installed: policykit-1-gnome 0 upgraded, 1 newly installed, 75 to remove and 0 not upgraded. Need to get 24.0 kB of archives. After this operation, 134 MB disk space will be freed. Do you want to continue? [Y/n] The expected behavior is that after we remove gstreamer, we should still have the desktop. Had I proceeded, it is likely that the machine just would have refused to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1848374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848394] [NEW] software properteries shows "open source" for proprietary nvidia driver
Public bug reported: User installed 19.10 and opened software properties. The nvidia binary driver shows as an "open source" driver. It should show "proprietary" See screenshot ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.98.5 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 01:23:12 2019 InstallationDate: Installed on 2019-10-16 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ** Attachment added: "photo_2019-10-16_23-20-33.jpg" https://bugs.launchpad.net/bugs/1848394/+attachment/5297574/+files/photo_2019-10-16_23-20-33.jpg -- 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/1848394 Title: software properteries shows "open source" for proprietary nvidia driver Status in software-properties package in Ubuntu: New Bug description: User installed 19.10 and opened software properties. The nvidia binary driver shows as an "open source" driver. It should show "proprietary" See screenshot ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.98.5 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 01:23:12 2019 InstallationDate: Installed on 2019-10-16 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1848394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working
not asking if the codec directly connects to DSP, please ask if internal mic connects to DSP or codec? -- 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/1793410 Title: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04 on it. Everything works except the internal microphone. I have also tested with an external microphone and this didn't work either. I have worked my way through all the suggested solutions I could find, including trying to reconfigure the pins using hdajacketask. In pavucontrol I have options for Internal Microphone and Microphone (unplugged) but the internal mic only captures static noise. The latest HD-Audio Codec-Specific Models has configurations for alc255-acer and alc256 for some other models, but setting options snd- hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve the issue with any of these. Some info - lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point- LP HD Audio (rev 21) cat /proc/asound/cards: 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf1a8000 irq 127 dmesg | grep snd: [3.944593] snd_hda_core: loading out-of-tree module taints kernel. [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0) [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0) [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, version 0.201808050301~ubuntu18.04.1 [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.013068] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [4.013069] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 info on node 12 from cat /proc/asound/card*/codec\#*: Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x02 0x02] Pincap 0x0020: IN Pin Default 0x4000: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x0 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Let me know if you need any other information. James --- Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 06/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Erdinger_KL dmi.board.vendor: KBL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF315-52 dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
This bug was fixed in the package unity-control-center - 15.04.0+19.10.20190921-0ubuntu1 --- unity-control-center (15.04.0+19.10.20190921-0ubuntu1) eoan; urgency=medium [ Khurshid Alam ] * Port media keys to use com.canonical.unity.settings-daemon. LP: #1842324 (LP: #1842324) -- Sebastien Bacher Sat, 21 Sep 2019 11:09:43 + ** Changed in: unity-control-center (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-control-center source package in Eoan: Fix Released Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848374] Re: apt remove of gstreamer also tries to remove ubuntu-desktop
The behaviour is correct. The desktop needs gstreamer so removing gstreamer removes the desktop. ** Changed in: apt (Ubuntu) Status: New => Won't Fix ** Changed in: apt (Ubuntu) Status: Won't Fix => Invalid -- 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/1848374 Title: apt remove of gstreamer also tries to remove ubuntu-desktop Status in apt package in Ubuntu: Invalid Bug description: Ubuntu 18.04 after a fresh install i've noticed that there are several packages, that although seem innocuous, if removed will remove the entire desktop with it. The following example contains an attempt to remove gstreamer as it was install unintentionally with the extra software checkmark on install. However, attempting to remove gstreamer will also remove the desktop? That doesn't seem correct. sudo apt remove gstreamer1.0-alsa gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 Reading package lists... Done Building dependency tree Reading state information... Done Package 'gstreamer1.0-plugins-bad' is not installed, so not removed The following packages were automatically installed and are no longer required: liba52-0.7.4 libaacs0 libavfilter6 libavformat57 libavresample3 libbdplus0 libbluray2 libbrotli1 libbs2b0 libchromaprint1 libdvdnav4 libdvdread4 libflite1 libgme0 libmpeg2-4 libmysofa0 libnorm1 libopencore-amrnb0 libopencore-amrwb0 libopenmpt0 libpgm-5.2-0 libpostproc54 librubberband2 libsidplay1v5 libssh-gcrypt-4 libwoff1 libzmq5 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: policykit-1-gnome The following packages will be REMOVED: apturl cheese deja-dup evince gdm3 gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0 gir1.2-rb-3.0 gir1.2-totem-1.0 gir1.2-webkit2-4.0 gnome-calendar gnome-control-center gnome-getting-started-docs gnome-initial-setup gnome-online-accounts gnome-shell gnome-software gnome-software-plugin-snap gnome-todo gnome-user-docs gnome-user-guide gnome-video-effects gstreamer1.0-alsa gstreamer1.0-clutter-3.0 gstreamer1.0-fluendo-mp3 gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-libav gstreamer1.0-packagekit gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio gstreamer1.0-tools gstreamer1.0-vaapi gstreamer1.0-x libcheese-gtk25 libcheese8 libclutter-gst-3.0-0 libdmapsharing-3.0-2 libedataserverui-1.2-2 libevview3-3 libfreerdp-client2-2 libgoa-backend-1.0-1 libgstreamer-gl1.0-0 libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libreoffice-avmedia-backend-gstreamer librhythmbox-core10 libtotem0 libwebkit2gtk-4.0-37 libyelp0 mutter nautilus-share packagekit packagekit-tools remmina-plugin-rdp rhythmbox rhythmbox-plugin-alternative-toolbar rhythmbox-plugins shotwell totem totem-plugins ubuntu-desktop ubuntu-docs ubuntu-release-upgrader-gtk ubuntu-session ubuntu-software update-manager update-notifier yelp zenity The following NEW packages will be installed: policykit-1-gnome 0 upgraded, 1 newly installed, 75 to remove and 0 not upgraded. Need to get 24.0 kB of archives. After this operation, 134 MB disk space will be freed. Do you want to continue? [Y/n] The expected behavior is that after we remove gstreamer, we should still have the desktop. Had I proceeded, it is likely that the machine just would have refused to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1848374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
Hello Khurshid, or anyone else affected, Accepted unity-control-center into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity- control-center/15.04.0+19.10.20190921-0ubuntu1 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: unity-control-center (Ubuntu Eoan) Status: In Progress => 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 ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Committed Status in unity-greeter package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-control-center source package in Eoan: Fix Committed Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848354] Re: upgrade-between-snapshots autopkgtest is flaky
Hello Balint, or anyone else affected, Accepted unattended-upgrades into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unattended- upgrades/1.14ubuntu1.1 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. ** Tags added: block-proposed-eoan ** 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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1848354 Title: upgrade-between-snapshots autopkgtest is flaky Status in unattended-upgrades package in Ubuntu: Fix Committed Status in unattended-upgrades source package in Eoan: Fix Committed Bug description: [Impact] * Flaky upgrade-between-snapshots autopkgtest prevents developers to use the test efficiently. [Test Case] * Run autopkgtests, observe the upgrade-between-snapshots test passing or failing but being marked as FLAKY. [Regression Potential] * None, the test was failing often due to connectivity/internal errors of snapshot.debian.org. [Other Info] * The whole autopkgtest is marked to be failing on amd64 to mitigate the single flaky test, this marking can be removed after marking this single flaky test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760910] Re: Gdebi crash in Ubuntu Studio 18.04
I've seen this problem in every recent Xubuntu release (17.10--19.04). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1760910 Title: Gdebi crash in Ubuntu Studio 18.04 Status in gdebi package in Ubuntu: Confirmed Bug description: Gdebi opens normal, but when you click install package, it closes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi 0.9.5.7+nmu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10 Uname: Linux 4.15.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Apr 3 12:31:17 2018 InstallationDate: Installed on 2018-03-29 (4 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180328) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1760910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821810] Re: gdebi crashes when trying to install packages
I'm a Xubuntu flavour user and I've never seen Gdebi work (17.10-19.04). It just closes immediately after I press "Install" button. If I run Gdebi with root privilege through terminal (sudo -i gdebi) then it works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1821810 Title: gdebi crashes when trying to install packages Status in gdebi package in Ubuntu: Confirmed Bug description: When I try to install some deb packages gdebi disapears. It does not show me any error report. It will just disapear from my screen. Lubuntu 18.4 LTS gdebi 0.9.5.7+nmu2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi 0.9.5.7+nmu2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 26 23:30:04 2019 InstallationDate: Installed on 2019-03-18 (8 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1821810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5
Hello Matthias, or anyone else affected, Accepted python3-stdlib-extensions into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-stdlib- extensions/3.7.5-1build1 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: python3-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 python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.5 Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Fix Committed Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in python3-defaults source package in Disco: New Status in python3-stdlib-extensions source package in Disco: New Status in python3.6 source package in Disco: New Status in python3.7 source package in Disco: New Status in python3-defaults source package in Eoan: New Status in python3-stdlib-extensions source package in Eoan: Fix Committed Status in python3.6 source package in Eoan: New Status in python3.7 source package in Eoan: Fix Committed Bug description: Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier subminor upstream releases (LP: #1822993). SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the 3.6.9 release. python3-stdlib-extensions also updates the modules to the 3.6.9 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. TODO: update after test rebuild http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848374] [NEW] apt remove of gstreamer also tries to remove ubuntu-desktop
Public bug reported: Ubuntu 18.04 after a fresh install i've noticed that there are several packages, that although seem innocuous, if removed will remove the entire desktop with it. The following example contains an attempt to remove gstreamer as it was install unintentionally with the extra software checkmark on install. However, attempting to remove gstreamer will also remove the desktop? That doesn't seem correct. sudo apt remove gstreamer1.0-alsa gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 Reading package lists... Done Building dependency tree Reading state information... Done Package 'gstreamer1.0-plugins-bad' is not installed, so not removed The following packages were automatically installed and are no longer required: liba52-0.7.4 libaacs0 libavfilter6 libavformat57 libavresample3 libbdplus0 libbluray2 libbrotli1 libbs2b0 libchromaprint1 libdvdnav4 libdvdread4 libflite1 libgme0 libmpeg2-4 libmysofa0 libnorm1 libopencore-amrnb0 libopencore-amrwb0 libopenmpt0 libpgm-5.2-0 libpostproc54 librubberband2 libsidplay1v5 libssh-gcrypt-4 libwoff1 libzmq5 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: policykit-1-gnome The following packages will be REMOVED: apturl cheese deja-dup evince gdm3 gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0 gir1.2-rb-3.0 gir1.2-totem-1.0 gir1.2-webkit2-4.0 gnome-calendar gnome-control-center gnome-getting-started-docs gnome-initial-setup gnome-online-accounts gnome-shell gnome-software gnome-software-plugin-snap gnome-todo gnome-user-docs gnome-user-guide gnome-video-effects gstreamer1.0-alsa gstreamer1.0-clutter-3.0 gstreamer1.0-fluendo-mp3 gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-libav gstreamer1.0-packagekit gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio gstreamer1.0-tools gstreamer1.0-vaapi gstreamer1.0-x libcheese-gtk25 libcheese8 libclutter-gst-3.0-0 libdmapsharing-3.0-2 libedataserverui-1.2-2 libevview3-3 libfreerdp-client2-2 libgoa-backend-1.0-1 libgstreamer-gl1.0-0 libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libreoffice-avmedia-backend-gstreamer librhythmbox-core10 libtotem0 libwebkit2gtk-4.0-37 libyelp0 mutter nautilus-share packagekit packagekit-tools remmina-plugin-rdp rhythmbox rhythmbox-plugin-alternative-toolbar rhythmbox-plugins shotwell totem totem-plugins ubuntu-desktop ubuntu-docs ubuntu-release-upgrader-gtk ubuntu-session ubuntu-software update-manager update-notifier yelp zenity The following NEW packages will be installed: policykit-1-gnome 0 upgraded, 1 newly installed, 75 to remove and 0 not upgraded. Need to get 24.0 kB of archives. After this operation, 134 MB disk space will be freed. Do you want to continue? [Y/n] The expected behavior is that after we remove gstreamer, we should still have the desktop. Had I proceeded, it is likely that the machine just would have refused to boot. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1848374 Title: apt remove of gstreamer also tries to remove ubuntu-desktop Status in apt package in Ubuntu: New Bug description: Ubuntu 18.04 after a fresh install i've noticed that there are several packages, that although seem innocuous, if removed will remove the entire desktop with it. The following example contains an attempt to remove gstreamer as it was install unintentionally with the extra software checkmark on install. However, attempting to remove gstreamer will also remove the desktop? That doesn't seem correct. sudo apt remove gstreamer1.0-alsa gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 Reading package lists... Done Building dependency tree Reading state information... Done Package 'gstreamer1.0-plugins-bad' is not installed, so not removed The following packages were automatically installed and are no longer required: liba52-0.7.4 libaacs0 libavfilter6 libavformat57 libavresample3 libbdplus0 libbluray2 libbrotli1 libbs2b0 libchromaprint1 libdvdnav4 libdvdread4 libflite1 libgme0 libmpeg2-4 libmysofa0 libnorm1 libopencore-amrnb0 libopencore-amrwb0 libopenmpt0 libpgm-5.2-0 libpostproc54 librubberband2 libsidplay1v5 libssh-gcrypt-4 libwoff1 libzmq5 Use 'sudo
[Touch-packages] [Bug 1377924] Re: ecryptfs fails to mount (Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING)
Issue happens if running in tmux. -- 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/1377924 Title: ecryptfs fails to mount (Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING) Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: Invalid Status in x2goclient package in Ubuntu: Confirmed Bug description: This is a reincarnation of Bug #1234412. Looks like issue is not related to specific kernel versions. Currently I am observing two Trusty (14.04) machines, with very close configuration, running same kernel: 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64. One is able to mount without the problem but the other is refusing: $ mount -t ecryptfs sec sec Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING; there is something wrong with your kernel keyring. Did you build key retention support into your kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1377924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5
Hello Matthias, or anyone else affected, Accepted python3.7 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3.7/3.7.5-1ubuntu1 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: python3.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 python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.5 Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: New Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in python3-defaults source package in Disco: New Status in python3-stdlib-extensions source package in Disco: New Status in python3.6 source package in Disco: New Status in python3.7 source package in Disco: New Status in python3-defaults source package in Eoan: New Status in python3-stdlib-extensions source package in Eoan: New Status in python3.6 source package in Eoan: New Status in python3.7 source package in Eoan: Fix Committed Bug description: Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier subminor upstream releases (LP: #1822993). SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the 3.6.9 release. python3-stdlib-extensions also updates the modules to the 3.6.9 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. TODO: update after test rebuild http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843381] Re: Dell system takes a long time to connect network with external dock
Also I marked this invalid for Eoan, as the retry-interface-renaming has been removed in Eoan; @cktenn can you test there and verify this bug doesn't exist for Eoan? ** Tags added: bionic ddstreet disco systemd -- 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/1843381 Title: Dell system takes a long time to connect network with external dock Status in OEM Priority Project: New Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: Invalid Bug description: This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1843381] Re: Dell system takes a long time to connect network with external dock
@cktenn could you try the systemd package for either bionic and/or disco from here: https://launchpad.net/~ddstreet/+archive/ubuntu/systemd That includes: https://git.launchpad.net/~ubuntu-support-team/ubuntu/+source/systemd/commit/?id=173071ae695e11c1549656a7b40d2201681e733e I don't love it, but I think that is the 'least bad' way of handling this without affecting any current users. ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Eoan) Status: New => Invalid ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Disco) Status: New => In Progress ** Changed in: systemd (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress -- 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/1843381 Title: Dell system takes a long time to connect network with external dock Status in OEM Priority Project: New Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: Invalid Bug description: This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1848360] [NEW] Screen alway returns to full brightness after wake up
Public bug reported: Every time when I open up my lid of my laptop, and wake up my system from sleeping,the screen will return to full brightness.Either I press the brightness - or + button,the brightness will back to normal immediately. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 00:05:56 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical 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:380c] InstallationDate: Installed on 2019-09-28 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: LENOVO 81BR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=d149e099-9234-443a-8b59-fa39ca1a8631 ro idle=nomwait ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6KCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 720S-13ARR dmi.modalias: dmi:bvnLENOVO:bvr6KCN30WW:bd07/04/2018:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR: dmi.product.family: ideapad 720S-13ARR dmi.product.name: 81BR dmi.product.sku: LENOVO_MT_81BR_BU_idea_FM_ideapad 720S-13ARR dmi.product.version: Lenovo ideapad 720S-13ARR 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan 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/1848360 Title: Screen alway returns to full brightness after wake up Status in xorg package in Ubuntu: New Bug description: Every time when I open up my lid of my laptop, and wake up my system from sleeping,the screen will return to full brightness.Either I press the brightness - or + button,the brightness will back to normal immediately. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 00:05:56 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical 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:380c] InstallationDate: Installed on 2019-09-28 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: LENOVO 81BR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=d149e099-9234-443a-8b59-fa39ca1a8631 ro idle=nomwait ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6KCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 720S-13ARR dmi.modalias:
[Touch-packages] [Bug 1843099] Re: Unattended upgrades maybe very slow and time out on shutdown
I created a separate bug (LP: #1848357) for the specific fix landing in the PR in #13, because the majority of this problem reported here will still be present. The full fix is being prepared here: https://github.com/rbalint/unattended-upgrades/tree/apply-pinning -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1843099 Title: Unattended upgrades maybe very slow and time out on shutdown Status in unattended-upgrades package in Ubuntu: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu * Ubuntu Xenial 16.04.6 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center * 1.1ubuntu1.18.04.7~16.04.3 3) What you expected to happen * Packages to be upgraded on reboot / shutdown. 4) What happened instead * The host just rebooted. Didn't perform upgrades. No useful output either until I enabled debug logging in the systemd unit file. I'm reporting a new bug but this is very similar to #1806487 and I'm actually wondering if it resurfaced somehow. We're running Ubuntu Xenial 16.04.6 which has 1.1ubuntu1.18.04.7~16.04.3 installed. I see that #1806487 was resolved with 1.1ubuntu1.18.04.7~16.04.2. However I'm seeing similar behavior. So far I've modified systemd to see if anything stands out. I do have an strace and then just debug mode. Unless needed, simply put, this is what a reboot with debug logging looks like (i.e. unattended-upgrades-shutdown.log): 2019-09-06 09:20:04,871 DEBUG - Waiting for signal to start operation 2019-09-06 09:20:43,996 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2019-09-06 09:20:43,996 DEBUG - Starting countdown of 25.0 minutes 2019-09-06 09:20:43,997 DEBUG - get_lock returned 7 2019-09-06 09:20:43,997 DEBUG - lock not taken I hope that helps, please let me know if you need anything else from me or if I can provide any more information. I've done this many times before, this is the first time it hasn't worked. When I patched around the end of May, all went well. My other variants worked, well mainly Trusty but that's EOL for public access. Bionic doesn't seem to have anything it needs to update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1843099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848357] [NEW] Adjusting transitive dependencies of packages slows down unattended-upgrades a lot
Public bug reported: [Impact] * Unattended-upgrades tries to mark packages for upgrade and when it fails to do so and falls back to mark adjusting packages to use candidates from allowed origins it can spend a lot of CPU time on packages which are not installable in the end. [Test Case] * Mark an upgradable package from the security pocket as held. * Observe u-u adjusting only direct dependencies, instead of doing it recursively. [Regression Potential] * U-u may fail to install updates due to APT not finding a solution without having transitive dependences adjusted. In those cases the update should mark the transitive dependencies which enable the update as direct dependencies. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1848357 Title: Adjusting transitive dependencies of packages slows down unattended- upgrades a lot Status in unattended-upgrades package in Ubuntu: New Bug description: [Impact] * Unattended-upgrades tries to mark packages for upgrade and when it fails to do so and falls back to mark adjusting packages to use candidates from allowed origins it can spend a lot of CPU time on packages which are not installable in the end. [Test Case] * Mark an upgradable package from the security pocket as held. * Observe u-u adjusting only direct dependencies, instead of doing it recursively. [Regression Potential] * U-u may fail to install updates due to APT not finding a solution without having transitive dependences adjusted. In those cases the update should mark the transitive dependencies which enable the update as direct dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843099] Re: Unattended upgrades maybe very slow and time out on shutdown
** Summary changed: - Unattended upgrades does not work on shutdown + Unattended upgrades maybe very slow and time out on shutdown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1843099 Title: Unattended upgrades maybe very slow and time out on shutdown Status in unattended-upgrades package in Ubuntu: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu * Ubuntu Xenial 16.04.6 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center * 1.1ubuntu1.18.04.7~16.04.3 3) What you expected to happen * Packages to be upgraded on reboot / shutdown. 4) What happened instead * The host just rebooted. Didn't perform upgrades. No useful output either until I enabled debug logging in the systemd unit file. I'm reporting a new bug but this is very similar to #1806487 and I'm actually wondering if it resurfaced somehow. We're running Ubuntu Xenial 16.04.6 which has 1.1ubuntu1.18.04.7~16.04.3 installed. I see that #1806487 was resolved with 1.1ubuntu1.18.04.7~16.04.2. However I'm seeing similar behavior. So far I've modified systemd to see if anything stands out. I do have an strace and then just debug mode. Unless needed, simply put, this is what a reboot with debug logging looks like (i.e. unattended-upgrades-shutdown.log): 2019-09-06 09:20:04,871 DEBUG - Waiting for signal to start operation 2019-09-06 09:20:43,996 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2019-09-06 09:20:43,996 DEBUG - Starting countdown of 25.0 minutes 2019-09-06 09:20:43,997 DEBUG - get_lock returned 7 2019-09-06 09:20:43,997 DEBUG - lock not taken I hope that helps, please let me know if you need anything else from me or if I can provide any more information. I've done this many times before, this is the first time it hasn't worked. When I patched around the end of May, all went well. My other variants worked, well mainly Trusty but that's EOL for public access. Bionic doesn't seem to have anything it needs to update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1843099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848354] [NEW] upgrade-between-snapshots autopkgtest is flaky
Public bug reported: [Impact] * Flaky upgrade-between-snapshots autopkgtest prevents developers to use the test efficiently. [Test Case] * Run autopkgtests, observe the upgrade-between-snapshots test passing or failing but being marked as FLAKY. [Regression Potential] * None, the test was failing often due to connectivity/internal errors of snapshot.debian.org. [Other Info] * The whole autopkgtest is marked to be failing on amd64 to mitigate the single flaky test, this marking can be removed after marking this single flaky test. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: Fix Committed ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1848354 Title: upgrade-between-snapshots autopkgtest is flaky Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: [Impact] * Flaky upgrade-between-snapshots autopkgtest prevents developers to use the test efficiently. [Test Case] * Run autopkgtests, observe the upgrade-between-snapshots test passing or failing but being marked as FLAKY. [Regression Potential] * None, the test was failing often due to connectivity/internal errors of snapshot.debian.org. [Other Info] * The whole autopkgtest is marked to be failing on amd64 to mitigate the single flaky test, this marking can be removed after marking this single flaky test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848348] [NEW] I get segmentation fault (core dumped) error when running some python scripts from the command line
Public bug reported: I get a segmentation fault (core dumped) error when running some python scripts from the command line. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.15.0-65.74~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 16 16:22:39 2019 InstallationDate: Installed on 2019-06-29 (109 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) SourcePackage: python-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Summary changed: - I get segmentation fault (core dumped) error when running some python scripts from the coamm + I get segmentation fault (core dumped) error when running some python scripts from the command line -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1848348 Title: I get segmentation fault (core dumped) error when running some python scripts from the command line Status in python-defaults package in Ubuntu: New Bug description: I get a segmentation fault (core dumped) error when running some python scripts from the command line. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.15.0-65.74~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 16 16:22:39 2019 InstallationDate: Installed on 2019-06-29 (109 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) SourcePackage: python-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1848348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848237] Re: amd64-only test running on i386
I just uploaded it to the Eoan unapproved queue. Apologies for not
updating the changelog with the bug, but I think we can just manually
track it via this bug. Sahid had run autopkgtests successfully but
seeing as it's release week I wanted to be safe and land it via bileto
but I've given up on that. Anyway it is fixed in python-pyeclib
1.5.0-1ubuntu6.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1848237
Title:
amd64-only test running on i386
Status in python-pyeclib package in Ubuntu:
New
Status in six package in Ubuntu:
Invalid
Bug description:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386
tests is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages
[18.0 kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in
__init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyeclib/+bug/1848237/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848237] Re: amd64-only test running on i386
Heh, so do I (ticket 3822), I pinged sil2100 about it and he said he
will take a look later.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1848237
Title:
amd64-only test running on i386
Status in python-pyeclib package in Ubuntu:
New
Status in six package in Ubuntu:
Invalid
Bug description:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386
tests is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages
[18.0 kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in
__init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyeclib/+bug/1848237/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848237] Re: amd64-only test running on i386
Hi Andreas,
We currently have a fix for this going in
https://bileto.ubuntu.com/#/ticket/3823
but autopkgtests don't seem to be returning results.
Thanks,
Corey
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1848237
Title:
amd64-only test running on i386
Status in python-pyeclib package in Ubuntu:
New
Status in six package in Ubuntu:
Invalid
Bug description:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386
tests is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages
[18.0 kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in
__init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyeclib/+bug/1848237/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846978] Re: wifi bug oscillating
** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- 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/1846978 Title: wifi bug oscillating Status in linux package in Ubuntu: Incomplete Bug description: the 2.4ghz band wifi network does not work properly and the other networks is oscillating is not stable, is oscillating and dropping the network all the time using this system, I've done testing on other systems like windows and works normally, an information about my machine and a hp pavilion dv4 notebook ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.13 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashDB: ubuntu Date: Sun Oct 6 17:10:07 2019 InstallationDate: Installed on 2019-10-02 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846978] Re: wifi bug oscillating
** Package changed: ubuntu-release-upgrader (Ubuntu) => network-manager (Ubuntu) -- 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/1846978 Title: wifi bug oscillating Status in network-manager package in Ubuntu: New Bug description: the 2.4ghz band wifi network does not work properly and the other networks is oscillating is not stable, is oscillating and dropping the network all the time using this system, I've done testing on other systems like windows and works normally, an information about my machine and a hp pavilion dv4 notebook ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.13 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashDB: ubuntu Date: Sun Oct 6 17:10:07 2019 InstallationDate: Installed on 2019-10-02 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1846978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848003] Re: Apt-get doesn't properly check free disk space on boot partition
** Package changed: ubuntu-release-upgrader (Ubuntu) => apt (Ubuntu)
--
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/1848003
Title:
Apt-get doesn't properly check free disk space on boot partition
Status in apt package in Ubuntu:
New
Bug description:
Probably regression of #1173468 . I have relatively small (237Mb) boot
partition everytime there is new kernel for upgrading I do uname -r,
aptget purge linux-{image,headers}-version-older-than-current-live-OS
then apt-get dist-upgrade .If I don't the upgrade is interrupted in
inconsistent state
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.34
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 14 13:50:02 2019
InstallationDate: Installed on 2015-05-08 (1620 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to bionic on 2018-08-26 (413 days ago)
VarLogDistupgradeXorgFixuplog:
INFO:root:/usr/bin/do-release-upgrade running
INFO:root:No xorg.conf, exiting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1848003/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846978] [NEW] wifi bug oscillating
You have been subscribed to a public bug: the 2.4ghz band wifi network does not work properly and the other networks is oscillating is not stable, is oscillating and dropping the network all the time using this system, I've done testing on other systems like windows and works normally, an information about my machine and a hp pavilion dv4 notebook ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.13 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashDB: ubuntu Date: Sun Oct 6 17:10:07 2019 InstallationDate: Installed on 2019-10-02 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade eoan -- wifi bug oscillating https://bugs.launchpad.net/bugs/1846978 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working
The response from Acer was that "the realtek codec is directly connected to the DSP". Is there anything else I should ask them? -- 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/1793410 Title: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04 on it. Everything works except the internal microphone. I have also tested with an external microphone and this didn't work either. I have worked my way through all the suggested solutions I could find, including trying to reconfigure the pins using hdajacketask. In pavucontrol I have options for Internal Microphone and Microphone (unplugged) but the internal mic only captures static noise. The latest HD-Audio Codec-Specific Models has configurations for alc255-acer and alc256 for some other models, but setting options snd- hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve the issue with any of these. Some info - lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point- LP HD Audio (rev 21) cat /proc/asound/cards: 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf1a8000 irq 127 dmesg | grep snd: [3.944593] snd_hda_core: loading out-of-tree module taints kernel. [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0) [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0) [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, version 0.201808050301~ubuntu18.04.1 [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.013068] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [4.013069] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 info on node 12 from cat /proc/asound/card*/codec\#*: Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x02 0x02] Pincap 0x0020: IN Pin Default 0x4000: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x0 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Let me know if you need any other information. James --- Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 06/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Erdinger_KL dmi.board.vendor: KBL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF315-52 dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837245] Re: Failed to bump fs.file-max, ignoring: Invalid argument
It looks to me like this was fixed upstream with the following: https://github.com/systemd/systemd/pull/12808 ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1837245 Title: Failed to bump fs.file-max, ignoring: Invalid argument Status in systemd package in Ubuntu: Triaged Bug description: $ journalctl -b [...] [3.786804] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 19 13:44:43 2019 InstallationDate: Installed on 2018-12-02 (228 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to eoan on 2018-12-02 (228 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848003] [NEW] Apt-get doesn't properly check free disk space on boot partition
You have been subscribed to a public bug:
Probably regression of #1173468 . I have relatively small (237Mb) boot
partition everytime there is new kernel for upgrading I do uname -r,
aptget purge linux-{image,headers}-version-older-than-current-live-OS
then apt-get dist-upgrade .If I don't the upgrade is interrupted in
inconsistent state
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.34
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 14 13:50:02 2019
InstallationDate: Installed on 2015-05-08 (1620 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to bionic on 2018-08-26 (413 days ago)
VarLogDistupgradeXorgFixuplog:
INFO:root:/usr/bin/do-release-upgrade running
INFO:root:No xorg.conf, exiting
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful2bionic bionic dist-upgrade third-party-packages
--
Apt-get doesn't properly check free disk space on boot partition
https://bugs.launchpad.net/bugs/1848003
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to apt in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)
Fix proposed to Debian: https://salsa.debian.org/science-team/fftw3/merge_requests/1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1843733 Title: fftw3 ftbfs in eoan (armhf only) Status in FFTW: New Status in fftw3 package in Ubuntu: In Progress Status in fftw3 source package in Eoan: In Progress Bug description: fftw3 ftbfs in eoan (armhf only). https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan- armhf.fftw3_3.3.8-2_BUILDING.txt.gz ( cd tests ; /usr/bin/make smallcheck ) make[1]: Entering directory '/<>/tests' perl -w ./check.pl -r -c=1 -v `pwd`/bench Executing "/<>/tests/bench --verbose=1 --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'" ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07 ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07 Segmentation fault (core dumped) FAILED /<>/tests/bench: --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304' make[1]: *** [Makefile:723: smallcheck] Error 1 make[1]: Leaving directory '/<>/tests' To manage notifications about this bug go to: https://bugs.launchpad.net/fftw3/+bug/1843733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'
The released fix does not appear to fully address the problem: https://github.com/lxc/lxd/issues/4656#issuecomment-542630903 -- 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/1779156 Title: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy' Status in linux package in Ubuntu: Triaged Status in lxc package in Ubuntu: Confirmed Status in linux source package in Cosmic: Triaged Status in lxc source package in Cosmic: Confirmed Status in linux source package in Disco: New Status in lxc source package in Disco: New Status in linux source package in Eoan: Triaged Status in lxc source package in Eoan: Confirmed Bug description: I'm not sure exactly what got me into this state, but I have several lxc containers that cannot be deleted. $ lxc info api_status: stable api_version: "1.0" auth: trusted public: false auth_methods: - tls environment: addresses: [] architectures: - x86_64 - i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificate_fingerprint: 3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb driver: lxc driver_version: 3.0.1 kernel: Linux kernel_architecture: x86_64 kernel_version: 4.15.0-23-generic server: lxd server_pid: 15123 server_version: "3.2" storage: zfs storage_version: 0.7.5-1ubuntu15 server_clustered: false server_name: milhouse $ lxc delete --force b1 Error: Failed to destroy ZFS filesystem: cannot destroy 'default/containers/b1': dataset is busy Talking in #lxc-dev, stgraber and sforeshee provided diagnosis: | short version is that something unshared a mount namespace causing | them to get a copy of the mount table at the time that dataset was | mounted, which then prevents zfs from being able to destroy it) The work around provided was | you can unstick this particular issue by doing: | grep default/containers/b1 /proc/*/mountinfo | then for any of the hits, do: | nsenter -t PID -m -- umount /var/snap/lxd/common/lxd/storage-pools/default/containers/b1 | then try the delete again ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: smoser31412 F pulseaudio /dev/snd/controlC2: smoser31412 F pulseaudio /dev/snd/controlC0: smoser31412 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jun 28 10:42:45 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (1071 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) MachineType: b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0246.2015.0309.1355 dmi.board.asset.tag: � dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-503 dmi.chassis.asset.tag: � dmi.chassis.type: 3 dmi.chassis.vendor: � dmi.chassis.version: � dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0246.2015.0309.1355:bd03/09/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr: dmi.product.family: � dmi.product.name: � dmi.product.version: � dmi.sys.vendor: � To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)
There's an additional bug that's slowing me down right now: If you run 'bench' under gdb or just compile the package using gcc-8 then 'bench' spins forever at 100% CPU never completing any tests. I will try to avoid having to fix that bug here... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1843733 Title: fftw3 ftbfs in eoan (armhf only) Status in FFTW: New Status in fftw3 package in Ubuntu: In Progress Status in fftw3 source package in Eoan: In Progress Bug description: fftw3 ftbfs in eoan (armhf only). https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan- armhf.fftw3_3.3.8-2_BUILDING.txt.gz ( cd tests ; /usr/bin/make smallcheck ) make[1]: Entering directory '/<>/tests' perl -w ./check.pl -r -c=1 -v `pwd`/bench Executing "/<>/tests/bench --verbose=1 --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'" ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07 ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07 Segmentation fault (core dumped) FAILED /<>/tests/bench: --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304' make[1]: *** [Makefile:723: smallcheck] Error 1 make[1]: Leaving directory '/<>/tests' To manage notifications about this bug go to: https://bugs.launchpad.net/fftw3/+bug/1843733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it
I did some test, with kernel 5.2.21 everything works (linux-image- unsigned-5.2.21-050221-generic_5.2.21-050221.201910111731_amd64.deb). I also tried kernel 5.3.6 and the screen is again black at boot (linux- headers-5.3.6-050306_5.3.6-050306.201910111731_all.deb) -- 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/1847980 Title: Lightdm is just a black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan Ermine (development branch). If i boot with linux-image-5.0.0-31-generic the Xorg works well. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 14 11:15:23 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.42 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.36 dmi.chassis.asset.tag: CZC64082W1 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: X3J10ET#ABZ dmi.sys.vendor: HP 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro nomodeset resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Tags: eoan ubuntu Uname: Linux 5.3.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/19/2019
[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)
** Changed in: fftw3 (Ubuntu Eoan) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1843733 Title: fftw3 ftbfs in eoan (armhf only) Status in FFTW: New Status in fftw3 package in Ubuntu: In Progress Status in fftw3 source package in Eoan: In Progress Bug description: fftw3 ftbfs in eoan (armhf only). https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan- armhf.fftw3_3.3.8-2_BUILDING.txt.gz ( cd tests ; /usr/bin/make smallcheck ) make[1]: Entering directory '/<>/tests' perl -w ./check.pl -r -c=1 -v `pwd`/bench Executing "/<>/tests/bench --verbose=1 --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'" ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07 ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07 Segmentation fault (core dumped) FAILED /<>/tests/bench: --verify 'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304' make[1]: *** [Makefile:723: smallcheck] Error 1 make[1]: Leaving directory '/<>/tests' To manage notifications about this bug go to: https://bugs.launchpad.net/fftw3/+bug/1843733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438014] Re: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts
** Package changed: gtk+3.0 (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1438014 Title: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts Status in Ubuntu: Confirmed Bug description: I put my laptop to sleep for an hour or so; when I restored it, gnome- terminal had crashed. It did not do this the previous time I suspended my laptop today, so I doubt that's immediately related. This crash can be reproduced by setting a shortcut in preferences. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 30 00:19:43 2015 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2014-02-03 (419 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f98e2afbf1f : testb $0x4,0x16(%rax) PC (0x7f98e2afbf1f) ok source "$0x4" ok destination "0x16(%rax)" (0xbcae) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel (widget=0x2580c30) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382 window_group_cleanup_grabs (group=, window=window@entry=0x252a230) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110 gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169 gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134 Title: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1438014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847666] Re: Ubuntu doesn't cannot be suspended via the suspend icon after you log out.
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1847666 Title: Ubuntu doesn't cannot be suspended via the suspend icon after you log out. Status in systemd package in Ubuntu: New Bug description: Pressing the suspend button in the top right menu when you are logged out doesn't work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-13-generic 5.3.0-13.14 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1766 F pulseaudio lyubomir 18081 F pulseaudio Date: Thu Oct 10 23:15:08 2019 HibernationDevice: RESUME=UUID=6f86efb8-0e86-4159-9412-28658da56f90 InstallationDate: Installed on 2019-07-23 (78 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID :0538 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-27 (12 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1826473] Re: package ubuntu-core-launcher 2.38 failed to install/upgrade: problemas de dependencias - se deja sin configurar
The real issue is: """ Configurando udev (229-4ubuntu21.21) ... addgroup: El grupo `input' ya existe como grupo del sistema. Saliendo. update-initramfs: deferring update (trigger activated) insserv: warning: script 'K07smfpd' missing LSB tags and overrides insserv: warning: script 'smfpd' missing LSB tags and overrides insserv: There is a loop at service plymouth if started insserv: There is a loop between service plymouth and procps if started insserv: loop involving service procps at depth 2 insserv: loop involving service udev at depth 1 insserv: There is a loop at service smfpd if started insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting smfpd depends on plymouth and therefore on system facility
[Touch-packages] [Bug 1826473] [NEW] package ubuntu-core-launcher 2.38 failed to install/upgrade: problemas de dependencias - se deja sin configurar
You have been subscribed to a public bug: a ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-core-launcher 2.38 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Apr 26 00:36:42 2019 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2017-09-26 (576 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: snapd Title: package ubuntu-core-launcher 2.38 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd Importance: Undecided Status: Invalid ** Affects: insserv (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- package ubuntu-core-launcher 2.38 failed to install/upgrade: problemas de dependencias - se deja sin configurar https://bugs.launchpad.net/bugs/1826473 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to insserv in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
