[Touch-packages] [Bug 1895490] [NEW] no destination host name is cups-browsed running
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 cups-browsed: Installed: 1.27.4-1 cups: Installed: 2.3.1-9ubuntu1.1 I expect to be able to print on my Brother HL-L2350DW printer. I have no problem printing to that printer via Windows 10. I also got this error on Kubuntu 20.04. What happened instead? I cannot get my pdf to print. Instead I get an error that says 'No destination host name supplied by cups-browsed for printer "Brother_HL_L2350DW_series", is cups-browsed running?'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 13 20:30:40 2020 InstallationDate: Installed on 2020-08-16 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Brother_HL_L2350DW_series: implicitclass://Brother_HL_L2350DW_series/ MachineType: LENOVO 20AN00DEUS Papersize: letter PpdFiles: Brother_HL_L2350DW_series: Brother HL-L2350DW series, driverless, cups-filters 1.27.4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=d3493ccb-75ba-4bb9-851d-b3fc4c5adb8f ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GLET96WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00DEUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET96WW(2.50):bd06/20/2018:svnLENOVO:pn20AN00DEUS:pvrThinkPadT440p:rvnLENOVO:rn20AN00DEUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00DEUS dmi.product.sku: LENOVO_MT_20AN_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Printing troubleshooter Queue not enabled" https://bugs.launchpad.net/bugs/1895490/+attachment/5410573/+files/is_cups-browsed_running.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895490 Title: no destination host name is cups-browsed running Status in cups package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 cups-browsed: Installed: 1.27.4-1 cups: Installed: 2.3.1-9ubuntu1.1 I expect to be able to print on my Brother HL-L2350DW printer. I have no problem printing to that printer via Windows 10. I also got this error on Kubuntu 20.04. What happened instead? I cannot get my pdf to print. Instead I get an error that says 'No destination host name supplied by cups-browsed for printer "Brother_HL_L2350DW_series", is cups-browsed running?'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 13 20:30:40 2020 InstallationDate: Installed on 2020-08-16 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Brother_HL_L2350DW_series: implicitclass://Brother_HL_L2350DW_series/ MachineType: LENOVO 20AN00DEUS Papersize: letter PpdFiles: Brother_HL_L2350DW_series: Brother HL-L2350DW series, driverless, cups-filters 1.27.4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=d3493ccb-75ba-4bb9-851d-b3fc4c5adb8f ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GLET96WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00DEUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET96WW(2.50):bd06/20/2018:svnLENOVO:pn20AN00DEUS:pvrThinkPadT440p:rvnLENOVO:rn20AN00DEUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00DEUS dmi.product.sku: LENOVO_MT_20AN_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO
[Touch-packages] [Bug 1841640] [NEW] package rsync 3.1.1-3ubuntu1 failed to install/upgrade: pacote rsync não está pronto para configuração não posso configurar (estado atual 'half-installed')
Public bug reported: No se bien lo que acontecio. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: rsync 3.1.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: oem-workaround-force-install-intel-red: Remove oem-workaround-force-install-qualcomm-red: Remove rsync: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon Aug 26 06:37:59 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DpkgTerminalLog: A remover oem-workaround-force-install-intel-red (1.4) ... A remover oem-workaround-force-install-qualcomm-red (3.2) ... dpkg: erro ao processar o pacote rsync (--configure): pacote rsync não está pronto para configuração não posso configurar (estado atual 'half-installed') ErrorMessage: pacote rsync não está pronto para configuração não posso configurar (estado atual 'half-installed') InstallationDate: Installed on 2019-08-01 (25 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.29ubuntu0.1 SourcePackage: rsync Title: package rsync 3.1.1-3ubuntu1 failed to install/upgrade: pacote rsync não está pronto para configuração não posso configurar (estado atual 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1841640 Title: package rsync 3.1.1-3ubuntu1 failed to install/upgrade: pacote rsync não está pronto para configuração não posso configurar (estado atual 'half-installed') Status in rsync package in Ubuntu: New Bug description: No se bien lo que acontecio. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: rsync 3.1.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: oem-workaround-force-install-intel-red: Remove oem-workaround-force-install-qualcomm-red: Remove rsync: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon Aug 26 06:37:59 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DpkgTerminalLog: A remover oem-workaround-force-install-intel-red (1.4) ... A remover oem-workaround-force-install-qualcomm-red (3.2) ... dpkg: erro ao processar o pacote rsync (--configure): pacote rsync não está pronto para configuração não posso configurar (estado atual 'half-installed') ErrorMessage: pacote rsync não está pronto para configuração não posso configurar (estado atual 'half-installed') InstallationDate: Installed on 2019-08-01 (25 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.29ubuntu0.1 SourcePackage: rsync Title: package rsync 3.1.1-3ubuntu1 failed to install/upgrade: pacote rsync não está pronto para configuração não posso configurar (estado atual 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1841640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Hola creo recordar que utilicé estos comandos: sudo mv / usr / share / dbus-1 / system- servicios / org.freedesktop .systemd1. servicio / usr / share / dbus-1 / system- servicios / org.freedesktop .systemd1. Servicio. bak sudo apt-get install -f sudo apt dist-upgrade sudo apt autoremove A mi me funcionó correctamente, pero no lo almacené. Puede ser otro problema con el mismo resultado. Otra solución, que apliqué en un laptop fue sacar un back-up de los archivos de usuario, documentos, descargas... Y reinstalar la nueva versión desde 0 Sañudos El jue., 11 abr. 2019 0:45, loluchayjose <1773...@bugs.launchpad.net> escribió: > Bueno, ninguna de las soluciones aquí está muy clara. Una de ellas es > "sudo apt purge gdm etc."... "etc." que? > > Varios dicen "borrar"... borrar como? > > Tu dijiste: "I solved problem sttoping services and erasing systemd-shim > upon console. > After I could updating my pc, also, from console"... Qué servicios > paraste, y como? Tengo que hacerlo en Safe Mode? > > Uno de los últimos dice: "The upload of systemd that was purported to > fix this bug report was superseded by a security update of systemd so > the fix is no longer available." Así que por lo que se ve, esa solucion > ya no sirve. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > Triaged > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial, ie. > > lxc launch ubuntu-daily:xenial test-shim-upgrade > lxc exec test-shim-upgrade > apt update > apt install systemd-shim > wget > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > apt install ./systemd-shim_10-3_amd64.deb > sed 's/xenial/bionic/' -i /etc/apt/sources.list > apt update > apt install systemd > > this currently passes, however, systemd-shim remains installed. It > should be removed instead. Apt install systemd should have lines like > this: > > The following packages will be REMOVED: > systemd-shim > ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > ... > > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > >
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Good night looking for internet, there are many solutions. The treat can help you. Kind regards. Buenas noches, busca en Internet hay muchas soluciones a este problema, creo que este hilo puede ayudarte. Saludos El mié., 10 abr. 2019 22:11, loluchayjose <1773...@bugs.launchpad.net> escribió: > Looks like I can't install anything (or most things) until this gets > fixed. Is there a consensus on the proper way to uninstall systemd-shim? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > Triaged > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial, ie. > > lxc launch ubuntu-daily:xenial test-shim-upgrade > lxc exec test-shim-upgrade > apt update > apt install systemd-shim > wget > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > apt install ./systemd-shim_10-3_amd64.deb > sed 's/xenial/bionic/' -i /etc/apt/sources.list > apt update > apt install systemd > > this currently passes, however, systemd-shim remains installed. It > should be removed instead. Apt install systemd should have lines like > this: > > The following packages will be REMOVED: > systemd-shim > ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > ... > > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Triaged Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering /
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Si claro, luego te dirá de pasar a la 18-04. Saludos El mar., 29 ene. 2019 22:50, juan angel Mora <1773...@bugs.launchpad.net> escribió: > La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5 > LTS. > Vale la pena actualizarla? > Graacias > > > El mar., 29 ene. 2019 a las 22:30, José Enrique (< > 1773...@bugs.launchpad.net>) > escribió: > > > Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no > > quieras perder y actualizarla a 18-04. > > Funcionar funciona pero estás a punto de que no se actualice más, y > puedes > > tener problemas de seguridad, ojo se trata de una actualización > importante, > > que debes realizar, seguramente en dos pasos, dos actualizaciones > > parciales. Primero a 16 y luego a 18-04. > > Configura el gestor de actualizaciones a versiones LTS, no obstante la > > 18-04 tiene soporte para 10 años. > > Saludos > > > > El mar., 29 ene. 2019 22:15, juan angel Mora <1773...@bugs.launchpad.net > > > > escribió: > > > > > Muchas gracias por la información. > > > Si no es mucho consultarte, a veces cuando me pide actualizaciones las > > hago > > > y luego me dice que tengo el Ubuntu 14. , que si lo quiero > actualizar a > > > la ultima versión 16. y no lo hago por miedo a que se me desbarate > todo > > > de nuevo, cual es tu consejo? > > > Un saludo > > > > > > > > > El lun., 28 ene. 2019 a las 19:35, Brian Murray () > > > escribió: > > > > > > > The upload of systemd that was purported to fix this bug report was > > > > superseded by a security update of systemd so the fix is no longer > > > > available. > > > > > > > > ** Changed in: systemd (Ubuntu Bionic) > > > >Status: Fix Committed => Triaged > > > > > > > > -- > > > > You received this bug notification because you are subscribed to a > > > > duplicate bug report (1787843). > > > > https://bugs.launchpad.net/bugs/1773859 > > > > > > > > Title: > > > > upgrades to 18.04 fail > > > > > > > > Status in systemd package in Ubuntu: > > > > Fix Released > > > > Status in systemd-shim package in Ubuntu: > > > > Won't Fix > > > > Status in systemd source package in Bionic: > > > > Triaged > > > > Status in systemd-shim source package in Bionic: > > > > Won't Fix > > > > Status in systemd source package in Cosmic: > > > > Fix Released > > > > Status in systemd-shim source package in Cosmic: > > > > Won't Fix > > > > > > > > Bug description: > > > > [Impact] > > > > > > > >* Some systems fail to upgrade due to conflicts between systemd > and > > > > the (now removed from the archive) systemd-shim / upstart. > > > > > > > >* Instead of trying to work out what's the problem in ordering / > > > > removal of diverts, ensure that systemd is never unpacked whilst > > > > systemd-shim/upstart are still on disk. Thus declare conflicts > > against > > > > systemd-shim/upstart packages in systemd package. > > > > > > > > [Test Case] > > > > > > > >* monitor drop-off of upgrades with below reported problem > > > > > > > >* Check that it is possible to upgrade to bionic's libpam-systemd > > > > from xenial with systemd-shim installed on xenial, ie. > > > > > > > > lxc launch ubuntu-daily:xenial test-shim-upgrade > > > > lxc exec test-shim-upgrade > > > > apt update > > > > apt install systemd-shim > > > > wget > > > > > > > > > > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > > > > apt install ./systemd-shim_10-3_amd64.deb > > > > sed 's/xenial/bionic/' -i /etc/apt/sources.list > > > > apt update > > > > apt install systemd > > > > > > > > this currently passes, however, systemd-shim remains installed. It > > > > should be removed instead. Apt install systemd should have lines > like > > > > this: > > > > > > > > The following packages will be REMOVED: > > > > systemd-shim > > > > ... > > > > Removing 'diversion of > > > > /usr/share
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no quieras perder y actualizarla a 18-04. Funcionar funciona pero estás a punto de que no se actualice más, y puedes tener problemas de seguridad, ojo se trata de una actualización importante, que debes realizar, seguramente en dos pasos, dos actualizaciones parciales. Primero a 16 y luego a 18-04. Configura el gestor de actualizaciones a versiones LTS, no obstante la 18-04 tiene soporte para 10 años. Saludos El mar., 29 ene. 2019 22:15, juan angel Mora <1773...@bugs.launchpad.net> escribió: > Muchas gracias por la información. > Si no es mucho consultarte, a veces cuando me pide actualizaciones las hago > y luego me dice que tengo el Ubuntu 14. , que si lo quiero actualizar a > la ultima versión 16. y no lo hago por miedo a que se me desbarate todo > de nuevo, cual es tu consejo? > Un saludo > > > El lun., 28 ene. 2019 a las 19:35, Brian Murray () > escribió: > > > The upload of systemd that was purported to fix this bug report was > > superseded by a security update of systemd so the fix is no longer > > available. > > > > ** Changed in: systemd (Ubuntu Bionic) > >Status: Fix Committed => Triaged > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (1787843). > > https://bugs.launchpad.net/bugs/1773859 > > > > Title: > > upgrades to 18.04 fail > > > > Status in systemd package in Ubuntu: > > Fix Released > > Status in systemd-shim package in Ubuntu: > > Won't Fix > > Status in systemd source package in Bionic: > > Triaged > > Status in systemd-shim source package in Bionic: > > Won't Fix > > Status in systemd source package in Cosmic: > > Fix Released > > Status in systemd-shim source package in Cosmic: > > Won't Fix > > > > Bug description: > > [Impact] > > > >* Some systems fail to upgrade due to conflicts between systemd and > > the (now removed from the archive) systemd-shim / upstart. > > > >* Instead of trying to work out what's the problem in ordering / > > removal of diverts, ensure that systemd is never unpacked whilst > > systemd-shim/upstart are still on disk. Thus declare conflicts against > > systemd-shim/upstart packages in systemd package. > > > > [Test Case] > > > >* monitor drop-off of upgrades with below reported problem > > > >* Check that it is possible to upgrade to bionic's libpam-systemd > > from xenial with systemd-shim installed on xenial, ie. > > > > lxc launch ubuntu-daily:xenial test-shim-upgrade > > lxc exec test-shim-upgrade > > apt update > > apt install systemd-shim > > wget > > > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > > apt install ./systemd-shim_10-3_amd64.deb > > sed 's/xenial/bionic/' -i /etc/apt/sources.list > > apt update > > apt install systemd > > > > this currently passes, however, systemd-shim remains installed. It > > should be removed instead. Apt install systemd should have lines like > > this: > > > > The following packages will be REMOVED: > > systemd-shim > > ... > > Removing 'diversion of > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > > by systemd-shim' > > ... > > > > > > [Regression Potential] > > > >* systemd-shim/upstart are both removed and not supported in bionic, > > thus forcing their removal via conflicts should bring the system into > > an expected state. > > > > [Other Info] > > > >* original bug report > > > > $ sudo apt upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... Done > > The following packages will be REMOVED: > > systemd-shim > > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > > 1 not fully installed or removed. > > After this operation, 71.7 kB disk space will be freed. > > Do you want to continue? [Y/n] y > > (Reading database ... 63 files and directories currently > installed.) > > Removing systemd-shim (9-1bzr4ubuntu1) ... > > Removing 'diversion of > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > > by systemd-shim' > > dpkg-divert: error: rename involves overwriting > > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > > different file > > > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > > not allowed > > dpkg: error processing package systemd-shim (--remove): > >subprocess installed post-removal script returned error exit status 2 > > Errors were encountered while processing: > >systemd-shim > > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > > Commenting out the dpkg-divert in systemd-shim's postrm solved this
Re: [Touch-packages] [Bug 1773859] Please test proposed package
Mira esta solucion Saludos El jue., 29 nov. 2018 19:31, Alejandro <1773...@bugs.launchpad.net> escribió: > José Enrique,disculpa y gracias por contestarme.Quería pedirte si me > puedes contar brevemente ¿cómo pudiste borrar el systemd-shim package?No se > cómo accederloMuchas graciasAlejandro > - > - > - > > > - > - - > José Enrique <1773...@bugs.launchpad.net> > > - > - Nov 19 at 2:01 PM > > >- To avertaness...@yahoo.com > - > > Message body > Thanks a lot for your help. I resolved my problem erasing systemd-shim and > updating. > I'll try new solution in another pc. > Kind regards > > > From: José Enrique <1773...@bugs.launchpad.net> > To: avertaness...@yahoo.com > Sent: Tuesday, November 27, 2018 3:01 PM > Subject: Re: [Bug 1773859] Please test proposed package > > Lo siento Alejandro, no soy Lucas > Saludos > > El mar., 27 nov. 2018 18:51, Alejandro <1773...@bugs.launchpad.net> > escribió: > > > Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make > > this test in the last weeks I will make them as soon as > > possibleRegardsAlejandro > > > > From: Łukasz Zemczak <1773...@bugs.launchpad.net> > > To: avertaness...@yahoo.com > > Sent: Tuesday, November 20, 2018 9:21 AM > > Subject: [Bug 1773859] Please test proposed package > > > > Hello Kees, or anyone else affected, > > > > Accepted systemd into bionic-proposed. The package will build now and be > > available at > > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few > > hours, and then in the -proposed repository. > > > > Please help us by testing this new package. See > > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > > to enable and use -proposed. Your feedback will aid us getting this > > update out to other Ubuntu users. > > > > If this package fixes the bug for you, please add a comment to this bug, > > mentioning the version of the package you tested and change the tag from > > verification-needed-bionic to verification-done-bionic. If it does not > > fix the bug for you, please add a comment stating that, and change the > > tag to verification-failed-bionic. In either case, without details of > > your testing we will not be able to proceed. > > > > Further information regarding the verification process can be found at > > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > > advance for helping! > > > > N.B. The updated package will be released to -updates after the bug(s) > > fixed by this package have been verified and the package has been in > > -proposed for a minimum of 7 days. > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (1796221). > > https://bugs.launchpad.net/bugs/1773859 > > > > Title: > > upgrades to 18.04 fail > > > > Status in systemd package in Ubuntu: > > Fix Released > > Status in systemd-shim package in Ubuntu: > > Won't Fix > > Status in systemd source package in Bionic: > > Fix Committed > > Status in systemd-shim source package in Bionic: > > Won't Fix > > Status in systemd source package in Cosmic: > > Fix Released > > Status in systemd-shim source package in Cosmic: > > Won't Fix > > > > Bug description: > > [Impact] > > > >* Some systems fail to upgrade due to conflicts between systemd and > > the (now removed from the archive) systemd-shim / upstart. > > > >* Instead of trying to work out what's the problem in ordering / > > removal of diverts, ensure that systemd is never unpacked whilst > > systemd-shim/upstart are still on disk. Thus declare conflicts against > > systemd-shim/upstart packages in systemd package. > > > > [Test Case] > > > >* monitor drop-off of upgrades with below reported problem > > > >* Check that it is possible to upgrade to bionic's libpam-systemd > > from xenial with systemd-shim installed on xenial, ie. > > > > lxc launch ubuntu-daily:xenial test-shim-upgrade > > lxc exec test-shim-upgrade > > apt update > > apt install systemd-shim > > wget > > > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > > apt install ./systemd-shim_10-3_amd64.deb > > sed 's/xenial/bionic/' -i /etc/apt/sources.list > > apt update > > apt install systemd > &
Re: [Touch-packages] [Bug 1773859] Please test proposed package
Hola mira esta solución. Saludos. El jue., 29 nov. 2018 22:51, b0w <1773...@bugs.launchpad.net> escribió: > Yo tambien tengo dudas de como resolverlo! I Still have some doubts on how > to fix it, but if in 7 days it will be available for everyone i will just > wait the update. > Greetings! > > On Thu, Nov 29, 2018 at 12:31 PM Alejandro <1773...@bugs.launchpad.net> > wrote: > > > José Enrique,disculpa y gracias por contestarme.Quería pedirte si me > > puedes contar brevemente ¿cómo pudiste borrar el systemd-shim package?No > se > > cómo accederloMuchas graciasAlejandro > > - > > - > > - > > > > > > - > > - - > > José Enrique <1773...@bugs.launchpad.net> > > > > - > > - Nov 19 at 2:01 PM > > > > > >- To avertaness...@yahoo.com > > - > > > > Message body > > Thanks a lot for your help. I resolved my problem erasing systemd-shim > and > > updating. > > I'll try new solution in another pc. > > Kind regards > > > > > > From: José Enrique <1773...@bugs.launchpad.net> > > To: avertaness...@yahoo.com > > Sent: Tuesday, November 27, 2018 3:01 PM > > Subject: Re: [Bug 1773859] Please test proposed package > > > > Lo siento Alejandro, no soy Lucas > > Saludos > > > > El mar., 27 nov. 2018 18:51, Alejandro <1773...@bugs.launchpad.net> > > escribió: > > > > > Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make > > > this test in the last weeks I will make them as soon as > > > possibleRegardsAlejandro > > > > > > From: Łukasz Zemczak <1773...@bugs.launchpad.net> > > > To: avertaness...@yahoo.com > > > Sent: Tuesday, November 20, 2018 9:21 AM > > > Subject: [Bug 1773859] Please test proposed package > > > > > > Hello Kees, or anyone else affected, > > > > > > Accepted systemd into bionic-proposed. The package will build now and > be > > > available at > > > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few > > > hours, and then in the -proposed repository. > > > > > > Please help us by testing this new package. See > > > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on > how > > > to enable and use -proposed. Your feedback will aid us getting this > > > update out to other Ubuntu users. > > > > > > If this package fixes the bug for you, please add a comment to this > bug, > > > mentioning the version of the package you tested and change the tag > from > > > verification-needed-bionic to verification-done-bionic. If it does not > > > fix the bug for you, please add a comment stating that, and change the > > > tag to verification-failed-bionic. In either case, without details of > > > your testing we will not be able to proceed. > > > > > > Further information regarding the verification process can be found at > > > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you > in > > > advance for helping! > > > > > > N.B. The updated package will be released to -updates after the bug(s) > > > fixed by this package have been verified and the package has been in > > > -proposed for a minimum of 7 days. > > > > > > -- > > > You received this bug notification because you are subscribed to a > > > duplicate bug report (1796221). > > > https://bugs.launchpad.net/bugs/1773859 > > > > > > Title: > > > upgrades to 18.04 fail > > > > > > Status in systemd package in Ubuntu: > > > Fix Released > > > Status in systemd-shim package in Ubuntu: > > > Won't Fix > > > Status in systemd source package in Bionic: > > > Fix Committed > > > Status in systemd-shim source package in Bionic: > > > Won't Fix > > > Status in systemd source package in Cosmic: > > > Fix Released > > > Status in systemd-shim source package in Cosmic: > > > Won't Fix > > > > > > Bug description: > > > [Impact] > > > > > >* Some systems fail to upgrade due to conflicts between systemd and > > > the (now removed from the archive) systemd-shim / upstart. > > > > > >* Instead of trying to work out what's the problem in ordering / > > > removal of diverts, ensure that systemd is never unpacked whilst > > >
Re: [Touch-packages] [Bug 1773859] Please test proposed package
Lo siento Alejandro, no soy Lucas Saludos El mar., 27 nov. 2018 18:51, Alejandro <1773...@bugs.launchpad.net> escribió: > Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make > this test in the last weeks I will make them as soon as > possibleRegardsAlejandro > > From: Łukasz Zemczak <1773...@bugs.launchpad.net> > To: avertaness...@yahoo.com > Sent: Tuesday, November 20, 2018 9:21 AM > Subject: [Bug 1773859] Please test proposed package > > Hello Kees, or anyone else affected, > > Accepted systemd into bionic-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few > hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested and change the tag from > verification-needed-bionic to verification-done-bionic. If it does not > fix the bug for you, please add a comment stating that, and change the > tag to verification-failed-bionic. In either case, without details of > your testing we will not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1796221). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > Fix Committed > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial, ie. > > lxc launch ubuntu-daily:xenial test-shim-upgrade > lxc exec test-shim-upgrade > apt update > apt install systemd-shim > wget > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > apt install ./systemd-shim_10-3_amd64.deb > sed 's/xenial/bionic/' -i /etc/apt/sources.list > apt update > apt install systemd > > this currently passes, however, systemd-shim remains installed. It > should be removed instead. Apt install systemd should have lines like > this: > > The following packages will be REMOVED: > systemd-shim > ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > ... > > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg:
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
I solved problem sttoping services and erasing systemd-shim upon console. After I could updating my pc, also, from console Kind regards El mié., 17 oct. 2018 23:11, Brian Murray escribió: > ** Tags added: bugpattern-written > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > In Progress > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial. > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial. [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Thanks a lot for your help. I resolved my problem erasing systemd-shim and updating. I'll try new solution in another pc. Kind regards El lun., 19 nov. 2018 15:11, Łukasz Zemczak <1773...@bugs.launchpad.net> escribió: > Hello Kees, or anyone else affected, > > Accepted systemd into bionic-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few > hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested and change the tag from > verification-needed-bionic to verification-done-bionic. If it does not > fix the bug for you, please add a comment stating that, and change the > tag to verification-failed-bionic. In either case, without details of > your testing we will not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Changed in: systemd (Ubuntu Bionic) >Status: In Progress => Fix Committed > > ** Tags added: verification-needed verification-needed-bionic > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > Fix Committed > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial. > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Hy, in this moment I can't update my laptop or install any package or program Greetings El mié., 17 oct. 2018 23:11, Brian Murray escribió: > ** Tags added: bugpattern-written > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > In Progress > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial. > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: In Progress Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial. [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ...
[Touch-packages] [Bug 1692361] [NEW] package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base is not ready for configuration cannot configure (current st
Public bug reported: al iniciar ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun May 21 00:02:11 2017 DuplicateSignature: package:language-pack-en-base:1:16.04+20160627 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package language-pack-en-base (--configure): package language-pack-en-base is not ready for configuration ErrorMessage: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-04-23 (393 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: language-pack-en-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/1692361 Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') Status in language-pack-en-base package in Ubuntu: New Bug description: al iniciar ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun May 21 00:02:11 2017 DuplicateSignature: package:language-pack-en-base:1:16.04+20160627 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package language-pack-en-base (--configure): package language-pack-en-base is not ready for configuration ErrorMessage: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-04-23 (393 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en-base/+bug/1692361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676076] [NEW] [X556UB, Realtek ALC255, Speaker, Internal] flac files skips or sttuter, rhytmbox and mpd
Public bug reported: Flac Files skips (like an old record scratch) on rhytmbox or mpd server (via soundcard or a DAC). The skip is random. Description:Ubuntu 16.10 Release:16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: brujo 2424 F...m pulseaudio /dev/snd/controlC0: brujo 2424 F pulseaudio CurrentDesktop: Unity Date: Sat Mar 25 12:11:59 2017 InstallationDate: Installed on 2017-01-30 (54 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [X556UB, Realtek ALC255, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.405 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.405:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1676076 Title: [X556UB, Realtek ALC255, Speaker, Internal] flac files skips or sttuter, rhytmbox and mpd Status in alsa-driver package in Ubuntu: New Bug description: Flac Files skips (like an old record scratch) on rhytmbox or mpd server (via soundcard or a DAC). The skip is random. Description: Ubuntu 16.10 Release: 16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: brujo 2424 F...m pulseaudio /dev/snd/controlC0: brujo 2424 F pulseaudio CurrentDesktop: Unity Date: Sat Mar 25 12:11:59 2017 InstallationDate: Installed on 2017-01-30 (54 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [X556UB, Realtek ALC255, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.405 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.405:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1676076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615474] Re: Network Indicator / Connectivity-API is not accessible
I also got the same error after getting a full disk message. I also played around with the WIFI access point like a previous user. I can confirm that it was enough for me to delete the file ~/.config/connectivity-service/config.ini.lock to get the network indicator back. It sis worth mentioning that I was able to connect via ssh, since the phone would still connect to *known* WIFI networks. I couldn't use the terminal application since it stopped working *I can use it again after the network indicator was back). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1615474 Title: Network Indicator / Connectivity-API is not accessible Status in Canonical System Image: Triaged Status in indicator-network package in Ubuntu: Triaged Bug description: Sometime in the last few days my phone lost the ability to connect to wifi networks and the network indicator at the top has stopped working. Currently between "Bluetooth" and "Sound" I have a gear icon and the caption "indicator-network". When I select it, the rest of the screen is blank. There are no settings available and no way to connect to a wifi network. On the System Settings app, if I tap on the "Wi-Fi" icon, I can see "Previous networks". But below that the page is just white, there is no way to select a wifi network. Rebooting the phone doesn't seem to fix the problem. Given that this is an MX4 and therefore the USB port doesn't work, and there's no SD card slot, there's vanishingly few ways to get data in and out of this phone now. If there's a solution to the problem, it's going to have to involve something other than updating system software. Current system software is Ubuntu 15.05 (OTA-12). - Per the comments the .config/connectivity-service/config.ini file seems to hold bad or outdated info and needs to be manually deleted and then recreated by the service. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652927] [NEW] package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de
Public bug reported: Second error by actualization from 16.04 to 16.10. First system reboot by terminal. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Wed Dec 28 12:15:32 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2016-04-21 (250 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to yakkety on 2016-12-28 (0 days ago) ** Affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1652927 Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post- installation devolvió el código de salida de error 1 Status in unity-scopes-api package in Ubuntu: New Bug description: Second error by actualization from 16.04 to 16.10. First system reboot by terminal. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Wed Dec 28 12:15:32 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2016-04-21 (250 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to yakkety on 2016-12-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1652927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553638] Re: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Hi: the quick fix was: 1. Use apt-get download perl and apt-get download perl-modules 2. Use dpkg -i each package, you must be started use package perl-modules, after install perl package. 3. Use apt-get upgrade and I could to fix the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1553638 Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in perl package in Ubuntu: New Bug description: Fail after an unexpected shutdown for low battery accidentally shutdown during a apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 15.10 Package: perl-modules 5.20.2-6ubuntu0.2 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sat Mar 5 21:29:30 2016 DuplicateSignature: package:perl-modules:5.20.2-6ubuntu0.2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-11-28 (98 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: perl Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1553638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553638] [NEW] package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Public bug reported: Fail after an unexpected shutdown for low battery accidentally shutdown during a apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 15.10 Package: perl-modules 5.20.2-6ubuntu0.2 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sat Mar 5 21:29:30 2016 DuplicateSignature: package:perl-modules:5.20.2-6ubuntu0.2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-11-28 (98 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: perl Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1553638 Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in perl package in Ubuntu: New Bug description: Fail after an unexpected shutdown for low battery accidentally shutdown during a apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 15.10 Package: perl-modules 5.20.2-6ubuntu0.2 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sat Mar 5 21:29:30 2016 DuplicateSignature: package:perl-modules:5.20.2-6ubuntu0.2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-11-28 (98 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: perl Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1553638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547262] [NEW] [OptiPlex 990, Realtek ALC269VB, Speaker, Internal] Cdplayer problem
Public bug reported: I have no proble with files ogg and mp3 but when I try to play a cd the sound is noise, ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic i686 ApportVersion: 2.20-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hck26001613 F pulseaudio /dev/snd/controlC2: hck26001613 F pulseaudio /dev/snd/controlC0: hck26001613 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 18 17:42:50 2016 InstallationDate: Installed on 2016-01-28 (21 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160127) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [OptiPlex 990, Realtek ALC269VB, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0VNP2H dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd04/02/2012:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0VNP2H:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1547262 Title: [OptiPlex 990, Realtek ALC269VB, Speaker, Internal] Cdplayer problem Status in alsa-driver package in Ubuntu: New Bug description: I have no proble with files ogg and mp3 but when I try to play a cd the sound is noise, ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic i686 ApportVersion: 2.20-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hck26001613 F pulseaudio /dev/snd/controlC2: hck26001613 F pulseaudio /dev/snd/controlC0: hck26001613 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 18 17:42:50 2016 InstallationDate: Installed on 2016-01-28 (21 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160127) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [OptiPlex 990, Realtek ALC269VB, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0VNP2H dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd04/02/2012:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0VNP2H:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1547262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1527617] [NEW] Xorg crash
Public bug reported: Updated kernel headers ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Dec 18 08:52:36 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.2.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053b] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:82b3] InstallationDate: Installed on 2015-10-25 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=00690a4c-1365-4414-a6c6-0d9f5368a520 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0709 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-VM HDMI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0709:bd12/05/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-VMHDMI:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Dec 18 08:50:34 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 crash ubuntu wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1527617 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: Updated kernel headers ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true
[Touch-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi
I also experienced a similar behavior in my BQ 5 with OTA 8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1526110] [NEW] Xorg freeze
Public bug reported: Symptons: Display freezes, but not mouse, after 30 seconds aprox display refreshes, and only background image is shown over 3 seconds aprox and then apport window appears to send report, other times apport window doesn't appear and everything just continues as normal. Steps to reproduce: 1. I think the goal in this is saturate GPU, so what I do is to open many images with GIMP say 20, open Firefox, Chrome, VLC player with a video running and Audacity. With those are sufficient to reproduce the issue which becomes recurrent to say every 2 minutes. To make it clear, not only xorg package gets involved in these freezes other many times it's compiz. I'd like you to give me guidelines to seriously troubleshoot this issue. Thanks ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 14 18:55:06 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.2.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053b] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:82b3] InstallationDate: Installed on 2015-10-25 (50 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=00690a4c-1365-4414-a6c6-0d9f5368a520 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0709 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-VM HDMI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0709:bd12/05/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-VMHDMI:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Dec 14 17:19:15 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1526110 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Symptons: Display freezes, but
[Touch-packages] [Bug 1502268] [NEW] Pop-up message asking to change SIM card for calls is not disabled
Public bug reported: I have an Aquarius E5 phone with two SIM cards. When I make a call, I always manually select one of the cards, then a pop up appears asking whether I want to change the defaults. I click on "Do not ask again" and then press "No". Despite choosing "Do not ask again", the pop-up appears every time I make a call. ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1502268 Title: Pop-up message asking to change SIM card for calls is not disabled Status in dialer-app package in Ubuntu: New Bug description: I have an Aquarius E5 phone with two SIM cards. When I make a call, I always manually select one of the cards, then a pop up appears asking whether I want to change the defaults. I click on "Do not ask again" and then press "No". Despite choosing "Do not ask again", the pop-up appears every time I make a call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1502268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1229401] Re: [Ubuntu Touch] adding number to existing contact does not work from call log
Just for the record, I have two SIM cards just in case that makes a difference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1229401 Title: [Ubuntu Touch] adding number to existing contact does not work from call log Status in dialer-app package in Ubuntu: Confirmed Bug description: From the "Call log" when you click on the plus sign image of un unknown number to create a new contact or add to an existing one, touching "Add to existing contact" does nothing. I should expect "contacts" open for adding the number to an existing contact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1229401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1229401] Re: [Ubuntu Touch] adding number to existing contact does not work from call log
This also is not working for me with the latests updates of Aquarius E5 as of 1st October 2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1229401 Title: [Ubuntu Touch] adding number to existing contact does not work from call log Status in dialer-app package in Ubuntu: Confirmed Bug description: From the "Call log" when you click on the plus sign image of un unknown number to create a new contact or add to an existing one, touching "Add to existing contact" does nothing. I should expect "contacts" open for adding the number to an existing contact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1229401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1478222] Re: Ubuntu Touch forgets WiFi settings after first connection. EDUROAM network WPA WPA2 Enterprise
I found the way to get this working: when prompted with the WiFi network configuration, select WPA WPA2 Enterprise, TTLS, MCHAPv2, scroll to the end and check Remember password. Then fill the rest of the fields: anonymous id, user id and password. The trick is not to get the on-display keyboard before the Remember password can be checked. Despite the fact that now it is working, this shows that there are still two bugs: 1) once the on-display keyboard is shown, one cannot scroll down the configuration all the way to the bottom. 2) If the Remember password is not set, when prompted for the password next times you connect, even entering the correct password doesn't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1478222 Title: Ubuntu Touch forgets WiFi settings after first connection. EDUROAM network WPA WPA2 Enterprise Status in indicator-network package in Ubuntu: New Bug description: Using WPA WPA2 Enterprise I connected to the EDUROAM WiFi network with Ubuntu Touch. This works fine. However, when leaving the WiFi range and coming back, Ubuntu Touch will not be able to connect again. It asks again for the password, but the correct password does not work anymore. The only (annoying) workaround is to delete EDUROAM network from previous networks in the WiFi setting and then apply all setting again. The WiFi access will work then until one leaves the WiFi range again. Additional info: The EDUROAM WiFi network is a unified WiFi network to get access almost any European University. Default set-up is described here: http://www.urz.uni-heidelberg.de/zugang/eduroam/linux_ubuntu.html System: Ubuntu Touch 15.04(r24). Device-Built: KRILIN01A-S15A_BQ_L100EN_2024_150713 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1478222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1478222] Re: Ubuntu Touch forgets WiFi settings after first connection. EDUROAM network WPA WPA2 Enterprise
The same problem happened to me with BQ Aquarius E5 SO Ubuntu 15.04 (r4). Last update 11/08/15, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1478222 Title: Ubuntu Touch forgets WiFi settings after first connection. EDUROAM network WPA WPA2 Enterprise Status in indicator-network package in Ubuntu: New Bug description: Using WPA WPA2 Enterprise I connected to the EDUROAM WiFi network with Ubuntu Touch. This works fine. However, when leaving the WiFi range and coming back, Ubuntu Touch will not be able to connect again. It asks again for the password, but the correct password does not work anymore. The only (annoying) workaround is to delete EDUROAM network from previous networks in the WiFi setting and then apply all setting again. The WiFi access will work then until one leaves the WiFi range again. Additional info: The EDUROAM WiFi network is a unified WiFi network to get access almost any European University. Default set-up is described here: http://www.urz.uni-heidelberg.de/zugang/eduroam/linux_ubuntu.html System: Ubuntu Touch 15.04(r24). Device-Built: KRILIN01A-S15A_BQ_L100EN_2024_150713 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1478222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442607] Re: I can't connect Bq Ubuntu to Ubuntu Store
I also have the same problem on Aquarius E5 which was last updated 11/8/15. My local is Spanish. However I was able to get a working Ubuntu Store until now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1442607 Title: I can't connect Bq Ubuntu to Ubuntu Store Status in unity-scope-click package in Ubuntu: Confirmed Bug description: I had exactly the same issue as described in this thread: https://lists.launchpad.net/ubuntu-phone/msg11847.html In ubuntu store scope I have empty page (just the header 'Ubuntu store' and below a blank page -- see the attached photo). Searching does not change anything - still blank page. The same with refreshing the scope (by pulling the top edge). Other scopes work without problems, and there is no problem with internet connection. I guess that restarting the phone should resolve the issue, but I haven't done this yet. I suspect that the problem occurred when the wi-fi connection was switched on/off - I did it several times (I checked which apps does not work offline) and at some point ubuntu store stopped working. If I can be of some help in debugging the issue please let me know. My phone: BQ Aquaris OS: Ubuntu 14.10 (r20) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1442607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
