[Touch-packages] [Bug 1811531]
openSUSE-SU-2019:0087-1: An update that solves one vulnerability and has one errata is now available. Category: security (important) Bug References: 1082318,1121717 CVE References: CVE-2019-6250 Sources used: openSUSE Leap 15.0 (src):zeromq-4.2.3-lp150.2.10.1 -- 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: Fix Released Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Fix Released 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 1811531]
released -- 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: Fix Released Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Fix Released 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 1811531] Re: remote execution vulnerability
** Changed in: zeromq (Suse) Status: Unknown => Fix Released -- 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: Fix Released Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Fix Released 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 1787824] Re: "rfkill: input handler disabled" boot time 11 seconds.
[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: util-linux (Ubuntu) Status: Incomplete => Expired -- 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/1787824 Title: "rfkill: input handler disabled" boot time 11 seconds. Status in util-linux package in Ubuntu: Expired Bug description: My computer is slowly opening, I looked at the output of dmesg and at 11th I get this post. What i need to do? thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rfkill 2.31.1-0.4ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 19:44:21 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libsmartcols1 2.31.1-0.4ubuntu3.1 InstallationDate: Installed on 2018-08-18 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1787824/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805077] Re: the audio pause and repeat for a very short of time randomly
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1805077 Title: the audio pause and repeat for a very short of time randomly Status in pulseaudio package in Ubuntu: Expired Bug description: the audio pause and repeat for a very short of time randomly when I use web browser to play music and use smplayer play video this bug happens randomly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 13716 F pulseaudio /dev/snd/controlC0: widon 13716 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-24 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI 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/pulseaudio/+bug/1805077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
This bug was fixed in the package openjdk-lts - 11.0.2+9-3ubuntu1 --- openjdk-lts (11.0.2+9-3ubuntu1) disco; urgency=medium * Sync packages with 11.0.2+9-3: - Fix Zero on sparc64 (Adrian Glaubitz). Closes: #920315. - Link zero on alpha with --no-relax (Michael Cree). Addresses: #920161. - Don't run the tests on alpha, causing build failure. - jhsdb isn't built on alpha. - Backport the fix for 8214002 (cannot use italic font style if the font has embedded bitmap). LP: #1799014. * Sync packages with 11.0.2+9-2: - Fix file permissions for autopkg tests. -- Matthias Klose Thu, 24 Jan 2019 15:14:20 +0100 ** Changed in: openjdk-lts (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: Fix Released Status in freetype source package in Bionic: New Status in openjdk-lts source package in Bionic: New Status in freetype source package in Cosmic: New Status in openjdk-lts source package in Cosmic: New Status in openjdk-11 package in Debian: Fix Released Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards
Issues is still present in 18.10. (I do see that the cosmic and disco tags were added). -- 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/1738676 Title: With natural scrolling, horizontal sliders behave backwards Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: When natural-scrolling is enabled, controlling horizontal sliders is backwards and counter intuitive. The volume control in the top-bar "speaker" icon is backwards. You have to... - scroll DOWN, to INCREASE the volume - scroll UP, to DECREASE the volume Expected behavior: Enable natural-scrolling and - scroll UP, to INCREASE the volume - scroll DOWN, to DECREASE the volume - scroll UP, to INCREASE the screen brightness - scroll DOWN, to DECREASE the screen brightness Enable natural-scrolling, hover over a horizontal slider, and... - scroll UP, to move the slider to the RIGHT - scroll DOWN, to move the slider to the LEFT This happens for the OSD volume icon, and for the volume slider in the topbar menu. This also happens for screen brightness controls. This problem occurs for both mouse natural-scrolling and touchpad natural scrolling. Expected fix: When the pointer hovers over the speaker icon in the scroll actions on the speaker icon in the top bar should be reversed. When the user interacts with a horizontal slider, scrolling to the top should always move the slider to the right, and scrolling down should always move the slider to the left, even if natural-scrolling is enabled. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 17 19:23:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-12-10 (7 days ago) InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1738676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813376] [NEW] i dont know what that is
Public bug reported: Please help me since I am new to linux and My wifi also got question mark all the time after 15-20 mins ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jan 25 17:45:45 2019 DistUpgraded: 2018-08-24 14:16:14,907 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-33-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-133-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Seymour [Radeon HD 6400M/7400M Series] [106b:00e1] InstallationDate: Installed on 2015-02-26 (1429 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Apple Inc. MacBookPro8,2 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=754616c8-84b9-4619-95cf-b7420df47da7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-24 (154 days ago) dmi.bios.date: 10/20/16 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B2D.1610201938 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B2D.1610201938:bd10/20/16:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Aug 23 23:14:20 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813376 Title: i dont know what that is Status in xorg package in Ubuntu: New Bug description: Please help me since I am new to linux and My wifi also got question mark all the time after 15-20 mins ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jan 25 17:45:45 2019 DistUpgraded: 2018-08-24 14:16:14,907 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-33-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-133-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Seymour [Radeon HD 6400M/7400M Series] [106b:00e1] InstallationDate: Installed on 2015-02-26 (1429 days ago) InstallationMedia: Ubuntu 14.04.2 LTS
[Touch-packages] [Bug 1810840] Re: whoopsie can't remember "always report" setting
** Changed in: whoopsie-preferences (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie-preferences in Ubuntu. https://bugs.launchpad.net/bugs/1810840 Title: whoopsie can't remember "always report" setting Status in whoopsie-preferences package in Ubuntu: Confirmed Bug description: After ticking the checkbox for whoopsie to automatically always send crash reports, I get the following error dialog (screenshot attached): *Can't remember send report status settings* Saving crash report state failed. Can't set auto or never reporting mode. Command '['/usr/bin/gdbus', 'call', '-y', '-d', 'com.ubuntu.WhoopsiePreferences', '-o', '/com/ubuntu/WhoopsiePreferences', '-m', 'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']' returned non-zero exit status 1. I'm pretty sure this error happens because whoopsie-preferences was not installed; afterwards I installed whoopsie-preferences and manually ran in a terminal: $ /usr/bin/gdbus call -y -d com.ubuntu.WhoopsiePreferences -o /com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.SetReportCrashes true and got a return value of () but no errors or warnings. This computer was freshly-installed with Xubuntu 18.04 less than 2 weeks ago... I've kept a record of everything I changed since then, and I've only removed five packages (sgt-puzzles, gnome-sudoku, gnome- mines, pidgin, mousepad). If whoopsie-preferences is not included in a fresh install of (X)ubuntu, then perhaps it should be; in any case, if it isn't installed then the checkbox for making crash reporting automatic should not be visible. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy whoopsie whoopsie: Installed: 0.2.62 Candidate: 0.2.62 Version table: *** 0.2.62 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy whoopsie-preferences whoopsie-preferences: Installed: (none) Candidate: 0.19 Version table: 0.19 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1810840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello Marc, or anyone else affected, Accepted ubiquity into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/18.04.14.11 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: ubiquity (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-failed-bionic -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in ubiquity source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813052] Re: who returns no results
re-assigning to systemD as requested.
** Package changed: coreutils (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1813052
Title:
who returns no results
Status in systemd package in Ubuntu:
New
Bug description:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and
an strace on a system that works (an unupdated xenial or a bionic
system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eed000
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f225391c000
mprotect(0x7f2253adc000, 2097152, PROT_NONE) = 0
mmap(0x7f2253cdc000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f2253cdc000
mmap(0x7f2253ce2000, 14752, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f2253ce2000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eec000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eeb000
arch_prctl(ARCH_SET_FS, 0x7f2253eec700) = 0
mprotect(0x7f2253cdc000, 16384, PROT_READ) = 0
mprotect(0x60a000, 4096, PROT_READ) = 0
mprotect(0x7f2253f0b000, 4096, PROT_READ) = 0
munmap(0x7f2253eee000, 117369) = 0
brk(NULL) = 0x9f9000
brk(0xa1a000) = 0xa1a000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253644000
close(3)= 0
access("/var/run/utmpx", F_OK) = 0
open("/var/run/utmpx", O_RDONLY|O_CLOEXEC) = 3
lseek(3, 0, SEEK_SET) = 0
alarm(0)= 0
rt_sigaction(SIGALRM, {0x7f2253a5d380, [], SA_RESTORER, 0x7f22539514b0},
{SIG_DFL, [], 0}, 8) = 0
alarm(10) = 0
fcntl(3, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
read(3, 0x7f2253ce5120, 384)= -1 EISDIR (Is a directory)
fcntl(3, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
alarm(0)= 10
rt_sigaction(SIGALRM, {SIG_DFL, [], SA_RESTORER, 0x7f22539514b0}, NULL, 8) = 0
close(3)= 0
close(1)= 0
close(2)= 0
exit_group(0) = ?
+++ exited with 0 +++
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu3~16.04
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Jan 23 10:39:00 2019
InstallationDate: Installed on 2016-07-08 (929 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813052/+subscriptions
--
Mailing list: https://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 1813052] Re: who returns no results
reassign 1813052 systemd
thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1813052
Title:
who returns no results
Status in coreutils package in Ubuntu:
New
Bug description:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and
an strace on a system that works (an unupdated xenial or a bionic
system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eed000
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f225391c000
mprotect(0x7f2253adc000, 2097152, PROT_NONE) = 0
mmap(0x7f2253cdc000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f2253cdc000
mmap(0x7f2253ce2000, 14752, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f2253ce2000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eec000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eeb000
arch_prctl(ARCH_SET_FS, 0x7f2253eec700) = 0
mprotect(0x7f2253cdc000, 16384, PROT_READ) = 0
mprotect(0x60a000, 4096, PROT_READ) = 0
mprotect(0x7f2253f0b000, 4096, PROT_READ) = 0
munmap(0x7f2253eee000, 117369) = 0
brk(NULL) = 0x9f9000
brk(0xa1a000) = 0xa1a000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253644000
close(3)= 0
access("/var/run/utmpx", F_OK) = 0
open("/var/run/utmpx", O_RDONLY|O_CLOEXEC) = 3
lseek(3, 0, SEEK_SET) = 0
alarm(0)= 0
rt_sigaction(SIGALRM, {0x7f2253a5d380, [], SA_RESTORER, 0x7f22539514b0},
{SIG_DFL, [], 0}, 8) = 0
alarm(10) = 0
fcntl(3, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
read(3, 0x7f2253ce5120, 384)= -1 EISDIR (Is a directory)
fcntl(3, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
alarm(0)= 10
rt_sigaction(SIGALRM, {SIG_DFL, [], SA_RESTORER, 0x7f22539514b0}, NULL, 8) = 0
close(3)= 0
close(1)= 0
close(2)= 0
exit_group(0) = ?
+++ exited with 0 +++
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu3~16.04
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Jan 23 10:39:00 2019
InstallationDate: Installed on 2016-07-08 (929 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1813052/+subscriptions
--
Mailing list: https://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 1813052] Re: who returns no results
reassign 1813052 systemd
On Fri, Jan 25, 2019 at 3:17 PM A Godshall wrote:
>
> OK, I found a workaround:
>
> $ sudo apt install systemd=229-4ubuntu4 libsystemd0=229-4ubuntu4
> libpam-systemd=229-4ubuntu4
>
> Looks like it's not a coreutils nor a who issue, it's a systemd issue,
> perhaps related to backport, since I'm not seeing it on bionic.
>
> Of course next upgrade will break it again, until the packages are fixed.
>
>
> On Fri, Jan 25, 2019 at 12:17 PM A Godshall wrote:
> >
> > Oh, and to be clear, this is a regression.
> >
> >
> > On Wed, Jan 23, 2019, 11:15 AM Anthony Godshall > wrote:
> >>
> >> Attempting to diagnose, I had added /var/run/utmp and /var/run/utmpx as
> >> directories. I just removed those, same empty result:
> >> # who
> >> # who;echo $?
> >> 0
> >> # strace who
> >> execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
> >> brk(NULL) = 0x1726000
> >> access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
> >> directory)
> >> access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
> >> directory)
> >> open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
> >> fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
> >> mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efc0bce
> >> close(3)= 0
> >> access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
> >> directory)
> >> open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
> >> read(3,
> >> "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 832) =
> >> 832
> >> fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
> >> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> >> 0x7efc0bcdf000
> >> mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0)
> >> = 0x7efc0b70e000
> >> mprotect(0x7efc0b8ce000, 2097152, PROT_NONE) = 0
> >> mmap(0x7efc0bace000, 24576, PROT_READ|PROT_WRITE,
> >> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7efc0bace000
> >> mmap(0x7efc0bad4000, 14752, PROT_READ|PROT_WRITE,
> >> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7efc0bad4000
> >> close(3)= 0
> >> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> >> 0x7efc0bcde000
> >> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> >> 0x7efc0bcdd000
> >> arch_prctl(ARCH_SET_FS, 0x7efc0bcde700) = 0
> >> mprotect(0x7efc0bace000, 16384, PROT_READ) = 0
> >> mprotect(0x60a000, 4096, PROT_READ) = 0
> >> mprotect(0x7efc0bcfd000, 4096, PROT_READ) = 0
> >> munmap(0x7efc0bce, 117369) = 0
> >> brk(NULL) = 0x1726000
> >> brk(0x1747000) = 0x1747000
> >> open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
> >> fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
> >> mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efc0b436000
> >> close(3)= 0
> >> access("/var/run/utmpx", F_OK) = -1 ENOENT (No such file or
> >> directory)
> >> open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
> >> directory)
> >> access("/var/run/utmpx", F_OK) = -1 ENOENT (No such file or
> >> directory)
> >> open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
> >> directory)
> >> close(1)= 0
> >> close(2)= 0
> >> exit_group(0) = ?
> >> +++ exited with 0 +++
> >> #
> >>
> >> --
> >> You received this bug notification because you are subscribed to the bug
> >> report.
> >> https://bugs.launchpad.net/bugs/1813052
> >>
> >> Title:
> >> who returns no results
> >>
> >> To manage notifications about this bug go to:
> >> https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1813052/+subscriptions
>
>
>
> --
> Best Regards.
> This is unedited.
> P-)
--
--
Best Regards.
This is unedited.
This message came out of me
via a suboptimal keyboard.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1813052
Title:
who returns no results
Status in coreutils package in Ubuntu:
New
Bug description:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and
an strace on a system that works (an unupdated xenial or a bionic
system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) =
Re: [Touch-packages] [Bug 1813052] Re: who returns no results
OK, I found a workaround:
$ sudo apt install systemd=229-4ubuntu4 libsystemd0=229-4ubuntu4
libpam-systemd=229-4ubuntu4
Looks like it's not a coreutils nor a who issue, it's a systemd issue,
perhaps related to backport, since I'm not seeing it on bionic.
Of course next upgrade will break it again, until the packages are
fixed.
On Fri, Jan 25, 2019 at 12:17 PM A Godshall wrote:
>
> Oh, and to be clear, this is a regression.
>
>
> On Wed, Jan 23, 2019, 11:15 AM Anthony Godshall wrote:
>>
>> Attempting to diagnose, I had added /var/run/utmp and /var/run/utmpx as
>> directories. I just removed those, same empty result:
>> # who
>> # who;echo $?
>> 0
>> # strace who
>> execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
>> brk(NULL) = 0x1726000
>> access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
>> directory)
>> access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
>> directory)
>> open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
>> fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
>> mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efc0bce
>> close(3)= 0
>> access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
>> directory)
>> open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
>> read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
>> 832) = 832
>> fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
>> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
>> 0x7efc0bcdf000
>> mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
>> 0x7efc0b70e000
>> mprotect(0x7efc0b8ce000, 2097152, PROT_NONE) = 0
>> mmap(0x7efc0bace000, 24576, PROT_READ|PROT_WRITE,
>> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7efc0bace000
>> mmap(0x7efc0bad4000, 14752, PROT_READ|PROT_WRITE,
>> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7efc0bad4000
>> close(3)= 0
>> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
>> 0x7efc0bcde000
>> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
>> 0x7efc0bcdd000
>> arch_prctl(ARCH_SET_FS, 0x7efc0bcde700) = 0
>> mprotect(0x7efc0bace000, 16384, PROT_READ) = 0
>> mprotect(0x60a000, 4096, PROT_READ) = 0
>> mprotect(0x7efc0bcfd000, 4096, PROT_READ) = 0
>> munmap(0x7efc0bce, 117369) = 0
>> brk(NULL) = 0x1726000
>> brk(0x1747000) = 0x1747000
>> open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
>> fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
>> mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efc0b436000
>> close(3)= 0
>> access("/var/run/utmpx", F_OK) = -1 ENOENT (No such file or
>> directory)
>> open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
>> directory)
>> access("/var/run/utmpx", F_OK) = -1 ENOENT (No such file or
>> directory)
>> open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
>> directory)
>> close(1)= 0
>> close(2)= 0
>> exit_group(0) = ?
>> +++ exited with 0 +++
>> #
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1813052
>>
>> Title:
>> who returns no results
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1813052/+subscriptions
--
Best Regards.
This is unedited.
P-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1813052
Title:
who returns no results
Status in coreutils package in Ubuntu:
New
Bug description:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and
an strace on a system that works (an unupdated xenial or a bionic
system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
[Touch-packages] [Bug 1798562] Re: After a side by side installation, resized filesystem is corrupted
Hello Jean-Baptiste, or anyone else affected, Accepted e2fsprogs into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/e2fsprogs/1.44.4-2ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: e2fsprogs (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: e2fsprogs (Ubuntu Bionic) Status: New => 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 e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1798562 Title: After a side by side installation, resized filesystem is corrupted Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Bionic: Fix Committed Status in e2fsprogs source package in Cosmic: Fix Committed Bug description: [Impact] - Users resizing filesystems using resize2fs. - Resizing an existing Linux filesystem from the Ubuntu installer. [Test cases] Test Case 1: With e2fsprogs 1.44.4-2: Download this file system image: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz Run the following commands: bunzip2 vda1b.qcow2.bz qemu-img convert vda1b.qcow2 vda1b.raw e2fsck -f vda1b.raw resize2fs vda1b.raw 6200M e2fsck -f vda1b.raw e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Inode 45746 extent block passes checks, but checksum does not match extent (logical block 1272, physical block 466167, len 776) Fix? Test Case 2 (Use case of the installer): 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... [Regression potential] This changes behavior in the update logic for extent blocks; as such, care should be taken to make sure that testing takes into account the possibility to introduce filesystem corruption while resizing. This is why the test cases include running e2fsck as last step. --- Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 10:53:57 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2018-10-18 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798562] Please test proposed package
Hello Jean-Baptiste, or anyone else affected, Accepted e2fsprogs into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/e2fsprogs/1.44.1-1ubuntu1.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1798562 Title: After a side by side installation, resized filesystem is corrupted Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Bionic: Fix Committed Status in e2fsprogs source package in Cosmic: Fix Committed Bug description: [Impact] - Users resizing filesystems using resize2fs. - Resizing an existing Linux filesystem from the Ubuntu installer. [Test cases] Test Case 1: With e2fsprogs 1.44.4-2: Download this file system image: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz Run the following commands: bunzip2 vda1b.qcow2.bz qemu-img convert vda1b.qcow2 vda1b.raw e2fsck -f vda1b.raw resize2fs vda1b.raw 6200M e2fsck -f vda1b.raw e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Inode 45746 extent block passes checks, but checksum does not match extent (logical block 1272, physical block 466167, len 776) Fix? Test Case 2 (Use case of the installer): 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... [Regression potential] This changes behavior in the update logic for extent blocks; as such, care should be taken to make sure that testing takes into account the possibility to introduce filesystem corruption while resizing. This is why the test cases include running e2fsck as last step. --- Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 10:53:57 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2018-10-18 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813362] [NEW] lxc-top flash error and blkio write is always zero
Public bug reported: When running lxc-top as root it flashes the following error messages for every container: Unable to read cgroup item memory.memsw.usage_in_bytes Unable to read cgroup item memory.memsw.limit_in_bytes Here output showing bad blkio write Container CPU CPU CPU BlkIOMem KMem Name Used Sys User Total(Read/Write) Used Used ltcd-root310.2298.26 196.88 315.06 MiB(315.06 MiB/ 0.00 ) 688.64 MiB 83.09 MiB ltcd-test236.0284.52 136.76 115.88 MiB(115.88 MiB/ 0.00 ) 384.39 MiB 31.89 MiB TOTAL 2 of 2 546.24 182.78 333.64 430.94 MiB(430.94 MiB/ 0.00 ) 1.04 GiB 114.97 MiB Doing an strace on lxc-top: openat(AT_FDCWD, "/sys/fs/cgroup/memory//lxc/ltcd-root/memory.memsw.usage_in_bytes", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) write(2, "Unable to read cgroup item memor"..., 55) = 55 openat(AT_FDCWD, "/sys/fs/cgroup/memory//lxc/ltcd-root/memory.memsw.limit_in_bytes", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) write(2, "Unable to read cgroup item memor"..., 55) = 55 Here is copy /sys/fs/cgroup/memory/lxc/ltcd-root mike@mike-desktop:/sys/fs/cgroup/memory/lxc/ltcd-root$ ls cgroup.clone_children memory.limit_in_bytes cgroup.event_controlmemory.max_usage_in_bytes cgroup.procsmemory.move_charge_at_immigrate init.scope memory.numa_stat memory.failcnt memory.oom_control memory.force_empty memory.pressure_level memory.kmem.failcnt memory.soft_limit_in_bytes memory.kmem.limit_in_bytes memory.stat memory.kmem.max_usage_in_bytes memory.swappiness memory.kmem.slabinfomemory.usage_in_bytes memory.kmem.tcp.failcnt memory.use_hierarchy memory.kmem.tcp.limit_in_bytes notify_on_release memory.kmem.tcp.max_usage_in_bytes system.slice memory.kmem.tcp.usage_in_bytes tasks memory.kmem.usage_in_bytes user.slice ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc-utils 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 25 15:56:04 2019 InstallationDate: Installed on 2018-02-23 (336 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to bionic on 2018-10-21 (95 days ago) mtime.conffile..etc.lxc.default.conf: 2019-01-24T17:40:41.527776 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1813362 Title: lxc-top flash error and blkio write is always zero Status in lxc package in Ubuntu: New Bug description: When running lxc-top as root it flashes the following error messages for every container: Unable to read cgroup item memory.memsw.usage_in_bytes Unable to read cgroup item memory.memsw.limit_in_bytes Here output showing bad blkio write Container CPU CPU CPU BlkIOMem KMem Name Used Sys User Total(Read/Write) Used Used ltcd-root310.2298.26 196.88 315.06 MiB(315.06 MiB/ 0.00 ) 688.64 MiB 83.09 MiB ltcd-test236.0284.52 136.76 115.88 MiB(115.88 MiB/ 0.00 ) 384.39 MiB 31.89 MiB TOTAL 2 of 2 546.24 182.78 333.64 430.94 MiB(430.94 MiB/ 0.00 ) 1.04 GiB 114.97 MiB Doing an strace on lxc-top: openat(AT_FDCWD, "/sys/fs/cgroup/memory//lxc/ltcd-root/memory.memsw.usage_in_bytes", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) write(2, "Unable to read cgroup item memor"..., 55) = 55 openat(AT_FDCWD, "/sys/fs/cgroup/memory//lxc/ltcd-root/memory.memsw.limit_in_bytes", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) write(2, "Unable to read cgroup item memor"..., 55) = 55 Here is copy /sys/fs/cgroup/memory/lxc/ltcd-root mike@mike-desktop:/sys/fs/cgroup/memory/lxc/ltcd-root$ ls cgroup.clone_children memory.limit_in_bytes cgroup.event_control memory.max_usage_in_bytes cgroup.procs memory.move_charge_at_immigrate init.scope
[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
** Bug watch added: github.com/systemd/systemd/issues #5882 https://github.com/systemd/systemd/issues/5882 ** Also affects: systemd via https://github.com/systemd/systemd/issues/5882 Importance: Unknown Status: Unknown ** No longer affects: systemd ** Bug watch added: github.com/systemd/systemd/issues #10874 https://github.com/systemd/systemd/issues/10874 ** Also affects: systemd via https://github.com/systemd/systemd/issues/10874 Importance: Unknown Status: Unknown -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: [Impact] Mounting manually a network share (NFS) and masking it breaks the state of other units (and their dependencies). Casper is masking a mounted NFS share, blocking the normal boot process as described in the original description, but the issue comes from systemd. [Test Case] - NFS mount point at /media root@iscsi-bionic:/home/ubuntu# mount | grep media 10.230.56.72:/tmp/mnt on /media type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72) - Test mount point (/test) defined in /etc/fstab: root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test tmpfs /test tmpfs nosuid,nodev 0 0 1. If media.mount is not masked, everything works fine: root@iscsi-bionic:/home/ubuntu# mount | grep test root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days ago root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago root@iscsi-bionic:/home/ubuntu# systemctl start test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test 2. If media.mount is masked, other mounts are failing: root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount Created symlink /etc/systemd/system/media.mount → /dev/null. root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) [Regression potential] Minimal. Originally, one failing mount point blocked the processing of the rest due to how the return codes were handled for every line in /proc/self/mountinfo. This patch removes this "dependency" and keeps the failure local to the affected mount point, allowing the rest to be processed normally. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10874 Fixed upstream with commit: https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3 [Original Description] netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1]
[Touch-packages] [Bug 1812760] Re: networkd: [Route] PreferredSource not working in *.network files
** Bug watch added: github.com/systemd/systemd/issues #5882 https://github.com/systemd/systemd/issues/5882 ** Also affects: systemd via https://github.com/systemd/systemd/issues/5882 Importance: Unknown Status: Unknown -- 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/1812760 Title: networkd: [Route] PreferredSource not working in *.network files Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the configuration of obscure network setups. The backport requires pulling in two further commits that also change behaviour: currently systemd deletes all addresses and routes that were attached to an interface. With this change, it will only delete those that are not specified in the configuration files. I do not know how this could cause issues - it moves from a surprising behaviour to a less surprising behaviour, but it's worth pointing out. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1812760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
This bug was fixed in the package upower - 0.99.9-3 --- upower (0.99.9-3) unstable; urgency=medium * d/p/daemon-Consider-pending-charge-when-calculating-the-displ.patch: - Detect AC state on pending state (LP: #1745032) -- Marco Trevisan (Treviño) Fri, 25 Jan 2019 11:35:14 + ** Changed in: upower (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 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 Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Status in gnome-control-center source package in Cosmic: In Progress Status in gnome-shell source package in Cosmic: In Progress Status in linux source package in Cosmic: New Status in upower source package in Cosmic: In Progress 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
Re: [Touch-packages] [Bug 1813052] Re: who returns no results
Oh, and to be clear, this is a regression.
On Wed, Jan 23, 2019, 11:15 AM Anthony Godshall Attempting to diagnose, I had added /var/run/utmp and /var/run/utmpx as
> directories. I just removed those, same empty result:
> # who
> # who;echo $?
> 0
> # strace who
> execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
> brk(NULL) = 0x1726000
> access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
> directory)
> access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
> directory)
> open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
> fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
> mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efc0bce
> close(3)= 0
> access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
> directory)
> open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
> read(3,
> "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 832) =
> 832
> fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7efc0bcdf000
> mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0)
> = 0x7efc0b70e000
> mprotect(0x7efc0b8ce000, 2097152, PROT_NONE) = 0
> mmap(0x7efc0bace000, 24576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7efc0bace000
> mmap(0x7efc0bad4000, 14752, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7efc0bad4000
> close(3)= 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7efc0bcde000
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7efc0bcdd000
> arch_prctl(ARCH_SET_FS, 0x7efc0bcde700) = 0
> mprotect(0x7efc0bace000, 16384, PROT_READ) = 0
> mprotect(0x60a000, 4096, PROT_READ) = 0
> mprotect(0x7efc0bcfd000, 4096, PROT_READ) = 0
> munmap(0x7efc0bce, 117369) = 0
> brk(NULL) = 0x1726000
> brk(0x1747000) = 0x1747000
> open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
> fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
> mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efc0b436000
> close(3)= 0
> access("/var/run/utmpx", F_OK) = -1 ENOENT (No such file or
> directory)
> open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
> directory)
> access("/var/run/utmpx", F_OK) = -1 ENOENT (No such file or
> directory)
> open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
> directory)
> close(1)= 0
> close(2)= 0
> exit_group(0) = ?
> +++ exited with 0 +++
> #
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1813052
>
> Title:
> who returns no results
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1813052/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1813052
Title:
who returns no results
Status in coreutils package in Ubuntu:
New
Bug description:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and
an strace on a system that works (an unupdated xenial or a bionic
system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eed000
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f225391c000
mprotect(0x7f2253adc000, 2097152, PROT_NONE) = 0
mmap(0x7f2253cdc000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f2253cdc000
mmap(0x7f2253ce2000, 14752, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f2253ce2000
close(3)= 0
mmap(NULL, 4096,
[Touch-packages] [Bug 1813353] [NEW] ctrl+g fails after ctrl+r and arrow up/down
Public bug reported: The usual way to find previous commands is ctrl+r and then use the arrow up/down keys. You can exit the search with ctrl+g. One day this stopped working (after an update of the package?). It still works when I don't touch the arrow keys, but when you do, the only way I know to get out is back-deleting the retrieved command. $ lsb_release -rd Description:Ubuntu 16.04.5 LTS $ bash --version GNU bash, version 4.3.48(1)-release (x86_64-pc-linux-gnu) $ apt-cache policy bash bash: Installed: 4.3-14ubuntu1.2 Candidate: 4.3-14ubuntu1.2 Version table: *** 4.3-14ubuntu1.2 500 500 mirror://mirrors.ubuntu.com/mirrors.txt xenial-updates/main amd64 Packages 500 mirror://mirrors.ubuntu.com/mirrors.txt xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 4.3-14ubuntu1 500 500 mirror://mirrors.ubuntu.com/mirrors.txt xenial/main amd64 Packages ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1813353 Title: ctrl+g fails after ctrl+r and arrow up/down Status in bash package in Ubuntu: New Bug description: The usual way to find previous commands is ctrl+r and then use the arrow up/down keys. You can exit the search with ctrl+g. One day this stopped working (after an update of the package?). It still works when I don't touch the arrow keys, but when you do, the only way I know to get out is back-deleting the retrieved command. $ lsb_release -rd Description:Ubuntu 16.04.5 LTS $ bash --version GNU bash, version 4.3.48(1)-release (x86_64-pc-linux-gnu) $ apt-cache policy bash bash: Installed: 4.3-14ubuntu1.2 Candidate: 4.3-14ubuntu1.2 Version table: *** 4.3-14ubuntu1.2 500 500 mirror://mirrors.ubuntu.com/mirrors.txt xenial-updates/main amd64 Packages 500 mirror://mirrors.ubuntu.com/mirrors.txt xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 4.3-14ubuntu1 500 500 mirror://mirrors.ubuntu.com/mirrors.txt xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1813353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110]
> Or do we have to compile it ourselves from this branch? There is prebuilt packages, if you need them: https://github.com/heikomat/linux/releases By the way, is UCM from Comment 68 is recent, or there is newer version somewhere? -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)
** This bug is no longer a duplicate of bug 857651 Unable to hide users from login screen / user switcher -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1667113 Title: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types) Status in accountsservice package in Ubuntu: Confirmed Status in base-passwd package in Ubuntu: Invalid Status in ceph package in Ubuntu: Won't Fix Status in ifmail package in Ubuntu: Won't Fix Status in libvirt package in Ubuntu: Won't Fix Status in lightdm package in Ubuntu: Confirmed Status in netqmail package in Ubuntu: Won't Fix Status in sddm package in Ubuntu: Fix Released Bug description: "Technical" user libvirt Qemu appears in the list of user in Ligthdm, among the real regular users. It probably shouldn't ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libvirt-bin 2.5.0-3ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Feb 22 22:09:24 2017 InstallationDate: Installed on 2017-02-01 (21 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201) KernLog: SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311951] Re: Save dialog New Folder Closes with Shift
The issue seems fixed in newer series, also the file selector is from gtk and not nautilus ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Invalid -- 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/1311951 Title: Save dialog New Folder Closes with Shift Status in gtk+3.0 package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Invalid Bug description: Steps to reproduce 1. Open an application you can save from (ex gedit, libreoffice writer) 2. Press Ctrl+S to save a document 3. Navigate to a directory (ex desktop) 4. Click "Create Folder" 5. Press shift and push any letter 6. Instead of typing a capital letter, it just cancels the New Folder operation Release: Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 21:47:42 2014 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2014-04-21 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1311951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311951] Re: Save dialog New Folder Closes with Shift
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- 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/1311951 Title: Save dialog New Folder Closes with Shift Status in gtk+3.0 package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Invalid Bug description: Steps to reproduce 1. Open an application you can save from (ex gedit, libreoffice writer) 2. Press Ctrl+S to save a document 3. Navigate to a directory (ex desktop) 4. Click "Create Folder" 5. Press shift and push any letter 6. Instead of typing a capital letter, it just cancels the New Folder operation Release: Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 21:47:42 2014 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2014-04-21 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1311951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
The issue is also present in cosmic. Wonder if someone might be kind enough to build a deb with the patch for cosmic too... Would be very much appreciated! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311951] [NEW] Save dialog New Folder Closes with Shift
You have been subscribed to a public bug: Steps to reproduce 1. Open an application you can save from (ex gedit, libreoffice writer) 2. Press Ctrl+S to save a document 3. Navigate to a directory (ex desktop) 4. Click "Create Folder" 5. Press shift and push any letter 6. Instead of typing a capital letter, it just cancels the New Folder operation Release: Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 21:47:42 2014 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2014-04-21 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: Fix Released ** Tags: amd64 apport-bug trusty -- Save dialog New Folder Closes with Shift https://bugs.launchpad.net/bugs/1311951 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1744536] Re: Zeitgeist homepage doesn't exist
This bug was fixed in the package zeitgeist - 1.0.1-1ubuntu1 --- zeitgeist (1.0.1-1ubuntu1) disco; urgency=medium * Resynchronize with Debian. Remaining changes: - Add add_datahub_autostart_delay.patch: Don't start for a little while - Add nodisplay_autostart.patch: Don't show in Startup Applications - Add pre_populator.patch: Pre-populate the log with some events so that the Unity dash isn't empty on first run. * Removed change, that's not useful nowadays - Add disable-fts-on-touch.patch: Drop redundant FTS/xapian indexer on Ubuntu Touch. -- Sebastien Bacher Fri, 25 Jan 2019 17:52:50 +0100 ** Changed in: zeitgeist (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1744536 Title: Zeitgeist homepage doesn't exist Status in zeitgeist package in Ubuntu: Fix Released Bug description: Zeitgeist package has a homepage address http://zeitgeist- project.com/. When I visit it, I get redirected to various shady advertising pages. As it looks like from the archive.org database, the true site ceased to exist between July 2016 and June 2017. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1744536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813339] [NEW] Apparmor is denying evince from running vivaldi
Public bug reported: It's similar to this bug https://bugs.launchpad.net/bugs/1432126 or discussed here; https://forum.vivaldi.net/topic/33591/vivaldi-opening- from-a-link-in-a-pdf-file/7 Apparmor is denying evince from running vivaldi by clicking on a http link kernel: [ 3271.799807] audit: type=1400 audit(1548434352.941:114): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=6795 comm="exo-helper-1" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Description:Ubuntu 18.04.1 LTS Release:18.04 vivaldi-stable: 2.2.1388.37-1 apparmor: 2.12-4ubuntu5.1 evince: 3.28.4-0ubuntu1 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor audit evince vivaldi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1813339 Title: Apparmor is denying evince from running vivaldi Status in apparmor package in Ubuntu: New Bug description: It's similar to this bug https://bugs.launchpad.net/bugs/1432126 or discussed here; https://forum.vivaldi.net/topic/33591/vivaldi-opening- from-a-link-in-a-pdf-file/7 Apparmor is denying evince from running vivaldi by clicking on a http link kernel: [ 3271.799807] audit: type=1400 audit(1548434352.941:114): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=6795 comm="exo-helper-1" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Description: Ubuntu 18.04.1 LTS Release: 18.04 vivaldi-stable: 2.2.1388.37-1 apparmor: 2.12-4ubuntu5.1 evince: 3.28.4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1813339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813334] [NEW] isc-dhcp-server & isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6
Public bug reported: Both isc-dhcp-server and isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 respectively which are declared in /etc/default/isc-dhcp-server It prevents the DHCP server to only operate on specific interfaces. isc-dhcp-server 4.3.5-3ubuntu7 Ubuntu 18.04 Bionic Beaver ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: Invalid ** Description changed: Both isc-dhcp-server and isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 respectively which are declared in /etc/default/isc-dhcp-server It prevents the DHCP server to only operate on specific interfaces. + + isc-dhcp-server 4.3.5-3ubuntu7 + Ubuntu 18.04 Bionic Beaver ** Changed in: isc-dhcp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1813334 Title: isc-dhcp-server & isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 Status in isc-dhcp package in Ubuntu: Invalid Bug description: Both isc-dhcp-server and isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 respectively which are declared in /etc/default/isc-dhcp-server It prevents the DHCP server to only operate on specific interfaces. isc-dhcp-server 4.3.5-3ubuntu7 Ubuntu 18.04 Bionic Beaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1813334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813334] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6
Please ignore, this is a duplicate of #1774342 which I missed when searching for previous reports -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1813334 Title: isc-dhcp-server & isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 Status in isc-dhcp package in Ubuntu: Invalid Bug description: Both isc-dhcp-server and isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 respectively which are declared in /etc/default/isc-dhcp-server It prevents the DHCP server to only operate on specific interfaces. isc-dhcp-server 4.3.5-3ubuntu7 Ubuntu 18.04 Bionic Beaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1813334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804864] Re: autopkgtest regression TEST-22-TMPFILES are not executable
This bug was supposed to be fixed on bionic with systemd (237-3ubuntu10.11) but it's still failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/amd64/s/systemd/20190118_154706_1d013@/log.gz == TEST-22-TMPFILES == make: Entering directory '/tmp/autopkgtest.wPokuU/build.7Yo/src/test/TEST-22-TMPFILES' /bin/sh: 1: ./test.sh: Permission denied make: *** [clean] Error 126 Makefile:4: recipe for target 'clean' failed make: Leaving directory '/tmp/autopkgtest.wPokuU/build.7Yo/src/test/TEST-22-TMPFILES' -- 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/1804864 Title: autopkgtest regression TEST-22-TMPFILES are not executable 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 Bug description: [Impact] * Newly added testcase in a security upload used a traditional GNU patch format, instead of using extended git patch format, as supported by GNU patch. Therefore, executable bits on shells scripts were lost, resulting in autopkgtest failures. [Test Case] * `upstream` test/TEST-22-TMPFILES autopkgtest case should pass. [Regression Potential] * This is testcode change only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451500] Re: Can't set any other program as default for *.m3u
The issue seems fixed in Ubuntu 18.10 ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released -- 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/1451500 Title: Can't set any other program as default for *.m3u Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Can't set any other program as default for *.m3u in Nautilus file details window. It is strange. See the screencast. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 4 20:12:13 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-11-04 (180 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1451500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
This bug was fixed in the package gnome-control-center - 1:3.30.2-4ubuntu1 --- gnome-control-center (1:3.30.2-4ubuntu1) disco; urgency=medium * Merge with debian unstable. Remaining changes: + debian/control.in: - Depend on language-selector-gnome and whoopsie-preferences - Depend on instead of Recommend system-config-printer - Recommend ibus and ubuntu-system-service - Suggest instead of Recommend gnome-user-share, realmd and rygel - Build-Depend on dh-migrations and libwhoopsie-preferences-dev - Don't recommend libnss-myhostname since systemd-resolved handles this functionality - Bump dep on g-s-d and schema + Split gnome-control-center-faces to a separate package so that it can be used by unity-control-center & recommend this + Install apport hook + debian/gnome-control-center-data.install: - Don't install gnome-control-center.pkla since we use policykit-desktop-privileges instead - Install additional assets used by unity-control-center + debian/ubuntu-logo-icon.png, debian/source/include-binaries, debian/gnome-control-center-data.install: Include an Ubuntu logo + debian/gnome-control-center-data.links: - Link audio-speaker-center* to audio-speaker-mono* so that an icon is shown in the test speaker panel. + debian/rules: Enable whoospie integration + Add migration script to transition from old user settings to new one. + debian/patches: - 52_region_language.patch: Adapt region panel to use Ubuntu style regions - 64_restore_terminal_keyboard_shortcut.patch Bring back terminal shortcut - 70_allow_sound_above_100.patch: Allow setting volume above 100% in the Ubuntu session - 71_ubuntu_dock_settings.patch Add Dock panel for Ubuntu session - 99_add_lock-on-suspend.patch Add option to lock on suspend - auto_quit_after_goa_add.patch Hide window after adding an online account from another app. - connectivity-switch.patch Add Connectivity Checking switch to Privacy panel - distro-logo.patch: Add Ubuntu branding to Details panel - privacy-panel-whoopsie.patch Support Ubuntu's whoopsie service in the Privacy panel - ubuntu-language-support.patch Add Language Support button to Region & Language panel to work around - ubuntu-legacy-notifications.patch Ubuntu ships compatibility names for .desktop that got renamed upstream, those use NoDisplay but the panel doesn't respect that key, skip known buggy entries for file-roller and nautilus - ubuntu-printer-support.patch Add Advanced Printer Settings button to work around missing printer sharing feature - ubuntu-region-langpack-install.patch: Check for missing language packs when loading region panel to pull in packs that aren't included with the installer - ubuntu-region-packagekit.patch Fix detection of installed language packs gnome-control-center (1:3.30.2-4) unstable; urgency=medium * debian/patches/power-Label-the-PENDING_CHARGING-state-as-Not-Charging.patch: - Label the PENDING_CHARGING state as "Not Charging" (LP: #1745032) -- Iain Lane Fri, 25 Jan 2019 14:02:27 + -- 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 Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Status in gnome-control-center source package in Cosmic: In Progress Status in gnome-shell source package in Cosmic: In Progress Status in linux source package in Cosmic: New Status in upower source package in Cosmic: In Progress 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
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
This bug was fixed in the package gnome-shell - 3.30.2-2ubuntu1 --- gnome-shell (3.30.2-2ubuntu1) disco; urgency=medium * Merge with debian, remaining changes: + Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds + Add some Recommends: - ubuntu-session (| gnome-session) to have the ubuntu session available - xserver-xorg-legacy - yaru-theme-gnome-shell for the default ubuntu theming + Update debian/gbp.conf with Ubuntu settings + gnome-shell-common.install: Install Ubuntu mode + gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative + ubuntu/desktop_detect.patch: - add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. + ubuntu/smarter_alt_tab.patch: - quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. + ubuntu/lightdm-user-switching.patch: - Allow user switching when using LightDM. + ubuntu/lock_on_suspend.patch - Respect Ubuntu's lock-on-suspend setting. + ubuntu/gdm.patch - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. + ubuntu/background_login.patch - Change default background color as we modified the default GDM color for our ubuntu session. Change it as well here, still applying the background noise loading. + ubuntu/gdm_alternatives.patch - Add support for GDM3 theme alternatives + ubuntu/block_mode_extension_update.patch - Don't allow ubuntu mode extension to update + optional-hot-corner.patch - enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. + volume-Add-back-sound-feedback-on-scroll.patch - Fix regression causing missing feedback on volume slider scroll + st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch - Fix possible crash on cache loading + main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: - Improve debug JS tracing for crash reports + st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Fix crash on theme changes + ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: - stop searches when requested from UI + keyboard-Do-not-call-KeyboardManager.holdKeyboard-with-se.patch: - Cherry-pick upstream commit to prevent focus stealing on password fields in firefox when ibus is used + debian/patches/ubuntu/background_login.patch: - match Yaru theme in the ubuntu session instead of our previous GDM background + debian/patches/ubuntu/resolve_alternate_theme_path.patch: - ensure we resolve finale theme file path to correctly load assets under gdm + debian/patches/st-button-Ignore-pointer-emulated-touch-events.patch: - Don't emit two click events on touch under X11 + debian/rules: - Run dh_translations and work around an issue with Rosetta and plural translations + Add desktop-icons to the Ubuntu session by default + Break nautilus << 3.30. We don't want two things trying to handle the desktop. gnome-shell (3.30.2-2) unstable; urgency=medium * d/p/power-Label-the-PENDING_CHARGE-state-as-Not-Charging.patch: - Label the PENDING_CHARGE state as "Not Charging" (LP: #1745032) * d/p/ibusManager-Don-t-pass-undefined-callback-to-ibus.patch: - Fix missing icon in keyboard indicator (LP: #1812266) -- Iain Lane Fri, 25 Jan 2019 13:24:52 + ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released ** Changed in: gnome-control-center (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 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 Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Also affects: gnome-control-center (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: upower (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu Cosmic) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu Cosmic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu Cosmic) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Cosmic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: upower (Ubuntu Cosmic) Status: New => In Progress ** Changed in: upower (Ubuntu Cosmic) 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: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Status in gnome-control-center source package in Cosmic: In Progress Status in gnome-shell source package in Cosmic: In Progress Status in linux source package in Cosmic: New Status in upower source package in Cosmic: In Progress 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] [Bug 1800055] Re: iwd does not work with network manager
Confirmed, that's still an issue but it works with the newest n-m version (which is currently being packaged/available for testing in the desktop team ppa) ** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Committed -- 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/1800055 Title: iwd does not work with network manager Status in network-manager package in Ubuntu: Fix Committed Bug description: I configured network manager to use iwd, unfortunately it doesn't work: Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.4358] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_type: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_get_string: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.7492] device (wlp4s0): new IWD device state is (null) Oct 25 15:12:23 malefic NetworkManager[17004]: [1540501943.7492] device (wlp4s0): State (null) unknown Oct 25 15:12:23 malefic NetworkManager[17004]: g_variant_unref: assertion 'value != NULL' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed Oct 25 15:12:23 malefic NetworkManager[17004]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789022] Re: libcaca0 still depends on old libncursesw5 and libtinfo5
The bug was fixed with the 0.99.beta19-2ubuntu2 update. ** Changed in: libcaca (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1789022 Title: libcaca0 still depends on old libncursesw5 and libtinfo5 Status in libcaca package in Ubuntu: Fix Committed Bug description: Ubuntu Cosmic switched some time ago from ncurses5 to ncurses6. However, the package libcaca0 still depends on old libncursesw5 and libtinfo5 instead of libncursesw6 and libtinfo6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcaca/+bug/1789022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806272] Re: resize2fs results in ext4 filesystem with warning/errors
*** This bug is a duplicate of bug 1798562 *** https://bugs.launchpad.net/bugs/1798562 This bug is marked as duplicate of bug #1798562. This is only partly correct. The "warning" about "extent tree (at level 1) could be narrower. Fix?" is not solved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1806272 Title: resize2fs results in ext4 filesystem with warning/errors Status in e2fsprogs package in Ubuntu: New Bug description: Resized (downsized) an offline ext4 filesystem on LVM. Before resizing, I confirmed filesystem was clean with e2fsck. After resizing, several warnings/errors were found. Tried first with version 1.44.1 from Ubuntu 18.04.1 LTS. Then I compiled the 1.44.4 source, but the error was still present. Using ESXi 6.7 and starts with a fresh copy of the filesystem before each run. root@vedlikehold:~# e2fsck -f /dev/skole-vg/root e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/skole-vg/root: 139206/8331264 files (0.2% non-contiguous), 3274416/33294336 blocks root@vedlikehold:~# resize2fs -P /dev/skole-vg/root resize2fs 1.44.4 (18-Aug-2018) Estimated minimum size of the filesystem: 3337578 root@vedlikehold:~# lvresize --resizefs -l 11776 /dev/skole-vg/root fsck from util-linux 2.31.1 /dev/mapper/skole--vg-root: clean, 139206/8331264 files, 3274416/33294336 blocks resize2fs 1.44.4 (18-Aug-2018) Resizing the filesystem on /dev/mapper/skole--vg-root to 12058624 (4k) blocks. The filesystem on /dev/mapper/skole--vg-root is now 12058624 (4k) blocks long. Size of logical volume skole-vg/root changed from <127.01 GiB (32514 extents) to 46.00 GiB (11776 extents). Logical volume skole-vg/root successfully resized. root@vedlikehold:~# e2fsck -f /dev/skole-vg/root e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Inode 8 extent tree (at level 1) could be narrower. Fix? yes Inode 44075 extent block passes checks, but checksum does not match extent (logical block 10240, physical block 421888, len 8691) Fix? yes Inode 44083 extent block passes checks, but checksum does not match extent (logical block 51200, physical block 3414016, len 10293) Fix? yes Inode 44087 extent block passes checks, but checksum does not match extent (logical block 34816, physical block 3444736, len 574) Fix? yes Inode 44091 extent block passes checks, but checksum does not match extent (logical block 28672, physical block 4087808, len 7804) Fix? yes Inode 44093 extent block passes checks, but checksum does not match extent (logical block 26624, physical block 4030464, len 351) Fix? yes Inode 44106 extent block passes checks, but checksum does not match extent (logical block 49152, physical block 1308672, len 8370) Fix? yes Inode 44112 extent block passes checks, but checksum does not match extent (logical block 69632, physical block 1607680, len 16969) Fix? yes Inode 44116 extent block passes checks, but checksum does not match extent (logical block 2848, physical block 7861156, len 178) Fix? yes Inode 44117 extent block passes checks, but checksum does not match extent (logical block 1592, physical block 7862368, len 98) Fix? yes Inode 44119 extent block passes checks, but checksum does not match extent (logical block 2150, physical block 15663, len 134) Fix? yes Inode 44120 extent block passes checks, but checksum does not match extent (logical block 24934, physical block 5329460, len 1014) Fix? yes Inode 44122 extent block passes checks, but checksum does not match extent (logical block 734, physical block 3257320, len 44) Fix? yes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/skole-vg/root: 139206/3014656 files (0.2% non-contiguous), 2938632/12058624 blocks root@vedlikehold:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1806272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813314] [NEW] [2537G98, Conexant CX20585, Speaker, Internal] Background noise or low volume. Low volume quality than on windows 10.
Public bug reported: When I increase the volume indicator to 1.0 (probably in the gnome desktop it is 100%) the sound is lower quality than in windows 10. Please. Repair it. Lenovo thinkpad t410, conexant cx 20585 soundcard, processor intel core i5 520M, (2.40GHZ, 2 cores 4 threats.) Ram 4GB. If it does matter, I use orca screenreader. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bogus 1794 F pulseaudio /dev/snd/pcmC0D0p: bogus 1794 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 25 15:55:07 2019 InstallationDate: Installed on 2019-01-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Wbudowany dźwięk - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_Type: High background noise, or volume is too low Title: [2537G98, Conexant CX20585, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2537G98 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2537G98:pvrThinkPadT410:rvnLENOVO:rn2537G98:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2537G98 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-25T15:02:33.273945 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1813314 Title: [2537G98, Conexant CX20585, Speaker, Internal] Background noise or low volume. Low volume quality than on windows 10. Status in alsa-driver package in Ubuntu: New Bug description: When I increase the volume indicator to 1.0 (probably in the gnome desktop it is 100%) the sound is lower quality than in windows 10. Please. Repair it. Lenovo thinkpad t410, conexant cx 20585 soundcard, processor intel core i5 520M, (2.40GHZ, 2 cores 4 threats.) Ram 4GB. If it does matter, I use orca screenreader. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bogus 1794 F pulseaudio /dev/snd/pcmC0D0p: bogus 1794 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 25 15:55:07 2019 InstallationDate: Installed on 2019-01-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Wbudowany dźwięk - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_Type: High background noise, or volume is too low Title: [2537G98, Conexant CX20585, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2537G98 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2537G98:pvrThinkPadT410:rvnLENOVO:rn2537G98:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2537G98 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-25T15:02:33.273945 To manage notifications about this bug go to:
[Touch-packages] [Bug 1798562] Re: After a side by side installation, resized filesystem is corrupted
** Also affects: e2fsprogs (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: e2fsprogs (Ubuntu Cosmic) Importance: Undecided Status: New ** Description changed: + [Impact] + - Users resizing filesystems using resize2fs. + - Resizing an existing Linux filesystem from the Ubuntu installer. + + [Test cases] + Test Case 1: With e2fsprogs 1.44.4-2: Download this file system image: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz Run the following commands: bunzip2 vda1b.qcow2.bz qemu-img convert vda1b.qcow2 vda1b.raw e2fsck -f vda1b.raw resize2fs vda1b.raw 6200M e2fsck -f vda1b.raw e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Inode 45746 extent block passes checks, but checksum does not match extent - (logical block 1272, physical block 466167, len 776) + (logical block 1272, physical block 466167, len 776) Fix? - Test Case 2 (Use case of the installer): 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... + + + [Regression potential] + This changes behavior in the update logic for extent blocks; as such, care should be taken to make sure that testing takes into account the possibility to introduce filesystem corruption while resizing. This is why the test cases include running e2fsck as last step. + + + --- Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 10:53:57 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2018-10-18 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1798562 Title: After a side by side installation, resized filesystem is corrupted Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Bionic: New Status in e2fsprogs source package in Cosmic: New Bug description: [Impact] - Users resizing filesystems using resize2fs. - Resizing an existing Linux filesystem from the Ubuntu installer. [Test cases] Test Case 1: With e2fsprogs 1.44.4-2: Download this file system image: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz Run the following commands: bunzip2 vda1b.qcow2.bz qemu-img convert vda1b.qcow2 vda1b.raw e2fsck -f vda1b.raw resize2fs vda1b.raw 6200M e2fsck -f vda1b.raw e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Inode 45746 extent block passes checks, but checksum does not match extent (logical block 1272, physical block 466167, len 776) Fix? Test Case 2 (Use case of the installer): 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... [Regression potential] This changes behavior in the update logic for extent blocks; as such, care should be taken to make sure that testing takes into account the possibility to introduce filesystem corruption while resizing. This is why the test cases include running e2fsck as last step. --- Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic
[Touch-packages] [Bug 1806272] Re: resize2fs results in ext4 filesystem with warning/errors
*** This bug is a duplicate of bug 1798562 *** https://bugs.launchpad.net/bugs/1798562 ** This bug has been marked a duplicate of bug 1798562 After a side by side installation, resized filesystem is corrupted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1806272 Title: resize2fs results in ext4 filesystem with warning/errors Status in e2fsprogs package in Ubuntu: New Bug description: Resized (downsized) an offline ext4 filesystem on LVM. Before resizing, I confirmed filesystem was clean with e2fsck. After resizing, several warnings/errors were found. Tried first with version 1.44.1 from Ubuntu 18.04.1 LTS. Then I compiled the 1.44.4 source, but the error was still present. Using ESXi 6.7 and starts with a fresh copy of the filesystem before each run. root@vedlikehold:~# e2fsck -f /dev/skole-vg/root e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/skole-vg/root: 139206/8331264 files (0.2% non-contiguous), 3274416/33294336 blocks root@vedlikehold:~# resize2fs -P /dev/skole-vg/root resize2fs 1.44.4 (18-Aug-2018) Estimated minimum size of the filesystem: 3337578 root@vedlikehold:~# lvresize --resizefs -l 11776 /dev/skole-vg/root fsck from util-linux 2.31.1 /dev/mapper/skole--vg-root: clean, 139206/8331264 files, 3274416/33294336 blocks resize2fs 1.44.4 (18-Aug-2018) Resizing the filesystem on /dev/mapper/skole--vg-root to 12058624 (4k) blocks. The filesystem on /dev/mapper/skole--vg-root is now 12058624 (4k) blocks long. Size of logical volume skole-vg/root changed from <127.01 GiB (32514 extents) to 46.00 GiB (11776 extents). Logical volume skole-vg/root successfully resized. root@vedlikehold:~# e2fsck -f /dev/skole-vg/root e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Inode 8 extent tree (at level 1) could be narrower. Fix? yes Inode 44075 extent block passes checks, but checksum does not match extent (logical block 10240, physical block 421888, len 8691) Fix? yes Inode 44083 extent block passes checks, but checksum does not match extent (logical block 51200, physical block 3414016, len 10293) Fix? yes Inode 44087 extent block passes checks, but checksum does not match extent (logical block 34816, physical block 3444736, len 574) Fix? yes Inode 44091 extent block passes checks, but checksum does not match extent (logical block 28672, physical block 4087808, len 7804) Fix? yes Inode 44093 extent block passes checks, but checksum does not match extent (logical block 26624, physical block 4030464, len 351) Fix? yes Inode 44106 extent block passes checks, but checksum does not match extent (logical block 49152, physical block 1308672, len 8370) Fix? yes Inode 44112 extent block passes checks, but checksum does not match extent (logical block 69632, physical block 1607680, len 16969) Fix? yes Inode 44116 extent block passes checks, but checksum does not match extent (logical block 2848, physical block 7861156, len 178) Fix? yes Inode 44117 extent block passes checks, but checksum does not match extent (logical block 1592, physical block 7862368, len 98) Fix? yes Inode 44119 extent block passes checks, but checksum does not match extent (logical block 2150, physical block 15663, len 134) Fix? yes Inode 44120 extent block passes checks, but checksum does not match extent (logical block 24934, physical block 5329460, len 1014) Fix? yes Inode 44122 extent block passes checks, but checksum does not match extent (logical block 734, physical block 3257320, len 44) Fix? yes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/skole-vg/root: 139206/3014656 files (0.2% non-contiguous), 2938632/12058624 blocks root@vedlikehold:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1806272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325525] Re: Missing 53-monospace-lcd-filter.conf from /etc/fonts/conf.d
The warning was fixed with https://launchpad.net/ubuntu/+source/fontconfig/2.13.0-5ubuntu3 ** Changed in: fontconfig (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1325525 Title: Missing 53-monospace-lcd-filter.conf from /etc/fonts/conf.d Status in fontconfig package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu-trusty, and noticed that in Thunderbird the fonts are rendered incorrectly. It seemed that the problem is with sub-pixel rendering. After much googling and finding nothing I've started to compare the /etc/fonts/conf.d dir on my Precise machin with the trusty one. I noticed that on trusty the 53-monospace-lcd-filter.conf file is missing from the conf.d dir, but is available in the conf.avail. After I created the symlink and rebooted, my thunderbird font rendering became normal again. But now if I start from something from the terminal it says: "Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 10: Having multiple values in isn't supported and may not work as expected" So the 1st question, why did you leave out the monospace-lcd- filter.conf from the fontconfig conf.d, and the second is why didn't you update it so it won't complaing about the multiple test tags. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 2 12:43:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:308c] MachineType: LENOVO 3492C4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=a1bd4186-b465-4605-845f-12c9de2dc180 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: LENOVO dmi.bios.version: F1KT44AUS dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrF1KT44AUS:bd12/21/2012:svnLENOVO:pn3492C4G:pvrThinkCentreEdge72:rvnLENOVO:rn:rvrNODPK:cvnLENOVO:ct3:cvr: dmi.product.name: 3492C4G dmi.product.version: ThinkCentre Edge72 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jun 2 12:37:17 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16498 vendor DEL xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768117] Re: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1759096 *** https://bugs.launchpad.net/bugs/1759096 ** This bug has been marked a duplicate of bug 1759096 package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1768117 Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: Confirmed Bug description: error came up during distro upgrade from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.12.6-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon Apr 30 22:06:01 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-01-23 (96 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: fontconfig Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1768117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780616] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1759096 *** https://bugs.launchpad.net/bugs/1759096 ** This bug has been marked a duplicate of bug 1759096 package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1780616 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: Confirmed Bug description: Upgrading from 16.04 to 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jul 8 05:09:36 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-01-23 (531 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.2.27 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-07-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1780616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780618] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1759096 *** https://bugs.launchpad.net/bugs/1759096 ** This bug is no longer a duplicate of bug 1780616 package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned ** This bug has been marked a duplicate of bug 1759096 package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1780618 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: Upgrading from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jul 8 05:09:36 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-01-23 (531 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.2.27 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-07-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1780618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789764] Re: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1759096 *** https://bugs.launchpad.net/bugs/1759096 ** This bug has been marked a duplicate of bug 1759096 package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1789764 Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: Confirmed Bug description: Upgrade to 18.04 error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.12.6-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 Uname: Linux 4.15.0-33-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Aug 30 02:42:47 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-24 (127 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: fontconfig Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-08-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1789764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768111] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1759096 *** https://bugs.launchpad.net/bugs/1759096 ** This bug is no longer a duplicate of bug 1768117 package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned ** This bug has been marked a duplicate of bug 1759096 package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1768111 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: no idea just posting it ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon Apr 30 14:39:35 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-27 (2 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.2.26 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1768111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772358] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1759096 *** https://bugs.launchpad.net/bugs/1759096 ** This bug has been marked a duplicate of bug 1759096 package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1772358 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: Error Attached ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Thu May 17 12:13:12 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-05-03 (17 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1772358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790948] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1759096 *** https://bugs.launchpad.net/bugs/1759096 ** This bug has been marked a duplicate of bug 1759096 package fontconfig 2.11.94-0ubuntu2 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1790948 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: Confirmed Bug description: The problem appeared during upgrading from 16.04 to 18.04 Similar problems were reported, but for upgrade 14.04 to 16.04, so I decided to open a new bug. The upgrade left the system in a broken state: root@storage:~# apt update Hit:1 http://ro.archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://ro.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://ro.archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done 2446 packages can be upgraded. Run 'apt list --upgradable' to see them. root@storage:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: audacious : Depends: libaudcore5 (= 3.9-2) but it is not installed audacious-plugins : Depends: audacious-plugins-data (= 3.9-1build2) but 3.6.2-2ubuntu1 is installed Depends: libaudcore5 (>= 3.9) but it is not installed Depends: libaudgui5 (>= 3.9) but it is not installed Depends: libaudtag3 (>= 3.8) but it is not installed Depends: libfluidsynth1 (>= 1.1.6-4~) but 1.1.6-3 is installed bogofilter-bdb : Depends: libgsl2 but it is not installable checkbox-converged : Depends: qtdeclarative5-ubuntu-ui-toolkit-plugin but it is not installable debconf : Breaks: update-notifier-common (< 3.187~) but 3.168.9 is installed gnupg : Breaks: software-properties-common (<= 0.96.24.3) but 0.96.20.7 is installed kdeconnect-plasma : Depends: plasma-workspace but it is not installed libavogadro1 : Depends: libglew2.0 (>= 1.12.0) but it is not installed libguvcview-1.1-1 : Depends: libgsl2 but it is not installable liboxideqtquick0 : Depends: liboxideqtcore0 (= 1.21.5-0ubuntu0.16.04.1) but it is not installable libunity-webapps0 : Depends: unity-webapps-service but it is not installable mplayer : Depends: libdirectfb-1.7-7 (>= 1.7.7) but it is not installed phonon4qt5-backend-gstreamer : Depends: phonon-backend-gstreamer-common (= 4:4.9.0-1) but 4:4.8.2-0ubuntu2 is installed software-properties-kde : Depends: python3-pyqt5 but it is not installed unity-control-center-signon : Depends: unity-control-center but it is not installed unity-webapps-qml : Depends: qtdeclarative5-ubuntu-ui-toolkit-plugin but it is not installable or qtdeclarative5-ubuntu-ui-toolkit-plugin-gles but it is not installable update-notifier : Depends: update-notifier-common (= 3.192.1.3) but 3.168.9 is installed xaos : Depends: libgsl2 but it is not installable xorg : Depends: xserver-xorg (>= 1:7.7+19ubuntu7.1) but 1:7.7+13ubuntu3.1 is installed E: Unmet dependencies. Try using -f. Details: 1) Description:Ubuntu 18.04.1 LTS Release:18.04 2) fontconfig: Installed: 2.11.94-0ubuntu1.1 Candidate: 2.12.6-0ubuntu2 Version table: 2.12.6-0ubuntu2 500 500 http://ro.archive.ubuntu.com/ubuntu bionic/main amd64 Packages *** 2.11.94-0ubuntu1.1 100 100 /var/lib/dpkg/status 3) I expected a successful upgrade from 16.04 to 18.04 4) Now I have a broken system :) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Sep 5 22:11:25 2018 ErrorMessage: triggers looping, abandoned RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.2.27 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-09-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1790948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1451500] Re: Can't set any other program as default for *.m3u
** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1451500 Title: Can't set any other program as default for *.m3u Status in gtk+3.0 package in Ubuntu: New Bug description: Can't set any other program as default for *.m3u in Nautilus file details window. It is strange. See the screencast. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 4 20:12:13 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-11-04 (180 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1451500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408624] Re: Improve application management for file opening
The widget comes from gtk, also it should really be reported upstream ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1408624 Title: Improve application management for file opening Status in gtk+3.0 package in Ubuntu: New Bug description: I'd be nice to have the following possibilities when dealing the the list of applications which can open a file: * Remove entries for the list of applications (I know that can be done somehow by editing files in `~/.local/share/applications`) * Add entries with custom commands, e.g. allow opening of .jnlp files with `javaws` (this usecase is currently not covered) * Add a quick search text field in order to filter entries in the list of available applications in order to improve the overview ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu15 Uname: Linux 3.17.7-031707-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 8 12:37:58 2015 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-01-03 (5 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1408624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451500] [NEW] Can't set any other program as default for *.m3u
You have been subscribed to a public bug: Can't set any other program as default for *.m3u in Nautilus file details window. It is strange. See the screencast. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 4 20:12:13 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-11-04 (180 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug vivid -- Can't set any other program as default for *.m3u https://bugs.launchpad.net/bugs/1451500 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408624] [NEW] Improve application management for file opening
You have been subscribed to a public bug: I'd be nice to have the following possibilities when dealing the the list of applications which can open a file: * Remove entries for the list of applications (I know that can be done somehow by editing files in `~/.local/share/applications`) * Add entries with custom commands, e.g. allow opening of .jnlp files with `javaws` (this usecase is currently not covered) * Add a quick search text field in order to filter entries in the list of available applications in order to improve the overview ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu15 Uname: Linux 3.17.7-031707-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 8 12:37:58 2015 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-01-03 (5 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug third-party-packages utopic -- Improve application management for file opening https://bugs.launchpad.net/bugs/1408624 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596723] Re: logger(1) continuously outputs same timestamp
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- 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/1596723 Title: logger(1) continuously outputs same timestamp Status in util-linux package in Ubuntu: Confirmed Bug description: As per the issue created on syslog-ng's GitHub repository: https://github.com/balabit/syslog-ng/issues/1098 When content is piped to `logger`, every message gets the timestamp of when the logger process started. This is a regression between 14.04 and 16.04. Previously, logger would report an individual timestamp per message. A workaround is to let syslog create the timestamp rather than logger. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1596723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812271] Re: Ubuntu 18.04.1, "Bad packet length nnnn."
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since this appears to be a kernel issue I'm marking the openssh task as Invalid for now. If there's any reason to think it's a problem in userspace, please change its status back to New. ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: Invalid Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package:
[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU
>From the above comments I think it's clear that the problem is caused by
some kind of misconfiguration resulting in a loop. It isn't clear if
that misconfiguration is coming from a user error or from some bug in an
upgrade path somewhere. If the latter, then it's a valid bug. However,
since we don't have steps to reproduce the problem, I'm marking this bug
as Incomplete in dnsmasq, to make it clear that developers aren't
expected to be able to make any progress on this problem until someone
can provide steps to reproduce.
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => Incomplete
** Description changed:
+ [Triage Notes]
+ "Incomplete" in dnsmasq: may be a valid bug, but developers cannot make
progress until someone can provide steps to reproduce. See comment 55.
+
+ [Original Description]
Sometimes systemd-resolved process is using 100% CPU.
After a while it changes back to normal.
It happens usually after connecting to the (wifi) network, like starting
the OS.
strace output:
sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}],
msg_flags=0}, 0) = 81
sendmsg(3, {msg_name(0)=NULL,
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}},
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0)
= 53
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\365I", 2, GRND_NONBLOCK)= 2
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\203;", 2, GRND_NONBLOCK)= 2
clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
connect(18, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576,
u64=94565471566608}}) = 0
write(18,
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
53) = 53
clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0
close(18) = 0
journalctl output:
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS
queries reached (max: 150)
As you can see, I would use it together with dnsmasq.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-18ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Wed Mar 8 08:20:18 2017
MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic
[Touch-packages] [Bug 1813268] Re: connection issues with Kopano IMAP servers
Thanks, setting as fix commited but technically it's fixed in disco and a request for a SRU, it would be a good idea to udpate to the current 3.30 version in cosmic indeed ** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Committed ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: Fix Committed Bug description: 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive
Upstream requested some informations ** Changed in: evolution-data-server (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1812474 Title: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive Status in evolution-data-server package in Ubuntu: Incomplete Bug description: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760910] Re: Gdebi crash in Ubuntu Studio 18.04
SUP, there is any information, how soon this bug will be fixed? it's strange when u want install deb package from GUI but u NEED to open a terminal and start gdebi-gtk from CONSOLE to make it work properly with GUI. =/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1760910 Title: Gdebi crash in Ubuntu Studio 18.04 Status in gdebi package in Ubuntu: Confirmed Bug description: Gdebi opens normal, but when you click install package, it closes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi 0.9.5.7+nmu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10 Uname: Linux 4.15.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Apr 3 12:31:17 2018 InstallationDate: Installed on 2018-03-29 (4 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180328) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1760910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812247] Re: ssh-agent fails for ssh-add -c: agent refused operation
Hi, I tried the same on Bionic/Cosmic/Disco (a VM each running the same commands) 1. created an ssh key (ssh-keygen) 2. added it to authorized key (cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys) 3. added it with ssh-add (ssh-add) 4. verified it was added (ssh-add -l) 5. logged to local IP via ssh using the key (ssh ubuntu@127.0.0.1 uname -a) (working) 6. removed the key (ssh-add -d) 7. added the key in confirm mode (ssh-add -c) 8. logged to local IP via ssh using the key (ssh ubuntu@127.0.0.1 uname -a) Got the confirmation prompt I only got the "sign_and_send_pubkey: signing failed: agent refused operation" if in the prompt that asked me if I should use the key I hit "cancel". That seems reasonable thou. Is the following sequence failing for you? If so would you report the full output for that sequence of commands that you get? Note: I used a clean VM with ssh -XY to allow the popup to come through to my host. sudo apt-get install ssh-askpass-gnome eval `ssh-agent -s` ssh-keygen cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys ssh-add ssh-add -l ssh ubuntu@127.0.0.1 uname -a ssh-add -d ssh-add -c ssh-add -l ssh ubuntu@127.0.0.1 uname -a # pupup should appear -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1812247 Title: ssh-agent fails for ssh-add -c: agent refused operation Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813268] [NEW] connection issues with Kopano IMAP servers
Public bug reported: 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: New Bug description: 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813266] [NEW] udhcpd: not dying on SIGTERM
Public bug reported: udhcpd in bionic does not stop on SIGTERM due to an upstream change. This was corrected by the following patch: https://git.busybox.net/busybox/commit/?id=3293bc146985c56790033409facc0ad64a471084 Please apply and backport/SRU this change to bionic. ** Affects: busybox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1813266 Title: udhcpd: not dying on SIGTERM Status in busybox package in Ubuntu: New Bug description: udhcpd in bionic does not stop on SIGTERM due to an upstream change. This was corrected by the following patch: https://git.busybox.net/busybox/commit/?id=3293bc146985c56790033409facc0ad64a471084 Please apply and backport/SRU this change to bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1813266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)
** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1799111 Title: lots of Classes missing from docs (e.g. QFileInfo) Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qttools-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Cosmic: Confirmed Status in qtdeclarative-opensource-src source package in Cosmic: Confirmed Status in qttools-opensource-src source package in Cosmic: Confirmed Status in qtbase-opensource-src package in Debian: Fix Released Bug description: [Impact] The packaged Qt documentation, which can be viewed in browser (qt*-doc-html packages) or in Qt Assistant (qt*-doc packages) is missing all documentation generated from C++ files. Only the static text is present. Qt is split by many modules (qtbase, qtdeclarative, qtwebengine, etc.). To properly fix this bug, we need changes in qtbase and qttools modules. In addition, I will be uploading a no-change rebuild of qtdeclarative module to demonstrate that the fixes work. If requested, I can also upload no-change rebuilds of some other modules to get their -doc packages properly regenerated. [Test Case] For qtbase5-doc-html: 1. Install qtbase5-doc-html package. 2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present. For qtdeclarative5-doc-html: 1. Install qtdeclarative5-doc-html package. 2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present. [Regression Potential] The proposed change in qtbase is affecting only builds of Qt modules documentation. So the worst thing it can do is breaking the build of -doc packages in other Qt modules. However, as confirmed by qtdeclarative example, it makes things only better, not worse. The proposed change in qttools can affect more packages. It can result in qdoc passing more -isystem flags to clang code analyzer. I am not aware of negative consequences of this, but if they happen, these consequences will be limited to potential build failures or wrong documentation contents. [Other Info] Description of the fix: qdoc is a tool that parses C++ source files and generates documentation from them. Recently, qdoc began using clang instead of its own C++ parser. Clang needs the C++ standard library to work. Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard library is no longer on clang’s default search paths, so we need to pass it explicitly as -I flag. The proposed qtbase patch (qdoc_default_incdirs.diff) does that. That patch fixes documentation build for qtbase, but for other modules there is another problem. The Qt headers are installed into /usr/include//qt5 directory, but it is also not on Clang default search path. qmake passes these directories as -isystem flags, but qdoc ignores -isystem by default, unless it is built with QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is building with this define. [Original Description] The Qt offline documentation for cosmic is incomplete. In fact there's virtually no content what so ever. It would be easier I think to list what actually got picked up that what was missed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1799111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
since the same versions are in cosmic I'm marking it verified ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789022] Re: libcaca0 still depends on old libncursesw5 and libtinfo5
The version 0.99.beta19-2ubuntu1 does not take this into account. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1789022 Title: libcaca0 still depends on old libncursesw5 and libtinfo5 Status in libcaca package in Ubuntu: New Bug description: Ubuntu Cosmic switched some time ago from ncurses5 to ncurses6. However, the package libcaca0 still depends on old libncursesw5 and libtinfo5 instead of libncursesw6 and libtinfo6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcaca/+bug/1789022/+subscriptions -- Mailing list: https://launchpad.net/~touch-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_2.33.1-0.1ubuntu1 will not install - unmet dependendies
The newest shadow (1:4.5-1.1ubuntu1) makes the package util-linux (2.33.1-0.1ubuntu1) installable. ** Changed in: util-linux (Ubuntu) Status: Invalid => Fix Released -- 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_2.33.1-0.1ubuntu1 will not install - unmet dependendies Status in util-linux package in Ubuntu: Fix Released 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
