[Touch-packages] [Bug 1811937] [NEW] Networkmanager shows network profiles on wrong network
Public bug reported: I have two network ports (ens 34 and ens 37) I'm able to create per port its own named profile where it is defined if this used profile should use DHCP, use manual DNS and others. But if I connect my android Smartphone with USB tethering all named Profiles are showing below the new network Port (USB Ethernet) and not any more below their defined port. (visual error only) That should only happened if a profile is not active but in this case I would prefer a separate profile menu where I could choose one and add to a specific port. Sometimes the network manager entry in the menu also shows confusing or empty entries. See print screen attached ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2019-01-16 08_07_59-Ubuntu.png" https://bugs.launchpad.net/bugs/1811937/+attachment/5229526/+files/2019-01-16%2008_07_59-Ubuntu.png -- 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/1811937 Title: Networkmanager shows network profiles on wrong network Status in network-manager package in Ubuntu: New Bug description: I have two network ports (ens 34 and ens 37) I'm able to create per port its own named profile where it is defined if this used profile should use DHCP, use manual DNS and others. But if I connect my android Smartphone with USB tethering all named Profiles are showing below the new network Port (USB Ethernet) and not any more below their defined port. (visual error only) That should only happened if a profile is not active but in this case I would prefer a separate profile menu where I could choose one and add to a specific port. Sometimes the network manager entry in the menu also shows confusing or empty entries. See print screen attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1811937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811902] Re: Echo cancelation should be enabled by default
I disagree that any modules which modify sound should be used by default. I think the defaults should keep audio in its original raw form as much as possible. However, if you can convince upstream to enable module-echo-cancel by default then Ubuntu would get it by default. Please send your request to: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues and tell us the new bug ID. ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Wishlist ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1811902 Title: Echo cancelation should be enabled by default Status in pulseaudio package in Ubuntu: Incomplete Bug description: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811863] Re: Screen flickering on ultra wide
According to your XorgLog.txt it looks like the choice of 75Hz is coming from the AMDGPU driver: [97.816] (II) AMDGPU(0): Modeline "3840x1600"x75.0 566.25 3840 4016 4104 4400 1600 1607 1617 1716 +hsync -vsync (128.7 kHz eP) However the AMDGPU driver is also confused by the monitor's aspect ratio, which might be the problem: [97.816] (WW) AMDGPU(0): Output HDMI-A-0: Strange aspect ratio (879/366), consider adding a quirk [97.816] (WW) AMDGPU(0): Output HDMI-A-0: Strange aspect ratio (879/366), consider adding a quirk [97.816] (WW) AMDGPU(0): Output HDMI-A-0: Strange aspect ratio (879/366), consider adding a quirk Does the same monitor work when plugged into an Intel or Nvidia GPU? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - Screen flickering on ultra wide + [amdgpu + nvidia PCI passthrough] Screen flickering on ultra wide ** Tags added: amdgpu nvidia radeon ** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1811863 Title: [amdgpu + nvidia PCI passthrough] Screen flickering on ultra wide Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I'm running 18.04 including all updates on an LG 38WK95C at 3840x1600@75. I'm experiencing constant flickering on screen when setting the refresh rate to 75Hz in settings. When I set to refresh rate to 60Hz, the flicking is gone. When enabeling freesync in the monitor's settings, the 60Hz isn't available and the only choices are 29.99Hz or 75Hz, which again causes flickering. This looks like the same issue in bug #1749975. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 16:43:10 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed nvidia, 415.25, 4.15.0-29-generic, x86_64: installed nvidia, 415.25, 4.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3734] Advanced Micro Devices, Inc. [AMD/ATI] Polaris12 [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Lexa PRO [Radeon RX 550] [1462:8a90] InstallationDate: Installed on 2019-01-02 (12 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9ac85046-be6e-411d-a51c-10b221c750d0 ro splash quiet iommu=1 amd_iommu=on vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd12/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4: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.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1811863/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-shell (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in gnome-control-center source package in Bionic: New Status in gnome-shell source package in Bionic: New Status in linux source package in Bionic: New Status in upower source package in Bionic: New Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811902] [NEW] Echo cancelation should be enabled by default
Public bug reported: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1811902 Title: Echo cancelation should be enabled by default Status in pulseaudio package in Ubuntu: New Bug description: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 293832] Re: printer prints page at wrong position, page cut
You should be able to change the default settings with lpoptions command : https://www.cups.org/doc/man-lpoptions.html?TOPIC=Man+Pages Take care of the default page format first, and check also the page dimension, it could be wrong for this format. Le mer. 9 janv. 2019 à 20:50, unfa a écrit : > Oh wait - I spoke too soon. > > It fixes the problem in Manjaro 18.0.2, but not in Linux Mint 18.3. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/293832 > > Title: > printer prints page at wrong position, page cut > > To manage notifications about this bug go to: > https://bugs.launchpad.net/poppler/+bug/293832/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/293832 Title: printer prints page at wrong position, page cut Status in Poppler: Unknown Status in brother-cups-wrapper-extra package in Ubuntu: Invalid Status in brother-lpr-drivers-extra package in Ubuntu: Invalid Status in cups package in Ubuntu: Invalid Status in poppler package in Ubuntu: Fix Released Status in brother-cups-wrapper-extra source package in Karmic: Invalid Status in brother-lpr-drivers-extra source package in Karmic: Invalid Status in cups source package in Karmic: Invalid Status in poppler source package in Karmic: Won't Fix Bug description: After updating to intrepid, my Brother DCP-7025 printed every page about 2 cm above the usual position. This leads to pages cut as if printing with wrong paper configuration though A4 paper is set everywhere (Cups settings, program settings). For example when printing a test page with the printer configuration tool I cannot see the upper part of the Ubuntu logo. I have used both a hardy and an intrepid live cd to test and found out that the problem only occurs using intrepid, so I think it's a problem with the intrepid driver packages. However I found out, that in the printer configuration tool a wrong driver "DCP-7025 BR-Script" is loaded. The correct (and working!) driver is "DCP-7025 for CUPS". So to manually solve the problem simply choose the correct driver in the tool. I think that during the installation process of the package "brother- cups-wrapper-laser" the correct driver is not set to be used as default driver and the system continues to use the wrong driver instead. To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/293832/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 467607] Re: Hostname changes breaks application loading
The bug is old and Ubuntu changed quite a lot since, there has also been no activity here nor similar reports. Closing since we believe the issue as described is deprecated but feel free to file a new report if you still have problems in recent Ubuntu versions. ** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/467607 Title: Hostname changes breaks application loading Status in nautilus package in Ubuntu: Invalid Status in sudo package in Ubuntu: Confirmed Bug description: Binary package hint: hostname On 9.10 changing the hostname via the terminal breaks the loading of applications until a reboot. You can see this below: joseph@joseph-work:~$ nautilus (nautilus:2068): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed [nautilus gives errors, but loads] joseph@joseph-work:~$ sudo hostname example sudo: unable to resolve host joseph-work [change hostname to example, complains about my previous hostname] joseph@joseph-work:~$ nautilus No protocol specified Could not parse arguments: Cannot open display: joseph@joseph-work:~$ [Nautilus fails to open] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/467607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)
Upgrading to Linux pan 4.19.13-sunxi #5.70 SMP Sat Jan 12 15:43:21 CET 2019 armv7l armv7l armv7l GNU/Linux solved the issue for me. -- 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/1804847 Title: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz) Status in systemd package in Ubuntu: Fix Released Bug description: The following description is taken from: https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237 Hello everyone, I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After a recent reboot I found most of my services to be in a failed state. The reason for that, I guess, are these log entries: Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/elasticsearch failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/systemd/netif failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/systemd/netif/links failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/systemd/netif/leases failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/log/journal failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: Invalid argument To verify I tried this: /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create elasticsearch.conf Reading config file "elasticsearch.conf". Running create action for entry d /var/run/elasticsearch Found existing directory "/var/run/elasticsearch". "/run/elasticsearch" has right mode 40755 chown "/run/elasticsearch" to 120.128 fchownat() of /run/elasticsearch failed: Invalid argument I can manually chown the directories, e.g. "chown elasticsearch:elasticsearch /var/run/elasticsearch" and restart the service successfully. My suspicion is, this is related to an upgrade of systemd to 229-4ubuntu21.8. At this point I don't know what to do. I'm also confused about the version I have installed, which I thought is systemd-229. Howver, I looked at https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found that fchownat() is only used from version 238+: Tag v237 (and earlier, including 229): /.../ if (chown(fn, i->uid_set ? i->uid : UID_INVALID, i->gid_set ? i->gid : GID_INVALID) < 0) return log_error_errno(errno, "chown(%s) failed: %m", path); } /.../ Tag v238 /.../ if (fchownat(fd, "", i->uid_set ? i->uid : UID_INVALID, i->gid_set ? i->gid : GID_INVALID, AT_EMPTY_PATH) < 0) return log_error_errno(errno, "fchownat() of %s failed: %m", path); /.../ Any help fixing this problem would be highly appreciated. Many thanks, Rafael === Notes === fchownat() was added to Linux in kernel 2.6.16; library support was added to glibc in version 2.4. checkinf if it is blocked/filtered/sandboxed, rarther than unavailable. glibc in bionic requires minimum linux 3.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Upgrade to Linux pan 4.19.13-sunxi #5.70 SMP Sat Jan 12 15:43:21 CET 2019 armv7l armv7l armv7l GNU/Linux solved the issue for me. -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1078226] Re: raring daily: background & lightdm look as if they are in 8bit greyscale mode
The bug is old and Ubuntu changed quite a lot since, there has also been no activity here nor similar reports. Closing since we believe the issue as described is deprecated but feel free to file a new report if you still have problems in recent Ubuntu versions. ** Changed in: ubiquity (Ubuntu) Status: Confirmed => Invalid ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- 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/1078226 Title: raring daily: background & lightdm look as if they are in 8bit greyscale mode Status in nautilus package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Bug description: I am using virt-manager / KVM. The wallpaper is grey square boxes, instead of orange mish- mash. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: compiz 1:0.9.8.4+bzr3412-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.2-0ubuntu3 Architecture: amd64 CasperVersion: 1.328 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDmesg: [ 19.517347] snd_hda_intel :00:04.0: >setting latency timer to 64 [ 20.637021] init: udev-fallback-graphics main process (2141) terminated with status 1 [ 28.600013] hda-intel: Invalid position buffer, using LPIB read method instead. Date: Tue Nov 13 09:51:16 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121113) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 xserver.bootTime: Tue Nov 13 09:44:11 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1078226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1740441] Re: Tag borders in nautilus search bar are truncated
** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1740441 Title: Tag borders in nautilus search bar are truncated Status in Ubuntu theme: New Status in nautilus package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: New Bug description: ubuntu 17.10 Nautilus search bar SS: https://i.hizliresim.com/rJWBP7.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1740441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811149] Re: 23 wireguard peers hang systemd-networkd
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811149 Title: 23 wireguard peers hang systemd-networkd Status in systemd: Fix Released Status in systemd package in Ubuntu: New Bug description: I'm running Ubuntu 18.04.1 LTS with systemd=237-3ubuntu10.9. Linux kernel version is 4.15.0-32-generic #35-Ubuntu SMP. wireguard=0.0.20181218-wg1~bionic from PPA. I have a Wireguard-based VPN server that has several peers. As soon as number of peers is 22 or lower, everything works okay. As soon as I add the 23rd peer, restart of `systemd-networkd` service fails with timeout while systemd-networkd hogs CPU. Moreover, if I reboot the box while wireguard configuration is "broken", systemd-networkd fails to apply network settings on boot and the box is no longer accessible over the network. Configuration is structured in a following way (keys are fake): ==> wg0.netdev [NetDev] Name=wg0 Kind=wireguard Description=Wireguard VPN server [WireGuard] ListenPort=4500 PrivateKey=kNl7tkhCM1Crj8RhUIn8xvwcg+UoOkw26kQjQEtZk1k= [WireGuardPeer] PublicKey=AfM1AN4IIUe5AVypFg2pcNrQmqOtZQIJLgusbkDYXkI= AllowedIPs=fd6f:b446:a2ca:0400:cb6f:b446:a2ca:bd0b/128 AllowedIPs=fd6f:b446:a2ca:cb6f:b446:a2ca::/96 # and 22 more [WireGuardPeer] like that ==> wg0.network Name=wg0 [Network] Address=fd6f:b446:a2ca:0400::1/64 [Route] Destination=fd6f:b446:a2ca:cb6f:b446:a2ca::/96 # and 22 more [Route] sections like that syslog logs are attached both for "good" and "bad" cases, sample of strace logs is also attached for "bad" case. I'm filling the issue here as the aforementioned systemd version is already out of scope of upstream bug tracker per https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md #filing-issues To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1811149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
@Dimitri John Ledkov (xnox) I manully upgrade to Linux pan 4.19.13-sunxi #5.70 SMP Sat Jan 12 15:43:21 CET 2019 armv7l armv7l armv7l GNU/Linux and the issue seems also to be fixed for me now -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
Hello Dean, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Committed Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64
[Touch-packages] [Bug 1811120] Re: Backport auth.conf.d
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1811120 Title: Backport auth.conf.d Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Triaged Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] Backport auth.conf.d support to allow specifying per-repository authentication data in separate files, so packages can setup authenticated repositories. [Regression potential] We ignore errors from opening auth.conf.d files, so regressions can only occur when parsing a file fails, in which case apt would exit with an error. [Test case] The test suite provides autopkgtests for auth.conf.d which creates an auth.conf.d file and checks that it is successfully used; so we can check if those passed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811893] [NEW] In Ubuntu on Virtualbox, the screen is blank after sign-in
Public bug reported: I installed xubuntu in my Windows box using the latest VBOX (6.0). It installed perfectly however after I log in the screen kind of freezes. I see the background however the icons and title bar do not appear. Also mouse inputs like right click do not work. Function keys do not work either like alt F2. Xubuntu system is updated and the guest addons are installed. I have tried disbling the 3d acceleration however that did not work. The only way I can get this to load the icons is to go to Devices -> Insert Guest Additions CD Image. Once I click on Insert Guest Additions the icons and title bar load and everything works fine. I checked online for solutions but have not found any that work. This also seems to be a problem with other versions of Ubuntu and other Linux distributions. xubuntu 10.04.1 Description:Ubuntu 18.04.1 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jan 15 15:20:31 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1811893 Title: In Ubuntu on Virtualbox, the screen is blank after sign-in Status in shadow package in Ubuntu: New Bug description: I installed xubuntu in my Windows box using the latest VBOX (6.0). It installed perfectly however after I log in the screen kind of freezes. I see the background however the icons and title bar do not appear. Also mouse inputs like right click do not work. Function keys do not work either like alt F2. Xubuntu system is updated and the guest addons are installed. I have tried disbling the 3d acceleration however that did not work. The only way I can get this to load the icons is to go to Devices -> Insert Guest Additions CD Image. Once I click on Insert Guest Additions the icons and title bar load and everything works fine. I checked online for solutions but have not found any that work. This also seems to be a problem with other versions of Ubuntu and other Linux distributions. xubuntu 10.04.1 Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jan 15 15:20:31 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1811893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
Hello Dean, or anyone else affected, Accepted apt into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.7.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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Cosmic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Committed Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64
[Touch-packages] [Bug 1811120] Re: Backport auth.conf.d
Hello Julian, or anyone else affected, Accepted apt into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.7.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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Cosmic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1811120 Title: Backport auth.conf.d Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Triaged Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] Backport auth.conf.d support to allow specifying per-repository authentication data in separate files, so packages can setup authenticated repositories. [Regression potential] We ignore errors from opening auth.conf.d files, so regressions can only occur when parsing a file fails, in which case apt would exit with an error. [Test case] The test suite provides autopkgtests for auth.conf.d which creates an auth.conf.d file and checks that it is successfully used; so we can check if those passed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
@Dimitri John Ledkov (xnox) I think I'm forced by Armbian to this kernel revision by default. TBH I don't know if a manual upgrade will break the OS or not. I also have not investigated on how to upgrade it manually. I have no permission issues like David (dasoto) I already checked that before I replied to this bug report. Everything on the root directory of my machine is root / root. -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
@Dimitri John Ledkov (xnox) It's Armbian (Xenial) for OrangePI One. Here df -Th of my filesystem: udev devtmpfs 165M 0 165M0% /dev tmpfs tmpfs 50M3,9M 46M8% /run /dev/mmcblk0p1 ext4 7,2G4,1G 3,1G 57% / tmpfs tmpfs 248M 0 248M0% /dev/shm tmpfs tmpfs 5,0M4,0K 5,0M1% /run/lock tmpfs tmpfs 248M 0 248M0% /sys/fs/cgroup tmpfs tmpfs 248M 12K 248M1% /tmp /dev/zram0 ext4 49M 20M 27M 42% /var/log tmpfs tmpfs 50M 0 50M0% /run/user/999 tmpfs tmpfs 50M 0 50M0% /run/user/1000 -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Hello guys, I followed your discussion to try to solve my problem. Now sound works in my PC, but I've got some other problems that came with. My PC is an Asus UX333FN, and I'm currently running on Ubuntu 18.04 with kernel 4.20. It came with 4.15.0.29.31 originally. When following the steps to install new kernels, above 4.18, I always get these messages : W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau (This time I was trying to install 4.18 for example) As I said, sound works, but my problem now is apparently the NVIDIA Card (it has a Geforce MX150). Sometimes my screen and my mouse freeze, and I also get something like in the attached picture. I also need to press two times the Fn keys for it to start working, which didn't happen with the other kernel. Has someone faced the same problem? Thank you a lot ** Attachment added: "Screenshot from 2019-01-15 19-55-23.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+attachment/5229398/+files/Screenshot%20from%202019-01-15%2019-55-23.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
This solve the issue. sudo chown root:root / I think this will affect a lot of NVIDIA Jetson TX2 users, due the Jetpack version that they include with ubuntu have the / folder with owner ubuntu: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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
** Changed in: sqlalchemy-migrate Status: New => In Progress ** Changed in: sqlalchemy-migrate Assignee: (unassigned) => Corey Bryant (corey.bryant) ** Changed in: sqlalchemy-migrate Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in sqlalchemy-migrate: In Progress Status in cinder package in Ubuntu: Fix Released Status in migrate package in Ubuntu: Fix Released Status in nova package in Ubuntu: Fix Released Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
@ David (dasoto) nvidia@tegra-ubuntu:/$ ls -la total 108 drwxrwxr-x 23 ubuntu ubuntu 4096 Oct 30 17:36 . drwxrwxr-x 23 ubuntu ubuntu 4096 Oct 30 17:36 .. drwxrwxr-x 22 ubuntu ubuntu 4096 Oct 29 20:31 lib drwxr-xr-x 5 nvidia nvidia 4096 Oct 29 20:36 media -rw-r--r-- 1 ubuntu ubuntu 62 May 17 2018 README.txt The above look very bad too me. Imho /README.txt shouldn't be there at all. Not sure why /media is owned by nvidia:nvidia, usually /media is owned by root. Ditto / and /lib should be owned by root. It is a security vulnerability for unpriviledged user to own these top level directories. Can you please try this: $ sudo chown root:root / /lib /media And check if systemd-tmpfiles works after that? -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
@Dimitri John Ledkov (xnox) nvidia@tegra-ubuntu:~$ mount /dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered) devtmpfs on /dev type devtmpfs (rw,relatime,size=7976720k,nr_inodes=1994180,mode=755) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/debug type cgroup (rw,nosuid,nodev,noexec,relatime,debug) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) configfs on /sys/kernel/config type configfs (rw,relatime) /dev/sda1 on /media type ext4 (rw,relatime,data=ordered) tmpfs on /run/user/1001 type tmpfs (rw,nosuid,nodev,relatime,size=804352k,mode=700,uid=1001,gid=1001) /dev/sda1 on /media/docker/overlay2 type ext4 (rw,relatime,data=ordered) nvidia@tegra-ubuntu:/$ ls -la total 108 drwxrwxr-x 23 ubuntu ubuntu 4096 Oct 30 17:36 . drwxrwxr-x 23 ubuntu ubuntu 4096 Oct 30 17:36 .. drwxr-xr-x 2 root root4096 Jan 12 00:17 bin drwxr-xr-x 5 root root4096 Oct 13 00:40 boot drwxr-xr-x 4 root root4096 Jan 3 23:00 data drwxr-xr-x 14 root root5480 Jan 15 01:14 dev drwxr-xr-x 141 root root 12288 Jan 15 17:41 etc drwxr-xr-x 4 root root4096 Jan 6 2017 home drwxrwxr-x 22 ubuntu ubuntu 4096 Oct 29 20:31 lib drwx-- 2 root root 16384 Oct 12 20:30 lost+found drwxr-xr-x 5 nvidia nvidia 4096 Oct 29 20:36 media drwxr-xr-x 2 root root4096 Apr 20 2016 mnt drwxr-xr-x 3 root root4096 Oct 12 20:28 opt dr-xr-xr-x 313 root root 0 Jan 1 1970 proc -rw-r--r-- 1 ubuntu ubuntu62 May 17 2018 README.txt drwx-- 4 root root4096 Jan 2 23:47 root drwxr-xr-x 23 root root 820 Jan 15 17:41 run drwxr-xr-x 2 root root 12288 Jan 12 00:17 sbin drwxr-xr-x 2 root root4096 Apr 19 2016 snap drwxr-xr-x 2 root root4096 Apr 20 2016 srv dr-xr-xr-x 12 root root 0 Jan 1 2000 sys drwxrwxrwt 7 root root4096 Jan 15 17:41 tmp drwxr-xr-x 12 root root4096 Oct 12 21:45 usr drwxr-xr-x 19 root root4096 Oct 12 20:51 var -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the
Re: [Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
On 01/15/2019 09:26 AM, Thadeu Lima de Souza Cascardo wrote: > Upstream is a little reluctant to accept my changes, and seems to > suggest that we find out the layout of the paths some other way (which > is possible, but would be such a special case on initramfs-tools, only > for nvme). > > Cascardo. > Hmm, I am really sorry about that - sux to do all that work and get that kind of response. So making the suggested changes seems like real work to me. Do you have a rough estimate? Terry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in makedumpfile source package in Cosmic: Invalid Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063
[Touch-packages] [Bug 1811531] Re: remote execution vulnerability
** Changed in: zeromq3 (Ubuntu) Assignee: (unassigned) => Eduardo dos Santos Barretto (ebarretto) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Unknown Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
@ Andreas Kar (thexmanxyz) 3.4.113-sun8i is an extremely ancient kernel. Why are you using such a kernel and where does it come from? Which filesystems are you using? is it btfs or something else? @ David (dasoto) Your system appears to have an up to date kernel... but also and odd one where does 4.4.38-tegra kernel comes from? Can you use stock ubuntu kernel? You are hitting this code path: fd = chase_symlinks(dn, NULL, CHASE_OPEN|CHASE_SAFE, NULL); if (fd == -EPERM) return log_error_errno(fd, "Unsafe symlinks encountered in %s, refusing.", path); Can you please show us your mountpoints? is / a symlink to somewhere? what about /tmp and /run? are they symlinks too? What filesystems are you using? What filesystems are you using? is it btfs? or something else? ** Information type changed from Public to Public Security ** Tags added: regression-security regression-update -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
Upstream is a little reluctant to accept my changes, and seems to suggest that we find out the layout of the paths some other way (which is possible, but would be such a special case on initramfs-tools, only for nvme). Cascardo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in makedumpfile source package in Cosmic: Invalid Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
I have exactly the same problem. I check and an auto update was made for systemd from 229-4ubuntu21.10 to 229-4ubuntu21.15 on many of my devices (Jetson TX2). Now devices rebooted doesn't start ssh and I lost complete communication with all those devices. I were able to log in through serial console and confirm that this is the issue. nvidia@tegra-ubuntu:~$ uname -a Linux tegra-ubuntu 4.4.38-tegra #1 SMP PREEMPT Mon Oct 15 15:16:41 MDT 2018 aarch64 aarch64 aarch64 GNU/Linux Start-Date: 2019-01-12 00:17:20 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:arm64 (229-4ubuntu21.10, 229-4ubuntu21.15), udev:arm64 (229-4ubuntu21.10, 229-4ubuntu21.15), libudev1:arm64 (229-4ubuntu21.10, 229-4ubuntu21.15), systemd-sysv:arm64 (229-4ubuntu21.10, 229-4ubuntu21.15), libpam-systemd:arm64 (229-4ubuntu21.10, 229-4ubuntu21.15), systemd:arm64 (229-4ubuntu21.10, 229-4ubuntu21.15) End-Date: 2019-01-12 00:17:35 nvidia@tegra-ubuntu:~$ sudo systemd-tmpfiles --create |more [sudo] password for nvidia: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Unsafe symlinks encountered in /var/log, refusing. Unsafe symlinks encountered in /var/lib, refusing. Unsafe symlinks encountered in /run/sendsigs.omit.d, refusing. Unsafe symlinks encountered in /run/lock/subsys, refusing. Unsafe symlinks encountered in /var/cache, refusing. Unsafe symlinks encountered in /var/cache/man, refusing. Unsafe symlinks encountered in /run/rpcbind, refusing. Unsafe symlinks encountered in /run/rpcbind/rpcbind.xdr, refusing. Unsafe symlinks encountered in /run/rpcbind/portmap.xdr, refusing. Unsafe symlinks encountered in /var/run/sshd, refusing. Unsafe symlinks encountered in /var/run/sudo, refusing. Unsafe symlinks encountered in /var/run/sudo/ts, refusing. Unsafe symlinks encountered in /run/user, refusing. Unsafe symlinks encountered in /run/systemd/ask-password, refusing. Unsafe symlinks encountered in /run/systemd/seats, refusing. Unsafe symlinks encountered in /run/systemd/sessions, refusing. Unsafe symlinks encountered in /run/systemd/users, refusing. Unsafe symlinks encountered in /run/systemd/machines, refusing. Unsafe symlinks encountered in /run/systemd/shutdown, refusing. Unsafe symlinks encountered in /run/systemd/netif, refusing. Unsafe symlinks encountered in /run/systemd/netif/links, refusing. Unsafe symlinks encountered in /run/systemd/netif/leases, refusing. Unsafe symlinks encountered in /run/log, refusing. Unsafe symlinks encountered in /var/lib/systemd, refusing. Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Unsafe symlinks encountered in /var/log/wtmp, refusing. Unsafe symlinks encountered in /var/log/btmp, refusing. Unsafe symlinks encountered in /var/spool, refusing. Unsafe symlinks encountered in /tmp/.X11-unix, refusing. Unsafe symlinks encountered in /tmp/.ICE-unix, refusing. Unsafe symlinks encountered in /tmp/.XIM-unix, refusing. Unsafe symlinks encountered in /tmp/.font-unix, refusing. Unsafe symlinks encountered in /tmp/.Test-unix, refusing. Unsafe symlinks encountered in /run/log/journal, refusing. Unsafe symlinks encountered in /run/log/journal/ae15719763c84b35196c20a95728b806, refusing. -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that
[Touch-packages] [Bug 1511840] Re: cannot apport-bug from IPv6-only network
Noted, I'll see what I can do - login.launchpad.net currently lives in an IPv4-only cloud. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1511840 Title: cannot apport-bug from IPv6-only network Status in apport package in Ubuntu: Fix Released Bug description: Attempting to report a bug using apport-bug from a machine without a legacy IP address fails: # apport-bug foopackage ... *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. *** Error: Network problem Cannot connect to crash database, please check your Internet connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1511840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811861] Re: incorrect permissions on /var/log after debootstrap
Actually, it looks like this is already fixed in cosmic. Can this be ported to bionic as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1811861 Title: incorrect permissions on /var/log after debootstrap Status in rsyslog package in Ubuntu: New Bug description: we are debootstrapping a full bionic distribution into a directory. After debootstrapping the permissions on /var/log are incorrect, causing rsyslog to fail because it cannot write into the directory to create the various files. Also, in the postinst of the rsyslog package I see that systemd-tmpfiles is attempted to be used to create the files defined in /usr/lib/tmpfiles.d/00rsyslog.conf, but from what I can tell this will never work because of the systemd-tmpfiles manpage: --create If this option is passed, all files and directories marked with f, F, w, d, D, v, p, L, c, b, m in the configuration files are created or written to. Files and directories marked with z, Z, t, T, a, and A have their ownership, access mode and security labels set. Since the files are configured with type "z" only ownership, access mode and security will be updated. # lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 # apt-cache policy rsyslog rsyslog: Installed: 8.32.0-1ubuntu4 Candidate: 8.32.0-1ubuntu4 Version table: *** 8.32.0-1ubuntu4 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1811861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811863] [NEW] Screen flickering on ultra wide
Public bug reported: I'm running 18.04 including all updates on an LG 38WK95C at 3840x1600@75. I'm experiencing constant flickering on screen when setting the refresh rate to 75Hz in settings. When I set to refresh rate to 60Hz, the flicking is gone. When enabeling freesync in the monitor's settings, the 60Hz isn't available and the only choices are 29.99Hz or 75Hz, which again causes flickering. This looks like the same issue in bug #1749975. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 16:43:10 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed nvidia, 415.25, 4.15.0-29-generic, x86_64: installed nvidia, 415.25, 4.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3734] Advanced Micro Devices, Inc. [AMD/ATI] Polaris12 [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Lexa PRO [Radeon RX 550] [1462:8a90] InstallationDate: Installed on 2019-01-02 (12 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9ac85046-be6e-411d-a51c-10b221c750d0 ro splash quiet iommu=1 amd_iommu=on vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd12/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4: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.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption possible-manual-nvidia-install third-party-packages 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/1811863 Title: Screen flickering on ultra wide Status in xorg package in Ubuntu: New Bug description: I'm running 18.04 including all updates on an LG 38WK95C at 3840x1600@75. I'm experiencing constant flickering on screen when setting the refresh rate to 75Hz in settings. When I set to refresh rate to 60Hz, the flicking is gone. When enabeling freesync in the monitor's settings, the 60Hz isn't available and the only choices are 29.99Hz or 75Hz, which again causes flickering. This looks like the same issue in bug #1749975. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 16:43:10 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed nvidia, 415.25, 4.15.0-29-generic, x86_64: installed nvidia, 415.25, 4.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3734] Advanced Micro Devices, Inc. [AMD/ATI] Polaris12 [1002:699f] (rev c7) (prog-if 00
[Touch-packages] [Bug 1811861] [NEW] incorrect permissions on /var/log after debootstrap
Public bug reported: we are debootstrapping a full bionic distribution into a directory. After debootstrapping the permissions on /var/log are incorrect, causing rsyslog to fail because it cannot write into the directory to create the various files. Also, in the postinst of the rsyslog package I see that systemd-tmpfiles is attempted to be used to create the files defined in /usr/lib/tmpfiles.d/00rsyslog.conf, but from what I can tell this will never work because of the systemd-tmpfiles manpage: --create If this option is passed, all files and directories marked with f, F, w, d, D, v, p, L, c, b, m in the configuration files are created or written to. Files and directories marked with z, Z, t, T, a, and A have their ownership, access mode and security labels set. Since the files are configured with type "z" only ownership, access mode and security will be updated. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy rsyslog rsyslog: Installed: 8.32.0-1ubuntu4 Candidate: 8.32.0-1ubuntu4 Version table: *** 8.32.0-1ubuntu4 100 100 /var/lib/dpkg/status ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1811861 Title: incorrect permissions on /var/log after debootstrap Status in rsyslog package in Ubuntu: New Bug description: we are debootstrapping a full bionic distribution into a directory. After debootstrapping the permissions on /var/log are incorrect, causing rsyslog to fail because it cannot write into the directory to create the various files. Also, in the postinst of the rsyslog package I see that systemd-tmpfiles is attempted to be used to create the files defined in /usr/lib/tmpfiles.d/00rsyslog.conf, but from what I can tell this will never work because of the systemd-tmpfiles manpage: --create If this option is passed, all files and directories marked with f, F, w, d, D, v, p, L, c, b, m in the configuration files are created or written to. Files and directories marked with z, Z, t, T, a, and A have their ownership, access mode and security labels set. Since the files are configured with type "z" only ownership, access mode and security will be updated. # lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 # apt-cache policy rsyslog rsyslog: Installed: 8.32.0-1ubuntu4 Candidate: 8.32.0-1ubuntu4 Version table: *** 8.32.0-1ubuntu4 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1811861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser
Uploaded to the cosmic queue now that 3.24.3 was released. ** Changed in: gtk+3.0 (Ubuntu Cosmic) Status: Triaged => In Progress -- 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/1807721 Title: Fix variant selection in emoji chooser Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: In Progress Status in gtk+3.0 source package in Cosmic: In Progress Bug description: Impact == The variant selector in the emoji chooser was broken and will crash the app if used. Test Case = In an app like gedit, right click in the text area and select Insert Emoji Look for one of the "people" emoji. Right-click (or long-click) on the emoji and select one of the skin tones instead of the default yellow. The emoji with the skin tone you selected should be added to the text area. Regression Potential This fix was included in the gtk 3.24.2 release. There is a standing microrelease exception for GNOME point releases. GTK 3.24 was a big enough release (with some bumped dependencies) that it's not very practical to push to Ubuntu 18.04 LTS so we selectively cherry-pick fixes there. https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b https://gitlab.gnome.org/GNOME/gtk/issues/1398 Other Info == This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: #1808233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511840] Re: cannot apport-bug from IPv6-only network
I no longer receive the "Network is unreachable" message from the command-line tool, so that part is fixed. I was unable to test the complete workflow of reporting a bug because login.launchpad.net does not have records therefore the browser window that was opened died in its tracks. I realize that's yet another infrastructure bug. Thanks for moving this forward. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1511840 Title: cannot apport-bug from IPv6-only network Status in apport package in Ubuntu: Fix Released Bug description: Attempting to report a bug using apport-bug from a machine without a legacy IP address fails: # apport-bug foopackage ... *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. *** Error: Network problem Cannot connect to crash database, please check your Internet connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1511840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications
** Also affects: gtk+3.0 (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu Cosmic) Status: New => In Progress ** Changed in: gtk+3.0 (Ubuntu Cosmic) Importance: Undecided => Low -- 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/1798861 Title: Tooltips flicker constantly in GTK3 applications Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Cosmic: In Progress Status in gtk+3.0 package in Debian: Fix Released Bug description: Tooltips are flicker constantly (i.e. repeatedly shown and the hidden again) in GTK3 applications under XFCE. It is a regression in the recent GTK 3.24. This is the upstream report and fix: https://gitlab.gnome.org/GNOME/gtk/issues/1371 https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2 A workaround for XFCE is as follows: Open Settings Editor. Set xsettings -> Gtk -> CursorThemeSize to 16. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.24.1-1ubuntu2 Uname: Linux 4.19.0-041900rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 12:23:53 2018 InstallationDate: Installed on 2017-02-01 (624 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811801] Re: i am not able to ssh to other servers manytimes
the log has those errors ' unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted' it looks a disk problem rather than a bug in the theme ** Changed in: ubuntu-themes (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1811801 Title: i am not able to ssh to other servers manytimes Status in ubuntu-themes package in Ubuntu: Invalid Bug description: There is always a message popped up on reboot that system encounter an internal error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-mono 14.04+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jan 15 10:03:19 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: package:ubuntu-mono:14.04+16.04.20160415-0ubuntu1 Unpacking ubuntu-mono (14.04+16.04.20180326-0ubuntu1) over (14.04+16.04.20160415-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/ubuntu-mono_14.04+16.04.20180326-0ubuntu1_all.deb (--unpack): unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-05 (40 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: ubuntu-themes Title: package ubuntu-mono 14.04+16.04.20160415-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1811801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white
** Changed in: gtk+3.0 (Ubuntu Cosmic) Status: Triaged => In Progress -- 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/1807719 Title: Some emoji in emoji chooser are black & white Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: In Progress Status in gtk+3.0 source package in Cosmic: In Progress Bug description: Impact == Some emoji in the emoji chooser show as black & white. This is because these emoji default to "text presentation" instead of "emoji presentation". More information and a screenshot can be found in the pango issue linked below. Test Case = In an app like gedit, right click in the text area and select Insert Emoji Browse through the emoji list. All should be in full color. Regression Potential This fix was included in the gtk 3.24.2 release. There is a standing microrelease exception for GNOME point releases. GTK 3.24 was a big enough release (with some bumped dependencies) that it's not very practical to push to Ubuntu 18.04 LTS so we selectively cherry-pick fixes there. https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/pango/issues/334 https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5 https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0 Other Info == This adds an extra variation selector byte to each emoji added via the emoji chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji added to GTK apps in other ways, such as copying and pasting from an app where the emoji doesn't have that variation selector added to it. This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: #1808233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.3
** Changed in: gtk+3.0 (Ubuntu Cosmic) Status: Triaged => In Progress -- 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/1808233 Title: Update gtk to 3.24.3 Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Cosmic: In Progress Bug description: Impact == There is a new release in the stable 3.24 series. This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and the Xfce flickering fix from LP: #1798861. https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.3 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. We will also be checking Xfce to validate the fix for LP: #1798861. Regression Potential There is a standing microrelease exception for GNOME point releases. I believe this is the second time in recent history that we've pushed a gtk point release as an SRU. The other example was 3.22.25 for Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS since it already included 3.22.30, the final 3.22 release. It hasn't been practical to update 18.04's gtk to the 3.24 series (bumped dependencies are one problem). https://wiki.ubuntu.com/StableReleaseUpdates#GNOME By the way, pre-release gtk3 is actually getting a bit more testing than a year ago since more developers and users are using development Flatpak releases of popular GNOME apps. (On the other hand, there were a few regressions in the 3.24.2 release.) This update changes the ON/OFF switches for GNOME's default Adwaita theme to use ⏽/⭘. Previously, it was ❙/○ for most languages but ON/OFF for English (because English has short words that could fit on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru which doesn't use labels on its switches. This is technically a UI change, but it is useful for compatibility with Flatpak apps that are being built with the new GTK. This change is small enough that it could be reverted for Ubuntu 18.10 if necessary. Other Info == The commit history shows themeing changes to the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes were reverted for this release to make it easier for distros like us to push the update to our stable release. The next scheduled gtk3 release (3.24.4 ? in March?) will include those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in- gtk-3/ for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.3
** Description changed: Impact == There is a new release in the stable 3.24 series. This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and the Xfce flickering fix from LP: #1798861. https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS - https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.2 + https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.3 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. We will also be checking Xfce to validate the fix for LP: #1798861. Regression Potential There is a standing microrelease exception for GNOME point releases. I believe this is the second time in recent history that we've pushed a gtk point release as an SRU. The other example was 3.22.25 for Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS since it already included 3.22.30, the final 3.22 release. It hasn't been practical to update 18.04's gtk to the 3.24 series (bumped dependencies are one problem). https://wiki.ubuntu.com/StableReleaseUpdates#GNOME By the way, pre-release gtk3 is actually getting a bit more testing than a year ago since more developers and users are using development Flatpak - releases of popular GNOME apps. + releases of popular GNOME apps. (On the other hand, there were a few + regressions in the 3.24.2 release.) + + This update changes the ON/OFF switches for GNOME's default Adwaita + theme to use ⏽/⭘. Previously, it was ❙/○ for most languages but ON/OFF + for English (because English has short words that could fit on a + switch). This doesn't affect default Ubuntu 18.10 which uses Yaru which + doesn't use labels on its switches. This is technically a UI change, but + it is useful for compatibility with Flatpak apps that are being built + with the new GTK. This change is small enough that it could be reverted + for Ubuntu 18.10 if necessary. Other Info == - One of the bigger changes in the git commit history were theming changes to the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3. Ubuntu 18.10 uses the Yaru theme as default instead.). But those changes were reverted for this release to make it easier for distros like us to push the update to our stable release. + The commit history shows themeing changes to the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes were reverted for this release to make it easier for distros like us to push the update to our stable release. + + The next scheduled gtk3 release (3.24.4 ? in March?) will include those + changes. See https://blog.gtk.org/2019/01/14/theme-changes-in-gtk-3/ for + more details. -- 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/1808233 Title: Update gtk to 3.24.3 Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Cosmic: Triaged Bug description: Impact == There is a new release in the stable 3.24 series. This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and the Xfce flickering fix from LP: #1798861. https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.3 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. We will also be checking Xfce to validate the fix for LP: #1798861. Regression Potential There is a standing microrelease exception for GNOME point releases. I believe this is the second time in recent history that we've pushed a gtk point release as an SRU. The other example was 3.22.25 for Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS since it already included 3.22.30, the final 3.22 release. It hasn't been practical to update 18.04's gtk to the 3.24 series (bumped dependencies are one problem). https://wiki.ubuntu.com/StableReleaseUpdates#GNOME By the way, pre-release gtk3 is actually getting a bit more testing than a year ago since more developers and users are using development Flatpak releases of popular GNOME apps. (On the other hand, there were a few regressions in the 3.24.2 release.) This update changes the ON/OFF switches for GNOME's default Adwaita theme to use ⏽/⭘. Previously, it was ❙/○ for most languages but ON/OFF for English (because English has short words that could fit on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru which doesn't use labels on its switches. This is technically a UI change, but it is useful for compatibility with Flatpak apps that are being built with the new GTK. This change is small enough that it could be reverted for
[Touch-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
The epson-inkjet-printer-escpr failures have all passed now after my restarts. There are still some libreoffice failures (1 arch on each Ubuntu release) which I have now re-triggered now. But do we really need libreoffice on s390x? On Bionic on openjdk-8/8u191-b12-0ubuntu0.18.04.1 all architectures fail.Can this be a problem of openjdk and not of CUPS? Also the failures of openjdk-lts are all ignored, so should we also ignore openjdk-8? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.3
** Summary changed: - Update gtk to 3.24.2 + Update gtk to 3.24.3 ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Released => Fix Committed -- 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/1808233 Title: Update gtk to 3.24.3 Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Cosmic: Triaged Bug description: Impact == There is a new release in the stable 3.24 series. This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and the Xfce flickering fix from LP: #1798861. https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.2 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. We will also be checking Xfce to validate the fix for LP: #1798861. Regression Potential There is a standing microrelease exception for GNOME point releases. I believe this is the second time in recent history that we've pushed a gtk point release as an SRU. The other example was 3.22.25 for Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS since it already included 3.22.30, the final 3.22 release. It hasn't been practical to update 18.04's gtk to the 3.24 series (bumped dependencies are one problem). https://wiki.ubuntu.com/StableReleaseUpdates#GNOME By the way, pre-release gtk3 is actually getting a bit more testing than a year ago since more developers and users are using development Flatpak releases of popular GNOME apps. Other Info == One of the bigger changes in the git commit history were theming changes to the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3. Ubuntu 18.10 uses the Yaru theme as default instead.). But those changes were reverted for this release to make it easier for distros like us to push the update to our stable release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1260855] Re: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity)
** Changed in: apport (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1260855 Title: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity) Status in apport package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Bug description: When installing on an IPv6 only network, the installer incorrectly reports that no Internet connectivity is available. Steps to reproduce: - Download desktop ISO. I used http://cdimage.ubuntu.com/xubuntu/daily-live/current/trusty-desktop-amd64.iso current at Fri Dec 13 15:00 EST - Boot ISO on a computer where only IPv6 connectivity is available - Choose Install Xubuntu - Choose language Results: - At "Preparing to install Xubuntu screen" it states For best results, please ensure that this computer: ✓ has at least 5.5GB available drive space ✕ is connected to the Internet Expected results: - A checkmark next to "is connected to the internet" The install is able to complete from the ISO. Once the installed machine is booted, updates are able to be applied indicating Internet connectivity is indeed available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1260855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511840] Re: cannot apport-bug from IPv6-only network
This should now work. If it doesn't please let me know :) ** Changed in: apport (Ubuntu) Assignee: Canonical IS (canonical-is-public) => Junien Fridrick (axino) ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1511840 Title: cannot apport-bug from IPv6-only network Status in apport package in Ubuntu: Fix Released Bug description: Attempting to report a bug using apport-bug from a machine without a legacy IP address fails: # apport-bug foopackage ... *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. *** Error: Network problem Cannot connect to crash database, please check your Internet connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1511840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811812] Re: Util-linux will not install - unmet dependendies
This bug only affects the version of the package in disco-proposed, which users should not be installing from. This will automatically resolve the bug with no changes required to the util-linux package, so there is no reason to keep a bug open on this package to track it; at the moment the bug is fixed, util-linux will be migratable to the disco release pocket. ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1811812 Title: Util-linux will not install - unmet dependendies Status in util-linux package in Ubuntu: Invalid Bug description: Package util-linux (2.33.1-0.1ubuntu1) cannot be installed due to unmet dependencies. Util-linux depends on login (>=1:4.5-1.1~) but the latest installable version is login (1:4.5-1ubuntu1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1811812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial
After investigation the problem is inside pvscan itself I test with and without this commit and it does the trick. Without I can reproduce, with I can't. --- commit 15da467b52465076a8d587b94cc638bab8a0a95c Author: David Teigland Date: Wed Jun 15 14:19:18 2016 -0500 pvscan: do activation when lvmetad is not running When pvscan --cache -aay fails to connect to lvmetad it will simply exit and do nothing. Change this so that it will skip the lvmetad cache step and do the activation step from disk. --- The commit above introduce a regression fix later in : -- commit f77fe436afb76ddb798d236d34daf50413a184f6 Author: David Teigland Date: Thu Jun 16 12:04:05 2016 -0500 pvscan: don't activate LVs when use_lvmetad=0 commit 15da467b was meant to address the case where use_lvmetad=1 in lvm.conf, and lvmetad is not available, in which case, pvscan --cache -aay should activate LVs. But the commit unintentionally also changed the case where use_lvmetad=0 in lvm.conf, in which case pvscan --cache -aay should not activate LVs, so fix that here -- Both above commits have been applied on top on a major code refactoring not yet in lvm2 xenial-updates : -- commit 9b640c36841e2790731d54a5830dcea8203f9e80 Author: David Teigland Date: Thu Apr 28 09:37:03 2016 -0500 pvscan: use process_each_vg for autoactivate This refactors the code for autoactivation. Previously, as each PV was found, it would be sent to lvmetad, and the VG would be autoactivated using a non-standard VG processing function (the "activation_handler") called via a function pointer from within the lvmetad notification path. Now, any scanning that the command needs to do (scanning only the named device args, or scanning all devices when there are no args), is done first, before any activation is attempted. During the scans, the VG names are saved. After scanning is complete, process_each_vg is used to do autoactivation of the saved VG names. This makes pvscan activation much more similar to activation done with vgchange or lvchange. The separate autoactivate phase also means that if lvmetad is disabled (either before or during the scan), the command can continue with the activation step by simply not using lvmetad and reverting to disk scanning to do the activation. -- I'll investigate and see how feasible a backport and if eligible for SRU. - Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1573982 Title: LVM boot problem - volumes not activated after upgrade to Xenial Status in curtin: Incomplete Status in MAAS: Incomplete Status in lvm2 package in Ubuntu: Confirmed Bug description: Soon after upgrade to Xenial (from 15.10) the boot process got broken. I'm using LVM for /root swap and other partitions. === The current behaviour is: When I boot short after the Grub login screen I'm getting log messages like: --- Scanning for Btrfs filesystems resume: Could not state the resume device file: '/dev/mapper/VolGroup' Please type in the full path... --- Then I press ENTER, for a few minutes some errors about floppy device access are raised (for some reason it tries to scan fd0 when floppy drive is empty). And then: --- Gave up waiting for root device. Common problems: ... ... ALERT! UUID=xxx-xxx does not exist. Dropping to a shell. --- From the BusyBox shell I managed to recover the boot by issuing "lvm vgchange -ay", then exit and then boot continues fine (all LVM file systems are successfully mounted). === One workaround so far is creating /etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange -ay". But I'm looking for cleaner solution. Boot used to work fine with 15.10. Actually the first boot after upgrading to Xenial actually worked OK too, I'm not sure what might changed meanwhile (I've been fixing some packages installation since mysql server upgrade has failed). === # lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1573982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
I have a similar problem on 18.04 on a Lenovo V330. Suspend works fine without external monitor, but no matter what I do it's inhibited when its connected. I want it to suspend always. $ grep -i lid /etc/systemd/logind.conf #HandleLidSwitch=suspend HandleLidSwitchDocked=suspend #LidSwitchIgnoreInhibited=yes $ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor true $ systemd-inhibit --list --mode=block Who: gdm (UID 121/gdm, PID 5935/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Who: gaute (UID 1000/gaute, PID 1713/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Only the second of these goes away when monitor is unplugged, but lid close still works. This is possibly due to a bug in gsd-power which is mentioned in the following guthub issues. https://github.com/systemd/systemd/issues/7137 https://github.com/linuxmint/cinnamon-settings-daemon/issues/224 https://github.com/linuxmint/Cinnamon/issues/7347 ** Bug watch added: github.com/linuxmint/cinnamon-settings-daemon/issues #224 https://github.com/linuxmint/cinnamon-settings-daemon/issues/224 ** Bug watch added: github.com/linuxmint/Cinnamon/issues #7347 https://github.com/linuxmint/Cinnamon/issues/7347 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811812] Re: Util-linux will not install - unmet dependendies
The dependencies must be corrected or newer login version must be built. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1811812 Title: Util-linux will not install - unmet dependendies Status in util-linux package in Ubuntu: New Bug description: Package util-linux (2.33.1-0.1ubuntu1) cannot be installed due to unmet dependencies. Util-linux depends on login (>=1:4.5-1.1~) but the latest installable version is login (1:4.5-1ubuntu1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1811812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811812] [NEW] Util-linux will not install - unmet dependendies
Public bug reported: Package util-linux (2.33.1-0.1ubuntu1) cannot be installed due to unmet dependencies. Util-linux depends on login (>=1:4.5-1.1~) but the latest installable version is login (1:4.5-1ubuntu1). ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1811812 Title: Util-linux will not install - unmet dependendies Status in util-linux package in Ubuntu: New Bug description: Package util-linux (2.33.1-0.1ubuntu1) cannot be installed due to unmet dependencies. Util-linux depends on login (>=1:4.5-1.1~) but the latest installable version is login (1:4.5-1ubuntu1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1811812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
Again I had to go to comment #20 -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Triaged Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811630] Re: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
Thanks for this. We have another process for merges in the server team (https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow) but I'll gladly take this work and sponsor it, so don't worry about that. If in the future you would like to give that process a try, feel free to ping us in #ubuntu-server. ** Changed in: openldap (Ubuntu) Status: New => In Progress ** Changed in: openldap (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Tags added: server-next ** Changed in: openldap (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1811630 Title: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main) Status in openldap package in Ubuntu: In Progress Bug description: Hello, I have prepared the merge of openldap 2.4.47+dfsg-2. This will probably be the version released in Debian buster unless any release critical bugs show up. I made changes in Debian to how the contrib modules are built. I made the same changes for nssov in this merge and tested it with the current nss/pam-ldapd. I also added its man page which doesn't seem to have been included before. I performed a test build in a PPA: https://launchpad.net/~rtandy/+archive/ubuntu/openldap2.4.47 Please consider sponsoring this update. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811801] Re: i am not able to ssh to other servers manytimes
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1811801 Title: i am not able to ssh to other servers manytimes Status in ubuntu-themes package in Ubuntu: New Bug description: There is always a message popped up on reboot that system encounter an internal error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-mono 14.04+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jan 15 10:03:19 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: package:ubuntu-mono:14.04+16.04.20160415-0ubuntu1 Unpacking ubuntu-mono (14.04+16.04.20180326-0ubuntu1) over (14.04+16.04.20160415-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/ubuntu-mono_14.04+16.04.20180326-0ubuntu1_all.deb (--unpack): unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-05 (40 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: ubuntu-themes Title: package ubuntu-mono 14.04+16.04.20160415-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1811801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811801] [NEW] i am not able to ssh to other servers manytimes
Public bug reported: There is always a message popped up on reboot that system encounter an internal error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-mono 14.04+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jan 15 10:03:19 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: package:ubuntu-mono:14.04+16.04.20160415-0ubuntu1 Unpacking ubuntu-mono (14.04+16.04.20180326-0ubuntu1) over (14.04+16.04.20160415-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/ubuntu-mono_14.04+16.04.20180326-0ubuntu1_all.deb (--unpack): unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-05 (40 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: ubuntu-themes Title: package ubuntu-mono 14.04+16.04.20160415-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1811801 Title: i am not able to ssh to other servers manytimes Status in ubuntu-themes package in Ubuntu: New Bug description: There is always a message popped up on reboot that system encounter an internal error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-mono 14.04+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jan 15 10:03:19 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: package:ubuntu-mono:14.04+16.04.20160415-0ubuntu1 Unpacking ubuntu-mono (14.04+16.04.20180326-0ubuntu1) over (14.04+16.04.20160415-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/ubuntu-mono_14.04+16.04.20180326-0ubuntu1_all.deb (--unpack): unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-12-05 (40 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: ubuntu-themes Title: package ubuntu-mono 14.04+16.04.20160415-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-dark/status/16/gpm-primary-080.svg.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1811801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750051] Re: cron doesn't support MAILFROM
It looks I accidentally changed status of this bug from "Triaged" to "Fix Released" (I clicked "fix released" in hope it will take me to the version in which it was fixed, but that wasn't a link, but an update action). I'm not sure how I even could change status, since I'm not maintainer. I've tried, but I cannot revert this change. Anyway, please somebody, revert status of tris to "Triaged". ** Changed in: cron (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1750051 Title: cron doesn't support MAILFROM Status in cron package in Ubuntu: Fix Released Status in cron package in Debian: New Bug description: Ubuntu's cron version doesn't support setting MAILFROM to set the "From:" header of cron generated emails. This feature would be nice to have and bring parity with RHEL/CentOS which has it since RHEL 6: $ cat /etc/redhat-release CentOS release 6.6 (Final) $ man 5 crontab | grep -1 FROM doesn´t do aliasing, and UUCP usually doesn´t read its mail. If MAIL- FROM is defined (and non-empty), it will be used as the envelope sender address, otherwise, ‘‘root’’ will be used. $ apt-cache policy cron cron: Installed: 3.0pl1-128ubuntu2 Candidate: 3.0pl1-128ubuntu2 Version table: *** 3.0pl1-128ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 16 15:52:54 2018 InstallationDate: Installed on 2016-12-06 (436 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161206) SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1750051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656100] Re: Unable to remove signing keys using gnome-software-properties
** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Changed in: software-properties (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1656100 Title: Unable to remove signing keys using gnome-software-properties Status in Ubuntu GNOME: Invalid Status in software-properties package in Ubuntu: Fix Committed Bug description: I have found that on Ubuntu GNOME 16.10 with GNOME 3.22 that I am unable to remove signing keys in the Authentication tab. If I select a key I wish to remove and click the Remove button, either nothing will happen, or it will ask me for authentication, upon giving it the correct password all that will happen is it will deselect the key I select, but at no point will it actually remove it, which is rather annoying. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: software-properties-gtk 0.96.24.7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 12 21:35:55 2017 InstallationDate: Installed on 2017-01-09 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) 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-gnome/+bug/1656100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
Thanks for reporting it upstream ** Changed in: network-manager (Ubuntu) Status: Confirmed => Triaged -- 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/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were created by Docker. Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged under the gnome system tray icon which is kind of annoying. I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 24 14:22:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-29 (632 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IpRoute: default via 192.168.178.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.40 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-08-19T11:46:06.705439 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720693] Re: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all
The issue sounds like it should be fixed with this kernel commit https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda/patch_realtek.c?id=bde1a7459623a66c2abec4d0a841e4b06cc88d9a ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => High ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Committed -- 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/1720693 Title: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Bug description: There is no sound from the front jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Oct 1 17:49:29 2017 InstallationDate: Installed on 2017-06-08 (115 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Symptom_amixerStderr: a m i x e r : M i x e r h w : P C H l o a d e r r o r : I n v a l i d a r g u m e n t Title: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: M1AKT17A dmi.board.name: 310B dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259612472445 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1AKT17A:bd04/13/2017:svnLENOVO:pn10MVCTO1WW:pvrThinkCentreM910q:rvnLENOVO:rn310B:rvrSDK0J40709WIN3259612472445:cvnLENOVO:ct3:cvrNone: dmi.product.name: 10MVCTO1WW dmi.product.version: ThinkCentre M910q dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1720693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810214] Re: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all
Looks like it should be fixed with that kernel commit https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda/patch_realtek.c?id=0bea4cc8383519f78f3f74caca7bdebdfb346d3b ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Fix Committed -- 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/1810214 Title: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all Status in linux package in Ubuntu: Fix Committed Bug description: There is no sound whatsoever while the controls all seems to indicate the playback is working. The patop's internal speaker, headphones, even bluetooth is not outputting any sound. Trying to upgrade the kernel to two different versions had no effect. There simply is no sound output nor is there any indication the microphone is working either, but without sound output that's hard to confirm. There are not issues with sounds when I boot into Windows ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.13-041913-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mac1193 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 1 14:18:09 2019 InstallationDate: Installed on 2018-12-30 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mac1193 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FA.204:bd09/19/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FA_UX433FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FA_UX433FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1489154] Re: NetworkManager does not start / fails to start
Further to comments #7 and #16, the reported issue was due to installing packages from -proposed. Unsure why two users have re-opened this without comment so closing again. Anyone still seeing an issue with network-manager should open their own report by running ubuntu-bug network-manager in a terminal so that their own logs get attached to the report. ** Changed in: hundredpapercuts Status: Confirmed => Invalid ** Changed in: network-manager (Ubuntu) Status: Confirmed => Invalid -- 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/1489154 Title: NetworkManager does not start / fails to start Status in One Hundred Papercuts: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: Yesterday i did the upgrade to version 1.0.4 of NetworkManger. Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash report. This also fails cause the start of the NetworkManger fails after booting. Trying manually to start with ~$ sudo systemctl start NetworkManager leads that the icon comes up, disappears, comes up, disappears for 3, 4 times and then it's gone forever. ~$ journalctl -xe Aug 26 22:02:34 Wily NetworkManager[1578]: monitoring ifupdown state file '/run/network/ifstate'. Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVxlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVethFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMTunFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMMacvlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMInfinibandFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMGreFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMEthernetFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBridgeFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBondFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMAtmManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWifiFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBluezManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWwanFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so) Aug 26 22:02:34 Wily NetworkManager[1578]: WiFi enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WWAN enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WiMAX enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: Networking is enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): new Ethernet device (carrier: ON, driver: 'e1000', ifindex: 2) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Aug 26 22:02:34 Wily NetworkManager[1578]: keyfile: add connection in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,"Kabelnetzwerkverbindung 1") Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): created default wired connection 'Kabelnetzwerkverbindung 1' Aug 26 22:02:34 Wily NetworkManager[1578]: urfkill disappeared from the bus Aug 26 22:02:34 Wily NetworkManager[1578]: wpa_supplicant running Aug 26 22:02:34 Wily NetworkManager[1578]: ModemManager available in the bus Aug 26 22:02:34 Wily NetworkManager[1578]: ofono is now available Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemAdded' is invalid for instance Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemRemoved' is invalid for instan Aug 26
[Touch-packages] [Bug 1784776] Re: kbd_mode - "Couldn't get fd referring to console"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kbd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
https://bugs.launchpad.net/bugs/1784776
Title:
kbd_mode - "Couldn't get fd referring to console"
Status in kbd package in Ubuntu:
Confirmed
Bug description:
Sorry for using your bug reporting mechanism directly. 'ubuntu-bug
'/'apport-cli' do not seem to agree with modifications to the text
that they generate (:@{).
Actually, bug #1621824 does fairly well in describing the problem.
Unfortunately, that was a xenial {"ubuntu 16.04"?) bug and the report
is closed. This bug is in "ubuntu 18.04" (bionic) and it is still
occurring. Below is output from 'apport-cli' with a bit of ADDITIONAL
INFORMATION. Right now 'apport-cli' rejects the text below as
"damaged".
-- Thanks,
--Paul Townsend
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jul 31 22:31:41 2018
Dependencies:
adduser 3.116ubuntu1
apt 1.6.3
apt-utils 1.6.3
ca-certificates 20180409
console-setup 1.178ubuntu2.3
console-setup-linux 1.178ubuntu2.3
debconf 1.5.66
debconf-i18n 1.5.66
dpkg 1.19.0.5ubuntu2
gcc-8-base 8-20180414-1ubuntu2
gpgv 2.2.4-1ubuntu1.1
init-system-helpers 1.51
kbd 2.0.4-2ubuntu1
keyboard-configuration 1.178ubuntu2.3
libacl1 2.2.52-3build1
libapt-inst2.0 1.6.3
libapt-pkg5.0 1.6.3
libattr1 1:2.4.47-2build1
libaudit-common 1:2.8.2-1ubuntu1
libaudit1 1:2.8.2-1ubuntu1
libbz2-1.0 1.0.6-8.1
libc6 2.27-3ubuntu1
libcap-ng0 0.7.7-3.1
libdb5.3 5.3.28-13.1ubuntu1
libffi6 3.2.1-8
libgcc1 1:8-20180414-1ubuntu2
libgcrypt20 1.8.1-4ubuntu1.1
libgmp10 2:6.1.2+dfsg-2
libgnutls30 3.5.18-1ubuntu1
libgpg-error0 1.27-6
libhogweed4 3.4-1
libidn2-0 2.0.4-1.1build2
liblocale-gettext-perl 1.07-3build2
liblz4-1 0.0~r131-2ubuntu3
liblzma5 5.2.2-1.3
libnettle6 3.4-1
libp11-kit0 0.23.9-2
libpam-modules 1.1.8-3.6ubuntu2
libpam-modules-bin 1.1.8-3.6ubuntu2
libpam0g 1.1.8-3.6ubuntu2
libpcre3 2:8.39-9
libseccomp2 2.3.1-2.1ubuntu4
libselinux1 2.7-2build2
libsemanage-common 2.7-2build2
libsemanage1 2.7-2build2
libsepol1 2.7-1
libssl1.1 1.1.0g-2ubuntu4.1
libstdc++6 8-20180414-1ubuntu2
libtasn1-6 4.13-2
libtext-charwidth-perl 0.04-7.1
libtext-iconv-perl 1.7-5build6
libtext-wrapi18n-perl 0.06-7.1
libudev1 237-3ubuntu10.3
libunistring2 0.9.9-0ubuntu1
libzstd1 1.3.3+dfsg-2ubuntu1
openssl 1.1.0g-2ubuntu4.1
passwd 1:4.5-1ubuntu1
perl-base 5.26.1-6ubuntu0.2
tar 1.29b-2
ubuntu-keyring 2018.02.28
xkb-data 2.23.1-1ubuntu1
zlib1g 1:1.2.11.dfsg-0ubuntu2
DistroRelease: Ubuntu 18.04
Package: kbd 2.0.4-2ubuntu1
PackageArchitecture: amd64
ProcCpuinfoMinimal:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 142
model name : Intel(R) Core(TM) i3-8130U CPU @ 2.20GHz
stepping : 10
microcode : 0x
cpu MHz: 2208.000
cache size : 256 KB
physical id: 0
siblings : 4
core id: 1
cpu cores : 2
apicid : 0
initial apicid : 0
fpu: yes
fpu_exception : yes
cpuid level: 6
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
pdpe1gb rdtscp lm pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma
cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes
xsave osxsave avx f16c rdrand
bogomips : 4416.00
clflush size : 64
cache_alignment: 64
address sizes : 36 bits physical, 48 bits virtual
power management:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Microsoft 4.4.0-17134.137-Microsoft 4.4.35
SourcePackage: kbd
Tags: bionic uec-images
Uname: Linux 4.4.0-17134-Microsoft x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
_MarkForUpload: True
ADDITIONAL INFORMATION:
- To duplicate the problem -
$ (sudo) kbd_mode
Couldn't get a file descriptor referring to the console
$
- A 'kbd' problem that is very similar is noted for xenial in the closed bug
report #1621824
You could probably substitute 'kbd_mode" for the 'loadkeys' invocations
specified in the text. I encountered the problem when I ran 'setupcon' and
that script uses both 'kbd_mode' and 'loadkeys'.
- If the xenial fix is still around, how do I get it. "xenial-proposed" does
not seem to have it.
- It really does not indicate as such above but this
