Re: [Dx-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: [Dx-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 DX Packages, which is subscribed to systemd-shim 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 / removal of
Re: [Dx-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Una cosa. Chequea el hardware en ocasiones equipos antiguos rinden mal o no rinden con el 18 Si es un equipo moderno sin problemas. También puedes valorar en utilizar escritorios más ligeros con equipos antiguos XCFE Xubuntu o LXDE Lubuntu. Yo con un equipo de 2007 y 2 GB ejecuto Xubuntu 18-04 sin problemas. Y en un Netbook con 1 Giga Lubuntu. Recuerda que Lubuntu ya no va a crear versiones de 32 bit a partir de 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, sy
Re: [Dx-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: [Dx-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: [Dx-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: [Dx-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: [Dx-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: [Dx-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 DX Packages, which is subscribed to systemd-shim 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 want to
Re: [Dx-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 DX Packages, which is subscribed to systemd-shim 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
Re: [Dx-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 DX Packages, which is subscribed to systemd-shim 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 ... 63 files
[Dx-packages] [Bug 1498199] Re: Switching to fullscreen app causes unity freeze
Thank you for taking the time to report this bug. We have tried to recreate this on the latest release of Ubuntu 15.10 and cannot reproduce it. This bug is being marked as Invalid. If you believe the problem to still exist in the latest version of Ubuntu please comment on why that is the case and change the bug status to NEW. ** Changed in: unity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1498199 Title: Switching to fullscreen app causes unity freeze Status in unity package in Ubuntu: Invalid Bug description: I'm reporting this for unity but it might just as well be compiz- related. Reproduce 1. Open fullscreen app (e.g. fullscreen HTML5 video, a game) 2. switch to another virtual desktop (i.e. using crtl+alt+arrow_keys) 3. switch back This started happening to me in 15.04. It does not happen all the time but can be reproduced by trying several times. If you need more info, let me know what and how to get it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Sep 21 23:18:19 2015 InstallationDate: Installed on 2014-03-11 (559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140302) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-05-20 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1498199/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
As part of the big bug review for 16.04 LTS I have tested this on 15.10 and the bug is still there. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Confirmed Status in gnome-screensaver package in Ubuntu: Triaged Status in unity package in Ubuntu: Confirmed Status in gnome-screensaver source package in Precise: Confirmed Status in unity source package in Precise: Confirmed Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1439599] Re: Search button not clickable on revealed unity launcher
Thank you for taking the time to report this bug. We have tried to recreate this on the latest release of Ubuntu and cannot reproduce it. This bug is being marked as Invalid. If you believe the problem to still exist in the latest version of Ubuntu please comment on why that is the case and change the bug status to NEW. ** Changed in: unity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1439599 Title: Search button not clickable on revealed unity launcher Status in Unity: New Status in unity package in Ubuntu: Invalid Bug description: I have auto-hide of launcher enabled and I am opening it with Alt+F1. When the launcher appears, the search button (the top-most button) is selected (has focus) and accessible when I press Enter - the search screen appears. But the button is not accessible by mouse - the mouse click is not handled immediatelly and the search screen does not appear. I need to click somewhere else or press Esc key - it behaves like the click is remembered, but processed later. Expected is that the search screen appears immediately when I click the search (the top-most) button of the launcher. I am using Ubuntu 14.04.2 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1439599/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
*** This bug is a duplicate of bug 1163041 *** https://bugs.launchpad.net/bugs/1163041 ** Also affects: nautilus Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in Nautilus: New Status in Unity: Triaged Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1170647/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295267] Re: Windows change Monitor/Desktop after screen lock
Same in 14.04. My laptop is a Samsung NP900X4C. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock Status in “unity” package in Ubuntu: Confirmed Bug description: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description: Ubuntu 13.10 Release: 13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295267/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
This also occurs here, with Ubuntu 14.04 x64. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “gtk+2.0” package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
I've been using the Raleigh override, and I have experienced no crashes. I also tried David's suggestions, though the libgtk-3-0 version in the Trusty repos seems to be the same as the one in the gnome3 ppa (Package libgtk3 is already the newest version etc.). I compiled oxygen-gtk locally, but the problem persists. All of the above on 14.04. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “gtk+2.0” package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy
This bug is still present in last daily build of ubuntu 14.04 LTS (16/04/2014). Is it planned to be solved before final release? Thx -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Eclipse: Confirmed Status in Unity GTK+ module: In Progress Status in “oracle-jdk7-installer” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: Fix Released Bug description: HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 959323] Re: compiz crashed with SIGSEGV in af_face_globals_is_digit() from af_loader_load_g() from af_loader_load_glyph() from af_autofitter_load_glyph() from FT_Load_Glyph() from _
** Changed in: nux (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/959323 Title: compiz crashed with SIGSEGV in af_face_globals_is_digit() from af_loader_load_g() from af_loader_load_glyph() from af_autofitter_load_glyph() from FT_Load_Glyph() from _cairo_ft_scaled_glyph_init() from ... from nux::TextEntry::DrawText() Status in Nux: Invalid Status in Unity: Invalid Status in Unity 5.0 series: Confirmed Status in “nux” package in Ubuntu: Fix Released Bug description: While starting up the system, hit Super key and started typing in 'liferea'. Got as far as 'life' ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: libnux-2.0-0 2.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 19 10:22:37 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) ProcCmdline: compiz ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f3b3e1438a3:cmp0x8(%rdx),%rax PC (0x7f3b3e1438a3) ok source 0x8(%rdx) (0x0008) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nux StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: Upgraded to precise on 2012-03-10 (8 days ago) UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/959323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1197647] Re: Date Time applet in control center does not start
The date time applet on ubuntu 13.10 doesn't update the day when I click in the applet. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1197647 Title: Date Time applet in control center does not start Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: After upgrade to 13.10, going to control center and clicking on Date Time causes the control center to relaunch in a loop and taking the focus each relaunch. Killing the control center stops the loop but there's no way for me to configure it, also, clock does not appear in the top right at the moment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1197647/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1219169] [NEW] unity lens doesnt show anything, and it seems that there is a .service config file missing from dbus-1 folder
Public bug reported: Ubuntu 13.10, completly updated i´ve been like a week withouth being able to use the dash for open applications, yes, i´ve doing that fom the console all this time, learning the bin programs names from share/applications folder, and is pretty fancy get more in touch with that, but, i want to be able of use the dash some time (i didnt did anything until now because i believed it was going to be fixed with an update(aniway i dont remeber if an update caused this)) : details: when i open de unity dash, its completly empty, no lens, no files, nothing, just the message nothing matches your search so: i executed: unity --replace , to see console output when i open the dash there is this error message: WARN 2013-08-31 01:57:37 unity.libunity-protocol-private unknown:0 unity-scope-proxy-remote.vala:399: Unable to set_active (/com/canonical/unity/home): GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.Unity.Scope.Home was not provided by any .service files then i tried to create my own .service file for the /usr/share/dbus-1/services folder, seeing how they wehere defined, and the structure of the /usr/share/unity/scopes too. I didnt found anything useful in the man doc for unity-scope-loader. And my pretty .service file was creating system errors. so i end up clueles... i logged out, and open a vitual console in f1 i purgen unity-services and other packages, and reinstalled them everything is the same i dont what to understand the complet way unity works internally, and i dont whant to purge all unity or ubuntu, so im asking here, and i hope my mecanically cold and desperate sorrows are heard :| ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1219169 Title: unity lens doesnt show anything, and it seems that there is a .service config file missing from dbus-1 folder Status in “unity” package in Ubuntu: New Bug description: Ubuntu 13.10, completly updated i´ve been like a week withouth being able to use the dash for open applications, yes, i´ve doing that fom the console all this time, learning the bin programs names from share/applications folder, and is pretty fancy get more in touch with that, but, i want to be able of use the dash some time (i didnt did anything until now because i believed it was going to be fixed with an update(aniway i dont remeber if an update caused this)) : details: when i open de unity dash, its completly empty, no lens, no files, nothing, just the message nothing matches your search so: i executed: unity --replace , to see console output when i open the dash there is this error message: WARN 2013-08-31 01:57:37 unity.libunity-protocol-private unknown:0 unity-scope-proxy-remote.vala:399: Unable to set_active (/com/canonical/unity/home): GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.Unity.Scope.Home was not provided by any .service files then i tried to create my own .service file for the /usr/share/dbus-1/services folder, seeing how they wehere defined, and the structure of the /usr/share/unity/scopes too. I didnt found anything useful in the man doc for unity-scope-loader. And my pretty .service file was creating system errors. so i end up clueles... i logged out, and open a vitual console in f1 i purgen unity-services and other packages, and reinstalled them everything is the same i dont what to understand the complet way unity works internally, and i dont whant to purge all unity or ubuntu, so im asking here, and i hope my mecanically cold and desperate sorrows are heard :| To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1219169/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1219169] Re: unity lens doesnt show anything, and it seems that there is a .service config file missing from dbus-1 folder
this is how it looks like ** Attachment added: Captura de pantalla de 2013-08-31 02:36:10.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1219169/+attachment/3796276/+files/Captura%20de%20pantalla%20de%202013-08-31%2002%3A36%3A10.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1219169 Title: unity lens doesnt show anything, and it seems that there is a .service config file missing from dbus-1 folder Status in “unity” package in Ubuntu: New Bug description: Ubuntu 13.10, completly updated i´ve been like a week withouth being able to use the dash for open applications, yes, i´ve doing that fom the console all this time, learning the bin programs names from share/applications folder, and is pretty fancy get more in touch with that, but, i want to be able of use the dash some time (i didnt did anything until now because i believed it was going to be fixed with an update(aniway i dont remeber if an update caused this)) : details: when i open de unity dash, its completly empty, no lens, no files, nothing, just the message nothing matches your search so: i executed: unity --replace , to see console output when i open the dash there is this error message: WARN 2013-08-31 01:57:37 unity.libunity-protocol-private unknown:0 unity-scope-proxy-remote.vala:399: Unable to set_active (/com/canonical/unity/home): GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.Unity.Scope.Home was not provided by any .service files then i tried to create my own .service file for the /usr/share/dbus-1/services folder, seeing how they wehere defined, and the structure of the /usr/share/unity/scopes too. I didnt found anything useful in the man doc for unity-scope-loader. And my pretty .service file was creating system errors. so i end up clueles... i logged out, and open a vitual console in f1 i purgen unity-services and other packages, and reinstalled them everything is the same i dont what to understand the complet way unity works internally, and i dont whant to purge all unity or ubuntu, so im asking here, and i hope my mecanically cold and desperate sorrows are heard :| To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1219169/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1219169] Re: unity lens doesnt show anything, and it seems that there is a .service config file missing from dbus-1 folder
thanks!, amazingly it was unninstalled, maybe there is a dependency missed in a unity package description? i maked a distro upgrade from 13.04 some months ago if it helps, maybe it is related to some bad update cheers! -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1219169 Title: unity lens doesnt show anything, and it seems that there is a .service config file missing from dbus-1 folder Status in “unity” package in Ubuntu: Incomplete Bug description: Ubuntu 13.10, completly updated i´ve been like a week withouth being able to use the dash for open applications, yes, i´ve doing that fom the console all this time, learning the bin programs names from share/applications folder, and is pretty fancy get more in touch with that, but, i want to be able of use the dash some time (i didnt did anything until now because i believed it was going to be fixed with an update(aniway i dont remeber if an update caused this)) : details: when i open de unity dash, its completly empty, no lens, no files, nothing, just the message nothing matches your search so: i executed: unity --replace , to see console output when i open the dash there is this error message: WARN 2013-08-31 01:57:37 unity.libunity-protocol-private unknown:0 unity-scope-proxy-remote.vala:399: Unable to set_active (/com/canonical/unity/home): GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.Unity.Scope.Home was not provided by any .service files then i tried to create my own .service file for the /usr/share/dbus-1/services folder, seeing how they wehere defined, and the structure of the /usr/share/unity/scopes too. I didnt found anything useful in the man doc for unity-scope-loader. And my pretty .service file was creating system errors. so i end up clueles... i logged out, and open a vitual console in f1 i purgen unity-services and other packages, and reinstalled them everything is the same i dont what to understand the complet way unity works internally, and i dont whant to purge all unity or ubuntu, so im asking here, and i hope my mecanically cold and desperate sorrows are heard :| To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1219169/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
