[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3
After the follow command it got updated. The log is attached. sudo systemctl stop snapd Warning: Stopping snapd.service, but it can still be activated by: snapd.socket ** Attachment added: "snapd log of telegram-desktop updating after 'stop snapd'" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+attachment/5426441/+files/snapd%20log%20on%20telegram-desktop%20updating%20after%20restart%20snap.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839237 Title: snapd disk write usage very high on 19.04 with snapd 2.39.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3
It seems yes, downloads fine after I restart snap. After today's restart, it hangs on the update again on downloading an update of "telegram-desktop". Log of `journalctl -u snapd` with SNAPD_DEBUG=1 SNAPD_DEBUG_HTTP=7 is attached. ** Attachment added: "Log of `journalctl -u snapd` with SNAPD_DEBUG=1 SNAPD_DEBUG_HTTP=7 is attached." https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+attachment/5426434/+files/snapd%20log%20on%20telegram-telegram-desktop%20updating.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839237 Title: snapd disk write usage very high on 19.04 with snapd 2.39.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3
To stop this SSD killing, I ran `sudo systemctl stop snapd`. The daemon doesn't stop (probably depends on `snapd.socket`). But then I run `snap change 79` again and see that` core` is installed, and the load percentage of `chromium` starts to update. The packets are installed in a minute. snap change 79 Status Spawn Ready Summary Donetoday at 06:19 MSK today at 06:19 MSK Проверка доступности необходимых компонентов "core" Donetoday at 06:19 MSK today at 08:34 MSK Загрузить пакет "core" (10185) с канала "latest/stable" Donetoday at 06:19 MSK today at 08:34 MSK Получить и проверить подтверждение для пакета "core" (10185) Donetoday at 06:19 MSK today at 08:34 MSK Подключить пакет "core" (10185) ... Donetoday at 06:19 MSK today at 08:34 MSK Проверка доступности необходимых компонентов "chromium" Donetoday at 06:19 MSK today at 08:36 MSK Загрузить пакет "chromium" (1362) с канала "latest/stable" Donetoday at 06:19 MSK today at 08:36 MSK Получить и проверить подтверждение для пакета "chromium" (1362) Donetoday at 06:19 MSK today at 08:36 MSK Подключить пакет "chromium" (1362) Donetoday at 06:19 MSK today at 08:36 MSK Run pre-refresh hook of "chromium" snap if present Donetoday at 06:19 MSK today at 08:36 MSK Stop snap "chromium" services ... Donetoday at 06:19 MSK today at 08:36 MSK Consider re-refresh of "core", "chromium" .. Consider re-refresh of "core", "chromium" 2020-10-23T08:36:32+03:00 INFO No re-refreshes found. Do I understand correctly that every time the computer starts, it is necessary to manually stop the snap or try to restart it? To avoid killing SSD and wasting resources? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839237 Title: snapd disk write usage very high on 19.04 with snapd 2.39.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3
date Пт 23 окт 2020 08:11:34 MSK snap changes ID Status Spawn Ready Summary 79 Doing today at 06:19 MSK - Автоматически обновить пакеты "core", "chromium" snap change 79 Status Spawn Ready Summary Donetoday at 06:19 MSK today at 06:19 MSK Проверка доступности необходимых компонентов "core" Doing today at 06:19 MSK - Загрузить пакет "core" (10185) с канала "latest/stable" (0.00%) Do today at 06:19 MSK - Получить и проверить подтверждение для пакета "core" (10185) ... skipping the minor "Do"s ... Do today at 06:19 MSK - Start snap "chromium" (1362) services Do today at 06:19 MSK - Remove data for snap "chromium" (1328) Do today at 06:19 MSK - Remove snap "chromium" (1328) from the system Do today at 06:19 MSK - Clean up "chromium" (1362) install Do today at 06:19 MSK - Run configure hook of "chromium" snap if present Do today at 06:19 MSK - Run health check of "chromium" snap Doing today at 06:19 MSK - Consider re-refresh of "core", "chromium" snap list chromium 86.0.4240.751350latest/stable canonical✓- core 16-2.47 10126 latest/stable canonical✓core snap refresh --list chromium 86.0.4240.111 1362canonical✓ - core 16-2.47.1 10185 canonical✓ core Using 23% of CPU. ps aux | grep snap root1124 23.0 0.2 2925732 35356 ? Ssl 06:19 20:18 /usr/lib/snapd/snapd The snap using 99% or 65% + 32% (btrfs filesystem) of SSD disk transfer. sudo atop -D PID SYSCPU USRCPU VGROW RGROW RDDSK WRDSK S CPUNR DSK CMD 1124 0.33s 2.00s 0K 0K 0K 41888K S 4 65% snapd 363 0.08s 0.00s 0K 0K 0K 20288K S 6 32% btrfs-transact sudo pidstat -d -T ALL -p `pidof snapd` 5 Linux 5.4.0-52-generic (desktop)23.10.2020 _x86_64_(12 CPU) 08:15:18 UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command 08:15:230 1124 0,00 4314,57 0,00 0 snapd How you can see, the snap using: 23% of CPU, ~99% disk transfer, writes 4.3 Mb/s (by `atop` writes 43-50 Mb per 10 seconds), I don't see any net traffic. Download status is "(0.00%)" since for 2 hours I turn on my computer. That is, snap written on SSD: 2 hour * 60 min * 60 sec * 4.3 Mb/s = 31 Gb for 2 hours!!! And such still almost each day non-stop... WTF??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839237 Title: snapd disk write usage very high on 19.04 with snapd 2.39.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3
Now I see. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839237 Title: snapd disk write usage very high on 19.04 with snapd 2.39.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3
Yes, "updating chromium" with 4Mb/s write non-stop without net traffic... I yesterday stop it with `sudo systemctl stop snapd`, `sudo kill -9 $(pgrep -fn snapd)`. I don't know if it turned on again later due to the fact that I didn't directly disable snapd.socket. It seems that the Chromium version has been updated from 85 to 86. snap change 76 Status Spawn Ready Summary ... Done3 days ago, at 14:56 MSK today at 00:12 MSKRun health check of "chromium" snap Done3 days ago, at 14:56 MSK today at 00:12 MSKConsider re-refresh of "chromium" Donetoday at 00:12 MSKtoday at 00:12 MSKПодключить chromium:etc-chromium-browser-policies к snapd:system-files Donetoday at 00:12 MSKtoday at 00:12 MSKПодключить chromium:system-packages-doc к snapd:system-packages-doc How can I see that the download is actually working? For example, by increasing the size of downloaded files or the percentage of completion counter. Since according to the commands and files above, there is absolutely no visible progress in downloading and traffic. Could you add such a percent complete counter? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839237 Title: snapd disk write usage very high on 19.04 with snapd 2.39.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3
The problem is still ongoing on 20.04. I have to open the console daily and run the following commands, due to snapd starts to use my SSD non- stop when I restart. This is faking as `updating Chromium`. sudo kill -9 $ (pgrep -fn snapd) sudo systemctl stop snapd sudo systemctl stop snapd.socket sudo systemctl stop snapd.service snap changes ID Status Spawn Ready Summary 76 Doing 2 days ago, at 14:56 MSK - Автоматически обновить "chromium" пакет sudo pidstat -d -T ALL -p `pidof snapd` 5 18:58:15 UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command 18:58:200 1108 0,00 4024,00 0,00 0 snapd sudo fnotifystat Total Open Close Read Write PID Process Pathname 57.0 18.0 18.0 21.00.0 1108 snapd /var/lib/snapd/assertions/asserts-v0/model/16/generic/generic-classic 55.0 18.0 18.0 19.00.0 1108 snapd /var/lib/snapd/assertions/asserts-v0/serial/generic/generic-classic/bd2c60ac-7492-417f-ad47-f1fbcf7e8656 54.0 18.0 18.0 18.00.0 1108 snapd /var/lib/snapd/assertions/asserts-v0/model/16/generic/generic-classic/active 54.0 18.0 18.0 18.00.0 1108 snapd /var/lib/snapd/assertions/asserts-v0/serial/generic/generic-classic/bd2c60ac-7492-417f-ad47-f1fbcf7e8656/active 36.0 18.0 18.00.00.0 1108 snapd /var/lib/snapd 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.4l5jJQdW0sP3~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.4nyNYbyTTJ21~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.54s0KBgLsdSg~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.5ydLLQG7tC30~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.8k0RWXmCjWC8~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.BHfwQMjR6PSV~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.CVcTY7Bmfmdm~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.DpPCvll2h5tG~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.GKBdLMJLJt5t~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.R6jlBXQmTWG7~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.chY4phGDgT2v~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.djJ2sckH3xK0~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.gsxWS3XBnxS8~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.hqsxj4M83rLD~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.mlfyStjYcShW~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.mpfTr1J1pjjG~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.rCTJHYgY9gYh~ 4.01.01.00.02.0 1108 snapd /var/lib/snapd/state.json.rDkhknkNqB3F~ Reading from the `/var/lib/snapd/assertions/...` files, it's just a "device-key". Writing to `/var/lib/snapd/state.json` and 2 files with subnames like `state.json.gTFjQFf8Kpps` it is fake. It writing each second and change only the timestamp string in the files. No any traffic recieving from net. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839237 Title: snapd disk write usage very high on 19.04 with snapd 2.39.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876477] Re: install broken
This is image from http://releases.ubuntu.com/focal/ via torrent. I , written it on a usb-stick and loaded PC from it. The bug was after launch installation. Next try of install with same conditions runs the installation normal. I tried re-installations several times (due to another bug of mysql after installation), and this error appears about in 30% tries of install. I don't know what you talk about /boot/grub/efi.img. I have SSD with BTRFS file system. There is a `boot` partition, remains from previous Ubuntu 19.04 installation. As I said above, on another run of installation it installed normal and work fine with all my partitions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876477 Title: install broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1876477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876477] [NEW] install broken
Public bug reported: Install broken when installing from usb-stick with the fresh Ubuntu 20.04 image ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Sat May 2 18:47:18 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=ru_RU.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876477 Title: install broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1876477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Hi everyone, same here with ubuntu 19.10 and with asus vivobook S14 X420F. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843507] Re: apt-get update to latest libidn2.so.0 causes multiple application failures including apt-update
Thank you VERY MUCH for the fast response @Ondřej, I can confirm it's fixed by just apt update && apt upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843507 Title: apt-get update to latest libidn2.so.0 causes multiple application failures including apt-update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn2/+bug/1843507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843507] Re: apt-get update to latest libidn2.so.0 causes multiple application failures including apt-update
** Changed in: libidn2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843507 Title: apt-get update to latest libidn2.so.0 causes multiple application failures including apt-update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn2/+bug/1843507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843507] Re: apt-get update to latest libidn2.so.0 causes multiple application failures including apt-update
root@tachyon ~ ツ # apt update && apt upgrade Des:1 http://ubuntu.mirrors.ovh.net/ubuntu bionic InRelease [242 kB] Des:2 http://ubuntu.mirrors.ovh.net/ubuntu bionic-updates InRelease [88,7 kB] Des:3 http://ubuntu.mirrors.ovh.net/ubuntu bionic-backports InRelease [74,6 kB] Obj:4 http://ppa.launchpad.net/libreoffice/ppa/ubuntu bionic InRelease Obj:5 http://ppa.launchpad.net/malteworld/ppa/ubuntu bionic InRelease Des:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease [20,8 kB] Des:7 http://security.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB] Obj:8 http://ppa.launchpad.net/transmissionbt/ppa/ubuntu bionic InRelease Obj:9 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease Ign:10 http://packages.elastic.co/elasticsearch/2.x/debian stable InRelease Obj:11 http://packages.elastic.co/elasticsearch/2.x/debian stable Release Des:12 http://repo.percona.com/percona/apt bionic InRelease [15,8 kB] Des:13 http://ppa.launchpad.net/ondrej/php/ubuntu bionic/main amd64 Packages [51,7 kB] Obj:14 http://nginx.org/packages/mainline/ubuntu bionic InRelease Des:15 http://ppa.launchpad.net/ondrej/php/ubuntu bionic/main Translation-en [24,3 kB] Des:16 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [503 kB] Des:18 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [170 kB] Des:19 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [6.712 B] Des:20 http://security.ubuntu.com/ubuntu bionic-security/restricted Translation-en [2.872 B] Des:21 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [604 kB] Descargados 1.893 kB en 2s (957 kB/s) Leyendo lista de paquetes... Hecho Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Calculando la actualización... Hecho Los siguientes paquetes se han retenido: linux-image-generic Se actualizarán los siguientes paquetes: libidn2-0 libidn2-0-dev libidn2-dev libnss-systemd libpam-systemd libsystemd0 libtomcat8-java libudev1 systemd systemd-sysv tomcat8 tomcat8-common udev 13 actualizados, 0 nuevos se instalarán, 0 para eliminar y 1 no actualizados. Se necesita descargar 5.545 kB/9.722 kB de archivos. Se utilizarán 135 kB de espacio de disco adicional después de esta operación. ¿Desea continuar? [S/n] Des:1 http://ppa.launchpad.net/ondrej/php/ubuntu bionic/main amd64 libidn2-dev amd64 2.2.0-1+ubuntu18.04.1+deb.sury.org+1 [68,0 kB] Des:2 http://ppa.launchpad.net/ondrej/php/ubuntu bionic/main amd64 libidn2-0 amd64 2.2.0-1+ubuntu18.04.1+deb.sury.org+1 [66,4 kB] Des:3 http://ppa.launchpad.net/ondrej/php/ubuntu bionic/main amd64 libidn2-0-dev amd64 2.2.0-1+ubuntu18.04.1+deb.sury.org+1 [6.156 B] Des:4 http://security.ubuntu.com/ubuntu bionic-security/main amd64 libnss-systemd amd64 237-3ubuntu10.29 [105 kB] Des:5 http://security.ubuntu.com/ubuntu bionic-security/main amd64 libsystemd0 amd64 237-3ubuntu10.29 [204 kB] Des:6 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 libtomcat8-java all 8.5.39-1ubuntu1~18.04.3 [4.989 kB] Des:7 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 tomcat8-common all 8.5.39-1ubuntu1~18.04.3 [59,3 kB] Des:8 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 tomcat8 all 8.5.39-1ubuntu1~18.04.3 [46,4 kB] Descargados 5.545 kB en 2s (2.243 kB/s) Leyendo el registro de cambios... Hecho Preconfigurando paquetes ... (Leyendo la base de datos ... 200965 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../libnss-systemd_237-3ubuntu10.29_amd64.deb ... Desempaquetando libnss-systemd:amd64 (237-3ubuntu10.29) sobre (237-3ubuntu10.28) ... Preparando para desempaquetar .../libsystemd0_237-3ubuntu10.29_amd64.deb ... Desempaquetando libsystemd0:amd64 (237-3ubuntu10.29) sobre (237-3ubuntu10.28) ... Configurando libsystemd0:amd64 (237-3ubuntu10.29) ... (Leyendo la base de datos ... 200965 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../libpam-systemd_237-3ubuntu10.29_amd64.deb ... Desempaquetando libpam-systemd:amd64 (237-3ubuntu10.29) sobre (237-3ubuntu10.28) ... Preparando para desempaquetar .../systemd_237-3ubuntu10.29_amd64.deb ... Desempaquetando systemd (237-3ubuntu10.29) sobre
[Bug 1843507] Re: apt-get update to latest libidn2.so.0 causes multiple application failures including apt-update
Can confirm here: # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" Errors from a lot of apps, even apt-get itself: /usr/lib/apt/methods/http: relocation error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: symbol _idn2_punycode_decode version IDN2_0.0.0 not defined in file libidn2.so.0 with link time reference E: Method http has died unexpectedly! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843507 Title: apt-get update to latest libidn2.so.0 causes multiple application failures including apt-update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn2/+bug/1843507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785427] [NEW] Ubuntu crashes while installing
Public bug reported: Error message: The installer encountered an error copying files to the hard disk: [Errno 5] Input/output error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 4 17:06:08 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785427 Title: Ubuntu crashes while installing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1785427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745123] Re: Elasticsearch 2.4.6 cause a Oops: 0010 [#37] SMP NOPTI
Just confirming this bug with the same exact versions in Linux Mint: Elasticsearch 2.4.6 + kernel 4.13.0-31-generic #34~16.04.1-Ubuntu syslog Jan 25 00:42:34 DevExMachina systemd[1]: Starting Elasticsearch... Jan 25 00:42:34 DevExMachina systemd[1]: Started Elasticsearch. Jan 25 00:42:35 DevExMachina kernel: [120549.349622] BUG: unable to handle kernel paging request at 06987877 Jan 25 00:42:35 DevExMachina kernel: [120549.350743] IP: 0x6987877 Jan 25 00:42:35 DevExMachina kernel: [120549.351867] PGD 8000b25e1067 Jan 25 00:42:35 DevExMachina kernel: [120549.351867] P4D 8000b25e1067 Jan 25 00:42:35 DevExMachina kernel: [120549.351867] PUD 789bc067 Jan 25 00:42:35 DevExMachina kernel: [120549.351868] PMD 0 Jan 25 00:42:35 DevExMachina kernel: [120549.351868] Jan 25 00:42:35 DevExMachina kernel: [120549.351869] Oops: 0010 [#12] SMP PTI Jan 25 00:42:35 DevExMachina kernel: [120549.351871] Modules linked in: binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp snd_hda_codec kvm_intel snd_hda_core kvm snd_hwdep irqbypass snd_pcm crct10dif_pclmul gpio_ich snd_seq_midi crc32_pclmul snd_seq_midi_event ghash_clmulni_intel snd_rawmidi pcbc snd_seq aesni_intel ipmi_si aes_x86_64 crypto_simd glue_helper cryptd ipmi_devintf snd_seq_device snd_timer intel_cstate hp_wmi input_leds joydev ipmi_msghandler intel_rapl_perf serio_raw sparse_keymap wmi_bmof snd soundcore mei_me mei shpchp lpc_ich tpm_infineon mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_generic usbhid hid dm_mirror dm_region_hash dm_log i915 video i2c_algo_bit drm_kms_helper syscopyarea sysfillrect e1000e Jan 25 00:42:35 DevExMachina kernel: [120549.351895] sysimgblt ahci fb_sys_fops psmouse drm libahci ptp pps_core wmi Jan 25 00:42:35 DevExMachina kernel: [120549.351899] CPU: 1 PID: 15290 Comm: java Tainted: G D 4.13.0-31-generic #34~16.04.1-Ubuntu Jan 25 00:42:35 DevExMachina kernel: [120549.351900] Hardware name: Hewlett-Packard HP Compaq 8200 Elite SFF PC/1495, BIOS J01 v02.15 11/10/2011 Jan 25 00:42:35 DevExMachina kernel: [120549.351900] task: 9d249c8bdd00 task.stack: b51c04064000 Jan 25 00:42:35 DevExMachina kernel: [120549.351901] RIP: 0010:0x6987877 Jan 25 00:42:35 DevExMachina kernel: [120549.351902] RSP: 0018:b51c04067f50 EFLAGS: 00010202 Jan 25 00:42:35 DevExMachina kernel: [120549.351902] RAX: 03e7 RBX: RCX: 7fd744b314d9 Jan 25 00:42:35 DevExMachina kernel: [120549.351903] RDX: 7fd73c5e9830 RSI: 4d73aa93 RDI: Jan 25 00:42:35 DevExMachina kernel: [120549.351903] RBP: R08: 7fd743f97b64 R09: 000c Jan 25 00:42:35 DevExMachina kernel: [120549.351904] R10: 06987877 R11: 9d249c8bdd00 R12: Jan 25 00:42:35 DevExMachina kernel: [120549.351904] R13: R14: R15: Jan 25 00:42:35 DevExMachina kernel: [120549.351905] FS: 7fd74562c700() GS:9d256e24() knlGS: Jan 25 00:42:35 DevExMachina kernel: [120549.351906] CS: 0010 DS: ES: CR0: 80050033 Jan 25 00:42:35 DevExMachina kernel: [120549.351906] CR2: 06987877 CR3: 55dbe004 CR4: 000606e0 Jan 25 00:42:35 DevExMachina kernel: [120549.351907] Call Trace: Jan 25 00:42:35 DevExMachina kernel: [120549.351913] ? entry_SYSCALL_64_fastpath+0x33/0xa3 Jan 25 00:42:35 DevExMachina kernel: [120549.351914] Code: Bad RIP value. Jan 25 00:42:35 DevExMachina kernel: [120549.351915] RIP: 0x6987877 RSP: b51c04067f50 Jan 25 00:42:35 DevExMachina kernel: [120549.351915] CR2: 06987877 Jan 25 00:42:35 DevExMachina kernel: [120549.351934] ---[ end trace fc665251d9746e58 ]--- journalctl -xe ene 25 00:44:51 DevExMachina systemd[1]: Starting Elasticsearch... -- Subject: Unit elasticsearch.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit elasticsearch.service has begun starting up. ene 25 00:44:51 DevExMachina systemd[1]: Started Elasticsearch. -- Subject: Unit elasticsearch.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit elasticsearch.service has finished starting up. -- -- The start-up result is done. ene 25 00:44:51 DevExMachina kernel: BUG: unable to handle kernel paging request at 06987877 ene 25 00:44:51 DevExMachina kernel: IP: 0x6987877 ene 25 00:44:51 DevExMachina kernel: PGD 8000349a2067 ene 25 00:44:51 DevExMachina kernel: P4D 8000349a2067 ene 25 00:44:51 DevExMachina kernel: PUD b25ed067 ene 25 00:44:51 DevExMachina kernel: PMD 0 ene 25 00:44:51 DevExMachina kernel: ene 25
[Bug 1387930] Re: Broken update of duplicity 0.7 in Ubuntu 12.04
Hi Michael ! Sorry for the long time with no updates, you were absolutely right, I had no other installed version, but after checking, in some moment my system lost the PPA keys, so when I updated it no longer got the 0.7 version, so: - I removed the package via apt-get - I manually removed any reference in the system to duplicity - Installed the PPA keys again - Updated - Installed the package again And everything is running smothly now, thank you mate ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387930 Title: Broken update of duplicity 0.7 in Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1387930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387930] Re: Broken update of duplicity 0.7 in Ubuntu 12.04
Not sure if this can help, full output (spanish, sorry!) of the ppa source, remove, reinstall, and version, seems to be installing 0.7.0-0ubuntu0ppa1013~ubuntu12.04.1: UBUNTU ~ # cat /etc/apt/sources.list.d/duplicity-team-ppa-precise.list deb http://ppa.launchpad.net/duplicity-team/ppa/ubuntu precise main deb-src http://ppa.launchpad.net/duplicity-team/ppa/ubuntu precise main UBUNTU ~ # sudo apt-get remove duplicity Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Los siguientes paquetes se ELIMINARÁN: duplicity 0 actualizados, 0 se instalarán, 1 para eliminar y 0 no actualizados. Se liberarán 790 kB después de esta operación. ¿Desea continuar [S/n]? S (Leyendo la base de datos ... 586691 ficheros o directorios instalados actualmente.) Desinstalando duplicity ... Procesando disparadores para man-db ... UBUNTU ~ # sudo apt-get install duplicity Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Paquetes sugeridos: ncftp python-boto Se instalarán los siguientes paquetes NUEVOS: duplicity 0 actualizados, 1 se instalarán, 0 para eliminar y 0 no actualizados. Se necesita descargar 0 B/189 kB de archivos. Se utilizarán 790 kB de espacio de disco adicional después de esta operación. Seleccionando el paquete duplicity previamente no seleccionado. (Leyendo la base de datos ... 586560 ficheros o directorios instalados actualmente.) Desempaquetando duplicity (de .../duplicity_0.7.0-0ubuntu0ppa1013~ubuntu12.04.1_i386.deb) ... Procesando disparadores para man-db ... Configurando duplicity (0.7.0-0ubuntu0ppa1013~ubuntu12.04.1) ... UBUNTU ~ # duplicity -V duplicity 0.6.22 Traceback (most recent call last): File /usr/bin/duplicity, line 1509, in module util.release_lockfile() AttributeError: 'module' object has no attribute 'release_lockfile' UBUNTU ~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387930 Title: Broken update of duplicity 0.7 in Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1387930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387930] Re: Broken update of duplicity 0.7 in Ubuntu 12.04
Still coulnd't update. Tried to remove reinstall, everything went smoohtly, but still have this message version: marcos@copias:~$ duplicity -V duplicity 0.6.22 Traceback (most recent call last): File /usr/bin/duplicity, line 1509, in module util.release_lockfile() AttributeError: 'module' object has no attribute 'release_lockfile' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387930 Title: Broken update of duplicity 0.7 in Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1387930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387930] [NEW] Broken update of duplicity 0.7 in Ubuntu 12.04
Public bug reported:
Ubuntu 12.04.5 LTS
Expected: correct update
Happened: weird errors about gdocs backend
When i do the update:
==
Configuring duplicity (0.7.0-0ubuntu0ppa1012~ubuntu12.04.1) ...
SyntaxError: ('invalid syntax',
('/usr/lib/python2.7/dist-packages/duplicity/backends/gdocsbackend.py', 51,
197, self.client = gdata.docs.client.DocsClient(source='duplicity
Usage: dpkg Options: parser options:
output formats, defaults to 'dpkg'
for compatibility with dpkg
than version
number is lower than 0) ')\n))
dpkg: error processing duplicity (--configure):
duplicity
E: Sub-process /usr/bin/dpkg returned an error code (1)
And afterwards:
==
marcos@copias:~$ duplicity -V
duplicity 0.6.22
Traceback (most recent call last):
File /usr/bin/duplicity, line 1509, in module
util.release_lockfile()
AttributeError: 'module' object has no attribute 'release_lockfile'
APT:
==
marcos@copias:~$ cat /etc/apt/sources.list.d/duplicity-team-ppa-precise.list
deb http://ppa.launchpad.net/duplicity-team/ppa/ubuntu precise main
deb-src http://ppa.launchpad.net/duplicity-team/ppa/ubuntu precise main
marcos@copias:~$ apt-cache policy duplicity
duplicity:
Instalados: 0.7.0-0ubuntu0ppa1012~ubuntu12.04.1
Candidato: 0.7.0-0ubuntu0ppa1012~ubuntu12.04.1
Tabla de versión:
*** 0.7.0-0ubuntu0ppa1012~ubuntu12.04.1 0
500 http://ppa.launchpad.net/duplicity-team/ppa/ubuntu/ precise/main
i386 Packages
100 /var/lib/dpkg/status
0.6.18-0ubuntu3.5 0
500 http://es.archive.ubuntu.com/ubuntu/ precise-updates/main i386
Packages
0.6.18-0ubuntu3 0
500 http://es.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
Thank you.
** Affects: duplicity (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/1387930
Title:
Broken update of duplicity 0.7 in Ubuntu 12.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1387930/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387930] Re: Broken update of duplicity 0.7 in Ubuntu 12.04
sudo apt-get install python-lockfile as suggested in other threads doesn't fix any of the two errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387930 Title: Broken update of duplicity 0.7 in Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1387930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324506] Re: Mouse has suddenly no contact, till X-Server restart
I also have this bug, and it seems to be very similar to the that is described here for archlinux : http://bugs.archlinux.org/task/17037 Apparently, it is besause of xorg-server equals to xserver-xorg on ubuntu... ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Confirmed -- Mouse has suddenly no contact, till X-Server restart https://bugs.launchpad.net/bugs/324506 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
