[Dx-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_un
** Also affects: ayatana-indicator-messages (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in ayatana-indicator-messages package in Ubuntu: New Status in indicator-messages package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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 1871538] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Released Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited
[Dx-packages] [Bug 1871538] Please test proposed package
Hello Christian, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.5 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, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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 a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Hello Christian, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.16 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, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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 Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Hello Christian, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.4 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, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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 Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: dbus (Ubuntu Hirsute) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Incomplete Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: rls-ff-incoming rls-hh-incoming rls-ii-incoming -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: New Status in dbus source package in Groovy: New Status in gnome-shell source package in Groovy: New Status in accountsservice source package in Hirsute: New Status in dbus source package in Hirsute: New Status in gnome-shell source package in Hirsute: New Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr
[Dx-packages] [Bug 1867996] [libappindicator/bionic] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] Status in libappindicator package in Ubuntu: Fix Released Status in libappindicator source package in Bionic: Fix Committed Status in libappindicator package in Arch Linux: New Bug description: [ Impact ] Discord and several other applications using libappindicator are widely reported to have been crashing for several years. See: https://github.com/flathub/com.discordapp.Discord/issues/30 (and others) [ Test case ] - Run discord application - It must not crash in ubuntu (or when indicators are enabled) [ Regression potential ] Very low, icons might not appear in some cases, if any. - This is the backtrace: (gdb) bt full #0 0x7fe1d5d2e00e in () at /app/lib/libappindicator.so #1 0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0 #2 0x7fe1f5a813d2 in () at /lib/libgobject-2.0.so.0 #3 0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0 #4 0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0 #5 0x7fe1d5d2ed4f in app_indicator_set_icon_full () at /app/lib/libappindicator.so #6 0x0077851a in () #7 0x01de7123 in () #8 0x01e4bd4e in () #9 0x01e6e34c in () #10 0x01e6e668 in () #11 0x01e6e9cb in () #12 0x01df971a in () #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0 #14 0x7fe1f354b430 in () at /lib/libglib-2.0.so.0 #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0 #16 0x01df9606 in () #17 0x01e6e0e7 in () #18 0x01e29570 in () #19 0x00c37ec8 in () #20 0x00c37d15 in () #21 0x00c1da7d in () #22 0x00a9282e in () #23 0x007892d4 in () #24 0x007896e0 in () #25 0x03b830a3 in main () Happens in all versions of libappindicator built from latest sources available on launchpad. I ran into the issue yesterday when installing Discord for the first time. I have tracked the problem down to libappindicator passing in an extra vararg item to g_signal_emit that the signal's definition in libappindicator was not declaring, causing the crash you see above in gobject's g_signal dispatch machinery. Patch is attached. I am presuming this is 'upstream' for libappindicator, whatever that may mean for what appears to be an unmaintained project. If it is not, and since it is an Ubuntu/Canonical-sourced project originally, I respectfully request that you assist in upstreaming it since this bug is causing severe breakage for users across all distros. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: champagne -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught signal, shutting down... Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service:
[Dx-packages] [Bug 1843982] Update Released
The verification of the Stable Release Update for accountsservice has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1843982 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Fix Released Status in accountsservice package in Debian: Confirmed Bug description: [ Description ] When accountsservice's daemon is restarted - particularly when there is a user configured for auto login - it can cause code using its library to crash. This is bad because gnome-shell is one of those users which crashes. [ QA ] Configure a user for automatic login in gnome-shell. Update to this SRU, and then *restart your system*. The crash is in the library part, and so you will still see it if programs loaded the buggy version. Restarting is the easiest way to make sure you're not on it. Restart accounts-daemon.service (sudo systemctl restart accounts- daemon.service) a few times, leaving several seconds between each attempt. See that it crashes if you don't have this SRU, and doesn't if you do have it. --- Test that fast user switching still works properly. --- Take a look at the error reports listed below and hopefully see them not occurring (barring the usual noise) with the SRU. [ Regression potential ] We think this is safe - it tells clients that the daemon is away when it quits, and is back when it comes back. They should get appropriate signals to indicate this. Nevertheless, these signals are sent when they weren't before now, so that could cause problems. Watch out for errors creeping up with this SRU. We wondered upstream whether some more protections might be needed. I'm thinking that those should be *additional* safety rails around this fix, but it could actually be that more is needed and this fix isn't complete. [ Original report ] https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 14 10:29:16 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-05-24 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1843982/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Also affects: dbus (Ubuntu Focal) Importance: High Status: Incomplete ** Also affects: gnome-shell (Ubuntu Focal) Importance: Undecided Status: Invalid ** Also affects: accountsservice (Ubuntu Focal) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught signal, shutting down... Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group on interface vnet0.IPv6 with address
[Dx-packages] [Bug 1773859] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released 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 -- 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 1773859] Re: upgrades to 18.04 fail
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 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 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 -- 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 1773859] Re: upgrades to 18.04 fail
** Tags added: bugpattern-written -- 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 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 -- 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 1787540] Re: 16.04 to 18.04.1 ubgrade fails because of diversion of org.freedesktop.systemd1.service
*** This bug is a duplicate of bug 1773859 *** https://bugs.launchpad.net/bugs/1773859 ** Package changed: ubuntu-release-upgrader (Ubuntu) => systemd-shim (Ubuntu) ** Changed in: systemd-shim (Ubuntu) Status: Incomplete => New ** This bug has been marked a duplicate of bug 1773859 upgrades to 18.04 fail -- 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/1787540 Title: 16.04 to 18.04.1 ubgrade fails because of diversion of org.freedesktop.systemd1.service Status in systemd-shim package in Ubuntu: New Bug description: I ran do-release-upgrade from a terminal. The process eventually failed because of "too many errors". The root cause appears to be this: 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 I appear to have worked around this by manually removing /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service, purging systemd-shim via `dpkg -P` and then doing `apt-get install -f`, which completed without errors. After that, another `apt-get dist-upgrade` was apparently enough to complete the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1787540/+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 1776956] Re: /usr/bin/dconf:11:dconf_engine_change_sync:dconf_client_write_sync:dconf_reset:_vala_main:__libc_start_main
I received a crash report in the linked bucket after upgrading from Ubuntu 16.04 to Ubuntu 18.04. -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1776956 Title: /usr/bin/dconf:11:dconf_engine_change_sync:dconf_client_write_sync:dconf_reset:_vala_main:__libc_start_main Status in d-conf package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding d-conf. This problem was most recently seen with package version 0.26.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/78420c7b413d368ab6bcf6504f0bf62b34a401d2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1776956/+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 1768610] Re: leftover conffile forces GNOME is software rendering
** Changed in: nux (Ubuntu) Milestone: None => ubuntu-18.04.1 -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Confirmed Bug description: After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+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 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration
** Changed in: nux (Ubuntu) Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team) ** Changed in: nux (Ubuntu) Milestone: None => ubuntu-18.04.1 -- 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/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration Status in nux package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 18.04 on a very plain Intel Skylake graphics, hardware acceleration is gone. Glxinfo and System Information report 'llvmpipe' (software rasterizer) It is caused by the file /etc/X11/Xsession.d/50_check_unity_support which can be deleted and then this problem goes away. > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglvnd0 1.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:24:48 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (735 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libglvnd UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+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 1773859] Re: upgrades to 18.04 fail
** Changed in: systemd-shim (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) ** Changed in: systemd-shim (Ubuntu Bionic) Milestone: None => ubuntu-18.04.1 -- 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: New Status in systemd-shim package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd-shim source package in Bionic: New Bug description: $ 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 -- 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 1773859] Re: upgrades to 18.04 fail
** Tags added: xenial2bionic -- 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: New Status in systemd-shim package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd-shim source package in Bionic: New Bug description: $ 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 -- 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 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration
The mentioned file,/etc/X11/Xsession.d/50_check_unity_support, should only run on systems using Xubuntu. Is that what everyone is using? Additionally, I tried to recreate this by uninstalling unity but unity_support_test still passes for me. [ 1:24PM 10282 ] [ bdmurray@impulse:~/source-trees/metarelease/ubuntu ] $ /usr/lib/nux/unity_support_test; echo $? 0 [ 1:24PM 10283 ] [ bdmurray@impulse:~/source-trees/metarelease/ubuntu ] [ 1:24PM 10285 ] [ bdmurray@impulse:~/source-trees/metarelease/ubuntu ] $ sudo apt-get remove unity [sudo] password for bdmurray: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: gtk3-nocsd libgtk3-nocsd0 python3-feedparser session-shortcuts unity-scope-calculator unity-scope-chromiumbookmarks unity-scope-colourlovers unity-scope-devhelp unity-scope-firefoxbookmarks unity-scope-home unity-scope-manpages unity-scope-openclipart unity-scope-texdoc unity-scope-virtualbox unity-scope-yelp unity-scope-zotero unity-scopes-master-default Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: unity unity-session unity-tweak-tool 0 upgraded, 0 newly installed, 3 to remove and 13 not upgraded. After this operation, 9,766 kB disk space will be freed. Do you want to continue? [Y/n] Y [ 1:25PM 10286 ] [ bdmurray@impulse:~/source-trees/metarelease/ubuntu ] $ /usr/lib/nux/unity_support_test; echo $? 0 Is the unity_support_test failing for you all? -- 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/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration Status in nux package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 18.04 on a very plain Intel Skylake graphics, hardware acceleration is gone. Glxinfo and System Information report 'llvmpipe' (software rasterizer) It is caused by the file /etc/X11/Xsession.d/50_check_unity_support which can be deleted and then this problem goes away. > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglvnd0 1.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:24:48 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (735 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libglvnd UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+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 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on
Hello Marco, or anyone else affected, Accepted nux into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nux/4.0.8+16.04.20170816-0ubuntu1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nux (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1664205 Title: Copy-paste and text selection doesn't work when caps-lock is on Status in nux package in Ubuntu: Fix Released Status in nux source package in Xenial: Fix Committed Bug description: [Impact] Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps Lock is on [Test case] 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off [Possible regression] Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling won't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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 1703046] Update Released
The verification of the Stable Release Update for indicator-printers has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1703046 Title: indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() Status in indicator-printers package in Ubuntu: Fix Released Status in indicator-printers source package in Artful: Fix Released Bug description: [ Impact ] indicators-printers crashes, notifying the error to the user. [ Test case ] This was one of the most hit crash in errors.ubuntu.com. Make sure this will no longer happen once the fix is released. The link is https://errors.ubuntu.com/problem/43e6488fd8640c6a0cb8ca237286153b5b547f80 [ Regression potential ] Nothing really possible, other not crashing. Just got this from the recent update ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: indicator-printers 0.1.7+17.04.20170227-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 7 16:55:07 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service InstallationDate: Installed on 2015-12-17 (567 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fa9166826b5 <__GI_strtol_l_internal+53>: movsbq (%r14),%rax PC (0x7fa9166826b5) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-printers StacktraceTop: __GI_strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=, loc=0x7fa916a09400 <_nl_global_locale>) at ../stdlib/strtol_l.c:293 () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() UpgradeStatus: Upgraded to artful on 2017-02-14 (143 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo ubridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1703046/+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 1722151] Update Released
The verification of the Stable Release Update for language-selector has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1722151 Title: Incorrect syntax when writing to ~/.pam_environment Status in accountsservice package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in accountsservice source package in Artful: Fix Committed Status in language-selector source package in Artful: Fix Released Bug description: [Impact] When the syntax for the entries in ~/.pam_environment was changed, the GUI in language-selector-gnome for maintaining the language priority list was broken since language-selector-gnome reads from ~/.pam_environment. The language-selector upload to artful makes language-selector-gnome handle both the old and the new syntax correctly. An additional similar change to accountsservice (the update-langlist script) is needed; hence also an accountsservice upload to artful. [Test Case] * Log in to an "Ubuntu on Xorg" session. * Open Language Support and find that it appears as if you can only set one item before the "English" item in the language list. With the new version, it works as expected again. [Regression Potential] Low. This is necessary to fix the regression caused by the change in accountsservice. [Original description] While investigating bug #1662031, I found out that /usr/share /language-tools/save-to-pam-env writes to ~/.pam_environment using an incorrect syntax: "VARIABLE=value" on each line. The expected syntax is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: accountsservice 0.6.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 06:57:17 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (463 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: accountsservice UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1722151/+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 1703046] Re: indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()
Hello siucdude, or anyone else affected, Accepted indicator-printers into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/indicator- printers/0.1.7+17.10.20171021-0ubuntu1 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: indicator-printers (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-artful -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1703046 Title: indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() Status in indicator-printers package in Ubuntu: In Progress Status in indicator-printers source package in Artful: Fix Committed Bug description: [ Impact ] indicators-printers crashes, notifying the error to the user. [ Test case ] This was one of the most hit crash in errors.ubuntu.com. Make sure this will no longer happen once the fix is released. [ Regression potential ] Nothing really possible, other not crashing. Just got this from the recent update ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: indicator-printers 0.1.7+17.04.20170227-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 7 16:55:07 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service InstallationDate: Installed on 2015-12-17 (567 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fa9166826b5 <__GI_strtol_l_internal+53>: movsbq (%r14),%rax PC (0x7fa9166826b5) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-printers StacktraceTop: __GI_strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=, loc=0x7fa916a09400 <_nl_global_locale>) at ../stdlib/strtol_l.c:293 () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() UpgradeStatus: Upgraded to artful on 2017-02-14 (143 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo ubridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1703046/+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 1703046] Re: indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()
In the bug description I was expecting a link to the bucket which is the same crash as this e.g. https://errors.ubuntu.com/problem/43e6488fd8640c6a0cb8ca237286153b5b547f80 This way the SRU team can easily confirm that the new version of the package does not appear there. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1703046 Title: indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() Status in indicator-printers package in Ubuntu: In Progress Bug description: [ Impact ] indicators-printers crashes, notifying the error to the user. [ Test case ] This was one of the most hit crash in errors.ubuntu.com. Make sure this will no longer happen once the fix is released. [ Regression potential ] Nothing really possible, other not crashing. Just got this from the recent update ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: indicator-printers 0.1.7+17.04.20170227-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 7 16:55:07 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service InstallationDate: Installed on 2015-12-17 (567 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fa9166826b5 <__GI_strtol_l_internal+53>: movsbq (%r14),%rax PC (0x7fa9166826b5) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-printers StacktraceTop: __GI_strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=, loc=0x7fa916a09400 <_nl_global_locale>) at ../stdlib/strtol_l.c:293 () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() UpgradeStatus: Upgraded to artful on 2017-02-14 (143 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo ubridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1703046/+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 1722151] Re: Incorrect syntax when writing to ~/.pam_environment
Hello Olivier, or anyone else affected, Accepted accountsservice into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/accountsservice/0.6.42-0ubuntu3.1 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: accountsservice (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-artful ** Changed in: language-selector (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1722151 Title: Incorrect syntax when writing to ~/.pam_environment Status in accountsservice package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in accountsservice source package in Artful: Fix Committed Status in language-selector source package in Artful: Fix Committed Bug description: [Impact] When the syntax for the entries in ~/.pam_environment was changed, the GUI in language-selector-gnome for maintaining the language priority list was broken since language-selector-gnome reads from ~/.pam_environment. The language-selector upload to artful makes language-selector-gnome handle both the old and the new syntax correctly. An additional similar change to accountsservice (the update-langlist script) is needed; hence also an accountsservice upload to artful. [Test Case] * Log in to an "Ubuntu on Xorg" session. * Open Language Support and find that it appears as if you can only set one item before the "English" item in the language list. With the new version, it works as expected again. [Regression Potential] Low. This is necessary to fix the regression caused by the change in accountsservice. [Original description] While investigating bug #1662031, I found out that /usr/share /language-tools/save-to-pam-env writes to ~/.pam_environment using an incorrect syntax: "VARIABLE=value" on each line. The expected syntax is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: accountsservice 0.6.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 06:57:17 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (463 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: accountsservice UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1722151/+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 1722151] Please test proposed package
Hello Olivier, or anyone else affected, Accepted language-selector into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/language- selector/0.180.1 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1722151 Title: Incorrect syntax when writing to ~/.pam_environment Status in accountsservice package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in accountsservice source package in Artful: Fix Committed Status in language-selector source package in Artful: Fix Committed Bug description: [Impact] When the syntax for the entries in ~/.pam_environment was changed, the GUI in language-selector-gnome for maintaining the language priority list was broken since language-selector-gnome reads from ~/.pam_environment. The language-selector upload to artful makes language-selector-gnome handle both the old and the new syntax correctly. An additional similar change to accountsservice (the update-langlist script) is needed; hence also an accountsservice upload to artful. [Test Case] * Log in to an "Ubuntu on Xorg" session. * Open Language Support and find that it appears as if you can only set one item before the "English" item in the language list. With the new version, it works as expected again. [Regression Potential] Low. This is necessary to fix the regression caused by the change in accountsservice. [Original description] While investigating bug #1662031, I found out that /usr/share /language-tools/save-to-pam-env writes to ~/.pam_environment using an incorrect syntax: "VARIABLE=value" on each line. The expected syntax is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: accountsservice 0.6.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 06:57:17 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (463 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: accountsservice UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1722151/+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 1611363] Re: vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()
** Tags removed: rls-aa-incoming ** Also affects: unity-gtk-module (Ubuntu) Importance: Undecided Status: New -- 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/1611363 Title: vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64() Status in vim: Confirmed Status in unity-gtk-module package in Ubuntu: New Status in vim package in Ubuntu: Confirmed Status in unity-gtk-module source package in Xenial: New Status in vim source package in Xenial: Confirmed Bug description: Hi, vim-gtk3 crashes so often on my system that it's borderline unusable. My system is a clean install of Ubuntu 16.04. I also (temporarily) renamed my customized ~/.vimrc and ~/.vim. My system is up-to-date as of today (2016-08-09); installed vim-gtk3 is 2:7.4.1689-3ubuntu1.1. The crash happens only (but very frequently, not always) when I launch gvim, either by calling it from a shell or by double-clicking a file in Nautilus. Note that the crash is independent of whether I'm opening a file or not. (At least I tried both variations from the terminal.) There's also a report on vim's bugtracker, but since unity appears in the backtrace, the consensus is that it's probably Ubuntu-specific. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: vim-gtk3 2:7.4.1689-3ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 9 14:34:31 2016 ExecutablePath: /usr/bin/vim.gtk3 InstallationDate: Installed on 2016-07-10 (29 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: gvim -f /home/username/Documents/schoul/2016/1G-TODO/01-systemes-equations-TODO/chap01_systemes-equations-NOTES.tex Signal: 11 SourcePackage: vim StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libunity-gtk3-parser.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: vim.gtk3 crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1611363/+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 1553592] Re: 16.04 casper 15_autologin file contains obsolete lightdm configuration
** Tags removed: rls-z-incoming ** Tags added: rls-aa-incoming -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1553592 Title: 16.04 casper 15_autologin file contains obsolete lightdm configuration Status in accountsservice package in Ubuntu: Triaged Status in casper package in Ubuntu: Triaged Bug description: /usr/share/initramfs-tools/scripts/casper-bottom/15autologin the lightdm section of the file contains a lightdm configuration that is incorrect for 15.10 and later for example it writes out /root/etc/lightdm/lightdm.conf according to the lightdm wiki this should be /root/etc/lightdm/lightdm.conf.d/xyz.conf Additionally using [SeatDefaults] is wrong. Again according the wiki [SeatDefaults] is obsolete and should be [Seat:*] Think this is probably why manual live CD creators and those who use Pinguy ISO Builder cannot create a lightdm autologin live CD ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.17.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 5 21:07:13 2016 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1553592/+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
Re: [Dx-packages] [Bug 269904] Re: Screen refresh problems with nvidia cards
On Fri, Apr 28, 2017 at 01:24:42AM -, Malachi de AElfweald wrote: > I just upgraded to 17.10 and am seeing the same problem with > 0.9.13.1+17.04.20170109-0ubuntu1 Please open a new bug report then as this is about a quite older version of Ubuntu. -- Brian Murray -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/269904 Title: Screen refresh problems with nvidia cards Status in Compiz: Fix Released Status in Compiz 0.9.11 series: In Progress Status in Compiz Core: New Status in Compiz Core 0.9.8 series: New Status in compiz package in Ubuntu: Fix Released Status in compiz-fusion-plugins-main package in Ubuntu: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in compiz source package in Precise: Confirmed Status in compiz-plugins-main source package in Precise: Confirmed Status in compiz source package in Trusty: Fix Released Status in compiz-plugins-main source package in Trusty: Invalid Status in compiz source package in Intrepid: Fix Released Status in compiz-plugins-main source package in Intrepid: Won't Fix Status in compiz-fusion-plugins-main package in Debian: Fix Released Bug description: [Impact] Users of Nvidia gfx using the proprietary driver may see screen corruption during certain operations. [Test Case] * Install an Nvidia graphics adapter and the proprietary driver. * Observe the graphics corrupt. * Install the version of Compiz with this fix. * Observe corruption is gone. [Regression Potential] The patch for this was provided by Nvidia. There could be some corner cases users hit that may cause other issues. That said, enough testing has been done to confidently say that the gains provided by this fix far outweigh any corner cases. --- Original Description: == Proposed compiz-fusion-plugins-main patch == See comment 234 by Anders Kaseorg and attached compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff. == Original report == Binary package hint: compiz I'm using latest compiz on intrepid. Since jockey-gtk does not work on my box (I already filed a bug), I manually installed nvidia-glx-177 and added the "driver → nvidia" line to xorg.conf. Now I seem to be having some screen refresh problems when using compiz: parts of the screen are refreshed, but others aren't. That means nautilus doesn't show files or folders until I move the cursor over them, firefox doesn't show webpages properly until I scroll down, and so on. Please, tell me if there is any additional info I can provide to find out the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/269904/+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 1681255] Stacktrace.txt
*** This bug is a duplicate of bug 1681870 *** https://bugs.launchpad.net/bugs/1681870 ** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1681255/+attachment/4860273/+files/Stacktrace.txt -- 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/1681255 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() Status in indicator-datetime package in Ubuntu: Confirmed Bug description: It appears every time I start the OS. Installed using daily build of the 8th April 2017. OS: Ubuntu 17.04 ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu3 Architecture: i386 CurrentDesktop: Unity:Unity7 Date: Sun Apr 9 20:11:45 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2017-04-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcEnviron: LANG=es_ES.UTF-8 LANGUAGE=es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: indicator-datetime StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681255/+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 1681255] StacktraceSource.txt
*** This bug is a duplicate of bug 1681870 *** https://bugs.launchpad.net/bugs/1681870 ** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1681255/+attachment/4860274/+files/StacktraceSource.txt -- 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/1681255 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() Status in indicator-datetime package in Ubuntu: Confirmed Bug description: It appears every time I start the OS. Installed using daily build of the 8th April 2017. OS: Ubuntu 17.04 ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu3 Architecture: i386 CurrentDesktop: Unity:Unity7 Date: Sun Apr 9 20:11:45 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2017-04-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcEnviron: LANG=es_ES.UTF-8 LANGUAGE=es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: indicator-datetime StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681255/+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 1681255]
*** This bug is a duplicate of bug 1681870 *** https://bugs.launchpad.net/bugs/1681870 StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new (sz=260) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:50 -- 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/1681255 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() Status in indicator-datetime package in Ubuntu: Confirmed Bug description: It appears every time I start the OS. Installed using daily build of the 8th April 2017. OS: Ubuntu 17.04 ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu3 Architecture: i386 CurrentDesktop: Unity:Unity7 Date: Sun Apr 9 20:11:45 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2017-04-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcEnviron: LANG=es_ES.UTF-8 LANGUAGE=es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: indicator-datetime StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681255/+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 1681255] ThreadStacktrace.txt
*** This bug is a duplicate of bug 1681870 *** https://bugs.launchpad.net/bugs/1681870 ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1681255/+attachment/4860275/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1681255/+attachment/4859117/+files/CoreDump.gz ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => Medium ** This bug has been marked a duplicate of bug 1681870 indicator-datetime-service crashed with SIGABRT in __malloc_assert() -- 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/1681255 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() Status in indicator-datetime package in Ubuntu: Confirmed Bug description: It appears every time I start the OS. Installed using daily build of the 8th April 2017. OS: Ubuntu 17.04 ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu3 Architecture: i386 CurrentDesktop: Unity:Unity7 Date: Sun Apr 9 20:11:45 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2017-04-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcEnviron: LANG=es_ES.UTF-8 LANGUAGE=es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: indicator-datetime StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6dd7780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681255/+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 1681870] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1681870/+attachment/4860239/+files/StacktraceSource.txt -- 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/1681870 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() Status in indicator-datetime package in Ubuntu: New Bug description: Install I386 version of desktop or run live desktop and the indicator is crashed. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu4 Architecture: i386 CurrentDesktop: Unity:Unity7 Date: Tue Apr 11 15:41:03 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ExecutableTimestamp: 1490207290 InstallationDate: Installed on 2017-04-11 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcCwd: /home/davmor2 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: indicator-datetime StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681870/+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 1681870] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1681870/+attachment/4860240/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1681870/+attachment/4860219/+files/CoreDump.gz ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => Medium ** Tags added: iso-testing -- 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/1681870 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() Status in indicator-datetime package in Ubuntu: New Bug description: Install I386 version of desktop or run live desktop and the indicator is crashed. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu4 Architecture: i386 CurrentDesktop: Unity:Unity7 Date: Tue Apr 11 15:41:03 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ExecutableTimestamp: 1490207290 InstallationDate: Installed on 2017-04-11 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcCwd: /home/davmor2 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: indicator-datetime StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681870/+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 1681870] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1681870/+attachment/4860238/+files/Stacktrace.txt -- 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/1681870 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() Status in indicator-datetime package in Ubuntu: New Bug description: Install I386 version of desktop or run live desktop and the indicator is crashed. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu4 Architecture: i386 CurrentDesktop: Unity:Unity7 Date: Tue Apr 11 15:41:03 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ExecutableTimestamp: 1490207290 InstallationDate: Installed on 2017-04-11 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcCwd: /home/davmor2 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: indicator-datetime StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681870/+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 1681870]
StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new (sz=260) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:50 -- 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/1681870 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() Status in indicator-datetime package in Ubuntu: New Bug description: Install I386 version of desktop or run live desktop and the indicator is crashed. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu4 Architecture: i386 CurrentDesktop: Unity:Unity7 Date: Tue Apr 11 15:41:03 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ExecutableTimestamp: 1490207290 InstallationDate: Installed on 2017-04-11 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service ProcCwd: /home/davmor2 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: indicator-datetime StacktraceTop: __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, function=) at malloc.c:301 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at malloc.c:2400 _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at malloc.c:3862 __GI___libc_malloc (bytes=260) at malloc.c:2925 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681870/+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 1637379] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted indicator-application into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /indicator-application/12.10.1+16.04.20170120-0ubuntu1 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1637379 Title: Hide 'Indicator Application' from Startup Applications Status in indicator-application package in Ubuntu: Fix Released Status in indicator-application source package in Xenial: Fix Committed Status in indicator-application source package in Yakkety: Fix Committed Bug description: Impact == Ubuntu still ships the Startup Applications app. System autostart files like 'Indicator Application' should not show up in this app as we don't want users to unintentionally disable these services that easily. Test Case = Open Startup Applications and check for 'Indicator Application' Regression Potential This should be safe. We've been setting NoDisplay=true for stuff in /etc/xdg/autostart/ for years. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1637379/+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 1637379] Re: Hide 'Indicator Application' from Startup Applications
Hello Jeremy, or anyone else affected, Accepted indicator-application into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /indicator-application/12.10.1+16.10.20170120-0ubuntu1 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: indicator-application (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: indicator-application (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1637379 Title: Hide 'Indicator Application' from Startup Applications Status in indicator-application package in Ubuntu: Fix Released Status in indicator-application source package in Xenial: Fix Committed Status in indicator-application source package in Yakkety: Fix Committed Bug description: Impact == Ubuntu still ships the Startup Applications app. System autostart files like 'Indicator Application' should not show up in this app as we don't want users to unintentionally disable these services that easily. Test Case = Open Startup Applications and check for 'Indicator Application' Regression Potential This should be safe. We've been setting NoDisplay=true for stuff in /etc/xdg/autostart/ for years. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1637379/+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 1574699] Re: All QSystemTrayIcon have the same icon, and QSystemTrayIcon::isSystemTrayAvailable remove all QSystemTrayIcon
Hello ogoffart, or anyone else affected,
Accepted appmenu-qt5 into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/appmenu-
qt5/0.3.0+16.04.20151130-0ubuntu2 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: appmenu-qt5 (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags added: verification-needed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1574699
Title:
All QSystemTrayIcon have the same icon, and
QSystemTrayIcon::isSystemTrayAvailable remove all QSystemTrayIcon
Status in appmenu-qt5:
New
Status in appmenu-qt5 package in Ubuntu:
Fix Released
Status in appmenu-qt5 source package in Xenial:
Fix Committed
Bug description:
# Impact
This affects all Qt applications that use
QSystemTrayIcon::isSystemTrayAvailable, in Unity environment. Confirmed
examples are owncloud-client and keepassxc, but there may be more applications.
# Test Case
See the original description below for the test case in C++.
# Proposed Fix
The proposed fix is identical to what was uploaded to Yakkety as version
0.3.0+16.10.20160628.1-0ubuntu1. The fix is using unique connections for all
AppMenuPlatformSystemTrayIcon instances.
# Regression Potential
The fix is in Yakkety since June and in Zesty, and nobody complained so far.
So it should not cause any regressions.
-
in appmenu-qt5 in ubuntu 16.04, the AppMenuPlatformSystemTrayIcon assumes
there is only one instance of a QPlatformSystemTrayIcon: it register the same
dbus name for all the instances. In fact, there is one instance of
QPlatformSystemTrayIcon per instance of QSystemTrayIcon, and one temporary is
created for QSystemTrayIcon::isSystemTrayAvailable.
This breaks the owncloud client [issue
https://github.com/owncloud/client/issues/4693 ]
This example reproduces the problem:
```
#include
int main(int argc, char *argv[])
{
QApplication a(argc, argv);
QImage img(64,64, QImage::Format_ARGB32);
img.fill(Qt::red);
QSystemTrayIcon sti(QIcon(QPixmap::fromImage(img)));
sti.show();
QSystemTrayIcon::isSystemTrayAvailable(); // with this line, the
QSystemTrayIcon does not appear
// comment the previous line to see that the QSystemTrayIcon works and
that there is a bug in that line
return a.exec();
}
```
This testcase shows that the
AppMenuPlatformSystemTrayIcon::~AppMenuPlatformSystemTrayIcon called
by the temporary object created inside
QSystemTrayIcon::isSystemTrayAvailable unregisters the icon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1574699/+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 1262022] Update Released
The verification of the Stable Release Update for overlay-scrollbar has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1262022 Title: incorrect multi-arch related meta information. Status in overlay-scrollbar package in Ubuntu: Fix Released Status in overlay-scrollbar source package in Xenial: Fix Released Status in overlay-scrollbar source package in Yakkety: Fix Released Bug description: == SRU Impact == overlay-scrollbar-gtk2:i386 is uninstallable on amd64, which blocks the installation of some packages. == Test Case == On amd64: dpkg --add-architecture i386 apt update apt install overlay-scrollbar-gtk2:i386 Either this succeeds, or fails (this bug) == Regression potential == Nil (or close enough) == Original Bug == I'm on a 64-bit system trying to install "overlay-scrollbar-gtk2:i386" which depends on the "overlay-scrollbar:i386" package. "overlay- scrollbar:i386" doesn't have an install candidate because it's a "multi-arch" package. This should (or so I've been told) be reflected in the meta information of the "overlay-scrollbar" package but isn't, which is why the former package fails to install. As a more competent person than I put it: "The overlay-scrollbar package does not come in i386 or amd64 flavors; it comes as an "all" flavor, which installs on all archs. It appears to be missing the Multi-Arch: allowed header so it won't satisfy an i386 package depending on it. You should file a bug report asking that the missing header be added." ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: overlay-scrollbar 0.2.16+r359+13.10.20130826-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 18 02:14:35 2013 InstallationDate: Installed on 2013-12-14 (3 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: overlay-scrollbar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1262022/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7
Hello Pat, or anyone else affected, Accepted unity-gtk-module into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity-gtk- module/0.0.0+15.04.20150118-0ubuntu3 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity-gtk-module (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed -- 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/1644323 Title: Installing unity8-session-snap adversely effects unity7 Status in Canonical System Image: Fix Committed Status in dbus package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Committed Status in unity-gtk-module source package in Xenial: Fix Committed Bug description: [ Description ] In Xenial, when dbus-user-session is installed, dbus' upstart job still starts a new bus. Things get confused about which bus to talk to. [ Fix ] Already fixed in Yakkety. Cherry-pick the upstart job. On top of Yakkety's version, call `dbus-update-activation-environment --verbose --systemd GTK_MODULES', because Xenial does not have the change in upstart to automatically publish to the systemd activation environment. /etc/X11/Xsession.d/95dbus_update-activation-env is called too early - before unity-gtk-module.conf is started - so dbus activated services miss the GTK_MODULES environment variable. Update unity-gtk- module.conf to set it in the dbus activation environment. [ QA ] Install dbus-user-session, press print screen. It should be delayed if you are experiencing this bug, and not delayed otherwise. Remove dbus-user-session, make sure the session still works properly - the global menu works, everything launches properly, etc. Test that gnome-terminal has global menus in both situations. [ Regression potential ] This change alters the way that the session bus is launched, even if you aren't using dbus-user-session. Even though this same change is deployed in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-session by default, so the case where you don't have it isn't as well tested. I would suggest focusing some testing on the non dbus-user-session case. [ Original report ] After installing the deb (and then the snap), certain things in the unity7 session take a very long time (30 to 60 secs), such as launching chromium and ctrl-alt-t for a new terminal session. Removing both the deb and the snap followed by a reboot does not fix the symptoms. Xenial amd64 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1262022] Please test proposed package
Hello Tomas, or anyone else affected, Accepted overlay-scrollbar into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/overlay- scrollbar/0.2.17.1+16.04.20151117-0ubuntu1.16.10.1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1262022 Title: incorrect multi-arch related meta information. Status in overlay-scrollbar package in Ubuntu: Fix Released Status in overlay-scrollbar source package in Xenial: Fix Committed Status in overlay-scrollbar source package in Yakkety: Fix Committed Bug description: == SRU Impact == overlay-scrollbar-gtk2:i386 is uninstallable on amd64, which blocks the installation of some packages. == Test Case == On amd64: dpkg --add-architecture i386 apt update apt install overlay-scrollbar-gtk2:i386 Either this succeeds, or fails (this bug) == Regression potential == Nil (or close enough) == Original Bug == I'm on a 64-bit system trying to install "overlay-scrollbar-gtk2:i386" which depends on the "overlay-scrollbar:i386" package. "overlay- scrollbar:i386" doesn't have an install candidate because it's a "multi-arch" package. This should (or so I've been told) be reflected in the meta information of the "overlay-scrollbar" package but isn't, which is why the former package fails to install. As a more competent person than I put it: "The overlay-scrollbar package does not come in i386 or amd64 flavors; it comes as an "all" flavor, which installs on all archs. It appears to be missing the Multi-Arch: allowed header so it won't satisfy an i386 package depending on it. You should file a bug report asking that the missing header be added." ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: overlay-scrollbar 0.2.16+r359+13.10.20130826-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 18 02:14:35 2013 InstallationDate: Installed on 2013-12-14 (3 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: overlay-scrollbar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1262022/+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 1262022] Re: incorrect multi-arch related meta information.
Hello Tomas, or anyone else affected, Accepted overlay-scrollbar into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/overlay- scrollbar/0.2.17.1+16.04.20151117-0ubuntu1.16.04.1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: overlay-scrollbar (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed ** Changed in: overlay-scrollbar (Ubuntu Yakkety) Status: New => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1262022 Title: incorrect multi-arch related meta information. Status in overlay-scrollbar package in Ubuntu: Fix Released Status in overlay-scrollbar source package in Xenial: Fix Committed Status in overlay-scrollbar source package in Yakkety: Fix Committed Bug description: == SRU Impact == overlay-scrollbar-gtk2:i386 is uninstallable on amd64, which blocks the installation of some packages. == Test Case == On amd64: dpkg --add-architecture i386 apt update apt install overlay-scrollbar-gtk2:i386 Either this succeeds, or fails (this bug) == Regression potential == Nil (or close enough) == Original Bug == I'm on a 64-bit system trying to install "overlay-scrollbar-gtk2:i386" which depends on the "overlay-scrollbar:i386" package. "overlay- scrollbar:i386" doesn't have an install candidate because it's a "multi-arch" package. This should (or so I've been told) be reflected in the meta information of the "overlay-scrollbar" package but isn't, which is why the former package fails to install. As a more competent person than I put it: "The overlay-scrollbar package does not come in i386 or amd64 flavors; it comes as an "all" flavor, which installs on all archs. It appears to be missing the Multi-Arch: allowed header so it won't satisfy an i386 package depending on it. You should file a bug report asking that the missing header be added." ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: overlay-scrollbar 0.2.16+r359+13.10.20130826-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 18 02:14:35 2013 InstallationDate: Installed on 2013-12-14 (3 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: overlay-scrollbar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1262022/+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 1443052] Update Released
The verification of the Stable Release Update for accountsservice has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history - patch Status in accountsservice: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Trusty: Fix Released Status in accountsservice source package in Xenial: Fix Released Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. [bdmurray] - What could go wrong? What should a user testing this look for? -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
While we don't see any crashes about that this from 16.10 on the Error Tracker, shouldn't this also be fixed in that release? ** Also affects: ido (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Xenial: New Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1443052] Re: User accounts login history showing incorrect history - patch
Hello Nikita, or anyone else affected, Accepted accountsservice into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/accountsservice/0.6.40-2ubuntu11.3 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Description changed: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. - + [bdmurray] - What could go wrong? What should a user testing this look for? -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. ** Changed in: accountsservice (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: accountsservice (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history - patch Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Trusty: Fix Committed Status in accountsservice source package in Xenial: Fix Committed Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact
[Dx-packages] [Bug 1443052] Please test proposed package
Hello Nikita, or anyone else affected, Accepted accountsservice into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/accountsservice/0.6.35-0ubuntu7.3 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history - patch Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Trusty: Fix Committed Status in accountsservice source package in Xenial: Fix Committed Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. [bdmurray] - What could go wrong? What should a user testing this look for? -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1577049] Update Released
The verification of the Stable Release Update for accountsservice has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1577049 Title: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04 Status in accountsservice: Unknown Status in Ubuntu GNOME: Fix Committed Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Xenial: Fix Released Status in accountsservice package in Debian: Fix Released Bug description: Impact == Ubuntu 16.04's accountsservice was built without systemd support because systemd dropped libsystemd-login because that functionality was merged into libsystemd. At a minimum, this broke GNOME Shell's "Switch User" feature. Test Case = 1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages. 2. Add a user if necessary to ensure you have at least 2 user accounts configured. 3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower case letter r. Or you can log out of all user accounts and log back in. 4. Click the system status area in the top right of GNOME Shell. 5. Click your user name. "Switch User" should appear in the list. Regression Potential None. The one-line change to accountsservice's configure check was made in Debian's accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was included in accountsservice 0.6.42 released in June. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1577049/+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 147312] Re: ccsm crashed with KeyError in UpdateEnabledPluginsList()
ccsm seems to be part of compiz now and people are still experiencing this crash on 16.04. ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to compizconfig-settings-manager in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/147312 Title: ccsm crashed with KeyError in UpdateEnabledPluginsList() Status in compiz package in Ubuntu: New Status in compizconfig-settings-manager package in Ubuntu: Invalid Bug description: Binary package hint: compizconfig-settings-manager Installed compizconfig-settings-manager, along with xserver-glx, using apt-get, and it came up with this error. ProblemType: Crash Architecture: i386 Date: Sun Sep 30 18:28:10 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/ccsm InterpreterPath: /usr/bin/python2.5 NonfreeKernelModules: ath_hal Package: compizconfig-settings-manager 0.5.2+git20070912-0ubuntu1 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/ccsm ProcCwd: /home/hraefn ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/ccsm'] SourcePackage: compizconfig-settings-manager Title: ccsm crashed with KeyError in UpdateEnabledPluginsList() Uname: Linux worker-ant 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/147312/+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 1598770] Please test proposed package
Hello Marco, or anyone else affected, Accepted compiz into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/compiz/1:0.9.12.2+16.04.20160714-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: Fix Committed Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Hello Marco, or anyone else affected, Accepted nux into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nux/4.0.8+16.04.20160705-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nux (Ubuntu Xenial) Status: New => Fix Committed -- 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/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: In Progress Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: Fix Committed Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Hello Marco, or anyone else affected, Accepted compiz into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/compiz/1:0.9.12.2+16.04.20160705-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: compiz (Ubuntu Xenial) Status: New => Fix Committed -- 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/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: In Progress Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: New Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Hello Marco, or anyone else affected, Accepted unity into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.4.0+16.04.20160705-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: In Progress Status in compiz source package in Xenial: New Status in nux source package in Xenial: New Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
** Summary changed: - Unity in low-graphics mode has animations and unneded redraws + Unity in low-graphics mode has animations and unneeded redraws -- 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/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: In Progress Status in compiz source package in Xenial: New Status in nux source package in Xenial: New Status in unity source package in Xenial: New Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1506744] Re: Newly installed applications do not show in the dash
Hello Cerberus, or anyone else affected, Accepted libunity into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libunity/7.1.4+16.04.20160701-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libunity (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash Status in GLib: Confirmed Status in bamf package in Ubuntu: In Progress Status in gnome-menus package in Ubuntu: Fix Released Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in gnome-menus source package in Xenial: Fix Released Status in libunity source package in Xenial: Fix Committed Bug description: [Impact] I am running 15.10 development version fully up to date, I installed it a few days ago and I have an issue with newly installed applications not appearing in the dash when I search for them, they can be started via console but the icons/launchers of newly installed applications will only appear in the dash after session is restarted. [Test case] 1. Install a new applicaiton (using apt-get or the software center) 2. Make sure the application is listed in the Unity Dash [Possible Regressions] Unity fails to list all the applications, not just the newly installed ones. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Oct 16 08:41:39 2015 InstallationDate: Installed on 2015-10-11 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install)Z To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+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 1598770] Re: Unity in low-graphics mode has animations and unneded redraws
** Also affects: compiz (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unity-control-center (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: unity-control-center (Ubuntu Xenial) Status: New => Fix Committed -- 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/1598770 Title: Unity in low-graphics mode has animations and unneded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: In Progress Status in compiz source package in Xenial: New Status in nux source package in Xenial: New Status in unity source package in Xenial: New Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1582433] Re: Dash does not handle .desktop files correctly if there are hyphens in the directory path
Hello Neil, or anyone else affected, Accepted unity-lens-applications into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unity-lens-applications/7.1.0+16.04.20160701-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity-lens-applications (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1582433 Title: Dash does not handle .desktop files correctly if there are hyphens in the directory path Status in unity-lens-applications package in Ubuntu: Fix Released Status in unity-lens-applications source package in Xenial: Fix Committed Bug description: [Impact] The Unity dash can fail to display the icon or title from a .desktop file correctly if it resides under a directory containing a hyphen character. [Test case] As an example (on my 16.04 machine): $ cat << EOF > test.desktop [Desktop Entry] Name=Hyphen test Exec=/bin/true Type=Application Icon=/usr/share/icons/suru/apps/256/dash.png EOF $ chmod +x test.desktop $ mkdir ~/.local/share/applications/hyphen-test $ mv test.desktop ~/.local/share/applications/hyphen-test/ Now, open the dash and search for "hyphen". On my machine, I see the correct icon but no title is displayed underneath. $ mv ~/.local/share/applications/hyphen-test ~/.local/share/applications/hyphen Searching for "hyphen" in the dash now shows an entry with the correct icon and title (but also still shows the defunct previous entry without title). The effect of the hyphenated path seems variable. Some apps show the wrong icon, some have a missing title, some have both errors. The problem only seems to be with hyphens in the directories. Hyphens in the file itself are fine. See the screenshot - Might and Magic 4&5 has had a desktop file installed under a subdirectory with a hyphen, whereas Heroes of Might and Magic has a desktop file in the root directory but contains a hyphen in the filename. The latter is shown correctly, but the desktop files in the former directory are not shown properly. [Possible Regressions] Nothing known. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1582433/+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 1582433] Re: Dash does not handle .desktop files correctly if there are hyphens in the directory path
** Also affects: unity-lens-applications (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1582433 Title: Dash does not handle .desktop files correctly if there are hyphens in the directory path Status in unity-lens-applications package in Ubuntu: Fix Released Status in unity-lens-applications source package in Xenial: New Bug description: [Impact] The Unity dash can fail to display the icon or title from a .desktop file correctly if it resides under a directory containing a hyphen character. [Test case] As an example (on my 16.04 machine): $ cat << EOF > test.desktop [Desktop Entry] Name=Hyphen test Exec=/bin/true Type=Application Icon=/usr/share/icons/suru/apps/256/dash.png EOF $ chmod +x test.desktop $ mkdir ~/.local/share/applications/hyphen-test $ mv test.desktop ~/.local/share/applications/hyphen-test/ Now, open the dash and search for "hyphen". On my machine, I see the correct icon but no title is displayed underneath. $ mv ~/.local/share/applications/hyphen-test ~/.local/share/applications/hyphen Searching for "hyphen" in the dash now shows an entry with the correct icon and title (but also still shows the defunct previous entry without title). The effect of the hyphenated path seems variable. Some apps show the wrong icon, some have a missing title, some have both errors. The problem only seems to be with hyphens in the directories. Hyphens in the file itself are fine. See the screenshot - Might and Magic 4&5 has had a desktop file installed under a subdirectory with a hyphen, whereas Heroes of Might and Magic has a desktop file in the root directory but contains a hyphen in the filename. The latter is shown correctly, but the desktop files in the former directory are not shown properly. [Possible Regressions] Nothing known. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1582433/+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 1562822] Re: Bluetooth Browse Files... not working
Hello Huck-bernhard, or anyone else affected, Accepted indicator-bluetooth into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /indicator-bluetooth/0.0.6+16.04.20160526-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: indicator-bluetooth (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1562822 Title: Bluetooth Browse Files... not working Status in OEM Priority Project: New Status in indicator-bluetooth package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Released Bug description: indicator * Impact The bluetooth indicator includes a non working "browse files..." items * Test case connect/pair a phone which does obex, open the bluetooth indicator and select the device, the only action listed should be "send" * Regression potential none, it's removing a widget which was doing nothing -- ucc * Impact The bluetooth settings include a non working "browse files..." items * Test case connect/pair a phone which does obex, open settings->bluetooth, the only action listed should be "send" * Regression potential none, it's removing a widget which was doing nothing -- Mobile phone: LG L40 Android 4.4.2 1. Connecting to Phone is successful shown. 2. Click on Button "Browse Files... " nothing happen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 28 13:31:39 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-02-04 (52 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1562822/+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 1581674] Re: package accountsservice 0.6.40-2ubuntu10 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio
Please try reinstalling the accountsservice package as indicated in the bug title. ** Changed in: accountsservice (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1581674 Title: package accountsservice 0.6.40-2ubuntu10 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in accountsservice package in Ubuntu: Incomplete Bug description: Doesn't install in ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: accountsservice 0.6.40-2ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri May 13 21:45:58 2016 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-05-05 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: accountsservice Title: package accountsservice 0.6.40-2ubuntu10 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/accountsservice/+bug/1581674/+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 1570902] Re: Touchpad turns back on
** Tags added: trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1570902 Title: Touchpad turns back on Status in d-conf package in Ubuntu: New Bug description: Release:Ubuntu 14.04.4 LTS I am using a Thinpad laptop with a TrackPoint, which I find more convenient to use than the TouchPad. Turned the TouchPad off via the System Settings (mouse & touchpad), which works for a while. Expected behavior: TouchPad should stay off unless I turn it back on (eg. for another user) What happens: TouchPad turns back on randomly, often after suspend, sometimes just in the middle of a session. When checking the System Settings, the touchpad button is indeed back to "on" without any intervention from me. I am unsure which package is causing the bug, most probably a process is ignoring the settings I set and has in its routine to turn the TouchPad on. Maybe the bug should be filed agains gsettings? This has been reported on askubuntu: http://askubuntu.com/questions/736035/how-to-completely-disable-the-touchpad-device-on-my-computer-its-back-on-afte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1570902/+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 1566502] [NEW] [MIR] indicator-applet
Public bug reported: indicator-datetime recommends indicator-applet although indicator-applet is in universe ** Affects: indicator-applet (Ubuntu) Importance: Undecided Assignee: Charles Kerr (charlesk) Status: New ** Tags: xenial ** Changed in: indicator-applet (Ubuntu) Assignee: (unassigned) => Charles Kerr (charlesk) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1566502 Title: [MIR] indicator-applet Status in indicator-applet package in Ubuntu: New Bug description: indicator-datetime recommends indicator-applet although indicator- applet is in universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1566502/+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 1493462] Re: Power notifications don't combine multiple batteries
** Tags added: rls-x-incoming wily xenial -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1493462 Title: Power notifications don't combine multiple batteries Status in indicator-power package in Ubuntu: Confirmed Bug description: Related to #880881: I have two batteries. One is empty, the other has 30 minutes left. I get notifications that battery status was "critically low" and that the computer will shut down soon. Instead, it should only show this notification if both batteries have a very low status. The notification icon already seems to combine them correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1493462/+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 1255500] Update Released
The verification of the Stable Release Update for unity-lens-music has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1255500 Title: banshee scope reports length in milliseconds for previews Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-music source package in Trusty: Fix Released Bug description: The banshee scope reports length in milliseconds, so the preview is pretty confused. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-lens-music 6.9.0+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 27 12:28:41 2013 SourcePackage: unity-lens-music UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/1255500/+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 1338820] Update Released
The verification of the Stable Release Update for unity-lens-music has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1338820 Title: Preview icon is pointing to the wrong location Status in Music Lens: Fix Committed Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-music source package in Trusty: Fix Released Bug description: The unity "album_missing.png" icon has been moved to a different location, so we get this error and a missing image: WARN 2014-07-08 00:44:29 unity.iconloader IconLoader.cpp:755 Unable to load icon file:///usr/share/unity/6/album_missing.png at size 96x96: Error opening file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-music/+bug/1338820/+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 1338820] Re: Preview icon is pointing to the wrong location
Hello Marco, or anyone else affected, Accepted unity-lens-music into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity-lens- music/6.9.0+14.04.20151120.2-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity-lens-music (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1338820 Title: Preview icon is pointing to the wrong location Status in Music Lens: Fix Committed Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-music source package in Trusty: Fix Committed Bug description: The unity "album_missing.png" icon has been moved to a different location, so we get this error and a missing image: WARN 2014-07-08 00:44:29 unity.iconloader IconLoader.cpp:755 Unable to load icon file:///usr/share/unity/6/album_missing.png at size 96x96: Error opening file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-music/+bug/1338820/+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 1255500] Re: banshee scope reports length in milliseconds for previews
Hello Michał, or anyone else affected, Accepted unity-lens-music into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity-lens- music/6.9.0+14.04.20151120.2-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: unity-lens-music (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: unity-lens-music (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1255500 Title: banshee scope reports length in milliseconds for previews Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-music source package in Trusty: Fix Committed Bug description: The banshee scope reports length in milliseconds, so the preview is pretty confused. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-lens-music 6.9.0+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 27 12:28:41 2013 SourcePackage: unity-lens-music UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/1255500/+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 1427167] Re: zeitgeist-datahub crashed with SIGSEGV in rate_limiter_free()
*** This bug is a duplicate of bug 1433551 *** https://bugs.launchpad.net/bugs/1433551 ** This bug has been marked a duplicate of bug 1433551 zeitgeist-datahub crashed with SIGSEGV in rate_limiter_free() -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1427167 Title: zeitgeist-datahub crashed with SIGSEGV in rate_limiter_free() Status in zeitgeist package in Ubuntu: New Bug description: none ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: zeitgeist-datahub 0.9.14-2.2ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 2 09:13:36 2015 ExecutablePath: /usr/bin/zeitgeist-datahub InstallationDate: Installed on 2014-10-24 (128 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: zeitgeist-datahub ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_UY:es PATH=(custom, no user) LANG=es_UY.UTF-8 SegvAnalysis: Segfault happened at: 0x7fbdcc8ce054:mov(%rdi),%rdi PC (0x7fbdcc8ce054) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: zeitgeist StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: zeitgeist-datahub crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to vivid on 2015-01-05 (55 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1427167/+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 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
** Also affects: compiz (Ubuntu Xenial) Importance: Critical Status: Confirmed ** Also affects: compiz-plugins-main (Ubuntu Xenial) Importance: Critical Status: Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Confirmed Status in Compiz Main Plugins: Fix Released Status in Compiz Desktop Wall Plugin: Fix Committed Status in OEM Priority Project trusty series: Fix Released Status in compiz package in Ubuntu: Confirmed Status in compiz-plugins-main package in Ubuntu: Fix Committed Status in compiz source package in Xenial: Confirmed Status in compiz-plugins-main source package in Xenial: Fix Committed Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+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 1433013] Re: Super -> exec vs Alt-F2 -> exec have different environment
** Tags removed: rls-w-incoming ** Tags added: rls-w-notfixing -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1433013 Title: Super -> exec vs Alt-F2 -> exec have different environment Status in Unity: Won't Fix Status in unity package in Ubuntu: Won't Fix Status in unity-lens-applications package in Ubuntu: Won't Fix Status in upstart package in Ubuntu: Confirmed Status in upstart source package in Trusty: Confirmed Status in upstart source package in Utopic: Confirmed Status in upstart source package in Vivid: Confirmed Bug description: upstart in user session manages environmental variables and most things have them, however Alt-f2 started proccesses lack them. to test Super Key -> "xterm" -> Enter -> env | grep SSH vs Alt+F2 -> "xterm" -> Enter -> env | grep SSH via Super Key -> the environment is correct via Alt-F2 -> it is not I believe Alt+F2 code path should call into upstart dbus api to "list-env" and import that environment before executing the search result. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1433013/+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 1430059] Re: LyX menu is not updated by indicator-appmenu in mode unity-all-menus
Hello apvieira, or anyone else affected, Accepted indicator-appmenu into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/indicator- appmenu/15.02.0+15.04.20150821-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: indicator-appmenu (Ubuntu Vivid) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1430059 Title: LyX menu is not updated by indicator-appmenu in mode unity-all-menus Status in indicator-appmenu package in Ubuntu: Fix Released Status in indicator-appmenu source package in Vivid: Fix Committed Bug description: SRU testcase: - Install lyx and run it - Create a new document - Open menus and ensure that those menus are not greyed out (disabled): * File menu: Close through Version control, plus Export and Print * Edit menu: all options * View menu: all but Messages pane, Toolbars and Fullscreen * Insert menu: all options * Navigate menu: all options * Document menu: all options * Tools menu: Spellchecker and Statistics Regression potential: fix has been in 15.10 for some months without any bug report that might be related to it, however a regression could cause menus for app not to be visible. Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 lyx: Installed: 2.1.3-1 Candidate: 2.1.3-1 Version table: *** 2.1.3-1 0 500 http://br.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: BugDistroRelease: Ubuntu 15.04 Package: lyx 2.1.3-1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 9 19:45:01 2015 ExecutablePath: /usr/bin/lyx InstallationDate: Installed on 2015-02-03 (33 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)SourcePackage: lyx UpgradeStatus: Upgraded to vivid on 2015-03-05 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1430059/+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 1466029] Re: Ubuntu Phone (Touch) won't turn off automatically after upgrade to OS 23
** Package changed: ubuntu = unity (Ubuntu) -- 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/1466029 Title: Ubuntu Phone (Touch) won't turn off automatically after upgrade to OS 23 Status in unity package in Ubuntu: New Bug description: After updating my Aquaris 4.5 to OS 23 (Build Ubuntu 15.04 armhf), the screen won't auto lock. It's forever turned on, the phone is heating and the battery, draining. However, if I manually press the power bottom, the screen turns off and locks. But, if inside my pocket the power bottom is pressed, the screen (locked, this time) will turn on again and won't turn off automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1466029/+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 1459121] Re: phone unlock screen
** Package changed: ubuntu = unity (Ubuntu) ** Tags added: vivid -- 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/1459121 Title: phone unlock screen Status in unity package in Ubuntu: New Bug description: ubuntu 15.04 for phones beta r.223 (bq aquaris ubuntu edition) Since r.222 upgrade i noticed that sometimes I cant unlock the phone. When i push unlock button (one time) looks like nothing happens, screen doesn't woke up. If i press a second time screen woke up for half second showing unlock screen. When it happens, i know that the OS is running because when i push the unlock button(first time), i can make a screen shot pushing up volume and down volume at same time it also reproduce the sound. Looks that the only problem is to wakeup the screen. It began to happen without install any program, just upgrades. When it happened to me I think that I haven't opened any app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1459121/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
Hello Francesco, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Users of the on-screen keyboard cannot properly use the Dash and the on-screen keyboard at the same time. [ Test Case ] 1. Install and start the on-screen keyboard Onboard. 2. Open the Dash. 3. Ensure you can interact with Onboard as you would expect. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+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 1246891] Re: Going back from quicklist to launcher in key-nav mode doesn't unfold the launcher
Hello Marco, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1246891 Title: Going back from quicklist to launcher in key-nav mode doesn't unfold the launcher Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Users the use Launcher keynav mode may end up with a Launcher that is not displayed correctly, leaving a poor user experience. [ Test Case ] 1. Make sure there are enough icons in the Launcher to cause the Launcher to fold. 2. Press Alt+F1 3. Press right-key 4. Press left-key 5. Observe the Launcher is not folder while still in keynav mode. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: 1) Press Alt+F1 2) Press right-key 3) Press left-key Expected result: 3) The launcher goes back to keynav mode and unfolds completely. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1246891/+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 1313597] Re: Shortcut overlay cannot be closed by clicking the close button in 14.04
Hello Po-Hsu, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/1313597 Title: Shortcut overlay cannot be closed by clicking the close button in 14.04 Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Due to an input handling race, the first time users log into Unity on their system, the shortcut overlay may not close when clicking the X in the corner. This leads to a poor user experience. [ Test Case ] 1. Remove ~/.config/unity/first_run.stamp. 2. Log into Unity. 3. Shortcut hints overlay should be shown. 4. Click on X in the corner. [ Regression Potential ] This is a workaround for a race, so some users may never see the race to begin with. That said, no regression should be observed as in worse case, the shortcut hints still cannot be closed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff --- Original Description: In 14.04, the shortcut overlay would pop-out automatically on first boot. Although there is a close button on the top-left corner, it cannot be closed by clicking it. (it could be dismissed by the super key, or open a new window) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313597/+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 1443178] Update Released
The verification of the Stable Release Update for accountsservice has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
Fix Released
Status in accountsservice source package in Trusty:
Fix Committed
Status in accountsservice source package in Vivid:
Fix Released
Bug description:
trusty and vivid SRU requests
=
[Impact]
Until a user has set the language or regional formats explicitly,
accountsservice makes the system default values available. The code
for 'calculating' the system defaults is expensive, and it's triggered
frequently. The case in the original description of this bug report is
one example of bad performance for this reason. Another example is a
system with many users (see e.g. bug #1350393).
This upload adds a couple of static variables inside the function in
question, to avoid that the expensive code is executed at each
invocation. Under certain conditions this improves the performance
significantly.
[Test Case]
Hmm.. There is no easy use case to reproduce the bug. The original
description below gives a hint.
[Regression Potential]
On a multi-user system, if the system defaults in /etc/default/locale
are changed, accountsservice will keep providing the old system
default values until the system is rebooted. (Previously it took
effect instantly.) I think the advantages with the proposed change
outweigh this subtle change in behavior (which hardly anyone will
notice anyway).
Can't think of anything besides that.
[Original description]
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/user, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user-language)
g_value_set_string (value, user-language);
else
g_value_set_string (value, user_get_fallback_value
(user, Language));
break;
case PROP_FORMATS_LOCALE:
if (user-formats_locale)
g_value_set_string (value, user-formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, FormatsLocale));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/user, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while
for accountsservice to reply back to indicator-sound when the sync
happens, possibly causing sync aborts (as indicator-sound only waits 1
second before
[Dx-packages] [Bug 886478] Re: New Alt + tab switcher doesn't follow system font
Hello Lê, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/886478 Title: New Alt + tab switcher doesn't follow system font Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Users who switch the system font and then use Alt+Tab will see a jarring effect when the Ubuntu font is displayed. This can also lead to not fully supported language issues. [ Test Case ] 1. Switch the system font to something else besides Ubuntu. 2. Use Alt+Tab. 3. Observe any fonts displayed in Alt+Tab follow the system font. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff -- Original Description: In my laptop, I have to change from default ubuntu font to droid font because the default one doesn't fully support vietnamese. Let it sit there will make the overall system feel awkward. And now, while the whole system is in droid, only the switcher is still using the ubuntu font. Plz make the switcher follow the system font or at least, make a way to configure its appearance. -- Desired solution: - Alt+tab switcher should use the system font - This change should result in ZERO change to the appearance of the font in Alt+Tab on a fresh installation of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/886478/+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 932486] Re: showing quicklist from launcher keynav mode focuses last application
Hello Thomi, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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/932486 Title: showing quicklist from launcher keynav mode focuses last application Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Poor user experience due to the app window not being focused as expected. [ Test Case ] 0. Have at least one application window open 1. Enter launcher keynav mode with Alt+F1 2. Select a launcher icon with the Up or Down keys. 3. Show the quicklist by pressing Right. 4. Collapse the quicklist by pressing Left. 5. Observe that the app window never has focus during the above steps. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff Original Description: To reproduce: 0) Have at least one application window open 1) Enter launcher keynav mode with Alt+F1 * Note that when entering keynav mode, the application loses focus. THe triangle to the right of it's launcher icon is no longer drawn, and the window title is not displayed in the panel. 2) Select a launcher icon with the Up or Down keys. 3) Show the quicklist by pressing Right. * Note that the application becomes active again - it's window title is drawn to the panel, and the triangle to the right of the launcher icon is drawn again. 4) Collapse the quicklist by pressing Left. * The app loses focus again. This seems like inconsistent behavior to me... either the app should never lose focus when we enter keynav mode, or should not be activated when we show a quicklist. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/932486/+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 1433013] Re: Super - exec vs Alt-F2 - exec have different environment
** Changed in: upstart (Ubuntu) Importance: Undecided = Medium ** Changed in: unity-lens-applications (Ubuntu) Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium -- 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/1433013 Title: Super - exec vs Alt-F2 - exec have different environment Status in Unity: New Status in unity package in Ubuntu: New Status in unity-lens-applications package in Ubuntu: New Status in upstart package in Ubuntu: New Status in unity source package in Trusty: New Status in unity-lens-applications source package in Trusty: New Status in upstart source package in Trusty: New Status in unity source package in Utopic: New Status in unity-lens-applications source package in Utopic: New Status in upstart source package in Utopic: New Status in unity source package in Vivid: New Status in unity-lens-applications source package in Vivid: New Status in upstart source package in Vivid: New Bug description: upstart in user session manages environmental variables and most things have them, however Alt-f2 started proccesses lack them. to test Super Key - xterm - Enter - env | grep SSH vs Alt+F2 - xterm - Enter - env | grep SSH via Super Key - the environment is correct via Alt-F2 - it is not I believe Alt+F2 code path should call into upstart dbus api to list-env and import that environment before executing the search result. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1433013/+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 1449429] Re: terminal minimizes to 2x2 square
** Tags added: vivid ** Package changed: ubuntu = unity (Ubuntu) -- 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/1449429 Title: terminal minimizes to 2x2 square Status in unity package in Ubuntu: New Bug description: I upgraded to 15.04 just recently, but when opening the 'Terminal' (gnome-terminal), it immediately minimized to the upper left corner of the screen. Dragging the edges of it would only work occasionally and limited the size of the terminal to about 32 characters wide x 4 characters long before jumping back to a 2x2 character size square. Please let me know with other information you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1449429/+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 1363630] Update Released
The verification of the Stable Release Update for indicator-session has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363630 Title: Since revision 446.1.3, Zenity backend is broken Status in Ubuntu GNOME Flashback: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Released Bug description: Currently the code in zenity_question() looks like: if (!g_spawn_check_exit_status (exit_status, error)) confirmed = TRUE; else confirmed = exit_status == 0; However !g_spawn_check_exit_status() call is mostly equivalent to exit_status != 0. Thus, confirmed will be *always* set to TRUE, even if the user cancelled the dialog. I have prepared a branch to fix this. == Impact == The Cancel buttons in shutdown/end session dialogs are not working, and do the same as OK buttons. This may lead to data loss due to unsaved documents/etc. == Test Case == * Log in to GNOME Flashback session. * Select Shutdown from indicator-session menu. * In the popped up dialog select Cancel. Expected result: the dialog will close, the machine won't shut down. == Development / Stable Fix == Please see the attached branches. == Regression Potential == The fix is part of 14.10 release and was confirmed to work fine. So no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1363630/+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 778054] Re: Packages shouldn't depend on the transitional package python-gobject
** Changed in: zeitgeist (Ubuntu) Importance: Undecided = Low ** Changed in: zeitgeist (Ubuntu) Status: Confirmed = In Progress ** Changed in: zeitgeist (Ubuntu) Assignee: (unassigned) = Brian Murray (brian-murray) ** Changed in: zeitgeist (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: zeitgeist (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: zeitgeist (Ubuntu Trusty) Assignee: (unassigned) = Brian Murray (brian-murray) -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/778054 Title: Packages shouldn't depend on the transitional package python-gobject Status in aptdaemon package in Ubuntu: Fix Released Status in desktopcouch package in Ubuntu: Invalid Status in eglibc package in Ubuntu: Invalid Status in gnome-utils package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Fix Released Status in openoffice.org package in Ubuntu: Won't Fix Status in system-config-printer package in Ubuntu: Fix Released Status in wine1.4 package in Ubuntu: Fix Released Status in zeitgeist package in Ubuntu: In Progress Status in aptdaemon source package in Trusty: Fix Released Status in desktopcouch source package in Trusty: Invalid Status in eglibc source package in Trusty: Invalid Status in gnome-utils source package in Trusty: Invalid Status in libreoffice source package in Trusty: Fix Released Status in openoffice.org source package in Trusty: Invalid Status in system-config-printer source package in Trusty: Fix Released Status in wine1.4 source package in Trusty: Invalid Status in zeitgeist source package in Trusty: In Progress Bug description: [Impact] python-zeitgeist depends on python-gobject, which means python-gobject cannot be removed from the system. python-gobject is a transitional package, and packages should be updated to no longer depend on it. [Test Case] * Install python-zeitgeist, and verify that python-gobject is not installed with it. * If it is already installed, you should be able to run 'apt-get purge python-gobject' without removing python-zeitgeist. [Regression Potential] Negligible. There are no code changes. The fix only removes a dependency on a transitional package that doesn't provide any files. --- [Impact] system-config-printer-gnome depends on python-gobject, which means python-gobject cannot be removed from the system. python-gobject is a transitional package, and packages should be updated to no longer depend on it. [Test Case] * Install system-config-printer-gnome, and verify that python-gobject is not installed with it. * If it is already installed, you should be able to run 'apt-get purge python-gobject' without removing system-config-printer-gnome. [Regression Potential] Negligible. There are no code changes. The fix only removes a dependency on a transitional package that doesn't provide any files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/778054/+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 1423752] Re: Sound Settings not opening from indicator
The regression-proposed tag is only for regressions from the -proposed pocket of a Stable Release, which vivid is not. ** Tags removed: regression-proposed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1423752 Title: Sound Settings not opening from indicator Status in indicator-sound package in Ubuntu: Invalid Bug description: Saw an update for indicator-sound just now . indicator-sound (12.10.2+15.04.20150205-0ubuntu1) vivid; urgency=medium Double checked that indicator-sound worked correctly. Updated and rebooted. Sound Settings no longer starts from indicator. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 19 23:39:35 2015 InstallationDate: Installed on 2015-01-09 (41 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1423752/+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 1198653] Re: It is not possible to drag drop and pin icon to launch bar when auto-hiding is turned on
** Tags removed: patch -- 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/1198653 Title: It is not possible to drag drop and pin icon to launch bar when auto-hiding is turned on Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: When you have auto-hiding of launch bar turned on, you can not drag an application from search, because when you just put mouse with icon over the bar, it hides all the time and if you want to add it though, you have to disable auto-hiding first. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Jul 7 13:23:45 2013 InstallationDate: Installed on 2013-06-20 (16 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1198653/+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 1415544] Re: New Workspace shows application icons highlighted what is opened in another Workspace
** Package changed: ubuntu = unity (Ubuntu) -- 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/1415544 Title: New Workspace shows application icons highlighted what is opened in another Workspace Status in unity package in Ubuntu: New Bug description: Suppose I have some opened applications in one workspace. Now I have switched to another workspace. The problem is, I can see the opened application icons of the previous workspace in this workspace. And I don't want that. Applications opened in another workspace shouldn't be visible in other workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1415544/+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 1307657] Update Released
The verification of the Stable Release Update for unity-gtk-module has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1307657 Title: [SRU] UBUNTU_MENUPROXY should not be set in Xfce Status in unity-gtk-module package in Ubuntu: Fix Released Status in xfce4-indicator-plugin package in Ubuntu: Invalid Status in unity-gtk-module source package in Trusty: Fix Released Status in xfce4-indicator-plugin source package in Trusty: Invalid Status in unity-gtk-module source package in Utopic: Fix Released Status in xfce4-indicator-plugin source package in Utopic: Invalid Bug description: [Impact] The upstart script for unity-gtk-module causes it to run under all desktop environments indiscriminately when it should only be running under Unity. It does this by adding unity-gtk-module to the environment variable GTK_MODULES. In Xfce, this causes the panel to crash when trying to add Unity indicators, as well as other related side effects (see: LP: #1314782, LP: #1347272). The fix to ensure we only modify GTK_MODULES under Unity is already in 14.10. [Test Case] Log into a Xubuntu session on a machine that has both ubuntu-desktop and xubuntu-desktop. Add the Indicator Plugin to the panel and open a terminal window. A crash dialog should appear notifying the user that the Indicator Plugin unexpectedly left the panel. [Regression Potential] The potential for regression is low since the only change is to preserve the original value of the GTK_MODULES environment variable, as well as to never set UBUNTU_MENUPROXY. The fix restores the desktop environment to its intended state of not running unity-gtk-module. Also, I've tested the change under Unity, and application menus still work properly under the global menu without regression. [Other Info] N/A === original bug report === To reproduce: either start with a fresh Ubuntu install and then install xubuntu-desktop, or start with Xubuntu and then install ubuntu-desktop - ie have both Xfce and Unity installed on the same machine. Xfce now has support for gtk3 indicators launched by upstart, but indicator-appmenu is totally broken - it will constantly crash the panel and applications. Xfce has a mechanism to hide indicators, and then the frontend UI will not be loaded in the panel, but it seems that UBUNTU_MENUPROXY is still being set in Xfce, which causes menus to disappear from applications, even though nothing is available to receive them. I discussed this with tedg and he suggested that the problem may be to do with the upstart service which sets UBUNTU_MENUPROXY, ie /usr/share/upstart/sessions/unity-gtk-module.conf We may in future get the appmenus working in Xfce, and then we would need some way to turn the menuproxy on and off depending on the user configuration. But for now, since they are broken anyway, it would be easiest to simply blacklist xubuntu desktop completely. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-gtk-module-common 0.0.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 14 19:40:36 2014 InstallationDate: Installed on 2014-02-11 (61 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140210) PackageArchitecture: all SourcePackage: unity-gtk-module UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1307657/+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 1363959] Update Released
The verification of the Stable Release Update for nux has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1363959 Title: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle() Status in Nux: Fix Committed Status in Nux trusty series: In Progress Status in nux package in Ubuntu: Fix Released Status in nux source package in Trusty: Fix Released Bug description: [Impact] An occasional unpredictable crash in the Unity shell occurs during a drag-and-drop operation. [Test Case] Unfortunately it is not possible to reproduce this bug at will. Apparently is is caused by an uninitialized pointer dereference that only occurs in a timing-dependent manner. Running a full autopilot test suite against the Unity desktop shell reveals no new regressions. [Regression Potential] The code change effectively adds a test for a null pointer. It is possible that this might introduce a regression in drag-and-drop functionality that previously relied on undefined behaviour to work when it didn't crash. [Other Info] Fix was released with Ubuntu 14.10 and no new regressions have been reported. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1363959/+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 1379031] Re: Screen doesn't lock anymore
** Package changed: ubuntu-meta (Ubuntu) = unity (Ubuntu) -- 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/1379031 Title: Screen doesn't lock anymore Status in “unity” package in Ubuntu: New Bug description: The automatic screen locking doesn't work anymore in utopic. I can reproduce this on two different machines. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-desktop 1.327 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 8 16:56:44 2014 InstallationDate: Installed on 2014-07-25 (75 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: ubuntu-meta SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to utopic on 2014-09-04 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1379031/+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 1374301] Re: osd notifications blurry
** Tags added: trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374301 Title: osd notifications blurry Status in “notify-osd” package in Ubuntu: New Bug description: Recently clean installed Ubuntu 14.04.1 Trusty Tahr. With hidpi scale set to 2, and text scale set to .75, all on screen notifications have been blurry to the point of being unreadable. Any ideas on what could cause this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1374301/+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 1335000] Re: Launcher regression super + shift + number doesn't work properly
** Tags added: trusty ** Package changed: ubuntu = unity (Ubuntu) -- 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/1335000 Title: Launcher regression super + shift + number doesn't work properly Status in “unity” package in Ubuntu: Confirmed Bug description: Looks like it correspondig to this issue: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/754565 Steps to reproduce: Pin some application on launcher panel in position 1 (it must be accesible by super+1 Press super + shift + 1 - no any visible changes will be occuried Expected behaviour: New instance of application must be started, just simmilar with shift + mouse1 on application icon. Reproduced since 14.04, was tested in 12.04, 13.04, 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1335000/+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 1298656] Update Released
The verification of the Stable Release Update for hud has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1298656 Title: hud-service crashed with g-assert-if-reached in GMenu call from qtgmenu::QtGMenuModel::CreateChild() Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Trusty: Fix Released Bug description: [Impact] * Unknown GTK application causes HUD service to crash by sending invalid menu updates via GMenu. [Test Case] * Not reproducable so far. [Regression Potential] * Worst case is that somehow HUD doesn't work on the desktop and phone. * There are, obviously, extensive unit and functional tests to verify this doesn't happen. [Other Info] * The patch will report the offending application to errors.ubuntu.com with all available debugging information. * The indexes are now range checked before processing. As soon as a window sends any invalid message it is blocked. * Further hardening around the memory management in QtGMenu has been carried out. * The change is not as large as it at first appears. The majority of the diff is simply replacing Type* with QSharedPointerType. The rest is the extra code for reporting the recoverable problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1298656/+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 1326931] Re: Unity doesn't work on Haswell GPU after recent update
** Package changed: ubuntu = unity (Ubuntu) ** Tags added: regression-update -- 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/1326931 Title: Unity doesn't work on Haswell GPU after recent update Status in “unity” package in Ubuntu: New Bug description: Unity doesn't launch(no panels) on Intel Haswell GPU after recent update, similar issue reported on http://askubuntu.com/questions/475683/unity-not-working-14-04 Looks like issue related to libgl1-mesa-dri Currently installed gnome which is not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1326931/+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 1298656] Re: hud-service crashed with g-assert-if-reached in GMenu call from qtgmenu::QtGMenuModel::CreateChild()
The new package version which should fix this bug seems to have included a typo in the version number. diff -Nru hud-13.10.1+14.04.20140425/debian/changelog hud-14.04+14.04.20140604/debian/changelog --- hud-13.10.1+14.04.20140425/debian/changelog 2014-06-05 16:24:32.0 -0700 +++ hud-14.04+14.04.20140604/debian/changelog 2014-06-05 16:24:32.0 -0700 @@ -1,3 +1,14 @@ +hud (14.04+14.04.20140604-0ubuntu1) trusty; urgency=medium Notice how the package version number starts off with 14.04 instead of 13.10. Was this intended? If so then the version number for Trusty will be greater than the one for Utopic. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1298656 Title: hud-service crashed with g-assert-if-reached in GMenu call from qtgmenu::QtGMenuModel::CreateChild() Status in “hud” package in Ubuntu: In Progress Status in “hud” source package in Trusty: In Progress Bug description: [Impact] * Unknown GTK application causes HUD service to crash by sending invalid menu updates via GMenu. [Test Case] * Not reproducable so far. [Regression Potential] * Worst case is that somehow HUD doesn't work on the desktop and phone. * There are, obviously, extensive unit and functional tests to verify this doesn't happen. [Other Info] * The patch will report the offending application to errors.ubuntu.com with all available debugging information. * The indexes are now range checked before processing. As soon as a window sends any invalid message it is blocked. * Further hardening around the memory management in QtGMenu has been carried out. * The change is not as large as it at first appears. The majority of the diff is simply replacing Type* with QSharedPointerType. The rest is the extra code for reporting the recoverable problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1298656/+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 1312749] Please test proposed package
Hello Jonas, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity/7.2.1+14.04.20140513-0ubuntu2 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1312749 Title: German translation: password wrong text is too long and destroys layout Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: When I try to log in with a wrong password, the string which informs me about the wrong password is too long (I will attach a screenshot) it makes the password box enlarge, which makes the right end of it (with the circle, that is spinning while logging in) disappear. [Test Case] (1) Log in to Unity (2) Set the local to German (Use the Language Support panel in System Settings) (3) Bring up the lockscren (eg. using control-alt-L) (4) Attempt to unlock but enter an incorrect password [Regression Potential] Rendering error message text in the password dialog has been modified. It is possible the text may break incorrectly or the box may be incorrectly sized. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1312749/+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 1317276] Please test proposed package
Hello Stephen, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity/7.2.1+14.04.20140513-0ubuntu2 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1317276 Title: Unity 7 GCC ICE on ARM64 Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “gcc-4.8” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Fix Released Bug description: Unity 7 failed to build from source on ARM64 on Utopic due to an internal compiler error in GCC. Build log excerpt as follows. [ 15%] Building CXX object UnityCore/CMakeFiles/unity-core-6.0.dir/Category.cpp.o cd /build/buildd/unity-7.2.0+14.10.20140507/obj-aarch64-linux-gnu/UnityCore /usr/bin/aarch64-linux-gnu-g++ -DUSE_X11 -Dunity_core_6_0_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -O2 -D_FORTIFY_SOURCE=2 -DGNOME_DESKTOP_USE_UNSTABLE_API -std=c++0x -fno-permissive -Werror -Wall -Wcast-align -Wempty-body -Wformat-security -Winit-self -Warray-bounds -Wno-error=unused-local-typedefs -fPIC -I/usr/include/gmock/include -I/usr/src/gmock/gtest/include -I/usr/include/Nux-4.0 -I/usr/include/sigc++-2.0 -I/usr/lib/aarch64-linux-gnu/sigc++-2.0/include -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/build/buildd/unity-7.2.0+14.10.20140507/obj-aarch64-linux-gnu -I/build/buildd/unity-7.2.0+14.10.20140507/obj-aarch64-linux-gnu/UnityCore -include unitycore_pch.hh -fpch-preprocess -Winvalid-pch -o CMakeFiles/unity-core-6.0.dir/Category.cpp.o -c /build/buildd/unity-7.2.0+14.10.20140507/UnityCore/Category.cpp aarch64-linux-gnu-g++: internal compiler error: Segmentation fault (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions. UnityCore/CMakeFiles/unity-core-6.0.dir/build.make:126: recipe for target 'UnityCore/CMakeFiles/unity-core-6.0.dir/Category.cpp.o' failed make[3]: *** [UnityCore/CMakeFiles/unity-core-6.0.dir/Category.cpp.o] Error 4 More information at https://launchpad.net/~ci-train-ppa-service/+archive/landing-008/+build/5987360 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317276/+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
