[Touch-packages] [Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session
I purged both xfce4-screensaver and light-locker packages, restarted lightdm and tested with x-p-m set to suspend on lid-close for battery (and AC as I've had the battery exhaust several times due to the length of these tests!) In this case there is no password challenge dialog on resume. It failed on 1st suspend-resume cycle. GUI TTY blanked, but console TTYs are fine. I was thinking back to the tests I did when this first hit 18.04 (when I reported this bug originally) and seem to recall that adding debug logging was enough to prevent the failure and led me to hypothesise this is a race condition. I'm going to try booting the systems with maxcpus= 1 and 0. -- 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/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Confirmed Status in light-locker package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+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 1832632] Re: building from source on Ubuntu 18.04 fails
** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832632 Title: building from source on Ubuntu 18.04 fails Status in gtk+3.0 package in Ubuntu: New Bug description: Trying to build gtk+3.0-3.22.30 from source fails. I got the source using package gtk-3-examples. $ apt policy gtk-3-examples gtk-3-examples: Installed: 3.22.30-1ubuntu3 Candidate: 3.22.30-1ubuntu3 Version table: *** 3.22.30-1ubuntu3 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.22.30-1ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Ubuntu version: Description: Ubuntu 18.04.2 LTS Release: 18.04 Steps to reproduce: apt source gtk-3-examples sudo apt build-dep gtk-3-examples sudo apt install devscripts cd gtk+3.0-3.22.30 debuild -i -us -uc -d -b 2>&1 | tee build.log The build failed. First error (to the best of my knowledge): ERROR:../../../../../testsuite/gtk/scrolledwindow.c:100:test_size: assertion failed (min_size == MIN_SIZE): (153 == 150) FAIL Attached is the build log (build.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1832632/+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 1822380] Re: Thunar right-click menu not expanded
** Changed in: gtk+3.0 (Ubuntu) Status: New => Triaged ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1822380 Title: Thunar right-click menu not expanded Status in GTK+: New Status in Thunar File Manager: Fix Released Status in gtk+3.0 package in Ubuntu: Triaged Status in thunar package in Ubuntu: Fix Released Bug description: Submitting this bug report with the SRU template, but hopefully we can go ahead have this uploaded before the final images have been built. [Impact] * The "Create Document" submenu in Thunar does not expand to a usable length. * The submenu is displayed at just a few pixels tall, enough to see menu items as you scroll, but not enough to read any item. * This breaks a standard use case for file managers: creating new files. * The proposed upload fixes the bug by loading the menu items synchronously, making the menu load with the items already populated instead of having to redraw once the items are added. * The patch provided comes from the upstream maintainer. [Test Case] * Open Thunar. * Right click in the blank space (not on an item). * Move the cursor to the "Create Document" menu. * Bug Present: The submenu is displayed but short, and no items are visible. * Bug Resolved: The submenu is displayed, items present in the ~/Templates folder are displayed. [Regression Potential] * Regression potential is minimal: * The modified code affects only the drawing of the submenu items. * The submenu is already ununsable, no items are displayed. * Some limited testing has already been completed: * 2 users confirmed the patch fixes the issue on the upstream bug report. * 2 Xubuntu team members (bluesabre, Unit193) have also confirmed the patch and no regressions. [Original Report] In Thunar, when I right click to create a new file, the menu shows up so small that I can't see the options. I have rebooted and the problem persists. Haven't checked other file managers yet. Running Xubuntu 19.04 (Development Branch), Thunar 1.8.4. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunar 1.8.4-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 29 16:41:29 2019 InstallationDate: Installed on 2019-03-29 (0 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: thunar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1822380/+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 1630137] Re: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive
Hi, I have encountered the same problem. Is there a solution? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1630137 Title: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive Status in gstreamer1.0 package in Ubuntu: Expired Bug description: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive, so the consequence is that nobody can install package `gstreamer1.0-vaapi` now: $ sudo apt install gstreamer1.0-vaapi Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gstreamer1.0-vaapi : Depends: libgstreamer-plugins-bad1.0-0 (< 1.8.1) but 1.8.2-1ubuntu0.1 is to be installed E: Unable to correct problems, you have held broken packages. Tested in recently installed Ubuntu 16.04.1. The culprit seems to be in: $ apt-cache show gstreamer1.0-vaapi Package: gstreamer1.0-vaapi Priority: optional Section: universe/libs Installed-Size: 714 Maintainer: Ubuntu Developers Original-Maintainer: Maintainers of GStreamer packages Architecture: amd64 Source: gstreamer-vaapi Version: 1.8.0-1 Depends: libc6 (>= 2.14), libdrm2 (>= 2.3.1), libegl1-mesa (>= 7.8.1) | libegl1-x11, libgl1-mesa-glx | libgl1, libglib2.0-0 (>= 2.37.3), libgstreamer-plugins-bad1.0-0 (>= 1.8.0), libgstreamer-plugins-bad1.0-0 (<< 1.8.1), libgstreamer-plugins-base1.0-0 (>= 1.6.0), libgstreamer1.0-0 (>= 1.6.0), libudev1 (>= 183), libva-drm1 (>= 1.1.0), libva-wayland1 (>= 1.3.0), libva-x11-1 (>= 1.0.3), libva1 (>= 1.4.0), libwayland-client0 (>= 1.3.92), libx11-6, libxrandr2, libxrender1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1630137/+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 48734] Re: Home permissions too open
** Changed in: ubuntu-rtm
Status: New => Won't Fix
** Changed in: ubuntu-rtm
Status: Won't Fix => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/48734
Title:
Home permissions too open
Status in adduser package in Ubuntu:
Opinion
Status in Ubuntu RTM:
Opinion
Bug description:
Binary package hint: debian-installer
On a fresh dapper install i noticed that the file permissons for the
home directory for the user created by the installer is set to 755,
giving read access to everyone on the system.
Surely this is a bad idea? If your set on the idea can we atleast have
a option during the boot proccess?
Also new files that are created via the console ('touch' etc.) are
done so with '644' permissons, is there anything that can be done
here? nautlius seems to create files at '600', which is a better
setting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/48734/+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 1832689] Re: TPM certification tests now failing after update to 1.1.1 (test_output_formats)
huh, ok, so actually the cert team mentioned that when they removed the redirect as well, it just all passed. So I guess the bug is invalid? Thanks for looking into it Dimitri! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832689 Title: TPM certification tests now failing after update to 1.1.1 (test_output_formats) Status in Provider for Plainbox - TPM2: Incomplete Status in openssl package in Ubuntu: Incomplete Bug description: The certification team is running automated tests for every supported ubuntu-core device for every new core18 snap update. The recent core18 includes the openssl 1.1.1 update and seems to have caused regressions in the TPM test suite (for the dawson-i device). I was able to dig out the test suite itself, with the failing test code located here: https://git.launchpad.net/plainbox-provider- tpm2/tree/data/tpm2-tools-3.0.4/test/system/test_output_formats.sh Test failure log seems to be this: openssl rsa -pubin -inform "$fmt" -text -in "$this_key" &> /dev/null on line 95 failed: 1 The certification team will follow up with more information. This is currently causing core18 promotions to be blocked (and there has been over a month without a new core18 stable snap). Setting to critical. I noticed a follow-up SRU for openssl with fix for LP: #1828215 and was wondering if it might be related? To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-tpm2/+bug/1832689/+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 1759950] Re: Lid-close suspend: blank screen when switching to user session
maxpus=1 still suffers the same issue. I then disabled and stopped the upower daemon but the issue remains with the only common factors being systemd-logind and lightdm. I tried console-only tests with lightdm stopped and CANNOT reproduce the issue. I installed sddm and changed the default display manager to use it: apt install --no-install-recommends sddm Tested with logind + sddm and CANNOT reproduce the issue. Re-enabled upower via the x-p-m applet. Tested with logind + sddm + upower/x-p-m and CANNOT reproduce the issue. Tested with logind + sddm + upower/x-p-m + light-locker and CANOT reproduce the issue (note: light-locker dies at some point so no password dialog on resume). Based on all this it seems to point the finger at ---> lightdm -- 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/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Confirmed Status in light-locker package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+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 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
I am using a bento/ubuntu18.04 box on vagrant/kitchen-ci with the kitchen-ansible provisioner and can reproduce this bug. Setting up python-idna (2.6-1) ... Setting up python-yaml (3.12-1build2) ... Setting up python-asn1crypto (0.24.0-1) ... Setting up python-pyasn1 (0.4.2-3) ... Setting up python-pkg-resources (39.0.1-2) ... Setting up python-markupsafe (1.0-1build1) ... Setting up python-httplib2 (0.9.2+dfsg-1ubuntu0.1) ... Setting up python-cffi-backend (1.11.5-1) ... Setting up python-six (1.11.0-2) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up sshpass (1.06-1) ... Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.2) ... Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Setting up python-enum34 (1.1.6-2) ... dpkg: dependency problems prevent configuration of python-cryptography: python-cryptography depends on libssl1.1 (>= 1.1.1); however: Package libssl1.1:amd64 is not configured yet. dpkg: error processing package python-cryptography (--configure): dependency problems - leaving unconfigured Processing triggers for man-db (2.8.3-2ubuntu0.1) ...No apport report written because the error message indicates its a followup error from a previous failure. Setting up python-ipaddress (1.0.17-1) ... Setting up python-setuptools (39.0.1-2) ... Setting up python-jinja2 (2.10-1ubuntu0.18.04.1) ... dpkg: dependency problems prevent configuration of libssl-dev:amd64: libssl-dev:amd64 depends on libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.2); however: Package libssl1.1:amd64 is not configured yet. dpkg: error processing package libssl-dev:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of python-paramiko:No apport report written because the error message indicates its a followup error from a previous failure The fix works, this has only been an issue since 14th July 2019. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832919 Title: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Status in openssl package in Ubuntu: Incomplete Bug description: The error happens when trying to configure libssl1.1:amd64 (dpkg --configure -D 2 libssl1.1) dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D02: check_triggers_cycle pnow=libc-bin:amd64 first Processing triggers for libc-bin (2.27-3ubuntu1) ... D02: post_postinst_tasks - trig_incorporate Errors were encountered while processing: libssl1.1:amd64 [ WORKAROUND TO RECOVER YOUR SYSTEM ] $ sudo dpkg-reconfigure libc6 $ sudo dpkg --configure libssl1.1 [ Reproducer steps ] # DO NOT DO THIS ON PRODUCTION MACHINES # # echo PURGE | debconf-communicate libpam0g:amd64 0 # echo PURGE | debconf-communicate libpam0g 0 # echo PURGE | debconf-communicate libc6:amd64 0 # echo PURGE | debconf-communicate libc6 0 # sh -x /var/lib/dpkg/info/libssl1.1\:amd64.postinst configure 1.1.1 + . /usr/share/debconf/confmodule + [ ! ] + PERL_DL_NONLAZY=1 + export PERL_DL_NONLAZY + [ ] + exec /usr/share/debconf/frontend /var/lib/dpkg/info/libssl1.1:amd64.postinst configure 1.1.1 Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... # echo $? 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919/+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 1808861] Re: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
Something similar here too, with DBUS crashing out, and not generating a complete core dump (though plenty of disk and RAM) un 17 00:10:40 xps15 gjs[2607]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 17 00:10:40 xps15 gjs[2607]: message repeated 8 times: [ g_object_unref: assertion 'G_IS_OBJECT (object)' failed] Jun 17 00:10:40 xps15 systemd[1991]: gnome-terminal-server.service: Main process exited, code=killed, status=15/TERM Jun 17 00:10:40 xps15 systemd[1991]: gnome-terminal-server.service: Succeeded. Jun 17 00:10:45 xps15 gsd-print-notif[2333]: Source ID 3 was not found when attempting to remove it Jun 17 00:10:45 xps15 kernel: [ 8851.668166] rfkill: input handler enabled Jun 17 00:10:45 xps15 systemd[1]: unattended-upgrades.service: Succeeded. Jun 17 00:10:45 xps15 systemd[1991]: Stopping D-Bus User Message Bus... Jun 17 00:10:45 xps15 systemd[1991]: at-spi-dbus-bus.service: Succeeded. Jun 17 00:10:45 xps15 gnome-session[2037]: gnome-session-binary[2037]: WARNING: Lost name on bus: org.gnome.SessionManager Jun 17 00:10:45 xps15 gnome-session[2037]: gnome-session-binary[2037]: CRITICAL: We failed, but the fail whale is dead. Sorry Jun 17 00:10:45 xps15 gnome-session-binary[2037]: WARNING: Lost name on bus: org.gnome.SessionManager Jun 17 00:10:45 xps15 gnome-session-binary[2037]: CRITICAL: We failed, but the fail whale is dead. Sorry Jun 17 00:10:45 xps15 gvfsd[2182]: A connection to the bus can't be made Jun 17 00:10:45 xps15 gnome-shell[2175]: [AppIndicatorSupport-DEBUG] Lost nameorg.kde.StatusNotifierWatcher Jun 17 00:10:45 xps15 gnome-shell[2175]: JS WARNING: [resource:///org/gnome/gjs/modules/signals.js 128]: Too many arguments to method Clutter.Actor.destroy: expected 0, got 1 Jun 17 00:10:45 xps15 systemd[1991]: run-user-1000-gvfs.mount: Succeeded. Jun 17 00:10:45 xps15 systemd[1991]: gvfs-daemon.service: Main process exited, code=killed, status=15/TERM Jun 17 00:10:45 xps15 systemd[1991]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE Jun 17 00:10:45 xps15 tracker-miner-f[2474]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Jun 17 00:10:45 xps15 systemd[1991]: xdg-permission-store.service: Failed with result 'exit-code'. Jun 17 00:10:45 xps15 tracker-miner-f[2474]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Jun 17 00:10:45 xps15 systemd[1991]: gvfs-metadata.service: Succeeded. Jun 17 00:10:45 xps15 kernel: [ 8851.715910] dbus-daemon[2029]: segfault at 0 ip 7fcf20d73e53 sp 7ffefaadc258 error 6 in libdbus-1.so.3.19.9[7fcf20d51000+2d000] Jun 17 00:10:45 xps15 kernel: [ 8851.715930] Code: 89 12 48 89 52 08 48 89 17 c3 0f 1f 44 00 00 48 89 d6 e9 80 fe ff ff 48 8b 46 08 48 39 f0 74 47 48 8b 16 48 89 42 08 48 8b 16 <48> 89 10 48 39 37 74 15 48 c7 46 08 00 00 00 00 48 c7 06 00 00 00 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: Invalid Status in chromium-browser package in Ubuntu: Invalid Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 warning: core file may not match specified executable file. Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UT
[Touch-packages] [Bug 935681] Re: "Restart services during package upgrades without asking?" fails to honor --yes for apt-get
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: eglibc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/935681 Title: "Restart services during package upgrades without asking?" fails to honor --yes for apt-get Status in eglibc package in Ubuntu: Confirmed Bug description: I left an old netbook to do an "apt-get -y dist-upgrade" overnight, and when I returned to it the next morning, the upgrades were unfinished because libc upgrade was waiting for me to respond to "Restart services during package upgrades without asking?" It looks like the question is prioritized depending on whether the upgrade is done on desktop or not, and if it's not, the priority is set critical. According to documentation [1], critical is for "Items that will probably break the system without user intervention." I don't think restart-without-asking satisfies that condition. * [1] http://www.debian.org/doc/packaging- manuals/debconf_specification.html#AEN101 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libc6 2.15-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 18 21:07:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=fi:en_US:en PATH=(custom, user) LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: eglibc UpgradeStatus: Upgraded to precise on 2012-02-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/935681/+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 1823053] Re: wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco
It seems this is also applicable to ubuntu bionic since openssl 1.1.1 landed in bionic-updates. We have bionic clients that cannot connect to the enterprise wifi because they attempt TLS 1.3. Recompiling openssl with the "no-tls1_3" Configure option fixes the problem. See also https://github.com/FreeRADIUS/freeradius-server/issues/2385 ** Bug watch added: github.com/FreeRADIUS/freeradius-server/issues #2385 https://github.com/FreeRADIUS/freeradius-server/issues/2385 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1823053 Title: wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco Status in wpa package in Ubuntu: New Bug description: Ubuntu 18.10 "Cosmic" and 19.04 "Disco" currently ship with both wpasupplicant 2.6 and openssl/libssl 1.1.1, although upstream only supports OpenSSL 1.1.1 starting with wpasupplicant 2.7. OpenSSL 1.1.1 introduced support for TLS 1.3, and introduced new APIs to configure the parameters governing TLS connections using TLS >= 1.3. OpenSSL also decided that it would enable TLS 1.3 by default even for software that had only been built for libssl <= 1.1.0 and hence couldn't "know" about the new APIs. This leads to a situation where software that was designed/built for OpenSSL 1.1.0 and TLS 1.2 will also offer TLS 1.3, without any possibility for end users to disable such behavior. One case where this causes problems is wpasupplicant: wpasupplicant 2.7 officially introduced support for OpenSSL 1.1.1, which mainly consists of disabling TLS 1.3 by default and adding a configuration flag allowing end users to selectively enable it for connections when they see fit. wpasupplicant 2.6, however, as shipped with Ubuntu 18.10 and 19.04, does not offer such a possibility, and hence tries negotiating TLS 1.3 (alongside with older versions all the way down to TLS 1.0). Sadly, there are RADIUS servers which suffer from TLS version intolerance and will refuse authentication when the client offers TLS 1.3. I know of such a case with a German university's eduroam wifi, but I doubt this is the only case where this causes problems. As a dirty stopgap measure, I've installed the wpasupplicant 2.7 package from Debian Buster (https://packages.debian.org/buster/wpasupplicant), and I've asked the NOC at the affected university to upgrade/reconfigure their RADIUS server to make the version intolerance go away - but still, this is a bug that should be fixed in Ubuntu, preferably by backporting wpasupplicant 2.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1823053/+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 1823053] Re: wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco
> Sadly, there are RADIUS servers which suffer from TLS version intolerance and will refuse authentication when the client offers TLS 1.3 This statement is completely missing the point. There are *no standards available* for using TLS 1.3 with *any* EAP method. The IETF is working on them, but they are in flux, and have not yet been published. EAP-TLS and TLS 1.3 is being defined here: https://tools.ietf.org/html /draft-ietf-emu-eap-tls13-05 TLS 1.3 for other EAP methods is being defined here: https://tools.ietf.org/html/draft-dekok-emu-tls-eap-types-00 > still, this is a bug that should be fixed in Ubuntu, preferably by backporting wpasupplicant 2.7. The bug is that the shipped versions wpasupplicant and FreeRADIUS allow negotiation of TLS 1.. Even though the standards that defining TLS 1.3 with EAP didn't exist. This issue only happens in older versions of the software. For FreeRADIUS, it's 3.0.15 and before. i.e. this was fixed two years ago in 3.0.16. The solution for the distributions is one of two paths: 1. Upgrade to newer versions of the software that disable support for TLS 1.3 by default 2. Patch the older versions of the software to disable TLS 1.3 by default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1823053 Title: wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco Status in wpa package in Ubuntu: New Bug description: Ubuntu 18.10 "Cosmic" and 19.04 "Disco" currently ship with both wpasupplicant 2.6 and openssl/libssl 1.1.1, although upstream only supports OpenSSL 1.1.1 starting with wpasupplicant 2.7. OpenSSL 1.1.1 introduced support for TLS 1.3, and introduced new APIs to configure the parameters governing TLS connections using TLS >= 1.3. OpenSSL also decided that it would enable TLS 1.3 by default even for software that had only been built for libssl <= 1.1.0 and hence couldn't "know" about the new APIs. This leads to a situation where software that was designed/built for OpenSSL 1.1.0 and TLS 1.2 will also offer TLS 1.3, without any possibility for end users to disable such behavior. One case where this causes problems is wpasupplicant: wpasupplicant 2.7 officially introduced support for OpenSSL 1.1.1, which mainly consists of disabling TLS 1.3 by default and adding a configuration flag allowing end users to selectively enable it for connections when they see fit. wpasupplicant 2.6, however, as shipped with Ubuntu 18.10 and 19.04, does not offer such a possibility, and hence tries negotiating TLS 1.3 (alongside with older versions all the way down to TLS 1.0). Sadly, there are RADIUS servers which suffer from TLS version intolerance and will refuse authentication when the client offers TLS 1.3. I know of such a case with a German university's eduroam wifi, but I doubt this is the only case where this causes problems. As a dirty stopgap measure, I've installed the wpasupplicant 2.7 package from Debian Buster (https://packages.debian.org/buster/wpasupplicant), and I've asked the NOC at the affected university to upgrade/reconfigure their RADIUS server to make the version intolerance go away - but still, this is a bug that should be fixed in Ubuntu, preferably by backporting wpasupplicant 2.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1823053/+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 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
** Changed in: openssl (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832919 Title: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Status in openssl package in Ubuntu: Confirmed Bug description: The error happens when trying to configure libssl1.1:amd64 (dpkg --configure -D 2 libssl1.1) dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D02: check_triggers_cycle pnow=libc-bin:amd64 first Processing triggers for libc-bin (2.27-3ubuntu1) ... D02: post_postinst_tasks - trig_incorporate Errors were encountered while processing: libssl1.1:amd64 [ WORKAROUND TO RECOVER YOUR SYSTEM ] $ sudo dpkg-reconfigure libc6 $ sudo dpkg --configure libssl1.1 [ Reproducer steps ] # DO NOT DO THIS ON PRODUCTION MACHINES # # echo PURGE | debconf-communicate libpam0g:amd64 0 # echo PURGE | debconf-communicate libpam0g 0 # echo PURGE | debconf-communicate libc6:amd64 0 # echo PURGE | debconf-communicate libc6 0 # sh -x /var/lib/dpkg/info/libssl1.1\:amd64.postinst configure 1.1.1 + . /usr/share/debconf/confmodule + [ ! ] + PERL_DL_NONLAZY=1 + export PERL_DL_NONLAZY + [ ] + exec /usr/share/debconf/frontend /var/lib/dpkg/info/libssl1.1:amd64.postinst configure 1.1.1 Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... # echo $? 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919/+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 1826459] Re: systemd-networkd not installing GatewayOnlink=true
heres btw the netplan config im using: network: version: 2 renderer: networkd ethernets: enp0s31f6: addresses: [ 95.216.96.148/26 ] gateway4: 95.216.96.129 nameservers: addresses: - "8.8.8.8" - "1.1.1.1" routes: - to: 95.216.96.128/26 via: 95.216.96.129 on-link: true if im modifing routes to routes: - to: 95.216.96.150/32 via: 95.216.96.129 on-link: true it works out for 150, (but well in this case i need to add plenty of routes..) -- 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/1826459 Title: systemd-networkd not installing GatewayOnlink=true Status in netplan: New Status in systemd package in Ubuntu: New Bug description: root@search-3 /run/systemd/network # for i in *; do echo $i; echo; cat $i; done ; sudo service systemd-networkd stop; SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd 10-netplan-enp0s31f6.network [Match] Name=enp0s31f6 [Network] LinkLocalAddressing=ipv6 Address=95.216.96.148/26 Gateway=95.216.96.129 DNS=8.8.8.8 DNS=1.1.1.1 Domains=148.96.216.95.clients.your-server.de VLAN=vlan4000 [Route] Destination=95.216.96.148/26 Gateway=95.216.96.129 GatewayOnlink=true 10-netplan-vlan4000.netdev [NetDev] Name=vlan4000 MTUBytes=1400 Kind=vlan [VLAN] Id=4000 10-netplan-vlan4000.network [Match] Name=vlan4000 [Network] LinkLocalAddressing=ipv6 Address=10.0.2.3/24 ConfigureWithoutCarrier=yes Failed to read $container of PID 1, ignoring: Permission denied Found container virtualization none. Bus n/a: changing state UNSET → OPENING Bus n/a: changing state OPENING → AUTHENTICATING Failed to open configuration file '/etc/systemd/networkd.conf': No such file or directory timestamp of '/etc/systemd/network' changed timestamp of '/run/systemd/network' changed Ignoring /run/systemd/network/10-netplan-enp0s31f6.network, because it's not a regular file with suffix .netdev. Ignoring /run/systemd/network/10-netplan-vlan4000.network, because it's not a regular file with suffix .netdev. Ignoring /lib/systemd/network/99-default.link, because it's not a regular file with suffix .netdev. Ignoring /lib/systemd/network/80-container-vz.network, because it's not a regular file with suffix .netdev. Ignoring /lib/systemd/network/80-container-ve.network, because it's not a regular file with suffix .netdev. Ignoring /lib/systemd/network/80-container-host0.network, because it's not a regular file with suffix .netdev. vlan4000: loaded vlan Ignoring /run/systemd/network/10-netplan-vlan4000.netdev, because it's not a regular file with suffix .network. Ignoring /lib/systemd/network/99-default.link, because it's not a regular file with suffix .network. tun0: MAC address not found for new device, continuing without tun0: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +POINTOPOINT +NOARP tun0: Link 12 added tun0: udev initialized link tun0: Saved original MTU: 1500 veth20a5a67: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST veth20a5a67: Link 8 added veth20a5a67: udev initialized link veth20a5a67: Saved original MTU: 1500 vlan4000: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST vlan4000: Link 6 added vlan4000: udev initialized link vlan4000: netdev has index 6 vlan4000: Saved original MTU: 1400 br-c7cc901345e8: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST br-c7cc901345e8: Link 5 added br-c7cc901345e8: udev initialized link br-c7cc901345e8: Saved original MTU: 1500 docker0: Flags change: +UP +MULTICAST +BROADCAST docker0: Link 3 added docker0: udev initialized link docker0: Saved original MTU: 1500 enp0s31f6: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST enp0s31f6: Link 2 added enp0s31f6: udev initialized link enp0s31f6: Saved original MTU: 1500 lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING lo: Link 1 added lo: udev initialized link lo: Saved original MTU: 0 vlan4000: Adding address: fe80::921b:eff:fe93:5015/64 (valid forever) vlan4000: Gained IPv6LL tun0: Adding address: 10.0.0.13/24 (valid forever) vlan4000: Adding address: 10.0.2.3/24 (valid forever) br-c7cc901345e8: Adding address: 172.18.0.1/16 (valid forever) docker0: Adding address: 172.17.0.1/16 (valid forever) enp0s31f6: Adding address: 95.216.96.148/26 (valid forever) lo: Adding address: 127.0.0.1/8 (valid forever) rtnl: received address with invalid family 129, ignoring Enumeration completed Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n
[Touch-packages] [Bug 1832967] Re: /etc/resolv.conf does not include the local domain name
Thanks for the quick response. Yesterday to fix the issue, I uninstalled the resolvconf package. I reinstalled it today, and now it is working with the correct "search" domain. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1832967 Title: /etc/resolv.conf does not include the local domain name Status in resolvconf package in Ubuntu: Incomplete Bug description: When I rebooted my system after an update, `/etc/resolv.conf` was symlinked to `/run/resolvconf/resolv.conf`. That file did not have my local domain name in the search even though it is supplied by the dhcp server. The systemd resolv.conf file (in `/run/systemd/resolve/resolv.conf`) had the correct search information. Please ensure that the search is correctly added. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 15 22:18:05 2019 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-08-21 (299 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1832967/+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 1817627] Re: systemd-analyze verify reports failure
This affects each system where /tmp is *not* on tmpfs which affects a lot of cloud-built servers and effectively prevents usage of systemd- analyze verify in Ansible, Puppet etc. -- 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/1817627 Title: systemd-analyze verify reports failure Status in Ubuntu Manpage Repository: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: Version 237 and 238 of systemd-analyze have a known issue: https://github.com/systemd/systemd/issues/8592 When will a fix be posted? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1817627/+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 1770792] Re: Clean up sync blacklist
> Or, you can punt this to me to do and I'll apply these changes when I have a chance. Since this bug went to 'expired', I'll take this now, for the subset of changes I agree are appropriate. ** Changed in: ubuntu-meta (Ubuntu) Status: Expired => Triaged ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1770792 Title: Clean up sync blacklist Status in ubuntu-meta package in Ubuntu: Triaged Bug description: I am attaching a bzr branch here. Because the sync blacklist is a "junk" bzr repository, Launchpad isn't letting me make a merge proposal for it. I think it makes the blacklist easier to read and use if we get rid of all the old entries. I went through and verified that these removals were removed from Debian. There are a few exceptions (gdm3 and openssl1.0) which didn't need to be blacklisted anymore. I mostly ignored the Mozilla extensions. The Mozilla situation is interesting this year, but I'll save that discussion for later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1770792/+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 1790098] Re: vlan created on bond fails auto activation on updating parent network bond
** Changed in: network-manager (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Won't Fix Status in network-manager package in Ubuntu: Won't Fix Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet -- encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e ethernet -- vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan -- As is seen, vlan(vlanbond.100) did not get activated Now, if manually I make vlan connection up, it gets activated: root@S36MANDAR:~# nmcli con up vlanbond.100 NAME
[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond
Since our focus is on netplan only, I'm changing the status to Won't Fix. ** Changed in: ubuntu-z-systems Status: Incomplete => Won't Fix -- 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/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Won't Fix Status in network-manager package in Ubuntu: Won't Fix Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet -- encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e ethernet -- vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan -- As is seen, vlan(vlanbond.100) did not get activated Now, if manually I make vlan connection up, it gets acti
[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
** Summary changed: - [Don't release SRU yet]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right + [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Fix Committed Status in xorg-server source package in Xenial: Confirmed Status in console-setup source package in Bionic: Fix Released Status in kbd source package in Bionic: Fix Committed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Released Status in kbd source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Released Status in kbd source package in Disco: Fix Committed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Fix Released Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (kbd) [Impact] * kbd_mode -u is documented to break keyboards in modes other than xlate and unicode, while it is still called by some scripts. Those scripts are called transitively by maintainer scripts such as the one already fixed in console-setup. * To avoid accidentally breaking keyboards a -f option is added to force such breaking mode changes. Without -f only the safe mode changes are performed and an error is printed when the requested mode change is not safe. Next upstream version will also exit with error, but the cherry-picked fix makes kbd_mode return success even when the mode switch is not performed to avoid regressions of scripts. [Test case] * Verify that safe mode switches work and dangerous ones are skipped without -f. Please note that the test will temporarily break the system's keyboard and it is recommended to run the test in a VM. rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $? The keyboard is in Unicode (UTF-8) mode 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in xlate (8-bit) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in some unknown mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in raw (scancode) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in raw (scancode) mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 [Regression Potential] * kbd_mode stops performing breaking mode switches and this may make scripts ineffective when trying to perform a breaking change. This is the intention of the change and the emitter error helps in finding the offending script. The following packages found to call kbd_mode directly: console-setup xinit console-cyrillic initramfs-tools dracut console-tools xview ubiquity's embedded console-setup copy console-data vnc4 The console related packages are expected to execute only safe mode changes because they should operate on consoles only and the rest seem to be safe, too. (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyb
[Touch-packages] [Bug 1770792] Re: Clean up sync blacklist
I've landed these blacklist changes now. ** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1770792 Title: Clean up sync blacklist Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: I am attaching a bzr branch here. Because the sync blacklist is a "junk" bzr repository, Launchpad isn't letting me make a merge proposal for it. I think it makes the blacklist easier to read and use if we get rid of all the old entries. I went through and verified that these removals were removed from Debian. There are a few exceptions (gdm3 and openssl1.0) which didn't need to be blacklisted anymore. I mostly ignored the Mozilla extensions. The Mozilla situation is interesting this year, but I'll save that discussion for later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1770792/+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 1685754] Re: gnome-terminal unduly forces umask=0022
Does anyone know where this bug is being tracked upstream now? GNOME has
migrated from Bugzilla to GitLab, and I haven't been able to find the
GitLab version of the Bugzilla bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1831775] Re: ss seems broken when using multiple filters in the same cmdline
** Merge proposal linked: https://code.launchpad.net/~smb/ubuntu/+source/iproute2/+git/iproute2/+merge/368924 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: In Progress Status in iproute2 source package in Disco: In Progress Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+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 1829968] Re: motd [on at least some instances] does not auto-update daily
** Description changed: + [Impact] + motd-news timer is not properly configured and may not run regularly so long running systems will not get an updated motd + + [Test Case] + The system being tested must have curl installed - base-files does not depend on it because reasons. + 1) Run 'systemctl status mot-news.timer' + 2) Observe that the Trigger section is n/a + + With the version of the package from -proposed the Trigger section + should instead contain something like the following: + + Trigger: Mon 2019-06-17 11:42:25 PDT; 20min left + + One should also wait to ensure that the trigger actually ran and that + /var/cache/motd-news has been updated. + + [Regression Potential] + I can't think of any on the client side as the job wasn't working at all but it may cause extra load on the motd server. + + + Original Description + I have a VM running on AWS. It was launched on May 9th: - $ uptime -05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 - $ date - Wed May 22 05:26:24 UTC 2019 + $ uptime + 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 + $ date + Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. - $ ls -l /var/cache/motd-news - -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news + $ ls -l /var/cache/motd-news + -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: - $ systemctl status motd-news.timer - ● motd-news.timer - Message of the Day - Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) - Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago - Trigger: n/a + $ systemctl status motd-news.timer + ● motd-news.timer - Message of the Day + Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) + Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago + Trigger: n/a - May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the + May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Bionic: Triaged Status in base-files source package in Cosmic: New Status in base-files source package in Disco: New Status in base-files source package in Eoan: Fix Released Bug description: [Impact] motd-news timer is not properly configured and may not run regularly so long running systems will not get an updated motd [Test Case] The system being tested must have curl installed - base-files does not depend on it because reasons. 1) Run 'systemctl status mot-news.timer' 2) Observe that the Trigger section is n/a With the version of the package from -proposed the Trigger section should instead contain something like the following: Trigger: Mon 2019-06-17 11:42:25 PDT; 20min left One should also wait to ensure that the trigger actually ran and that /var/cache/motd-news has been updated. [Regression Potential] I can't think of any on the client side as the job wasn't working at all but it may cause extra load on the motd server. Original Description I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+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 1833116] [NEW] chtmax98090 not working out of the box
Public bug reported: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsaucm -c chtmax98090 set _verb HiFi set _enadev Speakers #alsaucm -c chtmax98090 set _verb HiFi set _enadev Headphone alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug audio bionic intel -- 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/1833116 Title: chtmax98090 not working out of the box Status in alsa-driver package in Ubuntu: New Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsaucm -c chtmax98090 set _verb HiFi set _enadev Speakers #alsaucm -c chtmax98090 set _verb HiFi set _enadev Headphone alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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 1685754] Re: gnome-terminal unduly forces umask=0022
Currently, the upstream issue has NOT been migrated to GNOME GitLab yet,
but is still being tracked at
https://bugzilla.gnome.org/show_bug.cgi?id=780622
** Bug watch added: bugzilla.gnome.org/ #780622
https://bugzilla.gnome.org/show_bug.cgi?id=780622
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 269910] Re: Netmask automatically changes to 24
It is still an issue in Mint 19.1 -- 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/269910 Title: Netmask automatically changes to 24 Status in network-manager package in Ubuntu: Fix Released Bug description: Binary package hint: network-manager I have added a new wireless connection with a WPA2 password and a manual IP address, like this: IP address: 180.180.180.11, Netmask: 255.255.255.0 Gateway: 180.180.180.254 I also added two DNS servers. The connection is flawless (pass my compliments to whoever responsible for this, I could never get it to work on Hardy). However, when I edit the wireless connection again, for some reason, the Netmask changes to 24. Just 24. The connection still works. Everything else is the same. network-manager version: 0.7~~svn20080908t183521+eni0-0ubuntu2 I'm running Ubuntu Intrepid Ibex Alpha 5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/269910/+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 1817123] Re: tmpfiles.d files pointing to legacy directory /var/run
Just got the same bug again in Disco Dingo. Setting up systemd (240-6ubuntu5.1) ... [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfile s.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/spice-vdagentd.conf:2] Line references path below legacy directory /var/run/, updating /var/run/spice-vdagentd → /run/spice-vdagentd; please update the tmpfiles.d/ drop-in file accordingly. -- 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/1817123 Title: tmpfiles.d files pointing to legacy directory /var/run Status in systemd package in Ubuntu: Confirmed Status in speech-dispatcher package in Debian: New Status in spice-vdagent package in Debian: New Bug description: Just updated cosmic and got: Setting up systemd (239-7ubuntu10.8) ... [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/spice-vdagentd.conf:2] Line references path below legacy directory /var/run/, updating /var/run/spice-vdagentd → /run/spice-vdagentd; please update the tmpfiles.d/ drop-in file accordingly. andre@thinkpad:~$ lsb_release -rd Description:Ubuntu 18.10 Release:18.10 andre@thinkpad:~$ apt-cache policy systemd systemd: Installed: 239-7ubuntu10.8 Candidate: 239-7ubuntu10.8 Version table: *** 239-7ubuntu10.8 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 100 /var/lib/dpkg/status 239-7ubuntu10 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817123/+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 1833001] Re: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833001 Title: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing Status in openssl package in Ubuntu: Confirmed Bug description: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1833001/+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 1833001] Re: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing
I can confirm this affects the bionic-updates 1.1.1-1ubuntu2.1~18.04.2 package, therefore a backport to bionic and other affected releases will be required -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833001 Title: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing Status in openssl package in Ubuntu: Confirmed Bug description: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1833001/+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 1833001] Re: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing
For those affected, you can run: $ echo 'libssl1.1 libraries/restart-without-asking boolean true' | debconf-set-selections Previous to attempting to install the package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833001 Title: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing Status in openssl package in Ubuntu: Confirmed Bug description: openssl should register libraries/restart-without-asking template or handle gracefully when it is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1833001/+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 1685754] Re: gnome-terminal unduly forces umask=0022
Ah, OK, thanks. No news since 2018-08 then - I was hoping the GNOME
GitLab would have something new :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 269910] Re: Netmask automatically changes to 24
A workaround seems to be to add two sets of addresses and then delete the top one (which will have the erroneously saved mas address). -- 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/269910 Title: Netmask automatically changes to 24 Status in network-manager package in Ubuntu: Fix Released Bug description: Binary package hint: network-manager I have added a new wireless connection with a WPA2 password and a manual IP address, like this: IP address: 180.180.180.11, Netmask: 255.255.255.0 Gateway: 180.180.180.254 I also added two DNS servers. The connection is flawless (pass my compliments to whoever responsible for this, I could never get it to work on Hardy). However, when I edit the wireless connection again, for some reason, the Netmask changes to 24. Just 24. The connection still works. Everything else is the same. network-manager version: 0.7~~svn20080908t183521+eni0-0ubuntu2 I'm running Ubuntu Intrepid Ibex Alpha 5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/269910/+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 1759950] Re: Lid-close suspend: blank screen when switching to user session
Yet more results changing the target once again!
I was able to reproduce the issue whilst using sddm which tends to
suggest lightdm may not be the cause.
I also managed to prove (not sure why this did not occur to me before
now!) that the DPMS state is being set 'off' when switching to the GUI
tty and 'on' when switching away.
In a console TTY I had:
$ while true; do grep .
/sys/class/drm/card0-LVDS-1/{dpms,enabled,status}; sleep 1; done
And then switched to the GUI and closed the lid. After resuming from
suspend and unlocking the GUI blanked. Switching to the console TTY
showed that whilst on the GUI TTY
dpms=off
which changes to
dpms=on
when switching away from it.
This tends to point pack towards xfce4-power-manager and upower since,
as I currently understand it, they specifically 'do' DPMS 'stuff'.
Certainly x-p-m has a lot of DPMS handling code and user-config
properties exposed.
--
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/1759950
Title:
Lid-close suspend: blank screen when switching to user session
Status in Light-Locker:
New
Status in Xfce4 Power Manager:
Confirmed
Status in light-locker package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in xfce4-power-manager package in Ubuntu:
Confirmed
Status in xubuntu-default-settings package in Ubuntu:
New
Bug description:
I'm currently testing Xubuntu 18.04 after a do-release-upgrade from
16.04.
I discovered a very weird issue. When doing S3 sleep via closing the
lid, on resume the lock screen appears, I authenticate, but as soon as
it switches to the user session the screen goes blank - not even a
backlight.
Switching to other ttys works and they display correctly but the GUI
user session remains blank.
If the system is manually suspended (not using the lid), then resumed
either by opening the lid or pressing the power button, the GUI user
session is fine.
I narrowed it down to xfce4-power-manager and discovered disabling the
lock-screen cured the issue.
I cloned the repository and reviewed commits between 1.7 and 1.8.
Fortunately there aren't many. Looking at 6365683 "Proper exit status
for light-locker-command" I suspected the change in the SetActive
return value, and reverted it.
After a build/install cycle I've found the system now behaves
correctly so I think the change should be reverted.
I've created an issue upstream for this at
https://github.com/the-cavalry/light-locker/issues/108
To manage notifications about this bug go to:
https://bugs.launchpad.net/light-locker/+bug/1759950/+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 1833161] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all
Public bug reported: Hello to all, My Ubuntu version is 18.04.02 LTS and I've setup a dual-boot with windows 10. Speakers and audio jack work totally fine under Windows 10, but they never work with Ubuntu. List of some of the things I've tried: 1) I've tried all the steps from the "Sound Troubleshooting Procedure" 2) I've tried installing the "oem-audio-hda-daily-dkms" package; 3) I've tried to install/remove/reinstall alsa-base, alsa-utils, pulseaudio, pavucontrol many times 4) I've played with the options in the file /etc/modprobe.d/alsa-base.conf: a) I've tried to add "options snd-hda-intel model=auto" and I also tried different models: auto, clevo, laptop-eapd, clevo m-720, generic, basic and even z71v position_fix=1. 5) I've tried adding : Code: [General] description = Headphones + Digital Output (S/PDIF) in the file "/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf" 6) I've even tried a live USB stick with Ubuntu 19.04 (after reading somewhere that this was fixed on 19.04), but I found out that there was no sound on Ubuntu 19.04 as well. Also, you can find my ALSA information here: http://alsa- project.org/db/?f=bcdf5c8be31ce8b9e848a29ef292e9125f26def0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jproberge 1737 F pulseaudio /dev/snd/controlC0: jproberge 1737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:37:29 2019 InstallationDate: Installed on 2019-06-15 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1236 F pulseaudio jproberge 1737 F pulseaudio /dev/snd/controlC0: gdm1236 F pulseaudio jproberge 1737 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08P dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08P:bd05/07/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1833161 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello to all, My Ubuntu version is 18.04.02 LTS and I've setup a dual-boot with windows 10. Speakers and audio jack work totally fine under Windows 10, but they never work with Ubuntu. List of some of the things I've tried: 1) I've tried all the steps from the "Sound Troubleshooting Procedure" 2) I've tried installing the "oem-audio-hda-daily-dkms" package; 3) I've tried to install/remove/reinstall alsa-base, alsa-utils, pulseaudio, pavucontrol many times 4) I've played with the options in the file /etc/modprobe.d/alsa-base.conf: a) I've tried to add "options snd-hda-intel model=auto" and I also tried different models: auto, clevo, laptop-eapd, clevo m-720, generic, basic and even z71v position_fix=1. 5) I've tried adding : Code: [General] description = Headphones + Digital Output (S/PDIF) in the file "/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf" 6) I've even tried a live USB stick with Ubuntu 19.04 (after reading somewhere that this was fixed on 19.04), but I found out that there was no sound on Ubuntu 19.04 as well. Also, you can find my ALSA information here: http://alsa- project.org/db/?f=bcdf5c8be31ce8b9e848a29ef292e9125f26def0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvi
[Touch-packages] [Bug 1833161] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
Please edit /etc/modprobe.d/alsa-base.conf and add: options snd-hda-intel probe_mask=0x1 reboot and check if audio works. If it works, please remove that line int the alsa-base.conf and install 5.0 kernel to test. -- 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/1833161 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello to all, My Ubuntu version is 18.04.02 LTS and I've setup a dual-boot with windows 10. Speakers and audio jack work totally fine under Windows 10, but they never work with Ubuntu. List of some of the things I've tried: 1) I've tried all the steps from the "Sound Troubleshooting Procedure" 2) I've tried installing the "oem-audio-hda-daily-dkms" package; 3) I've tried to install/remove/reinstall alsa-base, alsa-utils, pulseaudio, pavucontrol many times 4) I've played with the options in the file /etc/modprobe.d/alsa-base.conf: a) I've tried to add "options snd-hda-intel model=auto" and I also tried different models: auto, clevo, laptop-eapd, clevo m-720, generic, basic and even z71v position_fix=1. 5) I've tried adding : Code: [General] description = Headphones + Digital Output (S/PDIF) in the file "/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf" 6) I've even tried a live USB stick with Ubuntu 19.04 (after reading somewhere that this was fixed on 19.04), but I found out that there was no sound on Ubuntu 19.04 as well. Also, you can find my ALSA information here: http://alsa- project.org/db/?f=bcdf5c8be31ce8b9e848a29ef292e9125f26def0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jproberge 1737 F pulseaudio /dev/snd/controlC0: jproberge 1737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:37:29 2019 InstallationDate: Installed on 2019-06-15 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1236 F pulseaudio jproberge 1737 F pulseaudio /dev/snd/controlC0: gdm1236 F pulseaudio jproberge 1737 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08P dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08P:bd05/07/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833161/+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 1823474] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- 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/1823474 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Expired Bug description: frequently fails; Devon:~$ systemctl status ssh * ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit-hit) since Sa 2019-04-06 17:42:35 CEST; 5min ago Process: 15706 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Apr 6 11:17:53 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-12-08 (119 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1823474/+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 1825380] Re: Add field architecture for "Other Software" entries
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1825380 Title: Add field architecture for "Other Software" entries Status in software-properties package in Ubuntu: Expired Bug description: Nowadays, many packages only offer amd64 versions and no i386 version (attribute [arch=amd64]). There is no way to specify this in software- properties-gtk! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1825380/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated) Status in lightdm package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated)
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated) Status in lightdm package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+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 1792164] Re: ImportError: /PATH/xxx.so: undefined symbol: PyFPE_jbuf
[Expired for python2.7 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: python2.7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1792164
Title:
ImportError: /PATH/xxx.so: undefined symbol: PyFPE_jbuf
Status in python2.7 package in Ubuntu:
Expired
Bug description:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
python2.7:
Installed: 2.7.15~rc1-1
Candidate: 2.7.15~rc1-1
-Python 2.7.15rc1 has the problem below ---
$ python
Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34)
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import fpectl
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named fpectl
>>> import sysconfig
>>> print sysconfig.get_config_var('CONFIG_ARGS')
'--enable-shared' '--prefix=/usr' '--enable-ipv6' '--enable-unicode=ucs4'
'--with-dbmliborder=bdb:gdbm' '--with-system-expat' '--with-computed-gotos'
'--with-system-ffi' 'CC=x86_64-linux-gnu-gcc' 'CFLAGS=-Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-nbjU53/python2.7-2.7.15~rc1=.
-fstack-protector-strong -Wformat -Werror=format-security '
'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro'
>>>
--while Python 2.7.12 has no problem
---
$ python
Python 2.7.12 (default, Dec 4 2017, 14:50:18)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import fpectl
>>> import sysconfig
>>> print sysconfig.get_config_var('CONFIG_ARGS')
'--enable-shared' '--prefix=/usr' '--enable-ipv6' '--enable-unicode=ucs4'
'--with-dbmliborder=bdb:gdbm' '--with-system-expat' '--with-computed-gotos'
'--with-system-ffi' '--with-fpectl' 'CC=x86_64-linux-gnu-gcc'
'CFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat
-Werror=format-security ' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro'
>>>
--
Please help to check '--with-fpectl'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1792164/+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 1385680] Re: Thinkpad X240 dock - no audio
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1385680 Title: Thinkpad X240 dock - no audio Status in alsa-driver package in Ubuntu: Expired Bug description: After connecting a thinkpad x240 to lenovo's ultra dock, an audio cable plugged into the dock's jack does not yield any sound output. This bug is very similar to bug #1265344 and was also reported at [1] and more context is available at [2]. Maybe it is sufficient to extend [3] to the x240 model? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1150594 [2] https://github.com/leoluk/thinkpad-stuff/wiki/Haswell-ThinkPad-problems#linux-docking-station-audio-compatibility [3] http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=1c37c22332a2d2c1b4ab32177a4f847c7fe06e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1385680/+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 1825940] Re: [graphics] Enable ICL
linux-oem-osp1 has backports in bionic-proposed ** Changed in: linux-oem-osp1 (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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1825940 Title: [graphics] Enable ICL Status in intel: Fix Committed Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Bug description: [Impact] Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based on 18.04.3 graphics stack with linux-oem-osp1 kernel. [Test case] The usual desktop usage, graphics tests etc. [Regression potential] Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and it can't regress any currently running system. Mesa backports are limited to ICL, so they shouldn't regress earlier generations either. -- Original description: ICL graphics is not enabled in 19.04. if you want to use 19.04 on ICL platform, you need do like this Add kernel option i915.alpha_support=1 Target Release:19.10 Target Kernel: 5.2 Target Mesa: 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1825940/+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 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
Will anything be done here? This basically breaks keepalived for bionic. I.e, will keepalived >= 2.0.x be available for bionic? -- 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/1819074 Title: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd Status in keepalived package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Systemd-networkd clobbers VIPs placed by other daemons on any reconfiguration triggering systemd-networkd restart (netplan apply for example). Keepalived < version 2.0.x will not restore a VIP lost in this fashion, breaking high availability on Ubuntu 18.04 LTS. A backport for keepalived >= 2.0.x should fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+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
