[Bug 1961557] [NEW] nagios4 is always stopped incorrectly, causing problems
Public bug reported: This is a bug in the init script of the nagios4 daemon, /etc/init.d/nagios4, part of the nagios4-common package. I found this bug in version 4.3.4-3 of that package, on Ubuntu server 20.04.3 LTS. The nagios4 deamon is always stopped by 'kill -9'. Because this happens after a timeout, this is: - slow - causes unintended side effects, the main one of which is that the nagios4 retention.dat file is not written on stopping the daemon. This means that on restart of the daemon, host and service states will have reverted back to what they were the last time the retention.dat was written (by default this happens once every hour, and on stopping the daemon). The cause of the issue is with line 149 of the init script /etc/init.d/nagios4: killproc -p $THEPIDFILE This is missing '$NAME', and should read: killproc -p $THEPIDFILE $NAME Fixing this allows for correctly stopping the nagios4 daemon. Note that I found the solution in the Debian bug tracker: https://www.mail-archive.com/search?l=debian-bugs- d...@lists.debian.org=subject:%22Bug%23992842%5C%3A+Slow+stop+due+to+killproc+in+%5C%2Fetc%5C%2Finit.d%5C%2Fnagios4%22=newest=1, so maybe this has been fixed upstream already. ** Affects: nagios4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961557 Title: nagios4 is always stopped incorrectly, causing problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios4/+bug/1961557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952797] [NEW] missing keyring dependency
Public bug reported:
After installing twine (apt install twine), running "twine upload" causes the
error:
Traceback (most recent call last):
File "/usr/bin/twine", line 11, in
load_entry_point('twine==3.1.1', 'console_scripts', 'twine')()
File "/usr/lib/python3/dist-packages/twine/__main__.py", line 25, in main
return dispatch(sys.argv[1:])
File "/usr/lib/python3/dist-packages/twine/cli.py", line 72, in dispatch
main = registered_commands[args.command].load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2445,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2451,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/twine/commands/upload.py", line 20, in
from twine import settings
File "/usr/lib/python3/dist-packages/twine/settings.py", line 22, in
from twine import auth
File "/usr/lib/python3/dist-packages/twine/auth.py", line 6, in
import keyring
ModuleNotFoundError: No module named 'keyring'
** Affects: twine (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952797
Title:
missing keyring dependency
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/twine/+bug/1952797/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1939951] Re: package ubuntu-advantage-tools 17 failed to install/upgrade: new ubuntu-advantage-tools package pre-installation script subprocess returned error exit status 1
I don't believe I can. After sending in this bug report I did a clean reinstall of ubuntu 20.04 and then cherry picked the files I wanted to transfer over from the HDD. I can say that neither my current configuration nor the backup has the files listed. Best, Michael From: nore...@launchpad.net on behalf of Lucas Albuquerque Medeiros de Moura <1939...@bugs.launchpad.net> Sent: Monday, August 16, 2021 08:17 To: MICHAEL JEFFREY GERARD Subject: [Bug 1939951] Re: package ubuntu-advantage-tools 17 failed to install/upgrade: new ubuntu-advantage-tools package pre-installation script subprocess returned error exit status 1 Hi Michael, looking at this issue, it seems that the problem is being caused by by the preinst script. When inspecing the preinst script in the package, I have found this: -- #!/bin/sh set -e # Automatically added by dh_installdeb/11.1.6ubuntu2 dpkg-maintscript-helper rm_conffile /etc/update-motd.d/99-esm 19.1~ ubuntu-advantage-tools -- "$@" # End automatically added section # Automatically added by dh_installdeb/11.1.6ubuntu2 dpkg-maintscript-helper rm_conffile /etc/update-motd.d/80-esm 19.1~ ubuntu-advantage-tools -- "$@" # End automatically added section # Automatically added by dh_installdeb/11.1.6ubuntu2 dpkg-maintscript-helper rm_conffile /etc/update-motd.d/80-livepatch 19.1~ ubuntu-advantage-tools -- "$@" # End automatically added section # Automatically added by dh_installdeb/11.1.6ubuntu2 dpkg-maintscript-helper rm_conffile /etc/cron.daily/ubuntu-advantage-tools 19.1~ ubuntu-advantage-tools -- "$@" # End automatically added section # Automatically added by dh_installdeb/11.1.6ubuntu2 dpkg-maintscript-helper rm_conffile /etc/init/ua-auto-attach.conf 20.2~ ubuntu-advantage-tools -- "$@" # End automatically added section ~ - It is trying to remove some config files related to the package. Can you verify if you have any of those files in your system ? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1939951 Title: package ubuntu-advantage-tools 17 failed to install/upgrade: new ubuntu-advantage-tools package pre-installation script subprocess returned error exit status 1 Status in ubuntu-advantage-tools package in Ubuntu: New Bug description: I backed up my Ubuntu 18.04 system on an HDD, installed Ubuntu 20.04 on a new computer and then attempted to restore my file system from my backup. After rsyinc-ing, I attempted to give "sude apt-get update && apt-get upgrade -y", which failed on both accounts. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ubuntu-advantage-tools 17 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Sat Aug 14 09:26:34 2021 Dependencies: ErrorMessage: new ubuntu-advantage-tools package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-10-23 (660 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: ubuntu-advantage-tools Title: package ubuntu-advantage-tools 17 failed to install/upgrade: new ubuntu-advantage-tools package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-10-08 (309 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1939951/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939951 Title: package ubuntu-advantage-tools 17 failed to install/upgrade: new ubuntu-advantage-tools package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1939951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939951] [NEW] package ubuntu-advantage-tools 17 failed to install/upgrade: new ubuntu-advantage-tools package pre-installation script subprocess returned error exit status 1
Public bug reported: I backed up my Ubuntu 18.04 system on an HDD, installed Ubuntu 20.04 on a new computer and then attempted to restore my file system from my backup. After rsyinc-ing, I attempted to give "sude apt-get update && apt-get upgrade -y", which failed on both accounts. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ubuntu-advantage-tools 17 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Sat Aug 14 09:26:34 2021 Dependencies: ErrorMessage: new ubuntu-advantage-tools package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-10-23 (660 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: ubuntu-advantage-tools Title: package ubuntu-advantage-tools 17 failed to install/upgrade: new ubuntu-advantage-tools package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-10-08 (309 days ago) ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939951 Title: package ubuntu-advantage-tools 17 failed to install/upgrade: new ubuntu-advantage-tools package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1939951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927998] [NEW] Jitter/noise in document scan
Public bug reported: Ubuntu 21.04 Documentscanner 3.38.1 When using the documentscanner about 10 times, without restarting the app, closing the previous scan (delete button), starting a new scan everytime, the background window (white) shows jitter/noise (in black) which will stay there every next scan. It may even become worse. The noise become part of the actual scan too! You will have to stop the app and reconnect the scanner. I've noticed this problem to be reproducable. See attached screen output. Kind regards, Gerard van Drielen ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "Schermafdruk van 2021-05-09 10-37-51.png" https://bugs.launchpad.net/bugs/1927998/+attachment/5496206/+files/Schermafdruk%20van%202021-05-09%2010-37-51.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927998 Title: Jitter/noise in document scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1927998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925991] [NEW] package ubuntu-release-upgrader-gtk 1:20.04.31 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: Voici ce que le terminal dit pendant une tentative d'upgrader vers Ubuntu 21.04; les données compressées sont corrompues dpkg-deb: erreur: subprocess returned error exit status 2 dpkg: erreur de traitement de l'archive /var/cache/apt/archives/ubuntu-release-u pgrader-gtk_1%3a20.04.32_all.deb (--unpack) : dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Vous pouvez lancer « apt --fix-broken install » pour corriger ces problèmes. Les paquets suivants contiennent des dépendances non satisfaites : ubuntu-release-upgrader-gtk : Dépend: ubuntu-release-upgrader-core (= 1:20.04.31) mais 1:20.04.32 est installé Dépend: python3-distupgrade (= 1:20.04.31) mais 1:20.04.32 est installé E: Dépendances non satisfaites. Essayez « apt --fix-broken install » sans paquet (ou indiquez une solution). agusti@agusti-F2M85P:~$ sudo apt J'ai realise apt -- fix-broken install , je vais redemarrer pour voir ce qui va ce passer. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-gtk 1:20.04.31 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: ubuntu-release-upgrader-gtk:amd64: Install ubuntu-release-upgrader-core:amd64: Install python3-distupgrade:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Sat Apr 24 08:14:40 2021 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-20 (34 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: ubuntu-release-upgrader Title: package ubuntu-release-upgrader-gtk 1:20.04.31 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925991 Title: package ubuntu-release-upgrader-gtk 1:20.04.31 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1925991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916641] [NEW] system service remains active if daemon fails
Public bug reported: Attempting to start the cachefiles service when /etc/default/cachefilesd has #RUN=yes commented out: systemctl start cachefilesd.service Leaves service "active" even though the daemon fails: systemctl status cachefilesd.service ● cachefilesd.service - LSB: CacheFiles daemon Loaded: loaded (/etc/init.d/cachefilesd; generated) Active: active (exited) since Tue 2021-02-23 13:24:57 EST; 1min 15s ago Docs: man:systemd-sysv-generator(8) Process: 26346 ExecStop=/etc/init.d/cachefilesd stop (code=exited, status=0/SUCCESS) Process: 26360 ExecStart=/etc/init.d/cachefilesd start (code=exited, status=0/SUCCESS) Feb 23 13:24:57 gerarddaily systemd[1]: Starting LSB: CacheFiles daemon... Feb 23 13:24:57 gerarddaily cachefilesd[26360]: * cachefilesd disabled, please set RUN=yes in /etc/default/cachefilesd Feb 23 13:24:57 gerarddaily systemd[1]: Started LSB: CacheFiles daemon. Feb 23 13:25:53 gerarddaily cachefilesd[26273]: Daemon Terminated This leads systemd to ignore future "start" commands even after then problem is fixed. Systemd services typically report a failure, not "Success" when their daemon fails to start. Work around: manually stopping and then starting service, or systemctl restart cachefilesd restarts the service. lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 apt-cache policy cachefilesd cachefilesd: Installed: 0.10.10-0.1ubuntu0.18.04.1 Candidate: 0.10.10-0.1ubuntu0.18.04.1 Version table: *** 0.10.10-0.1ubuntu0.18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 100 /var/lib/dpkg/status 0.10.10-0.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ** Affects: cachefilesd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916641 Title: system service remains active if daemon fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/1916641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression
The proposed solution fixes the bug I filed when joining against older Windows Active Directory servers. (https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1906673) i.e. The domain join works without the --use-ldaps. We do not currently have the correct certificate set up to use --use- ldaps, so I am not currently able exercise that test case. (Thank you to the Ubuntu team for the rapid response.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906627 Title: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1906627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906673] [NEW] Realm join hangs
Public bug reported: Following update sssd/bionic-updates,bionic-security,now 1.16.1-1ubuntu1.7 to the sssd et. al. packages, our realm joins not longer work. They hang at the step: root@dec03daily:~# realm join ourdomain.net -U admin-acct -v * Resolving: _ldap._tcp.ourdomain.net * Performing LDAP DSE lookup on: 0.0.0.01 * Performing LDAP DSE lookup on: 0.0.0.00 * Successfully discovered: ourdomain.net Password for admin-acct: * Unconditionally checking packages * Resolving required packages * LANG=C /usr/sbin/adcli join --verbose --domain ourdomain.net --domain-realm OURDOMAIN.NET --domain-controller 0.0.0.01 --login-type user --login-user admin-acct --stdin-password * Using domain name: ourdomain.net * Calculated computer account name from fqdn: DEC03DAILY * Using domain realm: ourdomain.net * Sending netlogon pings to domain controller: cldap://0.0.0.01 * Received NetLogon info from: ad2.ourdomain.net * Wrote out krb5.conf snippet to /var/cache/realmd/adcli-krb5-CxSBIC/krb5.d/adcli-krb5-conf-7CIGrq * Authenticated as user: admin-a...@ourdomain.net * Using GSS-SPNEGO for SASL bind (site specific identity data obfuscated) root@dec03daily:~# lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 root@dec03daily:~# apt-cache policy sssd sssd: Installed: 1.16.1-1ubuntu1.7 Candidate: 1.16.1-1ubuntu1.7 Version table: *** 1.16.1-1ubuntu1.7 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.16.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Note: we have been using prior versions of the sssd / realm et. al. packages to automatically build / domain join VMs for the past couple years; our process just stopped working with 1.16.1-1ubuntu1.7 update. ** Affects: sssd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906673 Title: Realm join hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1906673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905779] [NEW] mise à jour vers 20.04 depuis 18 impossible
Public bug reported: Je n'y connais rien... Donc je ne parviens pas à effectuer la mise à jour vers 20 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Thu Nov 26 20:07:46 2020 InstallationDate: Installed on 2018-12-22 (705 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-11-26 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905779 Title: mise à jour vers 20.04 depuis 18 impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1905779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673438] Re: update-grub: cannot restore the original directory
A nicer error message would be nice. Or use /tmp for tempfiles instead of current working directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/673438 Title: update-grub: cannot restore the original directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/673438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899831] [NEW] bionic python3-pip does not use alternate repositories
Public bug reported: Please see https://bugs.launchpad.net/ubuntu/+source/python- pip/+bug/1833229 . I have no idea why it was marked "fixed" in May, because it still active in bionic. ** Affects: python-pip (Ubuntu) Importance: Undecided Status: New ** Tags: bionic python3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899831 Title: bionic python3-pip does not use alternate repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1899831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833229] Re: `--extra-index-url` not working for PIP
Yesterday's (10-13) update of the PPA has broken the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833229 Title: `--extra-index-url` not working for PIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1833229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833229] Re: `--extra-index-url` not working for PIP
To stop automatic updates from overwriting the bug fix version of python3-pip, create file /etc/apt/preferences.d/citrain-pin-700 with the following content: Package: python3-pip Pin: origin "ppa.launchpad.net" Pin-Priority: 700 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833229 Title: `--extra-index-url` not working for PIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1833229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833229] Re: `--extra-index-url` not working for PIP
It appears the ppa is no longer "just working" because the mainline bionic Ubuntu version of python3-pip has incremented. That is to say, even after adding the ppa and doing apt update, apt-get install pulls the buggy one from the mainline repo. I was able to get the right version by using: apt install python3-pip=9.0.1-2.3~ubuntu1.18.04.2~ubuntu18.04.1~ppa202002141134 python-pip-whl=9.0.1-2.3~ubuntu1.18.04.2~ubuntu18.04.1~ppa202002141134 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833229 Title: `--extra-index-url` not working for PIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1833229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551949]
Yes, please; let's get back to the core issue. The Firefox print function does not save functioning hyperlinks when the output is PDF. I dislike having to switch to Chromium (I use Linux) to create a PDF with functioning hyperlinks. Can we please get Firefox to create a PDF with hyperlinks that work? As far as I'm concerned, it can be under either the 'Save Page As ...' menu item or the 'Print ...' menu item this bug was opened under. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551949 Title: Printing to PDF file loses URLs/links To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1551949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720693] Re: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all
** Changed in: alsa-driver (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720693 Title: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1720693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833229] Re: `--extra-index-url` not working for PIP
To make this copy-and-paste obvious for the next person to come by: add-apt-repository ppa:ci-train-ppa-service/3690 apt update apt install python3-pip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833229 Title: `--extra-index-url` not working for PIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1833229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867195] Re: vlc crashed with SIGSEGV playing music from SMB share
Additional note: the kernel is 5.5.8 from the kernel-ppa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867195 Title: vlc crashed with SIGSEGV playing music from SMB share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1867195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867195] [NEW] vlc crashed with SIGSEGV playing music from SMB share
Public bug reported: using Xubuntu 20.04 preview, vlc crashed when playing music from a SMB share via gvfs - it just did this twice in a row ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: vlc-bin 3.0.8-4 Uname: Linux 5.5.8-050508-generic x86_64 NonfreeKernelModules: 8723bu ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CrashCounter: 1 CurrentDesktop: XFCE Date: Thu Mar 12 18:20:24 2020 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2020-03-07 (5 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f5549a7c065: movdqu (%rdi),%xmm10 PC (0x7f5549a7c065) ok source "(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%xmm10" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: vlc StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgnutls.so.30 ?? () from /lib/x86_64-linux-gnu/libgnutls.so.30 ?? () from /lib/x86_64-linux-gnu/libgnutls.so.30 ?? () from /lib/x86_64-linux-gnu/libgnutls.so.30 ?? () from /lib/x86_64-linux-gnu/libgnutls.so.30 Title: vlc crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash focal need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867195 Title: vlc crashed with SIGSEGV playing music from SMB share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1867195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
Disregard. Looks like 4.15.0.1048 is installed but running uname -a shows 4.15.0.1047 so the box just hasn't been rebooted since the update and since it's an AWS ASG it's just reverting back to the 1047 version from the AMI every time it panics and AWS re-creates the instance. Time to rebuild the AMI with the new kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
I'm seeing the same kernel panic on linux-aws 4.15.0.1048.47 as well -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833415] [NEW] Version.sha256 throws SystemError
Public bug reported: Attempting to access the property raised the exception 'SystemError: error return without exception set' The error occurs when version._records.hashes.file_size == 0. The package occurred on (cups=2.2.7-1ubuntu2.5) on an Ubnuntu 18.04.2 LTS system ; attempting to download the source *deb file failed. Doing an apt-get clean / apt-get update / apt upgrade seemed to make the problem go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-apt 1.6.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 19 08:20:32 2019 InstallationDate: Installed on 2019-06-05 (13 days ago) InstallationMedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python-apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot showing object state in PyCharm debugger" https://bugs.launchpad.net/bugs/1833415/+attachment/5271571/+files/badhash.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833415 Title: Version.sha256 throws SystemError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1833415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829767] [NEW] upgrade to ubuntu 16 from 14 failed
Public bug reported: Upgrade from ubuntu 14 using update-manager failed. Console log follows : Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Building data structures... Done Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This can be caused by: * Upgrading to a pre-release version of Ubuntu * Running the current pre-release version of Ubuntu * Unofficial software packages not provided by Ubuntu If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done Building data structures... Done gerard@ASUS-HP-UB:~$ sudo ubuntu-bug ubuntu-release-upgrader-core (apport-gtk:15348): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. (firefox:15645): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.11 ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-80-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CrashDB: ubuntu Date: Mon May 20 16:39:21 2019 InstallationDate: Installed on 2015-09-25 (1332 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2019-05-20 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829767 Title: upgrade to ubuntu 16 from 14 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1829767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774645] Re: mount.cifs with sec=krb5 fails with No such file or directory
Thanks for the solution, this was no fun to debug on multiple servers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774645 Title: mount.cifs with sec=krb5 fails with No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1774645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806219] [NEW] package uuid-runtime 2.31.1-0.4ubuntu3.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1
Public bug reported: First time upgrade, fresh Bionic Beaver instance ProblemType: Package DistroRelease: Ubuntu 18.04 Package: uuid-runtime 2.31.1-0.4ubuntu3.2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Dec 1 19:29:07 2018 ErrorMessage: installed uuid-runtime package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-11-29 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: util-linux Title: package uuid-runtime 2.31.1-0.4ubuntu3.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806219 Title: package uuid-runtime 2.31.1-0.4ubuntu3.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1806219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772643] [NEW] package libdrm-intel1 2.4.83-1~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdrm-intel1/changelog.Debian.gz', which is different from other insta
Public bug reported: I cannot update becuase of some problem with tird party programs, howeve I deleted all of them an it is still occurring. It also appears a new user called LibvirtQuemu. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm-intel1 2.4.83-1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 814676/58728448 files, 20595592/234904576 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue May 22 13:14:54 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu DpkgHistoryLog: Start-Date: 2018-05-22 13:14:47 Commandline: apt-get install -f Install: libdrm-nouveau2:i386 (2.4.83-1~16.04.1, automatic), libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, automatic), libdrm2:i386 (2.4.83-1~16.04.1, automatic), libdrm-intel1:i386 (2.4.83-1~16.04.1, automatic), libdrm-radeon1:i386 (2.4.83-1~16.04.1, automatic) DuplicateSignature: package:libdrm-intel1:2.4.83-1~16.04.1 Unpacking libdrm2:i386 (2.4.83-1~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm2_2.4.83-1~16.04.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libdrm2/changelog.Debian.gz', which is different from other instances of package libdrm2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libdrm-intel1/changelog.Debian.gz', which is different from other instances of package libdrm-intel1:i386 GraphicsCard: NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF119 [NVS 310] [10de:1154] InstallationDate: Installed on 2017-09-30 (234 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision Tower 3620 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic.efi.signed root=UUID=bfbdba95-820f-486c-973f-e217079d780f ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: libdrm Title: package libdrm-intel1 2.4.83-1~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdrm-intel1/changelog.Debian.gz', which is different from other instances of package libdrm-intel1:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.5 dmi.board.name: 0MWYPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.5:bd08/06/2017:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 22 11:05:19 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 package-conflict third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772643 Title: package libdrm-intel1 2.4.83-1~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdrm- intel1/changelog.Debian.gz', which is different from other instances of package libdrm-intel1:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1772643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic
Hi, I am also affected by this bug but not on a Lenovo or Thinkpad laptop. Mine is an Asus Zenbook UX301L running Ubuntu 17.10. Latest working kernel version is 4.13.0-36-generic. Patches 37 and 38 cause the freeze on boot. Adding option noibpb solves the issue (at least with 4.13.0-38-generic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746418 Title: System freezes when starting Xorg after installing linux- image-4.13.0-32-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
Proposed update fixed the issue, thanks. product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation $ apt policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 17.2.4-0ubuntu1~16.04.4 Candidate: 17.2.4-0ubuntu1~16.04.4 Version table: *** 17.2.4-0ubuntu1~16.04.4 400 400 http://fr.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 17.2.4-0ubuntu1~16.04.2 500 500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 11.2.0-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740501] [NEW] package manpages 3.65-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/mtrace.1.gz', which is also in package libc-dev-bin 2.19-10ubuntu2
Public bug reported: cant install anything ProblemType: Package DistroRelease: Ubuntu 17.10 Package: manpages 3.65-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Fri Dec 29 08:34:18 2017 Dependencies: DuplicateSignature: package:manpages:3.65-1ubuntu1:trying to overwrite '/usr/share/man/man1/mtrace.1.gz', which is also in package libc-dev-bin 2.19-10ubuntu2 ErrorMessage: trying to overwrite '/usr/share/man/man1/mtrace.1.gz', which is also in package libc-dev-bin 2.19-10ubuntu2 InstallationDate: Installed on 2017-12-29 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: manpages Title: package manpages 3.65-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/mtrace.1.gz', which is also in package libc-dev-bin 2.19-10ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: manpages (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740501 Title: package manpages 3.65-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/mtrace.1.gz', which is also in package libc-dev-bin 2.19-10ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1740501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729305] Re: CouchDB service fails to start
Also, if you're so inclined, I now have CouchDB 1.7.0 test packages for Artful here: https://launchpad.net/~jderose/+archive/ubuntu/couchdb-1.7.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729305 Title: CouchDB service fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/1729305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729305] Re: CouchDB service fails to start
Devin, Thanks for the bug report! CouchDB 1.6.x doesn't work with the Erlang 20.0.4 packages in Artful. I've been working on CouchDB 2.1 packages for Artful for internal use at System76, but it's a much different beast in many ways and also has upstream packaging changes that make it very difficult (if not impossible) to get it into Ubuntu as an official package (even just in universe). However, the just announced CouchDB 1.7.0 RC is promising: https://lists.apache.org/thread.html/30162c3c859cf0dc66d489ae416a2e0e4f2fedecdf892b62c484abc7@%3Cdev.couchdb.apache.org%3E I'm currently testing it. Assuming I don't hit any deal breakers, I'm going to try and get this package into Bionic, and might also be able to get it released in Artful as the current CouchDB 1.6.0 package isn't usable in Artful (as you know). If you happen to spend any time testing 1.7.0, please let me know what your experience is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729305 Title: CouchDB service fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/1729305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637779] Re: ext4 filesystem fails randomly with checksum error
First of all thank you very much for your quickly response. I am glad to say you we fixed that issue thanks to your post :) The problem was we formatted the disk (sb5) using some tool from newer Ubuntu version which put metadata_csum feature on it. And because using on Ubuntu 14.04 it had some trouble with it. We also realize that the warning message on every reboot was for the impossibility to perform a fsck due to incompatibility with metdata_csum feature. Summarizing, we did the following: 1 - Fix checksum errors using SystemRescue live CD and executing the e2fsck tool (1.43.3 which is fully compatible with metadata_csum. 2 - Once we were sure there were not any error, we proceed disabling metadata_csum, using "tune2fs -O ^metadata_csum /dev/sdb5" with the file system umounted (as you advised us). 3 - Once boot up, it made a fsck successfully and no more warnings about disck errors. Thank you very much! Greetings -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637779 Title: ext4 filesystem fails randomly with checksum error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637779] Re: ext4 filesystem fails randomly with checksum error
We have an error quiet similar to this one reported. We are using Ubuntu 14.04 .. but I really think it's not a matter of version though. We are getting randomly the following errors: -- [97030.025645] EXT4-fs error (device sdb5): ext4_iget:4156: inode #26351669: comm apache2: checksum invalid -- It's more than one, just to keep it short ;) All of them are related to the same device sdb5, which we mount the '/var' partition. Having this errors, and trying to reboot, it gets stuck booting up when it tries to mount the '/var' partition, informing that errors have been found checking the partition. It shows up with different options (I (ignore) ,S (avoid mounting) ,M (fix manually). Either 'S' or 'M' are able to mount the partition without any trouble. But it's in every boot. We have tried to boot up from USB recovery tool, and repair those errors executing the following command: `e2fsck -y /dev/sdb5` with the result I attached. We have done it a couple of times, and after a random time these errors have showed up again. We also changed the disk (moving all the data from one to another) and it still happens the same. We would like to know the reason why it happens so randomly. And of course how to avoid those errors forever! ** Attachment added: "output_e2fsck" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+attachment/4920264/+files/errors_disk_backup_31.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637779 Title: ext4 filesystem fails randomly with checksum error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637779] Re: ext4 filesystem fails randomly with checksum error
Sorry I attached a wrong file, this one is the correct one! ** Attachment added: "e2fsck_output_ok" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+attachment/4920266/+files/error_32_1.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637779 Title: ext4 filesystem fails randomly with checksum error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697202] [NEW] package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1692042 *** https://bugs.launchpad.net/bugs/1692042 Public bug reported: cada rato me pide contraseña pára actualizar. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-79-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gerard 2014 F pulseaudio Date: Fri May 19 23:35:25 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=595a38ce-6c58-4906-9682-d2a981202920 InstallationDate: Installed on 2017-02-15 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E6510 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=81b6d11a-7392-4e00-9b63-d562bfae34bd ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9 SourcePackage: linux Title: package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/26/2011:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697202 Title: package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685699] [NEW] package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Received this error after login after a new install of ubuntu 17.04 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23' .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c: Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c' ApportVersion: 2.20.4-0ubuntu4 AptOrdering: shim:amd64: Install shim-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 BootEFIContents: fw fwupx64.efi Date: Mon Apr 24 17:01:01 2017 EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: EFI variables are not supported on this system. ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: shim-signed Title: package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685699 Title: package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1685699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681957] [NEW] package libwebkit2gtk-4.0-37:amd64 2.16.1-0ubuntu0.16.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: SE BLOQUEA MI MAQUINA, AL INSTALAR CROSSOVER ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libwebkit2gtk-4.0-37:amd64 2.16.1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Apr 11 16:48:01 2017 DuplicateSignature: package:libwebkit2gtk-4.0-37:amd64:2.16.1-0ubuntu0.16.04.1 Installing from local file /var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20170411.1.orig.tar.gz Flash Plugin installed. dpkg: error al procesar el paquete libjavascriptcoregtk-4.0-18:amd64 (--configure): El paquete está en un estado grave de inconsistencia - debe reinstalarlo ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2017-03-20 (22 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: webkit2gtk Title: package libwebkit2gtk-4.0-37:amd64 2.16.1-0ubuntu0.16.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681957 Title: package libwebkit2gtk-4.0-37:amd64 2.16.1-0ubuntu0.16.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1681957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565106] Re: Wifi works on W10 but not on Ub 16.04 nor 14.04
sorry, I just realize I did not post w/ the same Id. In order not to raise confusion winux = gerard -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565106 Title: Wifi works on W10 but not on Ub 16.04 nor 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565106] Re: Wifi works on W10 but not on Ub 16.04 nor 14.04
Hi Christopher As I already said, but surprising not stated here: - I've installed 17.04 beta one week ago - wifi works beautifully I could say - solved on the "17.04 non LTS" - BUT not solved on the "16.04 LTS" which I would like to use till the end of support (another 4 years) What is the difference that made it work on 17.04 but still not on the 16.04? Anyway we made a big step forward!! Thanks to the development team that accomplish miracles !!! I love Ubuntu and convinced a lot of people moving to it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565106 Title: Wifi works on W10 but not on Ub 16.04 nor 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672312] [NEW] package libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/40-libsane.rules'
*** This bug is a duplicate of bug 1667085 *** https://bugs.launchpad.net/bugs/1667085 Public bug reported: Je suis français. Je ne comprends RIEN à ce qui est écrit. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 13 10:11:48 2017 DuplicateSignature: package:libsane:1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] Unpacking libsane:i386 (1.0.25+git20150528-1ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/libsane_1.0.25+git20150528-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from other instances of package libsane:i386 ErrorMessage: trying to overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from other instances of package libsane:i386 InstallationDate: Installed on 2017-02-08 (32 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: sane-backends Title: package libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from other instances of package libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672312 Title: package libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from other instances of package libsane:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1672312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663299] [NEW] 16.04.2: `linux-signed-image-generic-hwe-16.04` is autoremovable after UEFI install
Public bug reported: Steps to reproduce: 1) Fresh UEFI install using 20170209 16.04.2 daily ISO (sha1sum: 93378778ba193f6fbcac222a8d60a4bae52c94e8) 2) Reboot into install and run `sudo apt-get autoremove` Thanks! ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663299 Title: 16.04.2: `linux-signed-image-generic-hwe-16.04` is autoremovable after UEFI install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1663299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632273] Re: Thunderbird crash after update
Hello. I Still have this problem with Thunderbird on Ubuntu 16.10 : - with 1 gmail account, Thunderbird is ok - with 2 gmail accounts, Thunderbird crashes. However my Thunderbird package is 1:45.5.1+build1-0ubuntu0.16.10.1. I have the same bug on Ubuntu 14.04. So the bug hasn't been fixed... Any solution ? Thank you. Bye. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632273 Title: Thunderbird crash after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1632273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Mathieu, Okay, just finished testing with xenial-proposed, no issues found. Things are working as expected for my use-case (with no adjustments on my end), so at least for the corners that my particular use-cases covers, this proposed package seems regression free. I tested PXE booting into a "diskless" read-only Ubuntu server environment (using syslinux as the bootloader). Tested in both BIOS and UEFI mode. Sorry it took me a bit to do this follow-up testing! Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
Steve, I'm not sure whether it was a truly representative test, but it works fine with latest Xenial daily desktop ISO under QEMU + OVMF, and these dailies do have xenial-proposed enabled. (I'm testing the 2016 ISO, sha1sum 0ed4db8dad7142837ce9175e2b9617c4dd93a326.) I recall that d-i needed to be rebuilt for a new shim to be properly represented in an ISO... has this happened yet? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Mathieu, I tested your PPA package with Xenial: with no config changes on my end, it's working as expected from my use case. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637985] Re: Install Fail - Attempt to configure apt to install additional packages from CD
FYI, same thing is happening with the latest Zesty server ISO (see attached). ** Attachment added: "Screenshot from 2016-10-31 14-32-09.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1637985/+attachment/4770253/+files/Screenshot%20from%202016-10-31%2014-32-09.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637985 Title: Install Fail - Attempt to configure apt to install additional packages from CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1637985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637985] Re: Install Fail - Attempt to configure apt to install additional packages from CD
Attaching tarbal of /var/log from lp:1638086 ** Attachment added: "log.tgz" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1637985/+attachment/4770249/+files/log.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637985 Title: Install Fail - Attempt to configure apt to install additional packages from CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1637985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638086] Re: Zesty: An attempt to configure apt to install additional packages from the CD failed
*** This bug is a duplicate of bug 1637985 *** https://bugs.launchpad.net/bugs/1637985 Attaching tarball of /var/log ** Attachment added: "log.tgz" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1638086/+attachment/4770250/+files/log.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638086 Title: Zesty: An attempt to configure apt to install additional packages from the CD failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1638086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638086] [NEW] Zesty: An attempt to configure apt to install additional packages from the CD failed
Public bug reported: The current Zesty daily desktop ISO can't be installed, fails with error message in bug title. Please see attached screenshot. I tried both "Install Ubuntu" and an OEM install, both fail. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2016-10-31 11-59-34.png" https://bugs.launchpad.net/bugs/1638086/+attachment/4770232/+files/Screenshot%20from%202016-10-31%2011-59-34.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638086 Title: Zesty: An attempt to configure apt to install additional packages from the CD failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1638086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248870] Re: [Upstream] Autosave causes document to scroll back to cursor position
And still present in version 5.1.4.2, under Linux version 4.4.0-36-generic (buildd@lcy01-01) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 Very annoying, had a similar problem with jEdit, which I could solve. It is a very annoying behaviour -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/248870 Title: [Upstream] Autosave causes document to scroll back to cursor position To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/248870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636207] [NEW] Patch proposal to do not apply symbolic links included in zip files.
Public bug reported: Zip files might include symbolic links which could be abused by an attacker to escape from restricted directories and/or from restricted environments. The attached patch includes a command line option -g which does not apply the symbolic links when zip file is extracted. In case a zip file includes a symbolic link a file is created instead containing the target of the symbolic link. ** Affects: unzip (Ubuntu) Importance: Undecided Status: New ** Patch added: "do_not_apply_symlinks.patch" https://bugs.launchpad.net/bugs/1636207/+attachment/4766457/+files/do_not_apply_symlinks.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636207 Title: Patch proposal to do not apply symbolic links included in zip files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/1636207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Okay, tested 0.122ubuntu8.5 from xenial-proposed, and it fixes the issue for my use-case. But I'm not changing verification-needed to verification-done yet as I don't know if it fixes the use case of the original reporter. @scotte - can you please confirm whether this fixes things for you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632767] Re: yakkety: desktop ISO fails to reboot after install: Failed deactivating swap
@jbicha hmm, I didn't experience this with the final Ubuntu desktop 16.10 ISOs... what was your experience with the final 16.10 Ubuntu GNOME ISOs? But I also don't think this is happening with perfect determinism either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632767 Title: yakkety: desktop ISO fails to reboot after install: Failed deactivating swap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Oh, and to be clear, I have no problem with this change in Yakkety. It's just starting to feel a bit too invasive in my opinion for Xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
@martin - I tested the proposed package, and it's workable, but there are behavior changes still compared to prior to when this regression was introduced (in particular, the boot is a lot slower when there are mulitple NICs but only one will be configured, even when I use "ip=:eth0:dhcp"). @scott - I think I agree with you. Considering this is an SRU for the LTS, I'd prefer that as little behavior change be introduced as possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Attaching a tarbal of everything i have in /var/log, not sure it's useful (not my "ephemeral" environment is read-only with /var/log on a tmpfs, so it's mostly empty). Also here's my exact /proc/cmdline from within the booted ephemeral environment: BOOT_IMAGE=vmlinuz-4.4.0-42-generic initrd=initrd.img-4.4.0-42-generic root=/dev/nfs nfsroot=10.17.76.1:/var/lib/tribble/ephemeral ip=dhcp ro nomodeset net.ifnames=0 BOOTIF=01-80-fa-5b-36-f5-86 ** Attachment added: "log.tgz" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4760012/+files/log.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
@chiluk - I tested the latest package in your PPA, but something seems slightly wonky for my use case. Networking seems to come up correctly, but it takes longer than it should and I see warnings like this repeated several times: ip: ether "dev" is duplicate, or "permanent" is garbage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632767] [NEW] yakkety: desktop ISO fails to reboot after install: Failed deactivating swap
Public bug reported: The 20161012.1 yakkety desktop ISO fails to reboot after the install completes (see attached screenshot). Tested on QEMU in BIOS and UEFI mode, which is where the screenshot is from. Same thing is seemingly happening on hardware (reboot hangs), although I don't see this particular debugging output on hardware. The systemd related logging might be a red haring... I'm not sure this is actually a systemd bug, just that it seems the correct starting point. Thanks! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety ** Attachment added: "Screenshot from 2016-10-12 06-14-05.png" https://bugs.launchpad.net/bugs/1632767/+attachment/4759958/+files/Screenshot%20from%202016-10-12%2006-14-05.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632767 Title: yakkety: desktop ISO fails to reboot after install: Failed deactivating swap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
@chiluk - the package in your PPA fixes it from my use case, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
As asked by chiluk on IRC, here's my PXE boot configuration (well, representative one anyway, the exact kernel version will obviously change): DEFAULT ubuntu LABEL ubuntu LINUX vmlinuz-4.4.0-36-generic APPEND initrd=initrd.img-4.4.0-36-generic root=/dev/nfs nfsroot=10.17.76.1:/var/lib/tribble/ephemeral ip=dhcp ro nomodeset net.ifnames=0 IPAPPEND 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
So far I haven't encountered this again... so might have been a fluke with the state of Yakkety for a brief period, phase of the moon, or whatever. But if I do encounter it again, I'll collect as many details as I can. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
I'm back to testing u-s-d started under systemd, and I found some serious wackiness observing `sudo journalctl -f` when I use the brigtness up/down hotkeys. The attached "wacky-journalctl.txt" file has the output of `sudo journalctl -f` during which I used the brightness hotkeys *twice*, and you'll see a slew interesting things happening *each* time I press a hot key. For example, this is a small excerpt of what I'm seeing for every hotkey press: Oct 06 10:44:50 jason-Gazelle-Professional systemd[1]: Created slice User Slice of root. Oct 06 10:44:50 jason-Gazelle-Professional systemd[1]: Starting User Manager for UID 0... Oct 06 10:44:50 jason-Gazelle-Professional systemd[1]: Started Session 1 of user root. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: pam_unix(systemd-user:session): session opened for user root by (uid=0) Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Paths. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Starting D-Bus User Message Bus Socket. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Timers. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Listening on D-Bus User Message Bus Socket. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Sockets. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Basic System. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Starting Run Click user-level hooks... Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Started D-Bus User Message Bus. Oct 06 10:44:50 jason-Gazelle-Professional dbus-daemon[4839]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' ** Attachment added: "wacky-journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756139/+files/wacky-journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1626651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
`sudo forkstat -D 4` when u-s-d is started under systemd and I press the brightness up hotkey. ** Attachment added: "with-systemd.txt" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756099/+files/with-systemd.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1626651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
Okay, an interesting hint is that this problem seems to be fixed if
u-s-d is started under the Upstart user session instead of the systemd
user session.
If anyone wants to try this, just comment out these three lines in
/etc/X11/Xsession.d/00upstart:
if [ "${1#*.target}" != "$1" ]; then
export
XDG_CONFIG_DIRS="/usr/share/upstart/systemd-session:$XDG_CONFIG_DIRS"
fi
I'm attaching the result of me starting u-s-d under Upstart, running
`sudo forkstat -D 4`, and then pressing the brightness up key.
(I'll attach the same from under systemd next comment.)
>From talking to Martin Pitt on IRC, sounds like switching u-s-d back to
being started by Upstart might not be viable, but hopefully this at
least helps narrow the search.
** Attachment added: "with-upstart.txt"
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756098/+files/with-upstart.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626651
Title:
brightness keys are handled slower in Yakkety than Xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1626651/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
And I sanity checked the server ISO on the same slew of UEFI hardware... no issues found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
Okay, the 20161005.1 ISOs seem to have done the trick. Tested the desktop and server ISOs under QEMU+OVMF, plus tested the desktop ISO on a slew of UEFI hardware. No issues encountered shim-wise. I'll test the server ISO on UEFI hardware shortly, but there are a few other things I need to finish up first. Big thanks to everyone who helped on this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
Oops, I attached the wrong screenshot, here's the correct one. ** Attachment added: "Screenshot from 2016-10-05 12-06-26.png" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+attachment/4755346/+files/Screenshot%20from%202016-10-05%2012-06-26.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
** Attachment removed: "Screenshot from 2013-11-11 11:45:50.png" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+attachment/4755311/+files/Screenshot%20from%202013-11-11%2011%3A45%3A50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
Yeah, I can do this, assuming I can reproduce it again. This is on my work machine, so I had to just kill `fwupd` so I could get on with my work in the meantime :D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
One other useful detail. There are actually 2 fwupd processes running, both started by PID 1: ps -ef | grep fwupd root 2823 1 99 11:41 ?01:35:03 /usr/lib/x86_64-linux-gnu/fwupd/fwupd root 4712 1 0 11:44 ?00:00:00 /usr/lib/x86_64-linux-gnu/fwupd/fwupd But it's only process "2823" that's chewing up all the CPU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] [NEW] fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
Public bug reported: Just hit this, haven't yet dug into details or tried to reproduce it. I booted up a nearly up-to-date Yakkety desktop, noticed my fans were running like crazy, and looking at top shows `fwupd` is the culprit (see attached screenshot). I don't know much about fwupd, but I'm guessing it's probably run through systemd services. Interestingly, `systemctl status` show "inactive (dead)" for the two service files installed by `fwupd`: fwupd.service fwupd-offline-update.service I also checked `fwupdate-cleanup.service` from the `fwupdate` package, and it likewise shows "inactive (dead)". So I'm not exactly sure how this fwupd process was started, why it's still running. Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: fwupd 0.7.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 5 12:15:10 2016 SourcePackage: fwupd UpgradeStatus: Upgraded to yakkety on 2016-10-03 (1 days ago) ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "Screenshot from 2013-11-11 11:45:50.png" https://bugs.launchpad.net/bugs/1630711/+attachment/4755311/+files/Screenshot%20from%202013-11-11%2011%3A45%3A50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630341] Re: yakkety: behavior change in `qemu-nbd -c $DEV $FILENAME`: doesn't automatically create partion devices
Thanks for the feedback, Robie! I believe the underlying problem was this kernel bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628336 The /dev/nbd0p1, etc, partition devices were never getting creating automatically after connecting the device, no matter how long you waited. So you had to call partprobe, whereas on Xenial and older you didn't. And you bring up some good points about my scripts being fragile unless I do some sort of polling or using inotify (although in practice I haven't had problems with this). But I agree this shouldn't really be treated as a bug, should be marked invalid. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630341 Title: yakkety: behavior change in `qemu-nbd -c $DEV $FILENAME`: doesn't automatically create partion devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1630341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
Hmmm, today's yakkety-desktop-amd64.iso (sha1:494bc027be3d29c494eb17d057dcc51cdfc6f50b) is seemingly still using the broken shim package? I'm guessing there's something special about how the shim package gets onto the ISO as it doesn't seem to be listed in yakkety-desktop- amd64.manifest? But for whatever reason, I'm still getting the same exception when debugging with `-serial stdio`: X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - RIP - 7E64D5BA, CS - 0038, RFLAGS - 00010202 ExceptionData - RAX - AFAFAFAFAFAFAFAF, RCX - 7F1C5820, RDX - 7F1C5820 RBX - 7F132198, RSP - 7FB1BA40, RBP - 7FB1BAF0 RSI - 7E6DBD9A, RDI - 7E62CFBA R8 - 0004, R9 - , R10 - 0020 R11 - 0002, R12 - 7EEB34B8, R13 - 7EEB34C0 R14 - 7FB33620, R15 - 7EDD6018 DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 8033, CR2 - , CR3 - 7FABA000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 7FAA8698 0047, LDTR - IDTR - 7F5E4018 0FFF, TR - FXSAVE_STATE - 7FB1B6A0 Find PE image (No PDB) (ImageBase=7E62D000, EntryPoint=7E64A000) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630341] [NEW] yakkety: behavior change in `qemu-nbd -c $DEV $FILENAME`: doesn't automatically create partion devices
Public bug reported: On Ubuntu 12.10 through Ubuntu 16.04, something like this worked with 100% reliability in my experience: sudo modprobe nbd sudo qemu-nbd -c /dev/nbd0 /my/vm/image.qcow2 sudo mount /dev/nbd0p1 /mnt But on Yakkety, this *almost* always fails because the /dev/nbd0p1 device doesn't exist by the time the `sudo mount /dev/nbd0p1 /mnt` command is run. I found an existing Debian bug about this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824553 Unfortunately, I feel the bug reporter got the brush off there, but I can confirm that `qemu-nbd` previously worked exactly as the bug reporter claims (on Ubuntu anyway, not sure about Debian). I have automated tooling that has done this exact thing many thousands of times on Ubuntu 12.10 through 16.04 without issue. Although in defense of the Debian maintainer, my hunch is this behavior change likely isn't the result of changes in the `qemu-img` package itself. A curiosity of note is that although this usually fails on Yakkety, it did work for me a few times (in my testing thus far, I'd say it succeeds less than 5% of the time). I haven't yet found a way to reproduce these successful cases, nor have I yet spotted any pattern in the cases in which it works vs. cases in which it doesn't work. On Yakkety I can *mostly* work-around this by calling `sudo partprobe /dev/nbd0` prior to trying to mount the device: sudo modprobe nbd sudo qemu-nbd -c /dev/nbd0 /my/vm/image.qcow2 sudo partprobe /dev/nbd0 sudo mount /dev/nbd0p1 /mnt At first I thought this was a 100% reliable solution on Yakkety, but it still sometimes fails. I haven't had as much time testing this yet, but I'd say it probably succeeds 80% of the time or so, fails the remaining 20%. I hate to say it, but on the surface this feels like a systemd bug as I've encountered systemd + qemu-nbd problems in the past: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428 Plus whenever I hear of "weird problems mounting or unmounting devices" plus "non-determinism"... systemd comes to mind :P So my hunch is this isn't actually a `qemu-img` bug. My best guess is systemd, but it could also be the Linux 4.4 vs 4.8 kernel or something else I haven't thought of. Still, without stronger evidence, to me it seems `qemu-img` is the best package to initially file this bug against. Also, I'm not yet sure how best to debug this, but the most helpful logging I've found thus far is in /var/log/syslog. Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: qemu-utils 1:2.6.1+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Tue Oct 4 10:44:58 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 18420 2 0.0 [kvm-irqfd-clean] MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic.efi.signed root=UUID=4b57bce3-eed0-426b-adfe-4f7a834e2ddf ro net.ifnames=0 quiet splash vt.handoff=7 SourcePackage: qemu UpgradeStatus: Upgraded to yakkety on 2016-10-03 (0 days ago) dmi.bios.date: 06/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RSY2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw8-17g dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: Serval WS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RSY2:bd06/09/2015:svnSystem76,Inc.:pnServalWS:pvrserw8-17g:rvnSystem76,Inc.:rnServalWS:rvrserw8-17g:cvnSystem76,Inc.:ct9:cvrServalWS: dmi.product.name: Serval WS dmi.product.version: serw8-17g dmi.sys.vendor: System76, Inc. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug yakkety ** Bug watch added: Debian Bug tracker #824553 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824553 ** Also affects: qemu (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824553 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630341 Title: yakkety: behavior change in `qemu-nbd -c $DEV $FILENAME`: doesn't automatically create partion devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1630341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626622] Re: yakkety server: fails to detect and mount CD-ROM
Ah, sorry, I forgot to follow up on this. Yes, the bug has been fixed for about a week now (but I was on vacation). Is it better to mark this as Fix Released instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626622 Title: yakkety server: fails to detect and mount CD-ROM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1626622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
@Mathieu - I was on vacation last week, so I wasn't in the loop on IRC. What's the current status of this? Does it seem feasible that the fixed shim package can be signed (and FFE'd) in time for 16.10? Or are we already at the point where reverting to the shim 0.8-0ubuntu2 package from Xenial (with whatever needed version trickery) is the only realistic hope for fixing this? If there's anything I can do to help, please don't hesitate to ask! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626622] Re: yakkety server: fails to detect and mount CD-ROM
** Summary changed: - yakkety server: fails to detect and mount CD-ROM (QEMU, BIOS mode) + yakkety server: fails to detect and mount CD-ROM ** Description changed: The latest yakkety server amd64 daily (20160921.1, sha1sum b3e9f59397389bf23390f4869d3aef46de5d105c) fails to detect and mount the CD-ROM. Please see attached screenshot. - I found this testing under QEMU (BIOS mode), not yet sure whether it - effects hardware. But I'll be testing on hardware shortly. + I confirmed that this is happening on physical hardware when booting the + server installer from a USB stick (I tested in both UEFI and BIOS mode, + both fail). + + This also happens under QEMU in BIOS mode. I can't test under QEMU in + UEFI mode because of lp:1624096 + + Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626622 Title: yakkety server: fails to detect and mount CD-ROM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1626622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626622] [NEW] yakkety server: fails to detect and mount CD-ROM (QEMU, BIOS mode)
Public bug reported: The latest yakkety server amd64 daily (20160921.1, sha1sum b3e9f59397389bf23390f4869d3aef46de5d105c) fails to detect and mount the CD-ROM. Please see attached screenshot. I found this testing under QEMU (BIOS mode), not yet sure whether it effects hardware. But I'll be testing on hardware shortly. ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety ** Attachment added: "Screenshot from 2016-09-22 09-29-46.png" https://bugs.launchpad.net/bugs/1626622/+attachment/4746306/+files/Screenshot%20from%202016-09-22%2009-29-46.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626622 Title: yakkety server: fails to detect and mount CD-ROM (QEMU, BIOS mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1626622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
@@Mathieu yeah, if you can get me a custom ISO with an updated shim package (doesn't need to be signed, I'm not using secure boot), then I'll giving a thorough testing under QEMU and on all the UEFI hardware I have access too (6 different laptops, 3 different desktops). Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
@Laszlo - darn, no luck. Following your recommendations, PXE booting is no longer attempted, but I still end up at Shell> and the installer doesn't launch. I'm attaching the isolated test script I'm using ATM. If I try it with the latest Yakkety desktop daily ISO, I hit the above hardware exception (as expected because of the issue in `shim`). However, if I try it with the same ISO modified to include /EFI/BOOT/fallback.efi, it goes directly to Shell> rather than launching the installer. Please let me know if you spot any goofs in my script or can think of anything else to try. (Note: my test script doesn't have any -net devices at all, but my image mastering tools do, so that's why I know that PXE booting wasn't being tried any more.) @Mathieu - under the assumption that there is more to this than just the issue in `shim`, or at least that the presence of fallback.efi can't fully work-around it, do you have any suggestions as to where I should go looking for other things that have changed between the Yakkety and Xenial ISOs, things that might be interacting with the `shim` bug in odd ways? Also, I should make it clear why this bug is critical to System76: our imaging mastering tools use QEMU + OVMF to create our UEFI images, so this is something we absolutely need to find some solution for in order to ship 16.10. Because (most likely) we'll need 16.10 to initially ship Kaby Lake :D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
Oops, forgot to attach my test script :P ** Attachment added: "test-yakkety-guest.sh" https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1624096/+attachment/4745643/+files/test-yakkety-guest.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
@Laszlo - thank you very much for the detailed explanation! Sounds like your tips, plus /EFI/BOOT/fallback.efi being present on the ISO, should be enough for me to work-around this issue. I'll let you know how it goes. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
@Mathieu - I've been doing some quick experiments with fallback.efi on the ISO, and I'm not sure that alone will fix things. The problem is that when fallback.efi is present, the installer isn't launching. Instead, OVMF tries to PXE boot (which in my test environment fails because I don't have the needed DHCP/TFTP setup), then OVMF falls back to Shell> I tried adding /EFI/BOOT/fallback.efi to both the latest Yakkety daily ISO and the 16.04.1 ISO. In both cases, the installer doesn't boot, I end up at Shell> So although fallback.efi can work around the X64 Exception in the Yakkety version of shim, it still doesn't give you a bootable installer. If there's something obvious I'm missing, please let me know! Also, do you have any idea why this faulty shim code path is taken when running under QEMU + OVMF, but does not seem to be taken when running on physical hardware? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode
@Laszlo - awesome, thanks! Do you happen to know what version introduced the bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode
@Laszlo - thanks for the debugging tips! I'm getting the same result that you are. I found a possibly related opensuse bug: https://lists.opensuse.org/opensuse-bugs/2016-01/msg00965.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] [NEW] yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode
Public bug reported: Sometime after August 25th (or so) something changed in the Yakkety ISOs that make them no longer boot under QEMU in UEFI mode. However, the ISOs do work fine still on the physical UEFI hardware I've tested (3 different systems). I'm not sure about other VM solutions like Virtual Box, etc., as I haven't tested under anything other than QEMU. But under QEMU, UEFI mode installs are definitely broken. You get stuck in the OVMF firmware with the following text on the screen (see attached screenshot): Boot Failed. EFI Floppy Boot Failed. EFI Floppy 1 Thus far I've only tested with a Xenial host, so I'm not sure whether this problem exists with a Yakkety host + Yakkety guest. This problem also doesn't seem to be the result of any changes in QEMU (and related) in Xenial. With a Xenial host, you can still do UEFI mode installs fine under QEMU when the guest is using the 16.04.1 ISOs, and likewise when the guest is using the latest Xenial daily (16.04.2 WIP) ISOs. So the problem seems to be only when using a Yakkety guest in UEFI mode. Note this problem effects both Yakkety desktop and server ISOs (when installing under QEMU in UEFI mode). Finally, on the off chance it might be helpful to anyone who comes across this bug report, I wrote a blog post a while back on how to use QEMU in UEFI mode on a Xenial (or newer) host: http://blog.system76.com/post/139138591598/howto-qemu-w-ubuntu-xenial- host-uefi-guest Thanks! ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: yakkety ** Attachment added: "Screenshot from 2016-09-14 11-48-54.png" https://bugs.launchpad.net/bugs/1624096/+attachment/4741575/+files/Screenshot%20from%202016-09-14%2011-48-54.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604173] Re: Clicking "Reboot Now" after 14.04-->16.04 upgrade has no effect
Brain, Strange. So I just tried the upgrade again, and after the upgrade completed, I: 1) Clicked "Reboot Now" (which did nothing, same as yesterday) 2) Ran `sudo reboot` - it worked, but seemed to hang for some time before doing anything (it hung for maybe 20 seconds or so) I'm not sure how clicking "Reboot Now" first might be interacting with then running `sudo reboot`. I wonder if I tried `sudo reboot` first if it would do nothing. I'll try that tomorrow if I have time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604173 Title: Clicking "Reboot Now" after 14.04-->16.04 upgrade has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1604173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604173] [NEW] Clicking "Reboot Now" after 14.04-->16.04 upgrade has no effect
Public bug reported: After doing a 14.04 to 16.04 upgrade, clicking "Reboot Now" has no effect. update-manager simply closes. However, I could then reboot fine using the indicator or the power button, which kinda suggests the problem is in update-manager rather than in the general state of such an upgraded but not yet rebooted system. In the 3 test upgrades I did, this was reproducible 100% of the time. Steps I used to reproduce: 1) Fresh install of 14.04.4 2) Run updates and reboot 3) Launch update-manager with `update-manager -d` 4) Start upgrade, let it complete 5) Once upgrade is completed, click "Reboot Now" on the shown dialogue FYI, thus far I've only tested on a UEFI system, haven't had time to test a BIOS system (and I wont likely have time to test on a BIOS system). But I wouldn't expect this to behave differently on a BIOS system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Jul 18 15:42:56 2016 InstallationDate: Installed on 2016-07-18 (0 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-07-18 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604173 Title: Clicking "Reboot Now" after 14.04-->16.04 upgrade has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1604173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599900] Re: compiz crashed with SIGSEGV in ccsObjectGetInterface_()
FYI, I seem to be hitting this same bug (under qemu) with the xenial daily ISO as well (which have xenial-proposed enabled by default). Will this be fixed in Xenial also? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599900 Title: compiz crashed with SIGSEGV in ccsObjectGetInterface_() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1599900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
@Marco: thanks for the FYI! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Here's another screenshot that shows the SegvAnalysis. In my testing thus far, this failure (assuming it's related to this unity/nux change) only seems to happen when trying to install under qemu. I tried -vga qxl, -vga std, and -vga virtio... none of them yield a working installation. Compiz always fails to start. ** Attachment added: "Screenshot from 2016-07-13 10-56-41.png" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1598770/+attachment/4700300/+files/Screenshot%20from%202016-07-13%2010-56-41.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Possibly as a result of this change, unity/compiz is failing to start when trying to install from the latest 16.04.1 daily ISO under qemu (xenial-desktop-amd64.iso 20160713, sha1sum c9b1ad9b1044c4e68684395daa3f85e016491c3a). I attached a screenshot as I couldn't file a bug from within the qemu VM (apport doesn't seem able to launch firefox). ** Attachment added: "Screenshot from 2016-07-13 10-36-40.png" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1598770/+attachment/4700286/+files/Screenshot%20from%202016-07-13%2010-36-40.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597876] Re: installing/upgrading packages containing systemd services results in prompt for cryptoswap passphrase [xenial]
Also attaching a screenshot, just so folks don't think I'm making this up :P ** Attachment added: "screenshot.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876/+attachment/4692953/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597876 Title: installing/upgrading packages containing systemd services results in prompt for cryptoswap passphrase [xenial] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597876] [NEW] installing/upgrading packages containing systemd services results in prompt for cryptoswap passphrase [xenial]
Public bug reported:
This is an extremely odd bug that requires a very specific scenario to
reproduce:
1) You need to be using an ecryptfs-style cryptoswap partition (as would
be setup when you choose "Encrypt my home directory" during the
installation)
2) The underlying physical swap partition used for the cryptoswap needs
to be on a GPT partitioned drive
3) The GUID specific bit 63 ("no auto mounting") must *not* be set on
the underlying physical swap partition
In this scenario, installing/upgrading/reinstalling seemingly *any*
package with a systemd service will result in the user getting *twice*
prompted for a passphrase to unlock their cryptoswap partition. If
upgrades are performed using the graphical Software Updater, the user
wont be aware of this issue unless they've expanded the details,
resulting in the Software Updater hanging indefinitely.
For example, if you have the needed setup, you can easily reproduce this
bug with:
sudo apt-get install --reinstall whoopsie
After which you'll encounter something like this:
(Reading database ... 177827 files and directories currently installed.)
Preparing to unpack .../whoopsie_0.2.52.1_amd64.deb ...
Please enter passphrase for disk primary (cryptswap1) on none!
Unpacking whoopsie (0.2.52.1) over (0.2.52) ...
Preparing to unpack .../libwhoopsie0_0.2.52.1_amd64.deb ...
Unpacking libwhoopsie0:amd64 (0.2.52.1) over (0.2.52) ...
Processing triggers for systemd (229-4ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Setting up libwhoopsie0:amd64 (0.2.52.1) ...
Setting up whoopsie (0.2.52.1) ...
Please enter passphrase for disk primary (cryptswap1) on none!
Processing triggers for libc-bin (2.23-0ubuntu3) ...
(You can just hit enter each time the "Please enter passphrase for..."
prompt comes up.)
For some background: in modern systemd times, ecryptfs-style cryptoswaps
are broken when the underlying physical GPT swap partition does not have
bit 63 set:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1447282
During the boot the user is erroneously prompted for a passpharase to
unlock the cryptoswap (you can hit enter for an empty passphrase, or
enter any passphrase you want... either way, nothing seems to actually
be done with it). After the boot completes, the underlying physical swap
partition will be mounted normally (ie, you wont actually be using
encrypted swap... so a false sense of security, which is of course
concerning).
Although lp:1447282 has been fixed for the most common hardware
configurations, it's still possible for users to encounter this problem
in the real-word: ecryptfs-setup-swap currently fails to set bit 63 when
the physical GPT swap partition is on an NVMe or MMC drive:
https://bugs.launchpad.net/ecryptfs/+bug/1597154
So one way to reproduce this is to install Ubuntu 16.04 onto an NVMe
drive and choose "Encrypt my home directory" during the installation.
To make debugging this easier without requiring an NVMe drive (and
especially so it's easier to debug in a UEFI VM), I'm attaching a script
that will unset bit 63 on the underlying GPT swap partitions used by any
ecryptfs-style cryptoswaps that are present.
If you run my script:
sudo python3 unset-bit-63.py
And then reboot, you should now be able to reproduce this bug.
Even though fixing lp:1597154 will mean users shouldn't encounter
(during normal real-world usage) this strange behavior when
installing/upgrading/reinstalling packages that contain systemd
services, I have a strong hunch that the fact this can happen at all
indicates something is quite wonky in either systemd itself or in the
Debian/Ubuntu specific systemd trigger handling.
Thanks!
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "unset-bit-63.py"
https://bugs.launchpad.net/bugs/1597876/+attachment/4692952/+files/unset-bit-63.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597876
Title:
installing/upgrading packages containing systemd services results in
prompt for cryptoswap passphrase [xenial]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447282] Re: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs)
@diwic - I agree, there have been problems in multiple places causing this. Yesterday I sorted out one of them. If you have swap on a GPT partitioned NVMe or MMC drive, ecryptfs-setup-swap isn't correctly marking the partition as non-auto-mounting, which leads the the user erroneously being prompted to enter a passphrase to unlock the swap partition. I filed a bug about this and have a merge proposal ready for review: https://bugs.launchpad.net/ecryptfs/+bug/1597154 This bug has been present in ecryptfs-utils since the original GPT auto mounting issues was fixed, but not that long ago in 16.04 it didn't result in being erroneously being prompted to enter a passphrase to unlock the swap partition. Some some recent-ish behavior change elsewhere has re-exposed this (I'm guessing a change in systemd). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447282 Title: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1447282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565106] Re: Wifi works on W10 but not on Ub 16.04 nor 14.04
after installing new kernel 4.7, RJ45 connected I rebooted a first time (on 4.7) took RJ45 out no wifi I connected RJ45 to install Chromium rebooted a 2nd time, RJ45 out, no wifi I rebooted a 3rd time, RJ45 out, wifi was visible (see the picture below) http://i68.tinypic.com/29479ly.jpg I did not connect to my wifi box (no wifi password declaration) rebooted no wifi again I shut-off / shut-on power supply wifi is back I've been connected to it (see picture below) http://i64.tinypic.com/fuumat.jpg I shut-off / shut-on power supply again to check a 2nd time NO wifi I reboot NO wifi, same Finally, as usual, when I do a major change (reinstall, but no improvement this time) or upstream kernel, I've got Wifi just ONCE which means my card is recognized by Ubuntu, but never again. Looks like a sort of flag is marked somewhere which no longer allows wifi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565106 Title: Wifi works on W10 but not on Ub 16.04 nor 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565106] Re: Wifi works on W10 but not on Ub 16.04 nor 14.04
Christopher in order to bring you as much info as I can, I did the following tests and the result is very strange!! after installing new kernel 4.7, RJ45 connected I rebooted a firt time (on 4.7) took RJ45 out no wifi I connected RJ45 to install Chromium rebooted a 2nd time, RJ45 out, no wifi I rebooted a 3rd time, RJ45 out, wifi was visible (see the picture below) http://i68.tinypic.com/29479ly.png I did not connect to my wifi box (no wifi password declaration) rebooted no wifi again I shut-off / shut-on power supply wifi is back I've been connected to it (see picture below) http://i64.tinypic.com/fuumat.png I shut-off / shut-on power supply again to check a 2nd time NO wifi I reboot NO wifi, same Finally, as usual, when I do a major change (reinstall, but no improvement this time) or upstream kernel, I've got Wifi just ONCE which means my card is recognized by Ubuntu, but never again. Looks like a sort of flag is marked somewhere which no longer allows wifi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565106 Title: Wifi works on W10 but not on Ub 16.04 nor 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565106] Re: Wifi works on W10 but not on Ub 16.04 nor 14.04
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565106 Title: Wifi works on W10 but not on Ub 16.04 nor 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565106] Re: Wifi works on W10 but not on Ub 16.04 nor 14.04
Hi Christopher I followed your recommendations as far as I understood - I reinstalled a brand new clean version with the current kernel - I declared the bug following your user guide link Here is the bug address https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1595960 Hope you "(new bug team) + you" will find what's going on because Ubuntu without wifi is no good for the promotion I do everyday on this nice distribution, far better than w10 (except this of course !) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565106 Title: Wifi works on W10 but not on Ub 16.04 nor 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
