[Bug 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)
Same issue on Ubuntu 24.04 noble LTS: - gnome-shell: 46.0-0ubuntu5 - linux 6.8.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 14 14:56:46 UTC 2024 x86_64 - DisplayManager: lightdm 1.30.0-0ubuntu14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007742 Title: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977689] [NEW] Wrong error msg: "state file /var/lib/logrotate/status is world-readable" although it is not
Public bug reported: Ubuntu 22.04 logrotate 3.19.0-1ubuntu1.1 Every hour, I receive this wrong message: Subject:Cron >cd / && run-parts --report /etc/cron.hourly /etc/cron.hourly/logrotate: error: state file /var/lib/logrotate/status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition... despite: # ls -al /var/lib/logrotate total 40 drwxr-x--- 2 root root 4096 Jun 5 17:17 . drwxr-xr-x 66 root root 4096 Jun 3 20:02 .. -rw-r- 1 root root 31974 Jun 5 17:17 status ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu 22.04 logrotate 3.19.0-1ubuntu1.1 Every hour, I receive this wrong message: + + Subject: Cron >cd / && run-parts --report /etc/cron.hourly /etc/cron.hourly/logrotate: error: state file /var/lib/logrotate/status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition... despite: # ls -al /var/lib/logrotate total 40 drwxr-x--- 2 root root 4096 Jun 5 17:17 . drwxr-xr-x 66 root root 4096 Jun 3 20:02 .. -rw-r- 1 root root 31974 Jun 5 17:17 status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977689 Title: Wrong error msg: "state file /var/lib/logrotate/status is world- readable" although it is not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1977689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947762] [NEW] package grub2-common 2.04-1ubuntu26.13 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: the error window appears when loading the desktop ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub2-common 2.04-1ubuntu26.13 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 AptOrdering: linux-modules-extra-5.11.0-36-generic:amd64: Remove linux-modules-5.11.0-36-generic:amd64: Remove linux-image-5.11.0-36-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 19 11:51:56 2021 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2021-03-07 (226 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=fd8ba57d-f002-4ff5-ac14-909ac7d7f275 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: grub2 Title: package grub2-common 2.04-1ubuntu26.13 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947762 Title: package grub2-common 2.04-1ubuntu26.13 failed to install/upgrade: problèmes de dépendances - laissé non configuré To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net when symlinks are used for configuration and/or
Thnaks for your backchannel with the upstream. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net when symlinks are used for configuration and/or database folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net when symlinks are used for configuration and/or
** Summary changed: - getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net + getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net when symlinks are used for configuration and/or database folders -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net when symlinks are used for configuration and/or database folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net
@Lucas Kanashiro (lucaskanashiro) Thanks for taking the time to read and answer it. You're right, it is not a bug per se, more a serious shortcoming. If we install the required packages, everything works fine. However, if we modify one of the aforementioned folders to a symlink which points to another folder with the same contents, then the issue described in this thread pops up. This is the first time I encounter this strange "symlink sensitivity" by any Ubuntu package and I believe this should never happen on Linux. I understand that clamav is also implemented on Windows and this could explain this undesired behavior on Linux. I have already posted a "feature request" on the clamav- de...@lists.clamav.net mailing list, but there is no response so far. @Utkarsh Gupta (utkarsh) Try this: # sudo systemctl stop clamav-daemon # sudo systemctl stop clamav-freshclam # sudo mv -f /etc/clamav /etc/clamav.sav # sudo ln -fsv /etc/clamav.sav /etc/clamav '/etc/clamav' -> '/etc/clamav.sav' # sudo systemctl restart clamav-daemon # sudo systemctl restart clamav-freshclam # sudo systemctl status clamav-freshclam ● clamav-freshclam.service - ClamAV virus database updater Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2021-03-23 18:45:15 CET; 5s ago Docs: man:freshclam(1) man:freshclam.conf(5) https://www.clamav.net/documents Process: 2460871 ExecStart=/usr/bin/freshclam -d --foreground=true (code=exited, status=2) Main PID: 2460871 (code=exited, status=2) Mar 23 18:45:15 host systemd[1]: Started ClamAV virus database updater. Mar 23 18:45:15 host freshclam[2460871]: ERROR: Can't open/parse the config file /etc/clamav/freshclam.conf Mar 23 18:45:15 host systemd[1]: clamav-freshclam.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Mar 23 18:45:15 host systemd[1]: clamav-freshclam.service: Failed with result 'exit-code'. Then back to normal: # sudo rm -f /etc/clamav # sudo mv -f /etc/clamav.sav /etc/clamav # sudo systemctl restart clamav-daemon # sudo systemctl restart clamav-freshclam # sudo systemctl status clamav-freshclam ● clamav-freshclam.service - ClamAV virus database updater Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2021-03-23 18:55:53 CET; 5s ago Docs: man:freshclam(1) man:freshclam.conf(5) https://www.clamav.net/documents Main PID: 2511510 (freshclam) Tasks: 1 (limit: 18975) Memory: 2.1M CGroup: /system.slice/clamav-freshclam.service └─2511510 /usr/bin/freshclam -d --foreground=true Mar 23 18:55:53 host systemd[1]: Started ClamAV virus database updater. Mar 23 18:55:53 host freshclam[2511510]: Tue Mar 23 18:55:53 2021 -> ClamAV update process started at Tue Mar 23 18:55:53 2021 Mar 23 18:55:53 host freshclam[2511510]: Tue Mar 23 18:55:53 2021 -> daily.cld database is up to date (version: 26118, sigs: 3965203, f-level: 63,> Mar 23 18:55:53 host freshclam[2511510]: Tue Mar 23 18:55:53 2021 -> main.cld database is up to date (version: 59, sigs: 4564902, f-level: 60, bui> Mar 23 18:55:53 host freshclam[2511510]: Tue Mar 23 18:55:53 2021 -> bytecode.cvd database is up to date (version: 333, sigs: 92, f-level: 63, bui> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net
I have found the cause of the issue: clamav does not support symlinks for any of the following: - /etc/clamav - /etc/ssl - /etc/ssl/certs - /var/lib/clamav If I make sure there is no symlink anymore for any of the above folders, then the issue is worked around: # freshclam --debug --verbose ... * Trying 104.16.219.84:443... * Connected to database.clamav.net (104.16.219.84) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: C=US; ST=CA; L=San Francisco; O=Cloudflare, Inc.; CN=sni.cloudflaressl.com * start date: Aug 15 00:00:00 2020 GMT * expire date: Aug 15 12:00:00 2021 GMT * subjectAltName: host "database.clamav.net" matched cert's "database.clamav.net" * issuer: C=US; O=Cloudflare, Inc.; CN=Cloudflare Inc ECC CA-3 * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x55631ca7a1e0) > GET /safebrowsing.cvd HTTP/2 Host: database.clamav.net user-agent: ClamAV/0.103.0 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64) accept: */* I'm not sure whether this symlink sensitivity is by design or a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net
** Description changed: Ubuntu 21.04 clamav-freshclam: 0.103.0+dfsg-3.1 + + /etc/clamav/freshclam.conf: + -- + DatabaseOwner clamav + UpdateLogFile /var/log/clamav/freshclam.log + LogVerbose false + LogSyslog false + LogFacility LOG_LOCAL6 + LogFileMaxSize 0 + LogRotate true + LogTime true + Foreground false + Debug true + MaxAttempts 5 + DatabaseDirectory /var/lib/clamav + DNSDatabaseInfo current.cvd.clamav.net + ConnectTimeout 30 + ReceiveTimeout 30 + TestDatabases yes + ScriptedUpdates yes + CompressLocalDatabase no + SafeBrowsing true + Bytecode true + NotifyClamd /etc/clamav/clamd.conf + # Check for new database 24 times a day + Checks 24 + DatabaseMirror db.fr.clamav.net + DatabaseMirror database.clamav.net Commands executed as root: # systemctl stop clamav-freshclam # freshclam --debug --verbose Sat Mar 20 16:00:21 2021 -> ClamAV update process started at Sat Mar 20 16:00:21 2021 Sat Mar 20 16:00:21 2021 -> *Current working dir is /var/lib/clamav/ Sat Mar 20 16:00:21 2021 -> *Querying current.cvd.clamav.net Sat Mar 20 16:00:21 2021 -> *TTL: 1623 Sat Mar 20 16:00:21 2021 -> *fc_dns_query_update_info: Software version from DNS: 0.103.1 Sat Mar 20 16:00:21 2021 -> *Current working dir is /var/lib/clamav/ Sat Mar 20 16:00:21 2021 -> *check_for_new_database_version: No local copy of "daily" database. Sat Mar 20 16:00:21 2021 -> *query_remote_database_version: daily.cvd version from DNS: 26115 Sat Mar 20 16:00:21 2021 -> daily database available for download (remote version: 26115) Sat Mar 20 16:00:21 2021 -> *Retrieving https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> *downloadFile: Download source: https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> *downloadFile: Download destination: /var/lib/clamav/tmp.5ee08cf0a0/clamav-746b5f842a022ff02206be76e0c77fe8.tmp * Trying 104.16.219.84:443... * Connected to database.clamav.net (104.16.219.84) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * Closing connection 0 Sat Mar 20 16:00:21 2021 -> ^Download failed (77) Sat Mar 20 16:00:21 2021 -> ^ Message: Problem with the SSL CA cert (path? access rights?) Sat Mar 20 16:00:21 2021 -> ^getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> Trying again in 5 secs... The alleged "error setting certificate verify locations" is false: # sudo -u clamav -EH ls -al /etc/ssl/certs/ca-certificates.crt -rw-r--r-- 1 root root 186336 Mar 15 08:45 /etc/ssl/certs/ca-certificates.crt # sudo -u clamav -EH ls -al /etc/ssl/certs total 556 drwxr-xr-x 3 root root 12288 Mar 15 08:45 . ... Also, it is possible to contact the website as clamav user, meaning there is no CA access issue for that user: # sudo -u clamav -EH wget https://database.clamav.net --2021-03-20 16:21:12-- https://database.clamav.net/ Resolving database.clamav.net (database.clamav.net)... 104.16.219.84, 104.16.218.84, 2606:4700::6810:da54, ... Connecting to database.clamav.net (database.clamav.net)|104.16.219.84|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘index.html’ index.html [ <=> ] 1.14K --.-KB/sin 0s 2021-03-20 16:21:12 (21.3 MB/s) - ‘index.html’ saved [1166] # more index.html - - http://www.clamav.net; http-equiv="Refresh"> - ClamAV database mirror + + http://www.clamav.net; http-equiv="Refresh"> + ClamAV database mirror + src="//www.clamav.net/assets/clamav-trademark.png"> You reached one of ClamAV virus database mirrors: http://database.clamav.net;>database.clamav.net + style="font-style: italic;" href="http://database.clamav.net;>database.clamav.net is a round robin record that tries to equally balance the traffic between all the database mirrors. For a complete list of our mirrors visit http://www.clamav.net/mirrors.html;>http://www.clamav.net/mirrors.html + href="http://www.clamav.net/mirrors.html;>http://www.clamav.net/mirrors.html You'll be redirected to ClamAV home page (http://www.clamav.net;>http://www.clamav.net) in 15 + href="http://www.clamav.net;>http://www.clamav.net) in 15 seconds... This mirror is sponsored by This is a very strange issue. Any suggestion on how to debug/workaround that issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net To manage notifications about this bug go to:
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net
There is no such issue on another Ubuntu device with the **exact** same SSL and freshclam configurations and located on the same private network as the failing device sharing the same IP public address. Is it possible that cloudflare enforces a limit on the number of devices which are allowed to download from https://database.clamav.net/daily.cvd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] [NEW] getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net
Public bug reported: Ubuntu 21.04 clamav-freshclam: 0.103.0+dfsg-3.1 Commands executed as root: # systemctl stop clamav-freshclam # freshclam --debug --verbose Sat Mar 20 16:00:21 2021 -> ClamAV update process started at Sat Mar 20 16:00:21 2021 Sat Mar 20 16:00:21 2021 -> *Current working dir is /var/lib/clamav/ Sat Mar 20 16:00:21 2021 -> *Querying current.cvd.clamav.net Sat Mar 20 16:00:21 2021 -> *TTL: 1623 Sat Mar 20 16:00:21 2021 -> *fc_dns_query_update_info: Software version from DNS: 0.103.1 Sat Mar 20 16:00:21 2021 -> *Current working dir is /var/lib/clamav/ Sat Mar 20 16:00:21 2021 -> *check_for_new_database_version: No local copy of "daily" database. Sat Mar 20 16:00:21 2021 -> *query_remote_database_version: daily.cvd version from DNS: 26115 Sat Mar 20 16:00:21 2021 -> daily database available for download (remote version: 26115) Sat Mar 20 16:00:21 2021 -> *Retrieving https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> *downloadFile: Download source: https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> *downloadFile: Download destination: /var/lib/clamav/tmp.5ee08cf0a0/clamav-746b5f842a022ff02206be76e0c77fe8.tmp * Trying 104.16.219.84:443... * Connected to database.clamav.net (104.16.219.84) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * Closing connection 0 Sat Mar 20 16:00:21 2021 -> ^Download failed (77) Sat Mar 20 16:00:21 2021 -> ^ Message: Problem with the SSL CA cert (path? access rights?) Sat Mar 20 16:00:21 2021 -> ^getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> Trying again in 5 secs... The alleged "error setting certificate verify locations" is false: # sudo -u clamav -EH ls -al /etc/ssl/certs/ca-certificates.crt -rw-r--r-- 1 root root 186336 Mar 15 08:45 /etc/ssl/certs/ca-certificates.crt # sudo -u clamav -EH ls -al /etc/ssl/certs total 556 drwxr-xr-x 3 root root 12288 Mar 15 08:45 . ... Also, it is possible to contact the website as clamav user, meaning there is no CA access issue for that user: # sudo -u clamav -EH wget https://database.clamav.net --2021-03-20 16:21:12-- https://database.clamav.net/ Resolving database.clamav.net (database.clamav.net)... 104.16.219.84, 104.16.218.84, 2606:4700::6810:da54, ... Connecting to database.clamav.net (database.clamav.net)|104.16.219.84|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘index.html’ index.html [ <=> ] 1.14K --.-KB/sin 0s 2021-03-20 16:21:12 (21.3 MB/s) - ‘index.html’ saved [1166] # more index.html http://www.clamav.net; http-equiv="Refresh"> ClamAV database mirror You reached one of ClamAV virus database mirrors: http://database.clamav.net;>database.clamav.net is a round robin record that tries to equally balance the traffic between all the database mirrors. For a complete list of our mirrors visit http://www.clamav.net/mirrors.html;>http://www.clamav.net/mirrors.html You'll be redirected to ClamAV home page (http://www.clamav.net;>http://www.clamav.net) in 15 seconds... This mirror is sponsored by This is a very strange issue. Any suggestion on how to debug/workaround that issue? ** Affects: clamav (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/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919341] Re: kernel package linux-headers-5.11.0-11-generic is not supported
Solved by: xtables-addons-common: 3.13-1ubuntu2 xtables-addons-dkms: 3.13-1ubuntu2 Preparing to unpack .../xtables-addons-common_3.13-1ubuntu2_amd64.deb ... Unpacking xtables-addons-common (3.13-1ubuntu2) over (3.13-1) ... Preparing to unpack .../xtables-addons-dkms_3.13-1ubuntu2_all.deb ... ... Building initial module for 5.11.0-11-generic Done. xt_ACCOUNT.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ compat_xtables.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_pknock.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_CHAOS.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_DELUDE.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_DHCPMAC.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_DNETMAP.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_ECHO.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_IPMARK.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_LOGMARK.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_PROTO.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_SYSRQ.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_TARPIT.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_condition.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_fuzzy.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_geoip.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_iface.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_ipp2p.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_ipv4options.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_length2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_lscan.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_psd.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_quota2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ depmod DKMS:
[Bug 1919341] [NEW] kernel package linux-headers-5.11.0-11-generic is not supported
Public bug reported:
Ubuntu 21.04
xtables-addons-common: 3.13-1
xtables-addons-dkms: 3.13-1
Upgrading the linux kernel leads to:
Setting up linux-headers-5.11.0-11-generic (5.11.0-11.12) ...
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 5.11.0-11-generic
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.11.0-11-generic -C
/lib/modules/5.11.0-11-generic/build
M=/var/lib/dkms/xtables-addons/3.13/build/extensions
XA_ABSTOPSRCDIR=/var/lib/dkms/xtables-
addons/3.13/build XA_TOPSRCDIR=/var/lib/dkms/xtables-addons/3.13/build V=1
modules ; find /var/lib/dkms/xtables-addons/3.13/build -name '*.ko' -exec mv -v
{} /var/lib/dkms/
xtables-addons/3.13/build \;...
ERROR (dkms apport): kernel package linux-headers-5.11.0-11-generic is not
supported
Error! Build of xt_ACCOUNT.ko failed for: 5.11.0-11-generic (x86_64)
Make sure the name of the generated module is correct and at the root of the
build directory, or consult make.log in the build directory
/var/lib/dkms/xtables-addons/3.13/build/ for more information.
...done.
/var/lib/dkms/xtables-addons/3.13/build/make.log is attached.
** Affects: xtables-addons (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1919341/+attachment/5477272/+files/make.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919341
Title:
kernel package linux-headers-5.11.0-11-generic is not supported
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1919341/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
Same issue with mysql-server 8.0.21-1 on groovy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
Sorry: I have inadvertently tested with a port matching another service (853 instead of 3306), so my previous post must be ignored. This issue is still there, even on groovy. Let me answer your questions again: 0) with a service answering correctly to TLS connections requests, we get with a wildcard server certificate: ... SSL_connect:SSLv3/TLS write finished --- Certificate chain 0 s:CN = *.domain i:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 -BEGIN CERTIFICATE- As my first post shows, there is an initial error in the connection preventing openssl to show the CA used or the server certificate: ... SSL_connect:error in error 139858538362176:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331: --- no peer certificate available --- 1) The full SSL configuration (besides the 3 parameters already described in my first post) also includes the following parameters which are IMHO not relevant because his issue still happens if I remove them: ssl-cipher=... tls-version=... require_secure_transport=ON 2) You don't seem to understand this issue. The client don't need special configuration, other than at least one matching cipher and required TLS version if they are specified on the server side. 3)I have already tried that: same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
** Changed in: mysql-8.0 (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
1. already shared in my first post 2. You don't seem to understand this issue. Not a problem, because in the meantime, I have upgraded to groovy with: mysql-server-8.0: Installed: 8.0.21-0ubuntu4 Now I get: ... SSL_connect:SSLv3/TLS write finished --- Certificate chain 0 s:CN = *.domain i:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 -BEGIN CERTIFICATE- This issue has been solved on groovy. FYI, the systemd service continues to show an incorrect warning: [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
I suggest you try to configure your mysql-server with SSL parameters using a public CA, since this is the use case of this issue. ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
I changed the title to better reflect the core issue of this thread. ** Summary changed: - mysql-server does not take into account configured ssl parameters + Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: mysql-server does not take into account configured ssl parameters
I meant let's encrypt as a public certificate ... authority. Also, if it is of any help: mysql> status -- mysql Ver 8.0.21-0ubuntu4 for Linux on x86_64 ((Ubuntu)) Connection id: 31 Current database: Current user: root@localhost SSL:Not in use Current pager: stdout Using outfile: '' Using delimiter:; Server version: 8.0.21-0ubuntu4 (Ubuntu) Protocol version: 10 Connection: Localhost via UNIX socket Server characterset:utf8mb4 Db characterset:utf8mb4 Client characterset:utf8mb4 Conn. characterset:utf8mb4 UNIX socket:/var/run/mysqld/mysqld.sock Binary data as: Hexadecimal Uptime: 15 hours 45 min 24 sec -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: mysql-server does not take into account configured ssl parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: mysql-server does not take into account configured ssl parameters
I appreciate the time you took to answer. However, your example is a different use case: you're using a self-signed certificate with a private CA. My use case use a public CA (namely let's encrypt, but it could be anything else). In my setup, client and servers are on totally different machines. They should be able to communicate over TLS like you're using your browser right now to communicate over https with the remote server https://bugs.launchpad.net/ which happens to also use let's encrypt as a public certificate. I am aware that the official mysql doc only displays SSL examples using only a private CA. I suspect this issue to come from an inability to perform correctly with a public CA/certificate. ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: mysql-server does not take into account configured ssl parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891020] Re: No IPv4 iptable kernel module can be loaded
Yes, the issue is solved: # uname -r 5.8.0-16-generic # lsmod | grep iptable_ iptable_filter 16384 1 iptable_nat16384 1 nf_nat 49152 3 ip6table_nat,iptable_nat,xt_MASQUERADE iptable_mangle 16384 1 ip_tables 32768 13 iptable_filter,iptable_nat,iptable_mangle x_tables 45056 19 ebtables,ip6table_filter,xt_conntrack,iptable_filter,xt_NFLOG,xt_tcpudp,xt_addrtype,xt_CHECKSUM,ip6t_rt,xt_geoip,ip6_tables,ipt_REJECT,ip_tables,xt_limit,xt_hl,ip6table_mangle,xt_MASQUERADE,ip6t_REJECT,iptable_mangle # systemctl status netfilter-persistent ● netfilter-persistent.service - netfilter persistent configuration Loaded: loaded (/lib/systemd/system/netfilter-persistent.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/netfilter-persistent.service.d └─iptables.conf Active: active (exited) since Thu 2020-08-13 00:45:54 CEST; 6min ago Docs: man:netfilter-persistent(8) Main PID: 1073 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 18998) Memory: 0B CGroup: /system.slice/netfilter-persistent.service Aug 13 00:45:53 samsung5-ubuntu systemd[1]: Starting netfilter persistent configuration... Aug 13 00:45:53 samsung5-ubuntu netfilter-persistent[1084]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables start Aug 13 00:45:54 samsung5-ubuntu netfilter-persistent[1084]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/25-ip6tables start Aug 13 00:45:54 samsung5-ubuntu systemd[1]: Finished netfilter persistent configuration. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1891020 Title: No IPv4 iptable kernel module can be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891020] Re: No IPv4 iptable kernel module can be loaded
** 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/1891020 Title: No IPv4 iptable kernel module can be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891020] Re: No IPv4 iptable kernel module can be loaded
Something has changed since my first post: now, right after boot,
iptable_filter is loaded, but not the other IPv4 iptable kernel modules:
# lsmod | grep iptable_
iptable_filter 16384 0
ip_tables 32768 1 iptable_filter
x_tables 45056 14
ebtables,ip6table_filter,xt_conntrack,iptable_filter,xt_NFLOG,xt_tcpudp,ip6t_rt,xt_geoip,ip6_tables,ip_tables,xt_limit,xt_hl,ip6table_mangle,ip6t_REJECT
# systemctl status netfilter-persistent
● netfilter-persistent.service - netfilter persistent configuration
Loaded: loaded (/lib/systemd/system/netfilter-persistent.service; enabled;
vendor preset: enabled)
Drop-In: /etc/systemd/system/netfilter-persistent.service.d
└─iptables.conf
Active: failed (Result: exit-code) since Wed 2020-08-12 10:09:33 CEST;
5min ago
Docs: man:netfilter-persistent(8)
Process: 1108 ExecStart=/usr/sbin/netfilter-persistent start (code=exited,
status=1/FAILURE)
Main PID: 1108 (code=exited, status=1/FAILURE)
Aug 12 10:09:32 samsung5-ubuntu systemd[1]: Starting netfilter persistent
configuration...
Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1113]: run-parts:
executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables start
Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1126]: iptables-restore
v1.8.5 (legacy): iptables-restore: unable to initialize table 'mangle'
Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1126]: Error occurred at
line: 2
Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1126]: Try
`iptables-restore -h' or 'iptables-restore --help' for more information.
Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1113]: run-parts:
/usr/share/netfilter-persistent/plugins.d/15-ip4tables exited with return code 2
Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1113]: run-parts:
executing /usr/share/netfilter-persistent/plugins.d/25-ip6tables start
Aug 12 10:09:33 samsung5-ubuntu systemd[1]: netfilter-persistent.service: Main
process exited, code=exited, status=1/FAILURE
Aug 12 10:09:33 samsung5-ubuntu systemd[1]: netfilter-persistent.service:
Failed with result 'exit-code'.
Aug 12 10:09:33 samsung5-ubuntu systemd[1]: Failed to start netfilter
persistent configuration.
It is possible to load the other IPv4 iptable kernel modules, but it seems
useless since the iptables cannot be loaded:
# for module in iptable_nat iptable_mangle
> do
> insmod
> /lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/${module}.ko
> done
# lsmod | grep iptable_
iptable_mangle 16384 0
iptable_nat16384 0
iptable_filter 16384 0
nf_nat 49152 2 ip6table_nat,iptable_nat
ip_tables 32768 3 iptable_filter,iptable_nat,iptable_mangle
x_tables 45056 15
ebtables,ip6table_filter,xt_conntrack,iptable_filter,xt_NFLOG,xt_tcpudp,ip6t_rt,xt_geoip,ip6_tables,ip_tables,xt_limit,xt_hl,ip6table_mangle,ip6t_REJECT,iptable_mangle
# systemctl restart netfilter-persistent
Job for netfilter-persistent.service failed because the control process exited
with error code.
See "systemctl status netfilter-persistent.service" and "journalctl -xe" for
details.
# systemctl status netfilter-persistent
● netfilter-persistent.service - netfilter persistent configuration
Loaded: loaded (/lib/systemd/system/netfilter-persistent.service; enabled;
vendor preset: enabled)
Drop-In: /etc/systemd/system/netfilter-persistent.service.d
└─iptables.conf
Active: failed (Result: exit-code) since Wed 2020-08-12 10:18:55 CEST; 3s
ago
Docs: man:netfilter-persistent(8)
Process: 5762 ExecStart=/usr/sbin/netfilter-persistent start (code=exited,
status=1/FAILURE)
Main PID: 5762 (code=exited, status=1/FAILURE)
Aug 12 10:18:55 samsung5-ubuntu systemd[1]: Starting netfilter persistent
configuration...
Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5764]: run-parts:
executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables start
Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5766]: iptables-restore
v1.8.5 (legacy): iptables-restore: unable to initialize table 'mangle'
Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5766]: Error occurred at
line: 2
Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5766]: Try
`iptables-restore -h' or 'iptables-restore --help' for more information.
Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5764]: run-parts:
/usr/share/netfilter-persistent/plugins.d/15-ip4tables exited with return code 2
Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5764]: run-parts:
executing /usr/share/netfilter-persistent/plugins.d/25-ip6tables start
Aug 12 10:18:55 samsung5-ubuntu systemd[1]: netfilter-persistent.service: Main
process exited, code=exited, status=1/FAILURE
Aug 12 10:18:55 samsung5-ubuntu systemd[1]: netfilter-persistent.service:
Failed with result 'exit-code'.
Aug 12 10:18:55 samsung5-ubuntu systemd[1]: Failed to start netfilter
persistent
[Bug 1891020] Re: No IPv4 iptable kernel module can be loaded
** Summary changed: - iptable_filter and ip6table_filter cannot be loaded with 5.8 kernel + No IPv4 iptable kernel module can be loaded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891020 Title: No IPv4 iptable kernel module can be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887891] Re: dav/davs behind proxy doesn't work
It's done : https://gitlab.gnome.org/GNOME/gvfs/-/issues/495 ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #495 https://gitlab.gnome.org/GNOME/gvfs/-/issues/495 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887891 Title: dav/davs behind proxy doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1887891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887891] [NEW] dav/davs behind proxy doesn't work
Public bug reported: I'm using Ubuntu 20.04 behind manual proxy. When I want to connect on a server with webdav, I have a message : "Erreur HTTP : Erreur de résolution de cloud.rochodc.com : Nom ou service inconnu" -> DNS Error Name ou service not known I can connect to a webdav server on my private network. I can connect to cloud.rochodc.com with Firefox and the proxy I use for the system. I can connect to cloud.rochodc.com with Ubuntu 18.04 with the same proxy and nautilus. Online account with parameters doesen't work at all. JC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 17 08:22:05 2020 InstallationDate: Installed on 2020-07-09 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887891 Title: dav/davs behind proxy doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866875] Re: option 'geoip-directory' was not enabled at compile time
I don't know what you mean by "MIR"; the following libmaxminddb0 was
already installed before I upgraded bind9 to **1:9.16.0-1ubuntu3**:
# apt-cache policy libmaxminddb0
libmaxminddb0:
Installed: 1.3.2-1
Candidate: 1.3.2-1
Version table:
*** 1.3.2-1 500
500 http://fr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
I had no such issue with previous bind9 versions in
/etc/bind/named.conf.options:
options {
...
geoip-directory "/usr/share/some/geoip/folder";
...
};
Upgrading to bind9 **1:9.16.0-1ubuntu4** does NOT solve this issue:
bind9:
Installed: 1:9.16.0-1ubuntu4
# systemctl restart bind9
# systemctl status bind9
● named.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset:
enabled)
Active: failed (Result: exit-code) since Wed 2020-03-11 19:44:18 CET; 5s
ago
Docs: man:named(8)
Process: 57887 ExecStart=/usr/sbin/named -f $OPTIONS (code=exited,
status=1/FAILURE)
Main PID: 57887 (code=exited, status=1/FAILURE)
Mar 11 19:44:18 samsung6-ubuntu named[57887]: adjusted limit on open files from
524288 to 1048576
Mar 11 19:44:18 samsung6-ubuntu named[57887]: found 8 CPUs, using 8 worker
threads
Mar 11 19:44:18 samsung6-ubuntu named[57887]: using 8 UDP listeners per
interface
Mar 11 19:44:18 samsung6-ubuntu named[57887]: using up to 21000 sockets
Mar 11 19:44:18 samsung6-ubuntu named[57887]: loading configuration from
'/etc/bind/named.conf'
Mar 11 19:44:18 samsung6-ubuntu named[57887]: /etc/bind/named.conf.options:48:
option 'geoip-directory' was not enabled at compile time
Mar 11 19:44:18 samsung6-ubuntu named[57887]: loading configuration: failure
Mar 11 19:44:18 samsung6-ubuntu named[57887]: exiting (due to fatal error)
Mar 11 19:44:18 samsung6-ubuntu systemd[1]: named.service: Main process exited,
code=exited, status=1/FAILURE
Mar 11 19:44:18 samsung6-ubuntu systemd[1]: named.service: Failed with result
'exit-code'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866875
Title:
option 'geoip-directory' was not enabled at compile time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1866875/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866875] [NEW] option 'geoip-directory' was not enabled at compile time
Public bug reported: Ubuntu 20.04 bind9 1:9.16.0-1ubuntu3 # systemctl status bind9 ● named.service - BIND Domain Name Server Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-03-10 18:22:42 CET; 2min 21s ago Docs: man:named(8) Main PID: 46665 (code=exited, status=1/FAILURE) Mar 10 18:22:42 samsung6-ubuntu named[46665]: adjusted limit on open files from 524288 to 1048576 Mar 10 18:22:42 samsung6-ubuntu named[46665]: found 8 CPUs, using 8 worker threads Mar 10 18:22:42 samsung6-ubuntu named[46665]: using 8 UDP listeners per interface Mar 10 18:22:42 samsung6-ubuntu named[46665]: using up to 21000 sockets Mar 10 18:22:42 samsung6-ubuntu named[46665]: loading configuration from '/etc/bind/named.conf' Mar 10 18:22:42 samsung6-ubuntu named[46665]: /etc/bind/named.conf.options:48: option 'geoip-directory' was not enabled at compile time Mar 10 18:22:42 samsung6-ubuntu named[46665]: loading configuration: failure Mar 10 18:22:42 samsung6-ubuntu named[46665]: exiting (due to fatal error) Mar 10 18:22:42 samsung6-ubuntu systemd[1]: named.service: Main process exited, code=exited, status=1/FAILURE Mar 10 18:22:42 samsung6-ubuntu systemd[1]: named.service: Failed with result 'exit-code'. ** Affects: bind9 (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/1866875 Title: option 'geoip-directory' was not enabled at compile time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1866875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866377] Re: update-initramfs fails on plymouth hook due to missing target dir
I confirm that it is fixed on Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866377 Title: update-initramfs fails on plymouth hook due to missing target dir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1866377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866377] Re: update-initramfs fails on plymouth hook due to missing target dir
Same issue on Ubuntu focal with linux 5.4.0-17-generic x86_64. Purging plymouth then installing it back with all upstream dependencies does not change anything: # apt purge plymouth Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libplymouth5 Use 'apt autoremove' to remove it. The following packages will be REMOVED: lightdm* plymouth* plymouth-label* plymouth-theme-spinner* plymouth-theme-ubuntu-gnome-logo* plymouth-theme-ubuntu-gnome-text* plymouth-theme-ubuntu-logo* plymouth-theme-ubuntu-text* slick-greeter* 0 upgraded, 0 newly installed, 9 to remove and 38 not upgraded. 1 not fully installed or removed. After this operation, 4,028 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 747060 files and directories currently installed.) ... update-alternatives: warning: alternative /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth (part of link group default.plymouth) doesn't exist; removi ng from list of alternatives update-alternatives: warning: /etc/alternatives/default.plymouth is dangling; it will be updated with best choice update-alternatives: using /usr/share/plymouth/themes/bgrt/bgrt.plymouth to provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in auto mode update-initramfs: deferring update (trigger activated) ... # apt autoremove ... # apt install lightdm plymouth plymouth-label plymouth-theme-spinner plymouth-theme-ubuntu-gnome-logo plymouth-theme-ubuntu-gnome-text plymouth-theme-ubuntu-logo plymouth-theme-ubuntu-text slick-greeter Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libplymouth5 Suggested packages: bindfs plymouth-themes The following NEW packages will be installed: libplymouth5 lightdm plymouth plymouth-label plymouth-theme-spinner plymouth-theme-ubuntu-gnome-logo plymouth-theme-ubuntu-gnome-text plymouth-theme-ubuntu-logo plymouth-theme-ubuntu-text slick-greeter 0 upgraded, 10 newly installed, 0 to remove and 38 not upgraded. Need to get 98.8 kB/896 kB of archives. After this operation, 4,453 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 libplymouth5 amd64 0.9.4git20200109-0ubuntu6 [98.8 kB] Fetched 98.8 kB in 0s (426 kB/s) Preconfiguring packages ... Selecting previously unselected package libplymouth5:amd64. ... update-initramfs: Generating /boot/initrd.img-5.4.0-17-generic cp: cannot create regular file '/var/tmp/mkinitramfs_K7OV2b/usr/share/plymouth/themes/spinner/watermark.png': No such file or directory E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-17-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools # apt-file search /usr/share/plymouth/themes/spinner/watermark.png # -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866377 Title: update-initramfs fails on plymouth hook due to missing target dir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1866377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811724] Re: libbd_mdraid.so.2: cannot open shared object file
Ubuntu focal linux 5.4.0-17-generic x86_64 udisks2 2.8.4-1ubuntu1 libblockdev-crypto2 2.23-2ubuntu3 Same issue: udisksd[1920]: Failed to load the 'mdraid' libblockdev plugin Installing libblockdev-mdraid2 pulls in mdadm which is not a solution on systems which don't implement RAID. On such systems, udisksd should not try to load the 'mdraid' libblockdev plugin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811724 Title: libbd_mdraid.so.2: cannot open shared object file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1811724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851144] Re: Switching from unity-greeter to lightdm-gtk-greeter prevents lightdm.service from starting
No such issue with eaon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851144 Title: Switching from unity-greeter to lightdm-gtk-greeter prevents lightdm.service from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1851144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851144] [NEW] Switching from unity-greeter to lightdm-gtk-greeter prevents lightdm.service from starting
Public bug reported: Ubuntu 20.04 lightdm 1.30.0-0ubuntu2 lightdm-gtk-greeter 2.0.6-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7 Uname: Linux 5.3.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 Date: Sun Nov 3 16:15:54 2019 InstallationDate: Installed on 2015-04-28 (1650 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: Upgraded to focal on 2019-11-03 (0 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-30T10:37:29 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851144 Title: Switching from unity-greeter to lightdm-gtk-greeter prevents lightdm.service from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1851144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles
It has been fixed in Fedora and Arch, where is the fix for Ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles
Is there a testing package including the fix that we could test please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658233] Re: missing apparmor rules
On eoan, we need to add even more lines (I prefer to use /etc/apparmor.d/local/usr.sbin.mysqld): dbus send bus=system path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=GetDynamicUsers peer=(name=org.freedesktop.systemd1), capability dac_read_search, /proc/*/status r, /sys/devices/system/node/ r, /sys/devices/system/node/** r, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658233 Title: missing apparmor rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1658233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785693] Re: package mysql-server-5.7 5.7.23-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
A very similar issue happened with 5.7.27-0ubuntu2 which needs to upgrade the database; in my setup, the datadir was not in the default folder /var/lib/mysql. This means that the variable datadir describing a non-default location in /etc/mysql/mysql.cnf pointed by /etc/mysql/my.cnf has been overlooked. A workaround is to: - stop mysql.service - rsync all data located in the folder pointed by datadir into /var/lib/mysql - upgrade mysql-server-5.7 - stop mysql.service - rsync all upgraded data back to its original non-default location - restart mysql.service Et voilà! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785693 Title: package mysql-server-5.7 5.7.23-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1785693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785693] Re: package mysql-server-5.7 5.7.23-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
** Changed in: mysql-5.7 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785693 Title: package mysql-server-5.7 5.7.23-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1785693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
I confirm that on Ubuntu Eoan with: - linux kernel 5.2.0-8.9 - gcc-9 9.1.0-8ubuntu1 I am able to: - build DPDK 19.05 - install xtables-addons-dkms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
Same issue with: Ubuntu 19.10 xtables-addons-dkms 3.2-1ubuntu2 linux kernel 5.0.0-17 and 5.0.0-20 gcc-9: 9.1.0-6ubuntu2 The compilation complains that: echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ but both files are present. Later on, I get a huge number of similar errors like the following: ./include/linux/compiler.h:192:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible Switching to gcc-8 works around this critical issue. ** Attachment added: "/var/crash/xtables-addons-dkms.0.crash" https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1830961/+attachment/5275942/+files/xtables-addons-dkms.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
** Also affects: xtables-addons (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/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831384] Re: .desktop files not working in Ubuntu 19.04 Gnome
In gnome-shell itself, in overview mode and either as favorite or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831384 Title: .desktop files not working in Ubuntu 19.04 Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831384] Re: .desktop files not working in Ubuntu 19.04 Gnome
Log in journalctl: gnome-shell[610]: g_environ_setenv: assertion 'value != NULL' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831384 Title: .desktop files not working in Ubuntu 19.04 Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831384] Re: .desktop files not working in Ubuntu 19.04 Gnome
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831384 Title: .desktop files not working in Ubuntu 19.04 Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831384] [NEW] .desktop files not working in Ubuntu 19.04 Gnome
Public bug reported: I use several instances of Firefox, that I usually launch from various launchers. For example, I have a `firefox-test.desktop` file in `~/.local/share/applications`, that contains: ``` [Desktop Entry] Version=1.0 Name=Firefox-Test StartupWMClass=firetest Exec=firefox --new-instance --no-remote -P Test --class firetest %u Icon=firefox-developer-icon Terminal=false Type=Application MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https; StartupNotify=true Categories=Network;WebBrowser; Keywords=web;browser;internet;pentest; Actions=new-window;new-private-window; ``` It worked for ages, in many DE, including GNOME in 18.04. But, in 19.04, clicking on my launchers does nothing. On the other hand, the commands works from the terminal: ``` firefox --new-instance --no-remote -P Test --class firetest ``` ** Affects: 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/1831384 Title: .desktop files not working in Ubuntu 19.04 Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1831384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
upstream bug report confirms that this is a bug in Ubuntu: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/132 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/issues #132 https://gitlab.gnome.org/GNOME/gnome-terminal/issues/132 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1691678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464064] Re: Ubuntu apt repos are not available via HTTPS
I cannot believe that Canonical has not decided to use https for all their apt repositories. - it is very easy to setup https sites - the users should at least have the choice between http and https to accommodate with die hard http fans (fanatics?) Maybe those year old arguments in favor of https may sway some votes: https://blog.packagecloud.io/eng/2018/02/21/attacks-against-secure-apt- repositories -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464064 Title: Ubuntu apt repos are not available via HTTPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1464064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
I have just found the following message in syslog: Feb 12 13:25:56 samsung5-ubuntu colord-sane: message repeated 2 times: [ [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address] that matches: ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled) Active: active (running) since Tue 2019-02-12 02:30:41 CET; 11h ago Main PID: 2098 (colord) Tasks: 3 (limit: 4915) Memory: 14.9M CGroup: /system.slice/colord.service └─2098 /usr/lib/colord/colord Feb 12 02:30:41 samsung5-ubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles... Feb 12 02:30:41 samsung5-ubuntu systemd[1]: Started Manage, Install and Generate Color Profiles. Feb 12 02:30:42 samsung5-ubuntu colord[2098]: failed to get session [pid 2118]: No data available Feb 12 02:30:42 samsung5-ubuntu colord-sane[2240]: [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address This lead me to investigate the SANE scanner and more specifically /etc/sane.d/dll.conf which seems to list image scanner hardware drivers, including canon ones. However, commenting out 'net' or all canon-related lines does not change anything: # systemctl restart colord # systemctl status colord ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled) Active: active (running) since Tue 2019-02-12 14:21:12 CET; 4s ago Main PID: 31838 (colord) Tasks: 4 (limit: 4915) Memory: 8.0M CGroup: /system.slice/colord.service └─31838 /usr/lib/colord/colord Feb 12 14:21:12 samsung5-ubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles... Feb 12 14:21:12 samsung5-ubuntu systemd[1]: Started Manage, Install and Generate Color Profiles. Feb 12 14:21:13 samsung5-ubuntu colord-sane[31859]: [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
I ha -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
If anyone knows a way to pinpoint some process which sends some specific packets, I'd be glad to investigate further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
I experience the same symptoms on Ubuntu 19.04 disco, but there is no cups* packages installed: # apt-cache policy cups*| grep Installed | grep -v none # The issue is definitely unrelated to CUPS. Some other process sends many strange IPv6/UDP packets to all IPv6 local nodes with 2 different types; the wireshark trace shows 2 types of "Discover scanner commands": 1. source port 8612 (canon-bjnp2) --> dest port 8610 (canon-mfnp) 2. source port 8612 (canon-bjnp2) --> dest port 8612 (canon-bjnp2) I have no canon device on the network nor on the server and no USB device connected on the server. There is no canon related package/kernel module installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable
Probably, lot of clues there: https://bugzilla.redhat.com/show_bug.cgi?id=1602985 Some upstream patches seem to be availabe, can they be ported to Ubuntu ? ** Bug watch added: Red Hat Bugzilla #1602985 https://bugzilla.redhat.com/show_bug.cgi?id=1602985 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787867 Title: Ubuntu 18.04 LTS bluetooth left discoverable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable
I can't believe that such a basic security/privacy issue has not been fixed yet. Normally, the device should only be discoverable when the bluetooth settings are opened. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787867 Title: Ubuntu 18.04 LTS bluetooth left discoverable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800464] Re: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0
Upgrading to disco 19.04 does not solve the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800464 Title: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800464] Re: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0
1. When I try "ubuntu-bug crashfile.crash" to send the report, the screen
becomes endlessly filled with dots.
2. The last report is 2 years old.
3. - Applying workaround (commenting out line 23 ("'problem_types': ['Bug',
'Package'],") in '/etc/apport/crashdb.conf')
- rebooting & crashing (no login)
- rebooting in recovery mode
- realizing that no new crash file has been generated
- apt install python-launchpadlib to solve issue from first step
- ubuntu-bug /var/crash/crashfile.crash
It has been privately reported as "gnome-control-center crashed with
SIGABRT".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800464
Title:
CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800464/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800464] Re: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0
On a different Cosmic platform, the symptoms are a little bit different: "traps: gnome-shell general protection error:0 in libglib-2.0.so.0.5800.1" ... Oct 28 22:00:24 msi-ge60-ubuntu kernel: [ 77.307798] traps: gnome-shell[4865] general protection ip:7f7b32927c00 sp:7fff46026330 error:0 in libglib-2.0.so.0.5800.1[7f7b32907000+7d000] Oct 28 22:00:25 msi-ge60-ubuntu gnome-session[4202]: gnome-session-binary[4202]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 28 22:00:25 msi-ge60-ubuntu gnome-session[4202]: gnome-session-binary[4202]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Oct 28 22:00:25 msi-ge60-ubuntu kernel: [ 77.469526] rfkill: input handler enabled Oct 28 22:00:25 msi-ge60-ubuntu gnome-session[4202]: gnome-session-binary[4202]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 28 22:00:25 msi-ge60-ubuntu gnome-session-binary[4202]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 28 22:00:25 msi-ge60-ubuntu gnome-session-binary[4202]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 28 22:00:25 msi-ge60-ubuntu pulseaudio[4495]: ICE default IO error handler doing an exit(), pid = 4495, errno = 11 Oct 28 22:00:25 msi-ge60-ubuntu kdeconnectd.desktop[4721]: ICE default IO error handler doing an exit(), pid = 4721, errno = 11 Oct 28 22:00:25 msi-ge60-ubuntu at-spi-bus-launcher[]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800464 Title: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800464] [NEW] CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0
Public bug reported: Ubuntu 18.10 gnome-shell 3.30.1-2ubuntu1 libmozjs-60-0 60.2.3-1 >From /var/log/syslog: ... Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: g_dir_open_with_errno: assertion 'path != NULL' failed Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: JS WARNING: [resource:///org/gnome/shell/ui/status/system.js 268]: reference to undefined property "names" Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: JS ERROR: TypeError: app.app_info.get_icon(...).names is undefined#012_createSubMenu@resource:///org/gnome/shell/ui/status/system.js:268:33#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init@resource:///org/gnome/shell/ui/status/system.js:126:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_init@resource:///org/gnome/shell/ui/panel.js:721:24#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1132:25#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_updateBox@resource:///org/gnome/shell/ui/panel.js:1143:29#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_updatePanel@resource:///org/gnome/shell/ui/panel.js:1053:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init@resource:///org/gnome/shell/ui/panel.js:831:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_initializeUI@resource:///org/gnome/shell/ui/main.js:187:13#012start@resource:///org/gnome/shell/ui/main.js:136:5#012@:1:31 Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: Execution of main.js threw exception: Script threw an exception Oct 29 13:50:40 samsung5-ubuntu kernel: [ 34.380764] gnome-shell[4827]: segfault at 168 ip 7ffb177078ae sp 7ffcb7739a00 error 4 in libmozjs-60.so.0.0.0[7ffb1767b000+709000] Oct 29 13:50:40 samsung5-ubuntu kernel: [ 34.380769] Code: fe ff ff 49 8b 54 24 40 48 89 95 a8 fe ff ff 48 8d 9d a0 fe ff ff 49 89 5c 24 40 49 8b 94 24 a8 00 00 00 48 8b 92 c8 2a 00 00 <48> 3b 82 68 01 00 00 0f 84 a3 66 00 00 49 8b 45 f8 48 89 85 f0 fe Oct 29 13:50:40 samsung5-ubuntu gnome-session[4565]: gnome-session-binary[4565]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 29 13:50:40 samsung5-ubuntu gnome-session[4565]: gnome-session-binary[4565]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 29 13:50:40 samsung5-ubuntu gnome-session[4565]: gnome-session-binary[4565]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 29 13:50:40 samsung5-ubuntu at-spi-bus-launcher[4567]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" ... I tried to uninstall all gnome-shell-extensions packages, but the behavior is exactly the same. ** Affects: gnome-shell (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/1800464 Title: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769016] Re: nsswitch.conf doesn't specify 'resolve' to support systemd-resolved
For some reason, libnss-resolve package was missing on my system. Now, it works as expected with the nsswitch.conf change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769016 Title: nsswitch.conf doesn't specify 'resolve' to support systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1769016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769016] Re: nsswitch.conf doesn't specify 'resolve' to support systemd-resolved
Same issue with OpenVPN, but my changes to nsswitch.conf seem to be ignored. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769016 Title: nsswitch.conf doesn't specify 'resolve' to support systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1769016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752081] Re: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Same issue on Cosmic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752081 Title: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1752081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741672] [NEW] Cannot build 235-3ubuntu3 due to missing ... libsystemd-shared-235.so
Public bug reported: Ubuntu 17.10 systemd 234-2ubuntu12.1 Building 235-3ubuntu3 from sources with: dpkg-buildpackage --no-sign --build=binary leads to: ... dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-journal-remote/lib/systemd/systemd-journal-remote (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-journal-remote/lib/systemd/systemd-journal-upload (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-journal-remote/lib/systemd/systemd-journal-gatewayd (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') ... dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-machined (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/bin/machinectl (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-export (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/usr/bin/systemd-nspawn (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-importd (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-import (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-pull (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') It's the first time I meet such a catch 22 issue when building a package. ** Affects: systemd (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/1741672 Title: Cannot build 235-3ubuntu3 due to missing ... libsystemd-shared-235.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738133] Re: gnatstub fails to generate any Ada code
For the record, I downloaded the tar.gz version from adacore website (http://mirrors.cdn.adacore.com/art/591c6d80c7a447af2deed1d7) and I don not experiment this problem with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738133 Title: gnatstub fails to generate any Ada code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asis/+bug/1738133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738403] Re: iptables-save duplicates libvirt rules
It appears that this issue concerns all Linux bridges: # cat iptables/rules.v4 | grep lxcbr0 | sort | uniq -c 7 -A FORWARD -i lxcbr0 -j ACCEPT 7 -A FORWARD -o lxcbr0 -j ACCEPT 7 -A INPUT -i lxcbr0 -p tcp -m tcp --dport 53 -j ACCEPT 7 -A INPUT -i lxcbr0 -p tcp -m tcp --dport 67 -j ACCEPT 7 -A INPUT -i lxcbr0 -p udp -m udp --dport 53 -j ACCEPT 7 -A INPUT -i lxcbr0 -p udp -m udp --dport 67 -j ACCEPT 13 -A POSTROUTING -o lxcbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill ** Summary changed: - iptables-save duplicates libvirt rules + iptables-save duplicates all rules related to Linux bridges -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738403 Title: iptables-save duplicates all rules related to Linux bridges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1738403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738403] [NEW] iptables-save duplicates libvirt rules
Public bug reported: Ubuntu 17.10 iptables 1.6.1-2ubuntu1 Before "iptables-save > /etc/iptables/rules.v4" --- # cat iptables/rules.v4 | grep virbr0 | sort | uniq -c 14 -A FORWARD -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT 14 -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable 14 -A FORWARD -i virbr0 -o virbr0 -j ACCEPT 14 -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable 14 -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT 14 -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT 14 -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT 14 -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT 14 -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT 14 -A OUTPUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT 33 -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill 1 -A ufw-user-input -i virbr0 -j ACCEPT 1 -A ufw-user-output -o virbr0 -j ACCEPT After "iptables-save > /etc/iptables/rules.v4" -- # cat iptables/rules.v4 | grep virbr0 | sort | uniq -c 15 -A FORWARD -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT 15 -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable 15 -A FORWARD -i virbr0 -o virbr0 -j ACCEPT 15 -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable 15 -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT 15 -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT 15 -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT 15 -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT 15 -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT 15 -A OUTPUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT 34 -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill 1 -A ufw-user-input -i virbr0 -j ACCEPT 1 -A ufw-user-output -o virbr0 -j ACCEPT It looks like iptables-save is confused by virbrn entries and duplicates them each time it is run. ** Affects: iptables (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/1738403 Title: iptables-save duplicates libvirt rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1738403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738133] Re: gnatstub fails to generate any Ada code
when I contacted Adacore abot this issue, I got the following answer: The way you are using gnatstub is correct, and I can confirm that it works for AdaCore products. But we cannot say anything for the GNAT versions built and distributed outside AdaCore. Somehow the issue seems specific to the binary distributed in the ubuntu package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738133 Title: gnatstub fails to generate any Ada code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asis/+bug/1738133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738133] [NEW] gnatstub fails to generate any Ada code
Public bug reported: I am trying to use gnatstub on my ubuntu 17.10 system. I have installed the asys-programs 2017-2 through the package manager. I am trying to generate the stub function (adb file) from the following file (tiny.ads). package tiny is procedure simple_procedure; function simple_function return boolean; end tiny; When I run gnatstub, I get the following output. $ gnatstub tiny.ads +===ASIS BUG DETECTED==+ | ASIS 2.0.R for GNAT 7.2.0 CONSTRAINT_ERROR a4g-gnat_int.adb:247 range check failed| | when processing A4G.Contt.SD.Read_and_Check_New (tree file /home/jcd/Projects/hypervisor/moth/tiny.adt)| | Please submit a bug report; see http://gcc.gnu.org/bugs.html.| | Use a subject line meaningful to you and us to track the bug.| | Include the entire contents of this bug box and the ASIS debug info | | in the report. | | Include the exact list of the parameters of the ASIS queries | | Asis.Implementation.Initialize and Asis.Ada_Environments.Associate | | from the ASIS application for which the bug is detected | | Also include sources listed below in gnatchop format | | (concatenated together with no headers between files). | | NOTE: ASIS bugs may be submitted to rep...@adacore.com | +==+ Please include these source files with error report Note that list may not be accurate in some cases, so please double check that the problem can still be reproduced with the set of files listed. $ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: asis-programs 2017-2 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 14 06:45:58 2017 InstallationDate: Installed on 2016-04-23 (599 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: asis UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: asis (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738133 Title: gnatstub fails to generate any Ada code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asis/+bug/1738133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731428] Re: gnome-session-binary: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
There is no TryExec in gnome-settings-daemon.desktop: [Desktop Entry] Type=Application Name=GNOME Settings Daemon Exec=/usr/lib/gnome-settings-daemon/gnome-settings-daemon-localeexec OnlyShowIn=GNOME; NoDisplay=false X-GNOME-Autostart-Phase=Initialization X-GNOME-Autostart-Notify=true X-GNOME-AutoRestart=true X-Ubuntu-Gettext-Domain=gnome-settings-daemon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731428 Title: gnome-session-binary: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731428] [NEW] gnome-session-binary: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Public bug reported: On Ubuntu 17.10 artful gnome-session 3.26.1-0ubuntu6 gnome-settings-daemon 3.26.1-0ubuntu5 Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: gnome-session-binary[6947]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: gnome-session-binary[6947]: CRITICAL: We failed, but the fail whale is dead. Sorry Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: CRITICAL: We failed, but the fail whale is dead. Sorry There is no other mention of org.gnome.SettingsDaemon.Color.desktop before in syslog and kern.log, which is odd. However, I found the following lines earlier in syslog regarding gnome-settings-daemon: Nov 10 09:17:12 samsung-ubuntu gnome-session[6947]: gnome-session-binary[6947]: WARNING: Could not parse desktop file gnome-settings-daemon.desktop or it references a not found TryExec binary Nov 10 09:17:12 samsung-ubuntu gnome-session-binary[6947]: WARNING: Could not parse desktop file gnome-settings-daemon.desktop or it references a not found TryExec binary I'll try to reinstall gnome-settings-daemon. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-settings-daemon 3.26.1-0ubuntu5 Uname: Linux 4.13.0-16-generic x86_64 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 10 09:18:44 2017 ** Affects: gnome-session (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/1731428 Title: gnome-session-binary: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1731428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692073] Re: check_clamav test fails
If, and only if, I add the following 2 lines to debian/rules, the build passes: override_dh_shlibdeps: dh_shlibdeps --dpkg-shlibdeps-params=--ignore-missing-info -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692073 Title: check_clamav test fails To manage notifications about this bug go to: https://bugs.launchpad.net/clamav/+bug/1692073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692073] Re: check_clamav test fails
Building 0.99.2+dfsg-6ubuntu2 in **Zesty**: dpkg-shlibdeps: error: no dependency information found for /usr/lib/libxml2.so.2 (used by debian/libclamav7/usr/lib/x86_64-linux-gnu/libclamav.so.7.1.1) Hint: check if the library actually comes from a package. dh_shlibdeps: dpkg-shlibdeps -Tdebian/libclamav7.substvars debian/libclamav7/usr/lib/x86_64-linux-gnu/libclamav.so.7.1.1 returned exit code 2 dh_shlibdeps: Aborting due to earlier error debian/rules:71: recipe for target 'binary' failed make: *** [binary] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 Although: # apt-cache policy libxml2-dev libxml2-dev: Installed: 2.9.4+dfsg1-2.2 It turns out that the requested file does not exist in Zesty: # apt-file search /usr/lib/libxml2.so.2 # However, the same requested lib file is offered in another location by libxml2: 1) in Zesty: --- # apt-file search libxml2.so.2 ... libxml2: /usr/lib/x86_64-linux-gnu/libxml2.so.2 ... 2) in Artful: # dpkg --contents libxml2_2.9.4+dfsg1-3build2_amd64.deb | grep libxml2.so.2 -rw-r--r-- root/root 1801528 2017-08-02 22:08 ./usr/lib/x86_64-linux-gnu/libxml2.so.2.9.4 lrwxrwxrwx root/root 0 2017-08-02 22:08 ./usr/lib/x86_64-linux-gnu/libxml2.so.2 -> libxml2.so.2.9.4 In both Ubuntu releases, the file libxml2.so.2 is located in: /usr/lib/x86_64-linux-gnu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692073 Title: check_clamav test fails To manage notifications about this bug go to: https://bugs.launchpad.net/clamav/+bug/1692073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692073] Re: check_clamav test fails
I tried to build it with: apt-cache policy llvm llvm: Installed: 1:4.0-34ubuntu2 I also had no issue when building from the exact same clamav sources (0.99.2+dfsg-6) while on Ubuntu yakkety which uses llvm-3.9. It seems that the issue originates from incompatibility(ies) between clamav and llvm-4.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692073 Title: check_clamav test fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1692073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647166] [NEW] systemd-networkd Lost wlan0 carrier although it is always there and strong
Public bug reported: On Ubuntu 16.10 4.8 with systemd 231-9ubuntu1 Wlan0 carrier is lost now and then although there is no apparent reason: the signal which is broadcasted by the nearby AP remains always strong just a few feet away. All the related logs are attached. What could trigger the error message "systemd-networkd[2940]: wlan0: Lost carrier" (line 577 in log) other than a weak signal? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: lost-carrier systemd-networkd ** Attachment added: "Logs" https://bugs.launchpad.net/bugs/1647166/+attachment/4787322/+files/WiFi-troubleshoot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647166 Title: systemd-networkd Lost wlan0 carrier although it is always there and strong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
Well… Switching to another window manager doesn't solve the “any 3D/GLX app would crash” issue… In my case I would have preferred to use the nouveau driver from the beginning, except that for ancient cards like the 6150SE it makes the whole system freeze after only a few minutes… Finally, I was so p*ssed off about this bug and the fact that I have to tune this or that after some security update, that I looked back into this nouveau driver bug for 2 days and finally found a way to use it without patching/installing anything or totally disabling all graphic accelerations. (options nouveau config="PMPEG=0" => works for me/my card) So now that I have returned to The open and happy world and am not concerned with this bug anymore. Goodluck everybody else! :-P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
FYI, after a kernel upgrade the NVIDIA driver was unusable again. This time was because of the DKMS mechanism which, for whatever reason I didn't investigate yet (could it be because of the apt-pinning??), didn't success to build and install the nvidia_304.ko module for the new kernel. If that happens to you, the solution is to run these commands: dpkg-reconfigure nvidia-304 service lightdm restart (no need to reboot) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
Sorry for the typos and long-lines… Can't find a way to edit back my posts… :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
In my case I have a GeForce 6150SE so I really need this 304.131 and can't higher version like 340.xx. For people needing to downgrade, this is one (among others) correct way to do so with Ubuntu 16.04: - first create a file named /etc/apt/preferences.d/local-nvidia-quirks with the following content: Explanation: block this specifique update because of OpenGL problem with 304.132 Package: nvidia-304 Pin: version 304.132-0ubuntu0.16.04.2 Pin-Priority: -10 Explanation: block this specifique update because of OpenGL problem with 304.132 Package: nvidia-opencl-icd-304 Pin: version 304.132-0ubuntu0.16.04.2 Pin-Priority: -10 - then reinstall the working old packages (they are still available in the repository): sudo apt install nvidia-304=304.131-0ubuntu3 nvidia-opencl- icd-304=304.131-0ubuntu3 - finally, reboot your computer (because it also affects the initrd boot image) The previous way only blocks the currently known not working version, without blocking future updates. If you want a way to stay at the known working version without further updates, here is the content you should use for your /etc/apt/preferences.d/local-nvidia-quirks: Explanation: do not use any other version than this one, ever (priority 1001 will ensure that) Package: nvidia-304 Pin: version 304.131-0ubuntu3 Pin-Priority: 1001 Explanation: do not use any other version than this one, ever (priority 1001 will ensure that) Package: nvidia-opencl-icd-304 Pin: version 304.131-0ubuntu3 Pin-Priority: 1001 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
Since this problem greatly affects usability (no graphic login anymore), may be it's worth (in the users' point of view) creating a “fake version” security-upgrade like "304.132-0ubuntu0.16.04.2+really304.131" to fill the gap while waiting for Nvidia to provide a fix for 304.132, IMHO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
** Bug watch added: Debian Bug tracker #840342 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342 ** Also affects: nvidia-graphics-drivers-legacy-304xx (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342 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/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
A debdiff between the packages shows the difference is mainly a version upgrade from 304.131 to 304.132. And it seems a lot of people are experiencing problems with version 304.132, cf https://devtalk.nvidia.com/search/more/sitecommentsearch/304.132/ A specific thread retained my attention: https://devtalk.nvidia.com/default/topic/968892/linux/geforce-7300le- with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request- badvalue-quot-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
FYI, downgrade “solved” the problem for me too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573464] Re: Could not install 'fwupdate' during upgrade 15.10 -> 16.04
It"s much too late. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573464 Title: Could not install 'fwupdate' during upgrade 15.10 -> 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1573464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385390] Re: package ack-grep 2.12-1 failed to install/upgrade: trying to overwrite `/usr/bin/ack', which is the diverted version of `/usr/bin/ack-grep'
Comment #3 fixes it for me as well. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385390 Title: package ack-grep 2.12-1 failed to install/upgrade: trying to overwrite `/usr/bin/ack', which is the diverted version of `/usr/bin/ack-grep' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ack-grep/+bug/1385390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447345] Re: Support the unprivileged namespace sandbox
Same here with Evince not being able to lauch the browser when you clic on a link inside a PDF: apparmor="DENIED" operation="capable" profile="/usr/bin/evince//sanitized_helper" pid=16137 comm="chromium- browse" capability=21 capname="sys_admin" ** Also affects: evince (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/1447345 Title: Support the unprivileged namespace sandbox To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1447345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619870] [NEW] fatal error during build: runtime: type offset out of range
Public bug reported:
Ubuntu 16.04 4.4.0-36
snapd git sources 2.14.2.16.04
echo
echo Cleaning
echo
cd git-snapd
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/cheggaaa/pb
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/mvo5/uboot-go
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/yaml.v2
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gorilla/context
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gorilla/mux
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/kr/pty
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/macaroon.v1
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/tomb.v2
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/tylerb/graceful.v1
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gorilla/websocket
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gosexy/gettext
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/jessevdk/go-flags
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/peterh/liner
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/testing-cabal/subunit-go
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/coreos/go-systemd
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/mvo5/goconfigparser
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/golang.org/x/crypto
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/check.v1
git checkout master
git reset --hard
git clean -fxd :/
git pull -v --progress --rebase
git checkout ${release_number}
echo ---
echo Checking Build Dependencies
echo ---
dpkg-checkbuilddeps
godeps -t -u dependencies.tsv
echo
echo Building
echo
dpkg-buildpackage -b -m"Jean-Christophe Manciot
<manciot.jeanchristo...@gmail.com>"
...
src/github.com/snapcore/snapd/i18n/i18n.go
runtime: typeOff 0x50dcc0 out of range 0x4f9000 - 0x55087f
fatal error: runtime: type offset out of range
runtime stack:
runtime.throw(0x542785, 0x21)
/usr/lib/go/src/runtime/panic.go:566 +0x95 fp=0x7fff24bea460
sp=0x7fff24bea440
runtime.(*_type).typeOff(0x52d4c0, 0x50dcc0, 0x0)
/usr/lib/go/src/runtime/type.go:233 +0x353 fp=0x7fff24bea4c0
sp=0x7fff24bea460
runtime.additab(0x5ce100, 0x7fff24be0001)
/usr/lib/go/src/runtime/iface.go:112 +0x1fb fp=0x7fff24bea5b0
sp=0x7fff24bea4c0
runtime.itabsinit()
/usr/lib/go/src/runtime/iface.go:149 +0x79 fp=0x7fff24bea5f0
sp=0x7fff24bea5b0
runtime.schedinit()
/usr/lib/go/src/runtime/proc.go:444 +0x6e fp=0x7fff24bea630
sp=0x7fff24bea5f0
runtime.rt0_go(0x7fff24bea668, 0x3dd, 0x7fff24bea668, 0x0, 0x0, 0x3dd,
0x7fff24bed885, 0x7fff24bed8f4, 0x7fff24bed8f7, 0x7fff24bed95d, ...)
/usr/lib/go/src/runtime/asm_amd64.s:145 +0x14f fp=0x7fff24bea638
sp=0x7fff24bea630
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- fatal error: runtime: type offset out of range
+ fatal error during build: runtime: type offset out of range
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619870
Title:
fatal error during build: runtime: type offset out of range
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1619870/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608179] Re: Multiple failed tests during 2.11 build
First off, your successful tests are not conclusive in this situation: you're
using 16.10 beta when I'm using stable 16.04.
Secondly, I am able to successfully build other go packages, so I don't think
my environment has an issue, but I remain open to all suggestions.
Third, in the meantime, I have found a way (unique to this package) to overcome
the previous error messages with:
echo
echo Cleaning
echo
cd git-snapd
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/cheggaaa/pb
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/mvo5/uboot-go
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/yaml.v2
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gorilla/context
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gorilla/mux
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/kr/pty
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/macaroon.v1
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/tomb.v2
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/tylerb/graceful.v1
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gorilla/websocket
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gosexy/gettext
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/jessevdk/go-flags
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/peterh/liner
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/testing-cabal/subunit-go
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/coreos/go-systemd
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/mvo5/goconfigparser
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/golang.org/x/crypto
rm -rv --dir
/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/check.v1
git checkout master
git reset --hard
git clean -fxd :/
git pull -v --progress --rebase
git checkout ${release_number}
echo ---
echo Checking Build Dependencies
echo ---
dpkg-checkbuilddeps
godeps -t -u dependencies.tsv
...
This forces the fetch of new versions:
update gopkg.in/macaroon.v1 failed; trying to fetch newer version
gopkg.in/macaroon.v1 now at ab3940c6c16510a850e1c2dd628b919f0f3f1464
update gopkg.in/tomb.v2 failed; trying to fetch newer version
gopkg.in/tomb.v2 now at 14b3d72120e8d10ea6e6b7f87f7175734b1faab8
update github.com/cheggaaa/pb failed; trying to fetch newer version
github.com/cheggaaa/pb now at e8c7cc515bfde3e267957a3b110080ceed51354e
update gopkg.in/yaml.v2 failed; trying to fetch newer version
gopkg.in/yaml.v2 now at 49c95bdc21843256fb6c4e0d370a05f24a0bf213
update github.com/coreos/go-systemd failed; trying to fetch newer version
github.com/coreos/go-systemd now at f743bc15d6bddd23662280b4ad20f7c874cdd5ad
update github.com/testing-cabal/subunit-go failed; trying to fetch newer version
github.com/testing-cabal/subunit-go now at
00b258565a5cf3adaa24b68d31c9e6ec3d2cdbe7
update gopkg.in/check.v1 failed; trying to fetch newer version
gopkg.in/check.v1 now at 64131543e7896d5bcc6bd5a76287eb75ea96c673
update github.com/jessevdk/go-flags failed; trying to fetch newer version
github.com/jessevdk/go-flags now at 6b9493b3cb60367edd942144879646604089e3f7
update gopkg.in/tylerb/graceful.v1 failed; trying to fetch newer version
gopkg.in/tylerb/graceful.v1 now at 842f31108f8d3512ce3176d00bf1a32db1d5e3af
update github.com/gorilla/context failed; trying to fetch newer version
github.com/gorilla/context now at 1c83b3eabd45b6d76072b66b746c20815fb2872d
update github.com/gorilla/websocket failed; trying to fetch newer version
github.com/gorilla/websocket now at 234959944d9cf05229b02e8b386e5cffe1e4e04a
update github.com/gosexy/gettext failed; trying to fetch newer version
github.com/gosexy/gettext now at 98b7b91596d20b96909e6b60d57411547dd9959c
update github.com/mvo5/uboot-go failed; trying to fetch newer version
github.com/mvo5/uboot-go now at 361f6ebcbb54f389d15dc9faefa000e996ba3e37
update github.com/mvo5/goconfigparser failed; trying to fetch newer version
github.com/mvo5/goconfigparser now at 26426272dda20cc76aa1fa44286dc743d2972fe8
update golang.org/x/crypto failed; trying to fetch newer version
golang.org/x/crypto now at 611beeb3d5df450a45f4b67f9e25235f54beda72
update github.com/gorilla/mux failed; trying to fetch newer version
github.com/gorilla/mux now at
[Bug 1608179] Re: Multiple failed tests during 2.11 build
I have overlooked some errors during the "godeps -t -u dependencies.tsv" step: /home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/cheggaaa/pb" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/mvo5/uboot-go" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/yaml.v2" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gorilla/context" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gorilla/mux" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/kr/pty" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/macaroon.v1" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/tomb.v2" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/tylerb/graceful.v1" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gorilla/websocket" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/gosexy/gettext" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/jessevdk/go-flags" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/peterh/liner" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/testing-cabal/subunit-go" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/coreos/go-systemd" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/github.com/mvo5/goconfigparser" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/golang.org/x/crypto" is not clean; will not update godeps: "/home/actionmystique/Program-Files/Ubuntu/GO-Packages/src/gopkg.in/check.v1" is not clean; will not update How can I correct this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608179 Title: Multiple failed tests during 2.11 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1608179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608179] [NEW] Multiple failed tests during 2.11 build
Public bug reported: Ubuntu 16.04 4.4.0-31 snapd sources 2.11 from https://github.com/snapcore/snapd echo --- echo Checking Build Dependencies echo --- apt-get update apt-get build-dep snapd cd snapd godeps -t -u dependencies.tsv echo echo Cleaning echo git reset --hard git clean -fxd :/ git checkout master git pull -v --progress --rebase git checkout 2.11 echo echo Building echo dpkg-buildpackage -b -m"Jean-Christophe Manciot <manciot.jeanchristo...@gmail.com>" ... -- FAIL: fsbackstore_test.go:53: fsBackstoreSuite.TestOpenCreateFail fsbackstore_test.go:61: c.Assert(err, ErrorMatches, "cannot create assert storage root: .*") ... value = nil ... regex string = "cannot create assert storage root: .*" ... Error value is nil ... -- FAIL: io_test.go:77: AtomicWriteTestSuite.TestAtomicWriteFileSymlinkNoFollow io_test.go:88: c.Assert(err, NotNil) ... value = nil -- FAIL: io_test.go:77: AtomicWriteTestSuite.TestAtomicWriteFileSymlinkNoFollow io_test.go:88: c.Assert(err, NotNil) ... value = nil ... -- FAIL: policy_test.go:103: policySuite.TestIterOpBadTargetdir policy_test.go:105: c.Check(err, ErrorMatches, `.*unable.*make.*directory.*`) ... error string = "unable to do policyOp(42) for /.Trash-0: not a regular file" ... regex string = ".*unable.*make.*directory.*" -- FAIL: policy_test.go:120: policySuite.TestIterOpInstallBadFilemode policy_test.go:124: c.Check(err, ErrorMatches, ".*unable to open.*") ... value = nil ... regex string = ".*unable to open.*" ... Error value is nil -- FAIL: policy_test.go:127: policySuite.TestIterOpInstallBadTarget policy_test.go:131: c.Check(err, ErrorMatches, ".*unable to create.*") ... value = nil ... regex string = ".*unable to create.*" ... Error value is nil -- FAIL: policy_test.go:134: policySuite.TestIterOpRemoveBadDirmode policy_test.go:140: c.Assert(err, ErrorMatches, ".*unable to remove.*") ... value = nil ... regex string = ".*unable to remove.*" ... Error value is nil ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Whole build log" https://bugs.launchpad.net/bugs/1608179/+attachment/4710735/+files/Multiple%20failed%20tests%20during%20snpad%202.11%20build.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608179 Title: Multiple failed tests during 2.11 build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1608179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586620] Re: debian/clean: config.log: not found
Thanks a lot for clarifying that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586620 Title: debian/clean: config.log: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1586620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586620] Re: debian/clean: config.log: not found
I haven't touch in any way "debian/clean". Regardless, you (or the person responsible for this) could format the version number in such a way that we could still link it to an upstream commit when it does not match a tag; for instance, there are 7.2p2-4ubuntu1, 7.2p2-4, 7.2p2-5... when the latest tag is 7.2p2, so we can't know which commit matches which version. However, if the version had a format such as 7.2p3~git20160520.39c0ceca, we would be able to map it to a known commit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586620 Title: debian/clean: config.log: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1586620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586623] [NEW] debian/clean: debian/openssh-server.sshd.pam: not found
Public bug reported: Ubuntu 16.04 4.4.0-22 Openssh debian 7.2p2-5 echo echo Cleaning echo cd git-openssh git reset --hard git clean -fxd :/ git fetch --progress --prune origin echo --- echo "Copying Debian control folder in the expected location" echo --- rsync -av ../debian . echo echo Building echo dpkg-buildpackage -m"Jean-Christophe Manciot <manciot.jeanchristo...@gmail.com>" ... make[1]: Leaving directory '/home/actionmystique/Program-Files/Ubuntu/OpenSSH/git-openssh' dh_autoreconf_clean dh_clean /home/actionmystique/Program-Files/Ubuntu/OpenSSH/git-openssh/debian/clean: 1: /home/actionmystique/Program-Files/Ubuntu/OpenSSH/git-openssh/debian/clean: config.log: not found /home/actionmystique/Program-Files/Ubuntu/OpenSSH/git-openssh/debian/clean: 2: /home/actionmystique/Program-Files/Ubuntu/OpenSSH/git-openssh/debian/clean: debian/openssh-server.sshd.pam: not found dh_clean: problem reading debian/clean: debian/rules:122: recipe for target 'clean' failed make: *** [clean] Error 127 dpkg-buildpackage: error: debian/rules clean gave error exit status 2 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Attachment added: "debian-clean config.log not found.txt" https://bugs.launchpad.net/bugs/1586623/+attachment/4671771/+files/debian-clean%20config.log%20not%20found.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586623 Title: debian/clean: debian/openssh-server.sshd.pam: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1586623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586620] [NEW] debian/clean: config.log: not found
Public bug reported: Ubuntu 16.04 4.4.0-22 Openssh debian 7.2p2-5 echo echo Cleaning echo cd git-openssh git reset --hard git clean -fxd :/ git fetch --progress --prune origin echo --- echo "Copying Debian control folder in the expected location" echo --- rsync -av ../debian . echo echo Building echo dpkg-buildpackage -m"Jean-Christophe Manciot <manciot.jeanchristo...@gmail.com>" ... make[1]: Leaving directory '/home/actionmystique/Program-Files/Ubuntu/OpenSSH/git-openssh' dh_autoreconf_clean dh_clean /home/actionmystique/Program-Files/Ubuntu/OpenSSH/git-openssh/debian/clean: 1: /home/actionmystique/Program-Files/Ubuntu/OpenSSH/git-openssh/debian/clean: config.log: not found ... ** Affects: openssh (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/1586620 Title: debian/clean: config.log: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1586620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586620] Re: debian/clean: config.log: not found
** Attachment added: "Full log" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1586620/+attachment/4671770/+files/debian-clean%20config.log%20not%20found.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586620 Title: debian/clean: config.log: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1586620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582986] [NEW] NetworkManager service does not start during bootup
Public bug reported: Ubuntu 16.04 4.4.0-22 systemd 229-4 network-manager 1.1.93 network-manager-gnome 1.2.0 Multiple services and targets are deleted by systemd to "break ordering cycle" (cf. boot.log), but NetworkManager is the only one of them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-fs- pre.target,iscsid.service,zfs-fuse.service - cf. their respective logs) which is not started after bootup: sudo systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: inactive (dead) May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job NetworkManager.service/verify-active deleted to break ordering cycle starting with network.target/start Attachments: --- - journalctl -l -b0 --system _COMM=systemd > boot.log - systemctl -l status rpcbind > rpcbind.log - systemctl -l status network.target > network.target.txt - systemctl -l status remote-fs-pre.target > remote-fs-pre.target.log - systemctl -l status sysinit.target > sysinit.target.log - systemctl -l status zfs-fuse.service > zfs-fuse.service.log - systemctl -l status open-iscsi.service > open-iscsi.service.log - systemctl -l status iscsid.service > iscsid.service.log ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: service startup systemd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582986 Title: NetworkManager service does not start during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582986] Re: NetworkManager service does not start during bootup
** Attachment added: "systemctl -l status sysinit.target" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665101/+files/sysinit.target.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582986 Title: NetworkManager service does not start during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582986] Re: NetworkManager service does not start during bootup
** Attachment added: "systemctl -l status rpcbind.service" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665098/+files/rpcbind.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582986 Title: NetworkManager service does not start during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582986] Re: NetworkManager service does not start during bootup
** Attachment added: "systemctl -l status remote-fs-pre.target" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665100/+files/remote-fs-pre.target.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582986 Title: NetworkManager service does not start during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582986] Re: NetworkManager service does not start during bootup
** Attachment added: "systemctl -l status open-iscsi.service" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665103/+files/open-iscsi.service.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582986 Title: NetworkManager service does not start during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582986] Re: NetworkManager service does not start during bootup
** Attachment added: "systemctl -l status zfs-fuse.service" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665102/+files/zfs-fuse.service.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582986 Title: NetworkManager service does not start during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582986] Re: NetworkManager service does not start during bootup
** Attachment added: "systemctl -l status iscsid.service" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665104/+files/iscsid.service.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582986 Title: NetworkManager service does not start during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582986] Re: NetworkManager service does not start during bootup
** Attachment added: "systemctl -l status network.target" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+attachment/4665099/+files/network.target.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582986 Title: NetworkManager service does not start during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
