[Dx-packages] [Bug 2060080] Re: 23.13.9-2ubuntu5 is FTBFS on armhf
So something changed to add -Werror=implicit-function-declaration at build time (gcc didn't change so maybe dpkg?), which should have caused the other arches to fail as well but since they ran at different times they pulled different versions of build dependencies. This will likely get fixed on a rebuild and these are getting queued en masse, so I'm marking as invalid unless we have a reason to track this later. ** Changed in: accountsservice (Ubuntu) Status: In Progress => 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/2060080 Title: 23.13.9-2ubuntu5 is FTBFS on armhf Status in accountsservice package in Ubuntu: Invalid Bug description: The armhf build fails with the following build error: ../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function ‘netgroup_debug_print_entry’: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] 25 | print_indent(stream, indent); | ^~~~ cc1: some warnings being treated as errors See the logs here: https://launchpadlibrarian.net/722843641/buildlog_ubuntu-noble- armhf.accountsservice_23.13.9-2ubuntu5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2060080/+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 2060080] [NEW] 23.13.9-2ubuntu5 is FTBFS on armhf
Public bug reported: The armhf build fails with the following build error: ../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function ‘netgroup_debug_print_entry’: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] 25 | print_indent(stream, indent); | ^~~~ cc1: some warnings being treated as errors See the logs here: https://launchpadlibrarian.net/722843641/buildlog_ubuntu-noble- armhf.accountsservice_23.13.9-2ubuntu5_BUILDING.txt.gz ** Affects: accountsservice (Ubuntu) Importance: Undecided Assignee: Chris Peterson (cpete) Status: In Progress ** Changed in: accountsservice (Ubuntu) Status: New => In Progress -- 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/2060080 Title: 23.13.9-2ubuntu5 is FTBFS on armhf Status in accountsservice package in Ubuntu: In Progress Bug description: The armhf build fails with the following build error: ../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function ‘netgroup_debug_print_entry’: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] 25 | print_indent(stream, indent); | ^~~~ cc1: some warnings being treated as errors See the logs here: https://launchpadlibrarian.net/722843641/buildlog_ubuntu-noble- armhf.accountsservice_23.13.9-2ubuntu5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2060080/+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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
I was finally able to get the browser approach to work (advice: there is a little slider at the very top of the gnome-extensions-app GUI that you have to click to get the extensions to activate, or else you begin to lose your mind thinking that you have to install it manually from source because clicking on the slider next to Appindicator and KStatusNotifierItem wasn't doing anything when I clicked it). I find that the CPU usage has improved. When I am running indicator- multiload in the top right corner (i.e. in the gnome status bar) I find that gnome-terminal takes up 7% of one of my cpu cores (and this drops to less than a percent when I turn off indicator-multiload). Earlier on 2022-03-01 I wrote that gnome-terminal was taking up 30% when I was running indicator-multiload (and of course it dropped to zero when I killed indicator-multiload) So fixed version 53 is definitely an improvement (thanks!). I am not sure if the bug can be declared to be squashed but this is much better than it was. Again I am using Ubuntu 20.04 which uses Gnome 3.36.8 by default. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 2015962] Proposed package upload rejected
An upload of ayatana-indicator-messages to lunar-proposed has been rejected from the upload queue for the following reason: "Rejecting from the queue as this is still missing SRU information, and that should notify someone who cares :). The diff itself looks fine, although the it now also needs fixing in mantic and the lunar upload needs a non- conflicting version number. Please feel free to reupload with those fixed.". -- 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: Incomplete Status in indicator-messages package in Ubuntu: Fix Released 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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
Do I need to checkout and compile from source or can I use the browser extension (i.e. gnome extension) to use the newer version? -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
I am typically using Gnome3 with ubuntu 20.04 (standard ubuntu). -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
Confirming that this is an issue even with the Dell customized ubuntu 20.04 version for the Dell XPS 13 laptop. I find about 30% cpu useage for gnome-shell when multiload-indicator is running. I also find that high framerate, high res youtube videos stutter when multiload-indicator is running but they run much smoother when multiload-indicator is closed. I am using an intel evo i7 processor and intel Xe graphics card. I am still struggling to understand if there is an update to fix this. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 1897434] Re: HUD Service Crash on boot
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1897434 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/1897434 Title: HUD Service Crash on boot Status in hud package in Ubuntu: New Bug description: Sep 27 07:10:45 btestserver rsyslogd: [origin software="rsyslogd" swVersion="8.32.0" x-pid="885" x-info="http://www.rsyslog.com;] rsyslogd was HUPed Sep 27 07:12:30 btestserver anacron[896]: Job `cron.daily' terminated Sep 27 07:12:30 btestserver anacron[896]: Normal exit (1 job run) Sep 27 07:14:02 btestserver kernel: [ 540.025328] perf: interrupt took too long (3956 > 3930), lowering kernel.perf_event_max_sample_rate to 50500 Sep 27 07:14:04 btestserver rtkit-daemon[1519]: Supervising 5 threads of 2 processes of 1 users. Sep 27 07:14:19 btestserver rtkit-daemon[1519]: message repeated 3 times: [ Supervising 5 threads of 2 processes of 1 users.] Sep 27 07:17:01 btestserver CRON[4630]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Sep 27 07:17:37 btestserver whoopsie[1396]: [07:17:37] Parsing /var/crash/_usr_lib_i386-linux-gnu_hud_hud-service.1000.crash. Sep 27 07:17:37 btestserver systemd[2486]: Starting Notification regarding a crash report... Sep 27 07:17:37 btestserver whoopsie[1396]: [07:17:37] Uploading /var/crash/_usr_lib_i386-linux-gnu_hud_hud-service.1000.crash. Sep 27 07:17:37 btestserver unity-panel-ser[3223]: window_menu_model_new: assertion 'BAMF_IS_APPLICATION(app)' failed Sep 27 07:17:37 btestserver unity-panel-ser[3223]: track_menus: assertion 'IS_WINDOW_MENU(menus)' failed Sep 27 07:17:38 btestserver systemd[2486]: Started Notification regarding a crash report. Sep 27 07:17:38 btestserver zeitgeist-daemon[3265]: #033[31m[05:17:38.849901 WARNING]#033[0m zeitgeist-daemon.vala:127: Unable to parse version info! Sep 27 07:17:39 btestserver whoopsie[1396]: [07:17:39] Sent; server replied with: No error Sep 27 07:17:39 btestserver whoopsie[1396]: [07:17:39] Response code: 200 Sep 27 07:17:39 btestserver whoopsie[1396]: [07:17:39] Reported OOPS ID c2ab1e24-0080-11eb-b355-fa163e6cac46 Sep 27 07:17:43 btestserver whoopsie[1396]: [07:17:43] Sent; server replied with: No error Sep 27 07:17:43 btestserver whoopsie[1396]: [07:17:43] Response code: 200 Sep 27 07:17:43 btestserver systemd[2486]: Starting Notification regarding a crash report... Sep 27 07:17:44 btestserver systemd[2486]: Started Notification regarding a crash report. Sep 27 07:20:08 btestserver systemd[1]: Starting Cleanup of Temporary Directories... Sep 27 07:20:09 btestserver systemd[1]: Started Cleanup of Temporary Directories. Sep 27 07:24:59 btestserver kernel: [ 1197.155088] perf: interrupt took too long (4954 > 4945), lowering kernel.perf_event_max_sample_rate to 40250 Sep 27 07:27:47 btestserver dbus-daemon[918]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.146' (uid=1000 pid=3406 comm="/usr/lib/firefox/firefox " label="unconfined") Sep 27 07:27:47 btestserver systemd[1]: Starting Hostname Service... Sep 27 07:27:47 btestserver hud-service[3293]: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface 'com.canonical.dbusmenu' on object at path /org/ayatana/bamf/window/50331811" Sep 27 07:27:47 btestserver dbus-daemon[918]: [system] Successfully activated service 'org.freedesktop.hostname1' Sep 27 07:27:47 btestserver systemd[1]: Started Hostname Service. Sep 27 07:27:49 btestserver gvfsd[2821]: mkdir failed on directory /var/cache/samba: Permission denied Sep 27 07:27:54 btestserver gvfsd[2821]: message repeated 11 times: [ mkdir failed on directory /var/cache/samba: Permission denied] Sep 27 07:28:57 btestserver rtkit-daemon[1519]: Supervising 5 threads of 2 processes of 1 users. Sep 27 07:29:19 btestserver rtkit-daemon[1519]: message repeated 3 times: [ Supervising 5 threads of 2 processes of 1 users.] Sep 27 07:29:28 btestserver systemd-resolved[881]: Using degraded feature set (UDP) for DNS server 81.24.247.45. Sep 27 07:29:34 btestserver MainThread[3406]: dbusmenu_menuitem_property_set_shortcut: assertion 'gtk_accelerator_valid(key, modifier)' failed Sep 27 07:29:40 btestserver unity-panel-ser[3223]: window_menu_model_new: assertion 'BAMF_IS_APPLICATION(app)' failed Sep 27 07:29:40 btestserver unity-panel-ser[3223]: track_menus: assertion 'IS_WINDOW_MENU(menus)' failed Sep 27 07:29:49
[Dx-packages] [Bug 1773859] Re: upgrades to 18.04 fail
I got nipped by this bug today moving from 16.04LTS to 18.04 LTS -- 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 1295267] Re: Windows change Monitor/Desktop after screen lock
Affects me on a fresh install of 16.04. Two monitors with different port types. xrandr: Screen 0: minimum 8 x 8, current 5520 x 2160, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected 1680x1050+3840+555 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 59.88*+ 59.95 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm 3840x2160 29.98*+ 2048x1080 59.99 1920x1080 60.0059.9450.0060.0050.04 1680x1050 59.95 1440x900 74.9859.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 disconnected (normal left inverted right x axis y axis) -- 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/1295267 Title: Windows change Monitor/Desktop after screen lock Status in Unity: Fix Released Status in Unity 7.1 series: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in unity package in Ubuntu: Triaged Bug description: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description: Ubuntu 13.10 Release: 13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1600136] Update Released
The verification of the Stable Release Update for libappindicator 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 appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Fix Released Status in libappindicator source package in Xenial: Fix Released Status in qtbase-opensource-src source package in Xenial: New Status in snapd source package in Xenial: New Status in sni-qt source package in Xenial: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1606246] Update Released
The verification of the Stable Release Update for appmenu-qt5 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 appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1606246 Title: Hard-coded X11 calls cause Unity 8 to fail to run on desktop Status in appmenu-qt5: Fix Released Status in Mir: Triaged Status in appmenu-qt5 package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Fix Released Status in unity8-desktop-session source package in Xenial: New Bug description: The appmenu-qt5 code has hardcoded Xlib calls that cause Unity 8 (or any other Qt-based applicaiton) to die on startup when run on Mir instead of X11. This library extension should either not hardcode X11 (preferred) or check for the presence of a $DISPLAY environment variable and avoid code paths that assume X11. The Unity 8 desktop currently has a hard-coded check for $QT_QPA_PLATFORMTHEME and unsets it as a workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1606246/+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 1664230] Re: systemd-logind[]: Failed to stop user service: Unknown unit: user@.service
** Changed in: systemd-shim (Ubuntu) Status: New => Invalid -- 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/1664230 Title: systemd-logind[]: Failed to stop user service: Unknown unit: user@.service Status in systemd-shim package in Ubuntu: Invalid Bug description: pad.lv/1654241 reverted a change in dbus which now causes the following messages to appear when logging into a xenial/upstart system: login: [ 284.753970] systemd-logind[1493]: Failed to start user service, ignoring: Unknown unit: usere [ 637.682127] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@111.service [ 637.691262] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service [ 637.701000] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@1000.service [ 637.711167] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@111.service [ 637.722544] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service If the following patch is reverse-applied things work correctly again: https://launchpadlibrarian.net/302225938/dbus_1.10.6-1ubuntu3.2_1.10.6-1ubuntu3.3.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1664230/+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 1664230] [NEW] systemd-logind[]: Failed to stop user service: Unknown unit: user@.service
Public bug reported: pad.lv/1654241 reverted a change in dbus which now causes the following messages to appear when logging into a xenial/upstart system: login: [ 284.753970] systemd-logind[1493]: Failed to start user service, ignoring: Unknown unit: usere [ 637.682127] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@111.service [ 637.691262] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service [ 637.701000] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@1000.service [ 637.711167] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@111.service [ 637.722544] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service If the following patch is reverse-applied things work correctly again: https://launchpadlibrarian.net/302225938/dbus_1.10.6-1ubuntu3.2_1.10.6-1ubuntu3.3.diff.gz ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: Invalid -- 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/1664230 Title: systemd-logind[]: Failed to stop user service: Unknown unit: user@.service Status in systemd-shim package in Ubuntu: Invalid Bug description: pad.lv/1654241 reverted a change in dbus which now causes the following messages to appear when logging into a xenial/upstart system: login: [ 284.753970] systemd-logind[1493]: Failed to start user service, ignoring: Unknown unit: usere [ 637.682127] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@111.service [ 637.691262] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service [ 637.701000] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@1000.service [ 637.711167] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@111.service [ 637.722544] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service If the following patch is reverse-applied things work correctly again: https://launchpadlibrarian.net/302225938/dbus_1.10.6-1ubuntu3.2_1.10.6-1ubuntu3.3.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1664230/+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] Update Released
The verification of the Stable Release Update for appmenu-qt5 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 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 Released
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 1295267] Re: Windows change Monitor/Desktop after screen lock
$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 DP1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.00*+ 74.9950.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1400x1050 59.95 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1440x576 50.00 1024x768 75.0870.0760.00 1440x480 60.0059.94 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 720x240 60.1260.05 HDMI2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.00*+ 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1400x1050 59.95 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1440x576 50.00 1024x768 75.0870.0760.00 1440x480 60.0059.94 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 720x240 60.1260.05 VIRTUAL1 disconnected (normal left inverted right x axis y axis) -- 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/1295267 Title: Windows change Monitor/Desktop after screen lock Status in Unity: Fix Released Status in Unity 7.1 series: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in unity package in Ubuntu: Triaged Bug description: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description: Ubuntu 13.10 Release: 13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295267] Re: Windows change Monitor/Desktop after screen lock
Just throwing my log on the fire... Intel NUC with 2x24" ViewSonic monitors attached. One connected via mini-Display and one connected via HTMI. Ubuntu 16.04 fresh install. -- 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/1295267 Title: Windows change Monitor/Desktop after screen lock Status in Unity: Fix Released Status in Unity 7.1 series: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in unity package in Ubuntu: Triaged Bug description: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description: Ubuntu 13.10 Release: 13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1654406] Re: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
** Package changed: d-conf (Ubuntu) => tracker (Ubuntu) ** Package changed: tracker (Ubuntu) => dconf (Ubuntu) -- 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/1654406 Title: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Status in dconf package in Ubuntu: New Bug description: chris@localhost:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 chris@localhost:~$ apt-cache policy tracker-extract tracker-extract: Installed: 1.8.2-0ubuntu1~xenial3 Candidate: 1.8.2-0ubuntu1~xenial3 Version table: *** 1.8.2-0ubuntu1~xenial3 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages Jan 5 15:10:42 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Jan 5 15:12:25 localhost tracker-extract.desktop[3459]: message repeated 2 times: [ (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Jan 5 15:14:27 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. and so on every two minutes +- a few seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dconf/+bug/1654406/+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 1654406] [NEW] Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
Public bug reported: chris@localhost:~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 chris@localhost:~$ apt-cache policy tracker-extract tracker-extract: Installed: 1.8.2-0ubuntu1~xenial3 Candidate: 1.8.2-0ubuntu1~xenial3 Version table: *** 1.8.2-0ubuntu1~xenial3 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages Jan 5 15:10:42 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Jan 5 15:12:25 localhost tracker-extract.desktop[3459]: message repeated 2 times: [ (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Jan 5 15:14:27 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. and so on every two minutes +- a few seconds. ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New -- 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/1654406 Title: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Status in d-conf package in Ubuntu: New Bug description: chris@localhost:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 chris@localhost:~$ apt-cache policy tracker-extract tracker-extract: Installed: 1.8.2-0ubuntu1~xenial3 Candidate: 1.8.2-0ubuntu1~xenial3 Version table: *** 1.8.2-0ubuntu1~xenial3 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages Jan 5 15:10:42 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Jan 5 15:12:25 localhost tracker-extract.desktop[3459]: message repeated 2 times: [ (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.] Jan 5 15:14:27 localhost tracker-extract.desktop[3459]: (tracker- extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. and so on every two minutes +- a few seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1654406/+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] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04
Hello Pascal, 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.2 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: accountsservice (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 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 Committed 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 1350523] Update Released
The verification of the Stable Release Update for frame 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 frame in Ubuntu. https://bugs.launchpad.net/bugs/1350523 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. Status in frame: In Progress Status in compiz package in Ubuntu: Won't Fix Status in frame package in Ubuntu: Fix Released Status in compiz source package in Xenial: Invalid Status in frame source package in Xenial: Fix Released Bug description: [Impact] Unity might crash on systems with touch screen or multi-gesture supporting touchpads. [Test case] The crash is pretty random, it happens in some cases where unity is locked and after a suspension. Without having to touch any input. [Regression Potential] Regression potential: fix is very safe. We're just removing asserts in code, returning safe values and printing errors instead. Not sure if the cause is running autopilot tests. ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AssertionMessage: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 30 21:46:07 2014 DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2014-02-13 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) MachineType: System manufacturer System Product Name ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7 Signal: 6SourcePackage: compiz StacktraceTop: __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92 __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101 frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1
[Dx-packages] [Bug 1350523] Re: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.
Hello Carla, or anyone else affected, Accepted frame into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/frame/2.5.0daily13.06.05+16.04.20160809-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: frame (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 frame in Ubuntu. https://bugs.launchpad.net/bugs/1350523 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. Status in frame: In Progress Status in compiz package in Ubuntu: Won't Fix Status in frame package in Ubuntu: Fix Released Status in compiz source package in Xenial: Invalid Status in frame source package in Xenial: Fix Committed Bug description: [Impact] Unity might crash on systems with touch screen or multi-gesture supporting touchpads. [Test case] The crash is pretty random, it happens in some cases where unity is locked and after a suspension. Without having to touch any input. [Regression Potential] Regression potential: fix is very safe. We're just removing asserts in code, returning safe values and printing errors instead. Not sure if the cause is running autopilot tests. ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AssertionMessage: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 30 21:46:07 2014 DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2014-02-13 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) MachineType: System manufacturer System Product Name ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7 Signal: 6SourcePackage: compiz StacktraceTop: __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92 __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101 frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N
[Dx-packages] [Bug 1350523] Re: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.
** Also affects: frame (Ubuntu) Importance: Undecided Status: New ** Also affects: compiz (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: frame (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: compiz (Ubuntu Xenial) Status: New => Invalid ** Changed in: frame (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to frame in Ubuntu. https://bugs.launchpad.net/bugs/1350523 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. Status in frame: In Progress Status in compiz package in Ubuntu: Won't Fix Status in frame package in Ubuntu: Fix Released Status in compiz source package in Xenial: Invalid Status in frame source package in Xenial: New Bug description: [Impact] Unity might crash on systems with touch screen or multi-gesture supporting touchpads. [Test case] The crash is pretty random, it happens in some cases where unity is locked and after a suspension. Without having to touch any input. [Regression Potential] Regression potential: fix is very safe. We're just removing asserts in code, returning safe values and printing errors instead. Not sure if the cause is running autopilot tests. ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AssertionMessage: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 30 21:46:07 2014 DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2014-02-13 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) MachineType: System manufacturer System Product Name ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7 Signal: 6SourcePackage: compiz StacktraceTop: __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92 __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101 frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
[Dx-packages] [Bug 1562822] Update Released
The verification of the Stable Release Update for unity-control-center 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-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: In Progress Status in unity-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth source package in Xenial: New Status in unity-control-center source package in Xenial: Fix Released Bug description: * 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 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
Ubuntu 14.04 x86, 2gb ram, 1.4ghz intel celeron, fujitsu amilo li2727 laptop ( its old but lovable :p ) For anybody suffering with this I just hit it yet again and recovered from it without needing to do any of the crash or kill techniques described above. i was trying the ctrl+alt+[arrow keys] and it just switched the work space but i couldnt do anything with the program i was moving that stick across work spaces not close the switcher. so i thought. ctrl+alt+L is what worked for me, managed to close the switcher properly and then just resized the program window and finished moving it to the work space. I would say this bug should be fixed by now. but in the mean time, i hope that helps. -- 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: Fix Released Status in Compiz Main Plugins: Fix Released Status in Compiz Desktop Wall Plugin: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in compiz package in Ubuntu: Triaged Status in compiz-plugins-main package in Ubuntu: Triaged Status in compiz source package in Xenial: Won't Fix 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 1573639] Update Released
The verification of the Stable Release Update for owncloud-client 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 appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1573639 Title: ownCloud Client system tray icon integration broken Status in appmenu-qt5 package in Ubuntu: Triaged Status in owncloud-client package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Confirmed Status in owncloud-client source package in Xenial: Fix Released Status in appmenu-qt5 source package in Yakkety: Triaged Status in owncloud-client source package in Yakkety: Fix Released Bug description: [Impact] The ownCloud client in Xenial is compiled against Qt 5.5.1. when starting the client, the system tray icon does not show up, making the application essentially useless. See also: https://github.com/owncloud/client/issues/4693. [Test case] install owncloud-client, run owncloud. It'll open a connection helper and should show an icon in the systray but doesn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+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 1341562] Re: indicator-printers not working on Ubuntu 14.04
I agree that this bug is fixed in 16.04 (I didn't try 15.10 -- I only do LTS). Thank you to whoever is responsible. -- 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/1341562 Title: indicator-printers not working on Ubuntu 14.04 Status in indicator-printers package in Ubuntu: Confirmed Bug description: This is a regression from bug 1304434 The bug is still there for quite a lot of users including myself. Please can the Ubuntu Dev Team look into this bug again for us please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1341562/+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
This just happened to me (i remember why i upgraded to 15 now) I needed to roll back as some programs that i need have not yet caught up. All the same the bug is as described. Can move between programs workspaces so long as you do not grab the title bar. Freeze occurs only freeing up after eventual crash forcing to log back in. This has been going on for several years now can this not be resolved? -- 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: Fix Released Status in Compiz Main Plugins: Fix Released Status in Compiz Desktop Wall Plugin: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in compiz package in Ubuntu: Triaged Status in compiz-plugins-main package in Ubuntu: Triaged Status in compiz source package in Xenial: Triaged Status in compiz-plugins-main source package in Xenial: Triaged 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 1341562] Re: indicator-printers not working on Ubuntu 14.04
Still no change. Can I elaborate on my observation of 2014-11-14? When the login prompt appears I need to wait at least 10 seconds before entering my password. Then the notification works. It may or may not be relevant that when the login prompt appears, the cursor flashes for just 10 seconds and then stops. There must be some process lasting or continuing for 10 seconds from the appearance of the login prompt (and which may or may not be linked to the appearance of the cursor) that is interrupted when you enter your password. It is possible to work round this bug, but it is a bug. It would be nice if someone could stamp on it for us. -- 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/1341562 Title: indicator-printers not working on Ubuntu 14.04 Status in indicator-printers package in Ubuntu: Confirmed Bug description: This is a regression from bug 1304434 The bug is still there for quite a lot of users including myself. Please can the Ubuntu Dev Team look into this bug again for us please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1341562/+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 1460626] 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/1460626 Title: Unity Lockscreen still shows unlocked desktop while shutting down Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in indicator-session package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: This was reported and supposedly fixed in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1370017, but the bug is still present in the current Unity version in Trusty. I've reported it in that bug already, but got ignored, so I'm opening a new bug about it. [Impact and Test Case] Steps to reproduce: 1 - Log into Unity 2 - Open a terminal. 3 - Lock the screen 4 - From the lockscreen, tell the computer to shut down / restart Expected behavior: * Session programs are closed while the screen is still locked * During shutdown, no user interaction is possible Observed behavior: * The lockscreen is gone immediately, with the rest of compiz (e.g. window decorations are not present) * But it's possible to interact with programs that are still running in the session for about 3 seconds Observed on an updated Trusty machine, running unity version 7.2.5+14.04.20150521.1-0ubuntu1 This bug is a security vulnerability because during those 3 seconds it could be possible to access and interact with sensitive information. Yes, it's short, but you could take a picture or even rm -rf / if there happened to be a root console available. = [Impact] A lockscreen should hide the screen content no matter what. A the moment there is no easy way to provide a good shutdown experience if the screen is locked so it's better to disable it. Please note that you can still shut down the system if the screen is locked just switching to unity-greeter using "Swtich Account..." (it's safe in this case) Needs to be backported to 14.04 LTS because can affect security. [Test Case] 1 - Lock the screen 2 - Push the hw shutdown button. 3 - Make sure that there is no shutdown option in the end of session dialog. 1 - Lock the screen 2 - Open the session indicator 3 - Make sure there is no shutdown option in the drop down menu [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1460626/+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 1381856] Update Released
The verification of the Stable Release Update for notify-osd-icons 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 notify-osd-icons in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1381856 Title: [Dell Latitude E5550] Microphone mute key does not work on this system Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in notify-osd-icons package in Ubuntu: Fix Committed Status in unity-settings-daemon package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in notify-osd-icons source package in Trusty: Fix Released Status in unity-settings-daemon source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Released Status in notify-osd-icons source package in Utopic: Won't Fix Status in unity-settings-daemon source package in Utopic: Won't Fix Bug description: * Impact the wrong icon is displayed when using the mic mute key * Test Case have a keyboard with a micmute key and press it, looks at what icon is used in the unity7 notification * Regression potential the change is limited to this action -- CID: 201406-15271 Dell Latitude E5550 The microphone mute key does not work at all. Key event cannot be captured by "xev" or "sudo showkey -s" But keycode 248 would be returned when testing with sudo showkey -k Alsa info: http://www.alsa-project.org/db/?f=006099fcf08709c82a74dba986a907a602a868ab Also note that with file at /etc/udev/hwdb.d/60-dell-mic-mute-hotkey.hwdb generated with the following content: # Dell platform kernel driver keyboard:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pn* KEYBOARD_KEY_150=f20 # Mic mute toggle And with udev database updated: sudo udevadm hwdb -u The microphone mute key works, but the mic mute led does not work. (Also the icon is not correct, which show a speaker instead of a mic) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 15 23:17:51 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381856/+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 1350821] Update Released
The verification of the Stable Release Update for ido 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 ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350821 Title: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press() Status in ido package in Ubuntu: Fix Released Status in ido source package in Trusty: Fix Released Bug description: [Impact] Unity panel service crashes when opening the Calendar menu [Test Case] There's not a way to reproduce this systemically. Just open frequently the calendar menu, but this crash can happen or not. [Regression Potential] None, the code change consists only on protecting against a null pointer (recorded in the stacktraces here), so it's just pretty safe. ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: unity-services 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jul 31 13:53:14 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.12, 3.16.0-5-generic, x86_64: installed virtualbox, 4.3.12, 3.16.0-6-generic, x86_64: installed ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2013-12-22 (221 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, user) LANGUAGE=de_DE XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7ffbbaf3b766:mov0x10(%rdx),%ecx PC (0x7ffbbaf3b766) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Jul 30 18:55:05 2014 xserver.configfile: default
[Dx-packages] [Bug 1381856] Re: [Dell Latitude E5550] Microphone mute key does not work on this system
Hello Po-Hsu, or anyone else affected, Accepted unity-settings-daemon into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unity-settings-daemon/14.04.0+14.04.20151012-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-settings-daemon (Ubuntu Trusty) Status: New => Fix Committed ** Tags removed: verification-failed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd-icons in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1381856 Title: [Dell Latitude E5550] Microphone mute key does not work on this system Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in notify-osd-icons package in Ubuntu: Fix Committed Status in unity-settings-daemon package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in notify-osd-icons source package in Trusty: Fix Committed Status in unity-settings-daemon source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Released Status in notify-osd-icons source package in Utopic: Won't Fix Status in unity-settings-daemon source package in Utopic: Won't Fix Bug description: * Impact the wrong icon is displayed when using the mic mute key * Test Case have a keyboard with a micmute key and press it, looks at what icon is used in the unity7 notification * Regression potential the change is limited to this action -- CID: 201406-15271 Dell Latitude E5550 The microphone mute key does not work at all. Key event cannot be captured by "xev" or "sudo showkey -s" But keycode 248 would be returned when testing with sudo showkey -k Alsa info: http://www.alsa-project.org/db/?f=006099fcf08709c82a74dba986a907a602a868ab Also note that with file at /etc/udev/hwdb.d/60-dell-mic-mute-hotkey.hwdb generated with the following content: # Dell platform kernel driver keyboard:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pn* KEYBOARD_KEY_150=f20 # Mic mute toggle And with udev database updated: sudo udevadm hwdb -u The microphone mute key works, but the mic mute led does not work. (Also the icon is not correct, which show a speaker instead of a mic) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 15 23:17:51 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1381856/+subscriptions
[Dx-packages] [Bug 1350821] Re: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press()
Hello Daniel, or anyone else affected, Accepted ido into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ido/13.10.0+14.04.20151021-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: ido (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 ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350821 Title: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press() Status in ido package in Ubuntu: Fix Released Status in ido source package in Trusty: Fix Committed Bug description: [Impact] Unity panel service crashes when opening the Calendar menu [Test Case] There's not a way to reproduce this systemically. Just open frequently the calendar menu, but this crash can happen or not. [Regression Potential] None, the code change consists only on protecting against a null pointer (recorded in the stacktraces here), so it's just pretty safe. ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: unity-services 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jul 31 13:53:14 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.12, 3.16.0-5-generic, x86_64: installed virtualbox, 4.3.12, 3.16.0-6-generic, x86_64: installed ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2013-12-22 (221 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, user) LANGUAGE=de_DE XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7ffbbaf3b766:mov0x10(%rdx),%ecx PC (0x7ffbbaf3b766) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1
[Dx-packages] [Bug 1460626] Re: Unity Lockscreen still shows unlocked desktop while shutting down
Hello Margarita, or anyone else affected, Accepted indicator-session into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/indicator- session/12.10.5+14.04.20151021.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: indicator-session (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed -- 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/1460626 Title: Unity Lockscreen still shows unlocked desktop while shutting down Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in indicator-session package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Committed Status in unity source package in Trusty: Fix Committed Bug description: This was reported and supposedly fixed in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1370017, but the bug is still present in the current Unity version in Trusty. I've reported it in that bug already, but got ignored, so I'm opening a new bug about it. [Impact and Test Case] Steps to reproduce: 1 - Log into Unity 2 - Open a terminal. 3 - Lock the screen 4 - From the lockscreen, tell the computer to shut down / restart Expected behavior: * Session programs are closed while the screen is still locked * During shutdown, no user interaction is possible Observed behavior: * The lockscreen is gone immediately, with the rest of compiz (e.g. window decorations are not present) * But it's possible to interact with programs that are still running in the session for about 3 seconds Observed on an updated Trusty machine, running unity version 7.2.5+14.04.20150521.1-0ubuntu1 This bug is a security vulnerability because during those 3 seconds it could be possible to access and interact with sensitive information. Yes, it's short, but you could take a picture or even rm -rf / if there happened to be a root console available. = [Impact] A lockscreen should hide the screen content no matter what. A the moment there is no easy way to provide a good shutdown experience if the screen is locked so it's better to disable it. Please note that you can still shut down the system if the screen is locked just switching to unity-greeter using "Swtich Account..." (it's safe in this case) Needs to be backported to 14.04 LTS because can affect security. [Test Case] 1 - Lock the screen 2 - Push the hw shutdown button. 3 - Make sure that there is no shutdown option in the end of session dialog. 1 - Lock the screen 2 - Open the session indicator 3 - Make sure there is no shutdown option in the drop down menu [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1460626/+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 1460626] Please test proposed package
Hello Margarita, 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.6+14.04.20151021-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 indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1460626 Title: Unity Lockscreen still shows unlocked desktop while shutting down Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in indicator-session package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Committed Status in unity source package in Trusty: Fix Committed Bug description: This was reported and supposedly fixed in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1370017, but the bug is still present in the current Unity version in Trusty. I've reported it in that bug already, but got ignored, so I'm opening a new bug about it. [Impact and Test Case] Steps to reproduce: 1 - Log into Unity 2 - Open a terminal. 3 - Lock the screen 4 - From the lockscreen, tell the computer to shut down / restart Expected behavior: * Session programs are closed while the screen is still locked * During shutdown, no user interaction is possible Observed behavior: * The lockscreen is gone immediately, with the rest of compiz (e.g. window decorations are not present) * But it's possible to interact with programs that are still running in the session for about 3 seconds Observed on an updated Trusty machine, running unity version 7.2.5+14.04.20150521.1-0ubuntu1 This bug is a security vulnerability because during those 3 seconds it could be possible to access and interact with sensitive information. Yes, it's short, but you could take a picture or even rm -rf / if there happened to be a root console available. = [Impact] A lockscreen should hide the screen content no matter what. A the moment there is no easy way to provide a good shutdown experience if the screen is locked so it's better to disable it. Please note that you can still shut down the system if the screen is locked just switching to unity-greeter using "Swtich Account..." (it's safe in this case) Needs to be backported to 14.04 LTS because can affect security. [Test Case] 1 - Lock the screen 2 - Push the hw shutdown button. 3 - Make sure that there is no shutdown option in the end of session dialog. 1 - Lock the screen 2 - Open the session indicator 3 - Make sure there is no shutdown option in the drop down menu [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1460626/+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 1501244] 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/1501244
Title:
indicator-session sporadically segfaults if used with winbind
Status in indicator-session package in Ubuntu:
Fix Released
Status in indicator-session source package in Trusty:
Fix Released
Bug description:
when looking into our pc pool with 44 machines, in around 2-5 sessions
the System Menu is missing after a crash of indicator-session-service,
making the users unable to log out using the mouse.
There are arround 100 ubuntu machines for students with 32000 real
users from an active directory. The users cannot see any users real
name.
I wasn't able to find the right debug symbols, but in the disassembly it
looks like a crash in service.c:321 .
In the attached crash dump the instruction pointer points to 0x4120a0 in
memory, which should be the get_current_realname function.
static const char *
get_current_real_name (IndicatorSessionService * self)
{
GHashTableIter iter;
gpointer key, value;
/* is it the guest? */
if (indicator_session_guest_is_active (self->priv->backend_guest))
return _("Guest");
/* is it a user? */
g_hash_table_iter_init (, self->priv->users);
while (g_hash_table_iter_next (, , ))
{
IndicatorSessionUser * user = value;
if (user->is_current_user) // SEGFAULT PROBABLY HERE (movzx edx, byte
ptr [r13]), r13=user ist NULL
return get_user_label (user);
}
return "";
}
The strange thing is: before inserting into the hashmap, every user is
checked to be != NULL. So maybe I guessed the wrong function, or there are
threading issues.
Disassembly:
0x00412081 <+1484>:movr13,rax
0x00412084 <+1487>:setne al
0x00412087 <+1490>:test al,al
0x00412089 <+1492>:je 0x411f56 <_start+1185>
0x0041208f <+1498>:jmp0x411f51 <_start+1180>
0x00412094 <+1503>:nopDWORD PTR [rax+0x0]
0x00412098 <+1507>:movr13,QWORD PTR [rdx+0x20]
0x0041209c <+1511>:movrsi,QWORD PTR [rdx+0x18]
=> 0x004120a0 <+1515>:movzx edx,BYTE PTR [r13+0x0]
0x004120a5 <+1520>:test dl,dl
0x004120a7 <+1522>:je 0x4120d6 <_start+1569>
0x004120a9 <+1524>:movrax,QWORD PTR [rip+0x248770]
# 0x65a820
0x004120b0 <+1531>:test BYTE PTR [rax+rdx*2+0x1],0x1
0x004120b5 <+1536>:je 0x411f51 <_start+1180>
0x004120bb <+1542>:movrdx,r13
0x004120be <+1545>:jmp0x4120cb <_start+1558>
Some command output:
$> lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Package version:
$> dpkg -l | grep indicator-session
ii indicator-session
12.10.5+14.04.20150404-0ubuntu1 amd64indicator
showing session management, status and user switching
~$> gsettings list-recursively com.canonical.indicator.session
com.canonical.indicator.session show-real-name-on-panel false
com.canonical.indicator.session suppress-logout-menuitem false
com.canonical.indicator.session suppress-restart-menuitem false
com.canonical.indicator.session suppress-shutdown-menuitem false
com.canonical.indicator.session suppress-logout-restart-shutdown false
com.canonical.indicator.session user-show-menu false
~$> wbinfo -u | wc -l
127390
iw18ejyg@cip-54-54: ~$> python -c
'print(__import__("pwd").getpwnam("iw18ejyg"))'
pwd.struct_passwd(pw_name='iw18ejyg', pw_passwd='*', pw_uid=1069023,
pw_gid=1000513, pw_gecos='', pw_dir='/home/stud/iw18ejyg', pw_shell='/bin/bash')
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1501244/+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 1381856] Re: [Dell Latitude E5550] Microphone mute key does not work on this system
Hello Po-Hsu, or anyone else affected, Accepted notify-osd-icons into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/notify-osd- icons/0.8+14.04.20151016-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: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: notify-osd-icons (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity-settings-daemon (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: notify-osd-icons (Ubuntu Utopic) Status: In Progress => Won't Fix ** Changed in: notify-osd-icons (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 notify-osd-icons in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1381856 Title: [Dell Latitude E5550] Microphone mute key does not work on this system Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in notify-osd-icons package in Ubuntu: Fix Committed Status in unity-settings-daemon package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in notify-osd-icons source package in Trusty: Fix Committed Status in unity-settings-daemon source package in Trusty: New Status in linux source package in Utopic: Fix Released Status in notify-osd-icons source package in Utopic: Won't Fix Status in unity-settings-daemon source package in Utopic: In Progress Bug description: * Impact the wrong icon is displayed when using the mic mute key * Test Case have a keyboard with a micmute key and press it, looks at what icon is used in the unity7 notification * Regression potential the change is limited to this action -- CID: 201406-15271 Dell Latitude E5550 The microphone mute key does not work at all. Key event cannot be captured by "xev" or "sudo showkey -s" But keycode 248 would be returned when testing with sudo showkey -k Alsa info: http://www.alsa-project.org/db/?f=006099fcf08709c82a74dba986a907a602a868ab Also note that with file at /etc/udev/hwdb.d/60-dell-mic-mute-hotkey.hwdb generated with the following content: # Dell platform kernel driver keyboard:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pn* KEYBOARD_KEY_150=f20 # Mic mute toggle And with udev database updated: sudo udevadm hwdb -u The microphone mute key works, but the mic mute led does not work. (Also the icon is not correct, which show a speaker instead of a mic) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 15 23:17:51 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: T43 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Dx-packages] [Bug 1501244] Re: indicator-session sporadically segfaults if used with winbind
Hello Jonathan, or anyone else affected,
Accepted indicator-session into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/indicator-
session/12.10.5+14.04.20151008-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: indicator-session (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: indicator-session (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 indicator-session in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1501244
Title:
indicator-session sporadically segfaults if used with winbind
Status in indicator-session package in Ubuntu:
Fix Released
Status in indicator-session source package in Trusty:
Fix Committed
Bug description:
when looking into our pc pool with 44 machines, in around 2-5 sessions
the System Menu is missing after a crash of indicator-session-service,
making the users unable to log out using the mouse.
There are arround 100 ubuntu machines for students with 32000 real
users from an active directory. The users cannot see any users real
name.
I wasn't able to find the right debug symbols, but in the disassembly it
looks like a crash in service.c:321 .
In the attached crash dump the instruction pointer points to 0x4120a0 in
memory, which should be the get_current_realname function.
static const char *
get_current_real_name (IndicatorSessionService * self)
{
GHashTableIter iter;
gpointer key, value;
/* is it the guest? */
if (indicator_session_guest_is_active (self->priv->backend_guest))
return _("Guest");
/* is it a user? */
g_hash_table_iter_init (, self->priv->users);
while (g_hash_table_iter_next (, , ))
{
IndicatorSessionUser * user = value;
if (user->is_current_user) // SEGFAULT PROBABLY HERE (movzx edx, byte
ptr [r13]), r13=user ist NULL
return get_user_label (user);
}
return "";
}
The strange thing is: before inserting into the hashmap, every user is
checked to be != NULL. So maybe I guessed the wrong function, or there are
threading issues.
Disassembly:
0x00412081 <+1484>:movr13,rax
0x00412084 <+1487>:setne al
0x00412087 <+1490>:test al,al
0x00412089 <+1492>:je 0x411f56 <_start+1185>
0x0041208f <+1498>:jmp0x411f51 <_start+1180>
0x00412094 <+1503>:nopDWORD PTR [rax+0x0]
0x00412098 <+1507>:movr13,QWORD PTR [rdx+0x20]
0x0041209c <+1511>:movrsi,QWORD PTR [rdx+0x18]
=> 0x004120a0 <+1515>:movzx edx,BYTE PTR [r13+0x0]
0x004120a5 <+1520>:test dl,dl
0x004120a7 <+1522>:je 0x4120d6 <_start+1569>
0x004120a9 <+1524>:movrax,QWORD PTR [rip+0x248770]
# 0x65a820
0x004120b0 <+1531>:test BYTE PTR [rax+rdx*2+0x1],0x1
0x004120b5 <+1536>:je 0x411f51 <_start+1180>
0x004120bb <+1542>:movrdx,r13
0x004120be <+1545>:jmp0x4120cb <_start+1558>
Some command output:
$> lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Package version:
$> dpkg -l | grep indicator-session
ii indicator-session
12.10.5+14.04.20150404-0ubuntu1 amd64indicator
showing session management, status and user switching
~$> gsettings list-recursively com.canonical.indicator.session
com.canonical.indicator.session show-real-name-on-panel false
com.canonical.indicator.session suppress-logout-menuitem false
com.canonical.indicator.session suppress-restart-menuitem false
com.canonical.indicator.session suppress-shutdown-menuitem false
com.canonical.indicator.session suppress-logout-restart-shutdown false
com.canonical.indicator.session user-show-menu false
~$> wbinfo -u | wc -l
127390
[Dx-packages] [Bug 1430059] Re: LyX menu is not updated by indicator-appmenu in mode unity-all-menus
** Also affects: indicator-appmenu (Ubuntu Trusty) Importance: Undecided Status: New -- 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 Released 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 1430059] Update Released
The verification of the Stable Release Update for indicator-appmenu 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-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 Released 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 1447224] Update Released
The verification of the Stable Release Update for totem 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-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1447224 Title: Regression: Unable to select audio or subtitle tracks Status in indicator-appmenu package in Ubuntu: Invalid Status in totem package in Ubuntu: Fix Released Status in vlc package in Ubuntu: Invalid Status in indicator-appmenu source package in Vivid: Invalid Status in totem source package in Vivid: Fix Released Status in vlc source package in Vivid: Invalid Bug description: [ Description ] Under Unity, the menu items Language and Subtitles do not show available languages and subtitles that can be selected. [ Fix ] Port to GMenu, which can correctly show the menu items. NOTE that this removes the menu from full screen under Unity. [ QA ] Test under both Unity and GNOME shell (and optionally other DEs) that you can load a video (e.g. http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/Sintel_DivXPlus_6500kbps.mkv [large - 819M]) with subtitles and languages and select between them. [ Development fix ] Identical already uploaded. [ Regression potential ] Due to the nature of this change, you won't get the app menu when full screened under Unity any more - langs and subtitles can only be selected from the regular menu which is visible when not in full screen. No other regressions are expected, so if you find any please report in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+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 1474615] [NEW] url-dispatcher should launch web browser for local .html files
Public bug reported: Trying to dispatch a url to a file:///home/phablet/blah/blah.html URL should launch the browser, but instead, does nothing but complain. ** (process:20675): WARNING **: Unable to dispatch url 'file:///home/phablet/Documents/submission_2015-07-15T01:08:13.920457.html':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'file:///home/phablet/Documents/submission_2015-07-15T01:08:13.920457.html' is not handleable by the URL Dispatcher ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: url-dispatcher (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 14 21:09:33 2015 InstallationDate: Installed on 2015-04-24 (81 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) SourcePackage: url-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: url-dispatcher (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1474615 Title: url-dispatcher should launch web browser for local .html files Status in url-dispatcher package in Ubuntu: New Bug description: Trying to dispatch a url to a file:///home/phablet/blah/blah.html URL should launch the browser, but instead, does nothing but complain. ** (process:20675): WARNING **: Unable to dispatch url 'file:///home/phablet/Documents/submission_2015-07-15T01:08:13.920457.html':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'file:///home/phablet/Documents/submission_2015-07-15T01:08:13.920457.html' is not handleable by the URL Dispatcher ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: url-dispatcher (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 14 21:09:33 2015 InstallationDate: Installed on 2015-04-24 (81 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) SourcePackage: url-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1474615/+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 1447224] Re: Regression: Unable to select audio or subtitle tracks
Hello Peter, or anyone else affected, Accepted totem into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/totem/3.14.3-0ubuntu0.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: totem (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/1447224 Title: Regression: Unable to select audio or subtitle tracks Status in indicator-appmenu package in Ubuntu: Invalid Status in totem package in Ubuntu: Fix Released Status in vlc package in Ubuntu: Invalid Status in indicator-appmenu source package in Vivid: Invalid Status in totem source package in Vivid: Fix Committed Status in vlc source package in Vivid: Invalid Bug description: [ Description ] Under Unity, the menu items Language and Subtitles do not show available languages and subtitles that can be selected. [ Fix ] Port to GMenu, which can correctly show the menu items. NOTE that this removes the menu from full screen under Unity. [ QA ] Test under both Unity and GNOME shell (and optionally other DEs) that you can load a video (e.g. http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/Sintel_DivXPlus_6500kbps.mkv [large - 819M]) with subtitles and languages and select between them. [ Development fix ] Identical already uploaded. [ Regression potential ] Due to the nature of this change, you won't get the app menu when full screened under Unity any more - langs and subtitles can only be selected from the regular menu which is visible when not in full screen. No other regressions are expected, so if you find any please report in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+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 1314095] Update Released
The verification of the Stable Release Update for nss-pam-ldapd 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Invalid Status in nss-pam-ldapd package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in nss-pam-ldapd source package in Trusty: Fix Released Status in unity source package in Trusty: Invalid Status in nss-pam-ldapd source package in Utopic: Fix Released Status in unity source package in Utopic: Invalid Status in nss-pam-ldapd package in Debian: Fix Released Bug description: SRU justification: [Impact] * Summary: in Trusty, when libnss-ldapd is used, LDAP users are not able to unlock the Unity lockscreen. Utopic and later are not affected. Some workarounds are listed in comment #29. * nslcd in Trusty and earlier does not permit unprivileged users to read shadow entries. When invoked by the Unity lockscreen, running as the logged-in user, pam_unix returns PAM_AUTHINFO_UNAVAIL in pam_acct_mgmt when it tries to get password expiry information from shadow. This leads to an authorization failure, so Unity refuses to unlock the screen. pam_ldap is not consulted for pam_acct_mgmt after pam_unix fails because its rule is in the Additional section. * In Utopic and later, nslcd returns partial shadow entries to unprivileged users. This is enough for the expiry check in pam_unix to succeed, so the screen can be unlocked. See http://bugs.debian.org/706913 for a discussion of the upstream fix. * This proposed SRU backports the upstream solution to Trusty's nslcd. This is a change of behaviour for shadow queries from unprivileged users, compared to the current package. An alternative, more targeted fix would be to change Unity to ignore AUTHINFO_UNAVAIL results from pam_acct_mgmt, like gnome-screensaver already does (see comment #29). The nslcd change is a more general fix for not just Unity, but any PAM-using program run by an unprivileged user. [Test Case] * Install and configure libnss-ldapd. Ensure ldap is enabled for at least the passwd and shadow services in /etc/nsswitch.conf. * Log into Unity as an LDAP user, lock the screen, and then try to unlock it again. [Regression Potential] * The patch is minimal, was written by the upstream author, and was backported (adjusting for whitespace changes) to Trusty. The change has already been released in Utopic and will be included in Debian Jessie as well. * Regression testing should include checking that shadow queries, both by name and for listing all users, are unchanged when issued as root. [Other Info] * Packages for testing are available in ppa:rtandy/lp1314095 Original description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log:
[Dx-packages] [Bug 1451613] Re: [regression] Unity/compiz crashes when locking screen
Hello Scaler, 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.20150603-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/1451613 Title: [regression] Unity/compiz crashes when locking screen Status in Unity: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] A crash is occurring for many users of Trusty when the screen is locking. [ Test Case ] Lock the screen. [ Regression Potential ] None as this is removing a commit causing this regression. The debdiff is found at https://bugs.launchpad.net/unity/+bug/1451613/+attachment/4409311/+files/unity.revert-3810.debdiff - Original Description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+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 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Hello Grzegorz, or anyone else affected, Accepted nss-pam-ldapd into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nss-pam- ldapd/0.8.13-3ubuntu1 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: nss-pam-ldapd (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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Invalid Status in nss-pam-ldapd package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in nss-pam-ldapd source package in Trusty: Fix Committed Status in unity source package in Trusty: Invalid Status in nss-pam-ldapd source package in Utopic: Fix Released Status in unity source package in Utopic: Invalid Status in nss-pam-ldapd package in Debian: Fix Released Bug description: SRU justification: [Impact] * Summary: in Trusty, when libnss-ldapd is used, LDAP users are not able to unlock the Unity lockscreen. Utopic and later are not affected. Some workarounds are listed in comment #29. * nslcd in Trusty and earlier does not permit unprivileged users to read shadow entries. When invoked by the Unity lockscreen, running as the logged-in user, pam_unix returns PAM_AUTHINFO_UNAVAIL in pam_acct_mgmt when it tries to get password expiry information from shadow. This leads to an authorization failure, so Unity refuses to unlock the screen. pam_ldap is not consulted for pam_acct_mgmt after pam_unix fails because its rule is in the Additional section. * In Utopic and later, nslcd returns partial shadow entries to unprivileged users. This is enough for the expiry check in pam_unix to succeed, so the screen can be unlocked. See http://bugs.debian.org/706913 for a discussion of the upstream fix. * This proposed SRU backports the upstream solution to Trusty's nslcd. This is a change of behaviour for shadow queries from unprivileged users, compared to the current package. An alternative, more targeted fix would be to change Unity to ignore AUTHINFO_UNAVAIL results from pam_acct_mgmt, like gnome-screensaver already does (see comment #29). The nslcd change is a more general fix for not just Unity, but any PAM-using program run by an unprivileged user. [Test Case] * Install and configure libnss-ldapd. Ensure ldap is enabled for at least the passwd and shadow services in /etc/nsswitch.conf. * Log into Unity as an LDAP user, lock the screen, and then try to unlock it again. [Regression Potential] * The patch is minimal, was written by the upstream author, and was backported (adjusting for whitespace changes) to Trusty. The change has already been released in Utopic and will be included in Debian Jessie as well. * Regression testing should include checking that shadow queries, both by name and for listing all users, are unchanged when issued as root. [Other Info] * Packages for testing are available in ppa:rtandy/lp1314095 Original description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1
[Dx-packages] [Bug 1431920] Re: Ubuntu Phone BQ: Message into welcome screen = No data sources available
why not hiding the whole circle when repirts are disabled? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1431920 Title: Ubuntu Phone BQ: Message into welcome screen = No data sources available Status in indicator-messages package in Ubuntu: Invalid Bug description: Hi! From a 2 weeks I'm getting this unique message inside the circle on the welcome screen: No data sources available I'm so sorry, but I can't report steps in this case. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1431920/+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 886478] Update Released
The verification of the Stable Release Update for unity 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 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 Released 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 1313597] Update Released
The verification of the Stable Release Update for unity 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 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 Released 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 1436095] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1436095
Title:
AP test failure:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
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 Released
Bug description:
[ Impact ]
Failed Autopilot tests are not good.
[ Test Case ]
1. Run 'autopilot run
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click'
2. Run 'autopilot run
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click'
3. Observe that the tests don't fail.
[ 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:
The following two AP tests consistently ERROR during regular Unity
testing.
==
ERROR:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
--
Empty attachments:
/var/log/syslog
unity-log: {{{WARN 2015-03-24 13:43:02 nux.inputmethod.ibus
InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
128, in test_scaled_window_closes_on_middle_click
self.assertWindowIsScaledEquals(target_xid, False)
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
68, in assertWindowIsScaledEquals
self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 421, in
assertThat
mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 471, in
_matchHelper
mismatch = matcher.match(matchee)
File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py,
line 113, in match
wait_fun(self.matcher, self.timeout)
File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py,
line 129, in _callable_wait_for
new_value = refresh_fn()
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
67, in lambda
refresh_fn = lambda: xid in [w.xid for w in
self.unity.screen.scaled_windows]
File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py,
line 520, in __getattr__
self.refresh_state()
File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py,
line 474, in refresh_state
_, new_state = self.get_new_state()
File /usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py,
line 564, in get_new_state
raise StateNotFoundError(self.__class__.__name__, id=self.id)
StateNotFoundError: Object not found with name 'Window' and properties {'id':
148832}.
==
ERROR:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click
--
Empty attachments:
/var/log/syslog
unity-log: {{{WARN 2015-03-24 14:00:34 nux.inputmethod.ibus
InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
148, in test_scaled_window_closes_on_close_button_click
self.assertWindowIsScaledEquals(target_xid, False)
File /usr/lib/python2.7/dist-packages/unity/tests/test_spread.py, line
68, in assertWindowIsScaledEquals
self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 421, in
assertThat
mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 471, in
_matchHelper
mismatch = matcher.match(matchee)
File /usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py,
line 113, in match
wait_fun(self.matcher, self.timeout)
File
[Dx-packages] [Bug 932486] Update Released
The verification of the Stable Release Update for unity 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 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 Released 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 926979] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/926979 Title: compiz crashed with SIGSEGV in nux::Propertybool::operator=(bool const) from unity::dash::DashView::AnalyseLensURI(std::string const) from unity::dash::DashView::OnActivateRequest(_GVariant*) Status in Unity: Fix Committed Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: Won't Fix Status in Unity 7.0 series: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [ Impact ] Certain cases when clicking on Dash items may cause a crash. [ Test Case ] It's not entirely clear how the crash is triggered, but no crash should be observed when clicking on Dash entries. [ Regression Potential ] The change is small and no regressions should be 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: Clicked dash, Internet applications. Opened a new bug as the others appear to suggest a fix is released for those bugs. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.0.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4 Uname: Linux 3.2.0-3-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Sun Feb 5 14:51:39 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7eff5ff51d10 _ZN3nux8PropertyIbEaSERKb+32: mov 0x18(%rdi),%rdi PC (0x7eff5ff51d10) ok source 0x18(%rdi) (0x03f0) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: nux::Propertybool::operator=(bool const) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::AnalyseLensURI(std::string const) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::OnActivateRequest(_GVariant*) () from /usr/lib/compiz/libunityshell.so unity::UBusManager::OnCallback(_GVariant*, void*) () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in nux::Propertybool::operator=() UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo usrp video To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/926979/+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 1308265] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308265 Title: First password letter not registered in lockscreen if screen off 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 Released Bug description: [ Impact ] Not having the first character registered when trying to unlock the lockscreen can most definitely lead to frustration and thus, poor user experience. [ Test Case ] 1. Lock the screen and let the monitor blank as well. 2. Try unlocking the screen by typing your password. 3. Observe lockscreen unlocks. [ 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: With the new lockscreen, if my screen is off, I just start typing, every time my password is too short. It looks like the first key only triggers the screen on and does not go to the input field. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140414.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 23:59:08 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308265/+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] Update Released
The verification of the Stable Release Update for unity 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 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 Released 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 1413165] Update Released
The verification of the Stable Release Update for unity 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 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 Released 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 1029114] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1029114 Title: With autohide and the HUD enabled the launcher can appear at incorrect times 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 Released Bug description: [ Impact ] When the Launcher is suddenly revealed when it's not intended to can cause confusion and a poor user experience. [ Test Case ] 1. Turn on launcher auto hide 2. Display the HUD (tap Alt) 3. Move the mouse to the left side of the screen (as if you are showing the launcher) 4. Note the launcher is not displayed 5. Now hide the HUD (either tap Alt or select the X in the top left corner) 6. Observe the Launcher is not revealed. [ 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 What Happened: 1) Turn on launcher auto hide 2) Display the HUD (tap Alt) 3) Move the mouse to the left side of the screen (as if you are showing the launcher) 4) Note the launcher is not displayed 5) Now hide the HUD (either tap Alt or select the X in the top left corner) 6) Note that the launcher is now displayed, after the HUD closes. What I expected to happen: - I expected that the launcher is not displayed at step 6. I expected for the launcher to not be displayed at step 6 because the user could have the HUD displayed for a long period of time then decide that they don't need the HUD. The launcher is then suddenly revealed to them as they moved their cursor to the left side of the screen a few minutes a ago. This could then confuse the user to why the launcher has appeared when all they did was close the HUD. Hope this can be fixed soon. Andy ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12.0-0ubuntu3~webapps7 [origin: LP-PPA-webapps-preview] ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,vpswitch,compiztoolbox,snap,resize,move,grid,imgpng,mousepoll,place,unitymtgrabhandles,wall,gnomecompat,session,regex,resizeinfo,animation,expo,fade,scale,ezoom,workarounds,unityshell] CrashDB: unity Date: Wed Jul 25 21:19:17 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.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/1029114/+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 1448229] Re: Launcher Trash icon: Empty Trash option opens nautilus @ home
*** This bug is a duplicate of bug 1445595 *** https://bugs.launchpad.net/bugs/1445595 I have the same bug on 2 systems, both fresh installations. -- 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/1448229 Title: Launcher Trash icon: Empty Trash option opens nautilus @ home Status in unity package in Ubuntu: Confirmed Bug description: Test case: Add a file to trash if none already Right click on Unity launcher trash icon click on Empty Trash option nautilus open a window @ home folder ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Apr 24 13:11:02 2015 InstallationDate: Installed on 2015-04-24 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448229/+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 1448229] Re: Launcher Trash icon: Empty Trash option opens nautilus @ home
*** This bug is a duplicate of bug 1445595 *** https://bugs.launchpad.net/bugs/1445595 Recorded a video of the issue in case there was any question what is happening. https://youtu.be/jpugIadlxz0 -- 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/1448229 Title: Launcher Trash icon: Empty Trash option opens nautilus @ home Status in unity package in Ubuntu: Confirmed Bug description: Test case: Add a file to trash if none already Right click on Unity launcher trash icon click on Empty Trash option nautilus open a window @ home folder ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Apr 24 13:11:02 2015 InstallationDate: Installed on 2015-04-24 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448229/+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] Re: Accounts Service always relies on language fallback if never set by the user
Hello Ricardo, or anyone else affected,
Accepted accountsservice into vivid-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.37-1ubuntu10.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: accountsservice (Ubuntu Vivid)
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/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 Committed
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);
[Dx-packages] [Bug 1443178] Re: Accounts Service always relies on language fallback if never set by the user
Hello Ricardo, 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.2
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: accountsservice (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 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:
In Progress
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)
[Dx-packages] [Bug 1404147] Re: Screen is stretched when using dual monitors
This still happens in a fresh install of Ubuntu 15.04 with NVIDIA binary driver - version 346.59 from nvidia-346 (proprietary, tested) installed from the Ubuntu Additional Drivers tool. Though I think I discovered a work-around. It seems like it only happens later if my monitor was plugged when the login screen was open. If I disconnect my monitor's HDMI cable, log out, log back in, and reconnect the monitor, it seems to work fine for that session so far. -- 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/1404147 Title: Screen is stretched when using dual monitors Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: When I'm in dual monitor mode (not mirrored mode; mirrored mode works 100% fine), the applications are stretched, and my mouse clicks don't line up with the applications. See the attached image. Notice the highlighted text in the webpage near the middle of the two screens. My mouse was where the red dot was when I made that highlight. (The mouse doesn't show up in screenshots I guess.) I was supposed to have the application menu bar on both screens, but it and the menus only show up on the right screen. They work fine relatively, though sometimes as dropdown menus close they momentarily visibly stretch like the applications are. System information: I was running Ubuntu 14.04 with the nvidia-331 drivers, dual monitor mode was working great, but then in the last few weeks it started acting up like this often. Probably related to some recent updates I guess. Logging out and back in would sometimes fix it. I decided to do a full reinstall to 14.10, but now the issue always happens. The login screen and gnome-shell both work fine with dual monitor mode. (I'll boot up my computer, see the login screen on my left monitor with the background going to the right monitor exactly as it should, I'll log in with Unity selected, and then it suddenly decides to stretch everything ridiculously until I switch to single or mirrored monitor mode.) I do not get this specific issue when I use the default nouvea driver, but I do get tons of graphical artifacting and the screen freezes eventually when I'm in dual or mirrored monitor mode (single works fine), so that's not an option for me. I'm currently using the nvidia-331 version 331.113-0ubuntu0.1 package. I've tried downgrading to nvidia-331 version 331.89-0ubuntu5, and adding the xorg-edgers PPA and upgrading to nvidia-346, but the exact issue persisted. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1404147/+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 1162291] Re: systray-whitelist gone
Still an issue. Any 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/1162291 Title: systray-whitelist gone Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: $ gsettings list-keys com.canonical.Unity.Panel No such schema 'com.canonical.Unity.Panel' What happened with the systray-whitelist? Is its absence in 13.04 the reason why the icon of my pet app Mail Notification (https://launchpad.net/mail-notification) no longer shows up? Please give us back a possibility to decide which icons to display in the systray. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1162291/+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 1072206] Update Released
The verification of the Stable Release Update for compiz 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Released Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+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 860970] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/860970 Title: Dash called with super key above fullscreen app is not interactive or does not show up at all. Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: Won't Fix Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Precise: Triaged Status in unity source package in Trusty: Fix Released Bug description: [IMPACT] The Dash was rendered underneath fullscreen windows so it was invisible, although it grabs keyboard input. [TEST CASE] - Launch an application in fullscreen (Firefox, Totem). - Hit the Super key to call the dash. - The Dash should appear. - Keyboard input should be directed to the Dash. - Clicking anywhere on the full screen application should close the Dash. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/860970/+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 1066157] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1066157 Title: dash +orca does not speak the names of application icons Status in OEM Priority Project: New Status in Unity: Fix Released Status in Unity 5.0 series: New Status in Unity 6.0 series: Won't Fix Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] Screen reader support for dynamic content in the Dash is enabled. [Test Case] (1) Enable Screen Reader (System Settings Universal Access Screen Reader) (2) Press Super + A to bring up the Applications lens of the Dash (3) Navigate displayed content (4) Choose an application for preview (5) Press Esc until the Dash is closed, repeat steps 2 to 4 You should hear the application description and preview description. [Regression Potential] Some new code deals with processing pointers: the usual problem potential of dealing with pointers in C code applies. [Other Info] This patch for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in public use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1066157/+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 955193] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/955193 Title: Menu bar - add option for the global menu to make it always visible Status in Ayatana Design: Triaged 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 Released Bug description: [ Impact ] [Test Case] (1) enable menus in the window title bar System Settings Appearance Behavior Show the menus for a window In the menu bar (2) run gsettings set com.canonical.Unity always-show-menus true in a terminal (3) move the mouse around between windows The menus should remain displayed [Regression Potential] Any change to the menu functionality has the potential to cause volunteer functionality in menu behaviour. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time with no apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/955193/+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 1413411] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1413411 Title: underscore in mounted drive name mishandled in menu Status in One Hundred Papercuts: In Progress 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 Released Bug description: [Impact] If you have a mounted drive with an underscore in it's name (e.g. host_S), then, when you right-click on the drive icon in the sidebar, the menu interprets the underscore as a keyboard-shortcut indicator, so shows the name as hostS (with S underlined). Hovering over the drive results in the correct host_S name; the bug is only in the right-click menu. Note that right-clicking on the Files icon will show a menu that includes the correct mounted disk names. It is only right-clicking on the drive-icons themselves that shows the incorrect name. [Test Case] (1) Create a mountable device with an underscore in its volume name (eg. host_S). (2) Right click on the icon for tha drive in the Launcher. It should display the underscore character correctly as a part of the drive name, and not as an underline. [Regression Potential] None. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1413411/+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 1401911] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1401911 Title: When the screen is locked edge barriers should be deactivated. 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 Released Bug description: [Impact] If the screen is locked, launcher/panel edge barriers at the moment are active. [Test Case] In a multi-monitor environment, lock the screen and move the mouse between monitors. There should be no sticky edge between the monitors. [Regression Potential] Code in the paths that handle the edge barriers was changed. Potentially this could impact the reveal of a hidden Launcher if there were errors introduced in these code paths. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1401911/+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 1410582] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1410582 Title: [Trusty / Unity] Desktop got unlocked on its own. 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 Released Bug description: [Impact] Certain code paths may cause the Unity lockscreen to crash, which can allow the screen to be unlocked without a password entry. [Test Case] Unfortunately this bug only appears under certain race conditions and is not reliably reproduce able. [Regression Potential] The change in the code simply assumes that if a screen is already locked, then it is lockable this avoiding certain operations that are inherently racy. It is possible that this fix does not avoid all possible crash conditions in the lockscreen and there may still be unaccounted-for crashes in the lockscreen. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivid Vervet dev release where it has been in testing for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1410582/+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 1413773] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1413773 Title: [Regressions] Dash dnd icons rendered behind 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 Released Bug description: [IMPACT] Dragged icons are rendered behind dash. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413773/+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 1413790] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1413790 Title: It's possible to bypasss lockscreen if user is in nopasswdlogin group. 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 Released Bug description: [IMPACT] A user is presented with a password dialog even if a member of the nopasswdlogin group (and may not have a password). [TEST CASE] (1) Create a test user. (2) Add the test user to the nopasswdlogin group. (3) Log in to a Unity session using that acocunt. (4) Lock the screen. (5) Attempt to unlock the screen: no password prompt should be presented. [REGRESSION POTENTIAL] Conceivably allowing a login with no authentication could present unexpected vulnerabilities in which unforseen code paths also exercise this function. Care has been taken by the developer to avoid such cases. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413790/+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 1404486] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1404486 Title: Session dialog does not show up over fullscreen windows. Status in Unity: Triaged Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [IMPACT] Unity session dialog does not show up over a fullscreen window if you press the hardware button. [TEST CASE] (1) open an application (eg. Firefix) and make it fullscreen (F11) (2) press the power button or choose Shut Down... from the Session indicator menu. (3) The Session (shutdown/restart) dialog should appear and be interactive. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1404486/+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 1390562] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1390562 Title: Moving the mouse out from the decoration hides the LIMs when Alt is pressed 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 Released Bug description: [Impact] Pressing the Alt key while a locally integrated menu is open causes the menu to hide. [Test Case] Prerequisite: from Appearance - Behavior - Set menu visible in window titlebar 1. Open a window with menus 2. Press and keep pressed the Alt key 3. Menus will show 4. Move the mouse over the window decoration 5. Move the mouse out from the window decoration Incorrect behavior: 6. Menus hides, also if the Alt key is pressed. Expected: 6. Menus should stay visible until the Alt key is released. [Regression Potential] Additional incorrect menu behaviour may be introduced. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1390562/+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 1363534] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363534 Title: Wrong keyboard shortcuts for Workspaces in Dash overlay 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 Released Bug description: [Impact] The Shortcuts displays the wrong key sequence for switching workspaces. [Test Case] (1) Enable workspaces (System Settings Appearance Behavior Enable Workspaces). (2) Hold down the Super key until the Shortcuts window appears. (3) Under Workspaces it should display Shift + Ctrl + Alt + Arrow Keys and not Shift + Ctrl + Alt + Left + Arrow Keys. [Regression Potential] Unlikely. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivi Vervet dev release where it has been in production use for some time without regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363534/+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 1312137] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1312137 Title: Local menus broken for Qt apps after opening dialog 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 Released Bug description: [Impact] I have selected to have window menus in the window's title bar. This works great, except for Qt apps. After selecting a menu item in a Qt app that produces a dialog, the menu is no longer accessible. The only way to get the menu back, is to switch to another window, and then back to the affected app. [Test Case] 1. Start qtcreator 2. Resize window so that it is not maximised 3. Select 'Help' - 'About Qt Creator' 4. Dismiss 'About Qt Creator' dialog 5. Move mouse over window titlebar. [Regression Potential] It's possible other menu interaction bugs may have been introduced. [Other Info] The fix for Ubuntu 14.04 LTS was cherry-picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1312137/+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 1374942] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374942 Title: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog 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 Released Bug description: [Impact] An invalid line of code would occasionally cause Unity to crash. [Test Case] (1) Download and run the attached Python script test-1374942 to create a candidate application. (2) Press the close button and wait for the Force Quit dialog to come up. (3) Choose the Force Quit button. The desktop shell should not crash. [Regression Potential] The fix for this bug involves converting an integer into a string and appending it to an error message instead of adding the integer value to the address of the error message. There is unlikely to be a regression from this. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been under daily use for some time without apparent regressioon. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1374942/+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 1302955] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1302955 Title: upstart user session leaks all the dbus events it receives Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Confirmed Status in unity source package in Trusty: Fix Released Bug description: [Impact] The unity-panel-service process has been caching D-Bus messages sent from upstart, effectively leaking memory. The solution replaces the offending code with a single upstart event emission. [Test Case] 0. Make sure there is a user session job with a dbus rule (eg unity-greeter-session-broadcast) 1. Install and run system-load-indicator (indicator-multiload) 2. Set the update interval to 100ms 3. Now watch the memory use of init --user increase by 100kb per second 4. Also open up upstart-monitor to see all the dbus messages being sent [Regression Potential] Some kind of hidden functionality depending on upstart events sent through D-Bus to the unity-panel-service may have become disconnected. Unlikely. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in regular use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302955/+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 1241757] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1241757 Title: Unity Launcher always assumes default background is active for a couple of seconds 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 Released Bug description: [IMPACT] Every time the computer boots and autologins to my desktop, I see the default background only behind the Unity Launcher for a couple of seconds, and then it is replaced with the current wallpaper. [TEST CASE] (1) Configure the desktop to use a non-default wallpaper. (2) Log in to a Unity session and observe the area behind the Launcher. [REGRESSION POTENTIAL] The solution to this problem was to eliminate the animation of the BFB icon on initial startup. Potentially this could cause the animation to not run at other times, although even if this did occur, it is unlikely to be noticed. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1241757/+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 1159249] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1159249 Title: HUD does not show up over fullscreen window 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 Released Bug description: [Impact] The HUD was not being rendered above fullscreen windows although it would grab the keyboard. [TEST CASE] 1. Open some site in firefox 2. Go to fullscreen mode (F11) 3. Press Alt once. 4 The HUD should appear and you should be able to interact with it. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1159249/+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 1398287] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1398287 Title: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen 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 Released Bug description: [Impact] When the power button is pressed, the shutdown dialog will be displayed. Then clicks the 'Lock' button in the shutdown dialog and it sometimes takes about 30~60s to lock screen. This happens on many Intel-only platforms. PS: If user moves the cursor out of the dialog window after clicking the 'Lock' button, it will switch to lock screen immediately. [Test Case] See description under Impact' above. [Regression Potential] The fix for this problem involves releasing the grab on the input devices earlier in the sequence, allowing the animation sequence to begin immediately without a grab-release timeout. It is unlikely that this could introduce any regressions. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivid Vervet dev release where it has been in test for some time without incident. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398287/+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 1440415] [NEW] notify-osd crashed with signal 5 in _XReply()
Public bug reported: This occurred while logging in to dropbox ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: notify-osd 0.9.35+15.04.20150126-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 4 14:12:54 2015 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd GtkTheme: 'Ambiance' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2015-04-04 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Dell Inc. OptiPlex 745 ProcCmdline: /usr/lib/x86_64-linux-gnu/notify-osd ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=abeaca93-cffc-4dfe-a6cb-88771f3f4bab ro quiet splash RelatedPackageVersions: xserver-xorg 1:7.7+7ubuntu4 libgl1-mesa-glx 10.5.2-0ubuntu1 libdrm2 2.4.59-0ubuntu1 xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 xserver-xorg-video-ati 1:7.5.0-1ubuntu2 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetGeometry () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_window_get_geometry () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: notify-osd crashed with signal 5 in _XReply() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/21/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0TY565 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd05/21/2007:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0TY565:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] No such file or directory: 'glxinfo' ** Affects: notify-osd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace vivid ** Information type changed from Private to Public -- 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/1440415 Title: notify-osd crashed with signal 5 in _XReply() Status in notify-osd package in Ubuntu: New Bug description: This occurred while logging in to dropbox ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: notify-osd 0.9.35+15.04.20150126-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 4 14:12:54 2015 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd GtkTheme: 'Ambiance' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2015-04-04 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Dell Inc. OptiPlex 745 ProcCmdline: /usr/lib/x86_64-linux-gnu/notify-osd ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=abeaca93-cffc-4dfe-a6cb-88771f3f4bab ro quiet splash RelatedPackageVersions: xserver-xorg 1:7.7+7ubuntu4 libgl1-mesa-glx 10.5.2-0ubuntu1 libdrm2 2.4.59-0ubuntu1 xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 xserver-xorg-video-ati 1:7.5.0-1ubuntu2 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetGeometry () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_window_get_geometry () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: notify-osd crashed with signal 5 in _XReply() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/21/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0TY565 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd05/21/2007:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0TY565:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. glxinfo:
[Dx-packages] [Bug 1429494] [NEW] Will not follow indexing settings
Public bug reported: In my privacy settings, I have turned off the option to index my music files. I have also put my music folders as well as banshee and audacious all into my exclude list All other music players have been uninstalled. I clear the usage data from all time, log out and back in, and yet I keep seeing music files in the search results in my dash. I just un- installed the music video lenses, and have the same results, it keeps listing music files. I simply do not want any music files to show up in the results. I am running Ubuntu 14.04 LTS x64, all updates have been installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: zeitgeist 0.9.14-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 20:14:40 2015 InstallationDate: Installed on 2014-08-31 (188 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1429494 Title: Will not follow indexing settings Status in zeitgeist package in Ubuntu: New Bug description: In my privacy settings, I have turned off the option to index my music files. I have also put my music folders as well as banshee and audacious all into my exclude list All other music players have been uninstalled. I clear the usage data from all time, log out and back in, and yet I keep seeing music files in the search results in my dash. I just un-installed the music video lenses, and have the same results, it keeps listing music files. I simply do not want any music files to show up in the results. I am running Ubuntu 14.04 LTS x64, all updates have been installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: zeitgeist 0.9.14-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 20:14:40 2015 InstallationDate: Installed on 2014-08-31 (188 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1429494/+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 1404147] Re: Screen is stretched when using dual monitors
Is this being worked on? Are there any known workarounds? (Besides switching to gnome-shell -- I ran into a bug there too! https://bugzilla.gnome.org/show_bug.cgi?id=741749 ) I'm the only one I know in real life or among my online contacts that doesn't use multiple monitors. It's especially frustrating since things had went from working great to suddenly not working in a regular update one day! ** Bug watch added: GNOME Bug Tracker #741749 https://bugzilla.gnome.org/show_bug.cgi?id=741749 -- 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/1404147 Title: Screen is stretched when using dual monitors Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: When I'm in dual monitor mode (not mirrored mode; mirrored mode works 100% fine), the applications are stretched, and my mouse clicks don't line up with the applications. See the attached image. Notice the highlighted text in the webpage near the middle of the two screens. My mouse was where the red dot was when I made that highlight. (The mouse doesn't show up in screenshots I guess.) I was supposed to have the application menu bar on both screens, but it and the menus only show up on the right screen. They work fine relatively, though sometimes as dropdown menus close they momentarily visibly stretch like the applications are. System information: I was running Ubuntu 14.04 with the nvidia-331 drivers, dual monitor mode was working great, but then in the last few weeks it started acting up like this often. Probably related to some recent updates I guess. Logging out and back in would sometimes fix it. I decided to do a full reinstall to 14.10, but now the issue always happens. The login screen and gnome-shell both work fine with dual monitor mode. (I'll boot up my computer, see the login screen on my left monitor with the background going to the right monitor exactly as it should, I'll log in with Unity selected, and then it suddenly decides to stretch everything ridiculously until I switch to single or mirrored monitor mode.) I do not get this specific issue when I use the default nouvea driver, but I do get tons of graphical artifacting and the screen freezes eventually when I'm in dual or mirrored monitor mode (single works fine), so that's not an option for me. I'm currently using the nvidia-331 version 331.113-0ubuntu0.1 package. I've tried downgrading to nvidia-331 version 331.89-0ubuntu5, and adding the xorg-edgers PPA and upgrading to nvidia-346, but the exact issue persisted. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1404147/+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 1393024] Re: Graphical corruption with hidpi scaling
** Changed in: unity Status: Incomplete = Confirmed ** Changed in: unity (Ubuntu) Status: Incomplete = Confirmed -- 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/1393024 Title: Graphical corruption with hidpi scaling Status in Compiz: New Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: With a hidpi scaling greater or equal than 2 there is graphical corruption of the window borders in gtk3 apps. Steps to reproduce: 1. Set hidpi scaling to 2. 2. Enlarge a window for nautilus or eye of gnome. Probably it is necessary to do resize the window more than one time to spot the problem. 3. See corrupted window border on the right and/or the bottom. Expected behavior: Clean rendering Ubuntu 14.10 64 Bit Compiz 0.9.12+14.10.20140918-0ubuntu1 Unity 7.3.1+14.10.20141016-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Nov 15 16:36:40 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:354e] InstallationDate: Installed on 2014-11-12 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-D3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=2a652086-a4da-44ed-ae7f-7b994401ef8b ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: GA-990FXA-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Nov 15 15:00:14 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1393024/+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 1362346] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1362346 Title: Dash/Hud/Spread search bar text doesn't honour the font scaling settings 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 Released Bug description: [ Impact ] Text scaling value is ignored by the dash search bar and the spread filter bar. - From u-c-c → accessibility → enable Big Text option Text should size should be increased in both search bar hint and content. [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell has the potential to introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1362346/+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 1362162] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1362162 Title: Dash buttons do not honour the text scaling 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 Released Bug description: [ Impact ] Text scaling value is ignored by dash buttons (filters and preview actions). - From u-c-c → accessibility → enable Big Text option Filters and preview action buttons should match this option. [ Test Case ] See above. [ Regression Potential ] Any code change in the Unity desktop shell has the potential to introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1362162/+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 1361751] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1361751 Title: Launcher Icon shortcut labels don't honor text scaling 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 Released Bug description: [ Impact ] Text scaling value is ignored by icons overlay text. - From u-c-c → accessibility → enable Big Text option Icons overlay text should honor that setting. [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell has the potential to introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for several weeks without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1361751/+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 1361679] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1361679 Title: Switcher Icons does not show progress emblem 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 Released Bug description: [ Impact ] - Open an application that shows progress information on its icon (i.e. nautilus or Hello Unity) - Open Alt-Tab switcher Expected behavior: - The icon should show the progress bar overlay Actual behavior: - No progress bar is shown. [ Test Case ] See above. [ Regression Potential ] Any change to Switcher rendering has the potential to mess up drawing icons in the Switcher or crashing Unity. [ Other Info ] The Ubuntu 14.04 LTS SRU was cherry-picked from the Ubuntu 14.10 release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1361679/+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 1384958] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1384958 Title: Ubuntu Desktop title is moved right as if the window buttons were there 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 Released Bug description: [ Impact ] 1. Open a maximized window 2. Hit Super+s 3. The Ubuntu Desktop title is moved some pixels to the right, as shown in the attached screenshot. [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell has the potential to introduce new crashes or lockups. [ Additional Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream Unity where it has been included in the Ubuntu Vivid Vervet dev release for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1384958/+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 1385285] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1385285 Title: Clicking in panel elements when the expo is active, performs to the maximized windows 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 Released Bug description: [ Impact ] 1. Open a maximized window (it must be focused when using global menus, not with LIMs) 2. Hit Super+s to enter in expo mode 3. Click in the panel, in different areas and you'll get: - top-left corner buttons will work (although when not visible) - grab area will make possible to grab and focus (when in LIM mode) a window [ Test Case ] See above. [ Regression Potential ] Any code change to the Unity desktop shell could potentially introduce new crashes or lockups. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream Unity where it has been in the Ubuntu Vivid Vervet dev release form several weeks without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1385285/+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 1383468] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1383468 Title: Windows in non-focused workspaces have not decorations in expo Status in Unity: Fix Committed Status in Unity 7.2 series: New Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [ Impact ] 1. Open multiple windows and put them in different workspaces 2. Hit Super+S to open the expo 3. Notice that windows that are not in the focused workspaces have no decorations [ Test Case ] See above: decorations should be present with fix. [ Regression Potential ] Decorations in the Spread could be drawn incorrectly. [ Other Info ] Fix for Ubuntu 14.01 LTS was cherry-picked from upstream Unity where it has been in production testing in Ubuntu Vivid Vervet dev release for a few months with no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1383468/+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 1375271] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1375271 Title: desktop or other past screen contents visible before lockscreen on resume Status in GNOME Screensaver: Invalid 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 Released Bug description: [Impact] On resume from suspend, screen contents are displayed for a brief time (perhaps 0.5 to 1 sec) before the lock dialog appears. These screen contents are not always the desktop or open application beneath the lock screen. On at least one occasion, the screen showed content from a full-screen video that had been playing in Firefox some time before the computer had been suspended: neither the video nor its underlying tab were open anymore, so the image(s) was likely part of a buffer somewhere. (Needless to say, if the wrong full-screen video had been watched, depending on the setting, this could be a quite serious issue for some users). [Test Case] Suspend and resume the computer (closing the lid or using the session indicator). Since this problem involves a race condition, it is not reliably reproducable at will. [Regression Potential] This fix unmaps windows when a suspend or shutdown event occurs: it is possible that the window(s) do not get remapped when a wake event occurs, or the wake even does not get propagated. This does not appear to occur in practice. [Other Info] The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where it has been released in the Ubuntu Vivid Vervet development release for a couple of months with no apparent regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/1375271/+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 1384910] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1384910 Title: Switching maximized windows using the spread might lead to wrong title and positioning 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 Released Bug description: [ Impact ] 1. Open at least two maximized windows 2. Select one of the windows (last opened seems better) 3. Hit Super + W 4. Start writing to select the other(s) window opened 5. Select it, hitting enter. The title will be wrong (the one of the previous title) while the window buttons will be in the wrong position (see attached sreenshot, in LIM mode, or empty panel otherwise). [ Test Case ] See above. [ Regression Potential ] Any change to the Unity desktop shell could potentially introducer a new crash or lockup. [ Additional Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from upstream Unity where it has been included in the Ubuntu Vivid Vervet dev release for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1384910/+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 1305440] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1305440 Title: Allow a distinct pam config file for greeter and for lock-screen Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Invalid Status in unity source package in Trusty: Fix Released Status in unity-greeter source package in Trusty: Invalid Bug description: [Impact] It might be desirable to have a distinct pam config file when logging in and when unlocking the screen. Specifically, using a fingerprint reader is fine for sudo or for unlocking, but you want to use your password when logging in, to provide a secret and be able to unlock the gnome-keyring for example. [Test Case] See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific- pam-config-in-the-lockscreen So this feature request is about allowing for a (optional) pam config file for the lock-screen, distinct from the /etc/pam.d/lightdm currently used and shared with the greeter. [Regression Potential] An additional configuration point could allow a system to be misconfigured for reduced security. The default configuration is to use the same PAM stack as the LightDM login process so no new regression is introduced without user modification. [Other Info] The Ubuntu 14.04 LTS SRU patch was cherry-picked from Ubuntu 14.10 where it has been in production use for a few months and appears stable. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305440/+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 1332509] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1332509 Title: Lockscreen misses arrow activator. 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 Released Bug description: [Impact] Unity lock screen password entry should have an activator arrow like unity-greeter. [Test Case] Using the Unity desktop shell, lock the screen using Super-L (or you favourite method). When the lockscreen is displayed, a little wedgie should be displayed at the right-hand end of the password entry field, and clicking on that wedgie should perform the authentication action. [Regression Potential] This is a cosmetic change to allow click-clicky mouse interaction to work just like hitting [Enter]. The biggest potential for regression is that the asset (artwork) does not get displayed or the mouse click does not work just like hitting Enter does. [Other Info] The Ubuntu 14.04 LTS SRU was cherry-picked from Ubuntu 14.10 whwere it has been in production use for some months without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1332509/+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 1301776] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1301776 Title: Update manager is really small and not resizeable Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in compiz package in Ubuntu: Triaged Status in unity package in Ubuntu: Fix Released Status in compiz source package in Trusty: Triaged Status in unity source package in Trusty: Fix Released Bug description: [ Impact ] update-manager 1:0.196.9, Ubuntu Trusty Update manager's window, and especially its fields inside the window, are way too small and also it's not resizeable, making it almost useless at least on my HiDPI screen (3200 x 1800). https://launchpadlibrarian.net/171657786/update-manager-is-small.png https://wiki.ubuntu.com/SoftwareUpdates#expanded: The Updates Available window should be manually resizable only when it is in this expanded state. [ Test Case ] Run the Ubuntu update manager and attempt to resize the window. See above. [ Regression Potential ] Any code change to the Unity desktop shell has the potential to introduce new crashes or lockups. [ Additional Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without apparent regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1301776/+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 1329584] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329584 Title: The label in the panel menu doesn't match the /etc/os-release NAME Status in Ubuntu Kylin: Fix Released 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 Released Bug description: [ Impact ] The label in the Unity Panel when the desktop is in the forground is not properly internationalizable or customizable for derivative distributrions. [ Test Case ] Install Ubuntu Kylin and observe the title in the Unity Panel when the desktop is in the foreground. [ Regression Potential ] Improperly implemented, this change could result in no label or an incorrect label displayed in the Unity Panel when the desktop is in the foreground. This does not appear to occur during testing. [ Additional Info ] The Ubuntu 14.04 LTS SRU has been cherry-picked from upstream Unity as released in Ubuntu 14.10 and has proved to be stable in daily use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1329584/+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 1302885] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1302885 Title: Media keyboard shortcuts not working 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 Released Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+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 1328677] Update Released
The verification of the Stable Release Update for unity 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 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1328677 Title: unity first-run stamp should not be in XDG_CACHE_HOME 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 Released Bug description: [ Impact ] The unity first_run.stamp file should not be in XDG_CACHE_HOME. As it is a _cache_, it can be ephemeral. Rather, it should be in XDG_CONFIG_HOME. Once the keyboard shortcut list, for example, has been presented, I don't need to be told about it again, even if I need to purge my ~/.cache directory. This is a problem at our site, where XDG_CACHE_HOME is stored on a temporary filesystem, to cut down on the tremendous amount of useless network traffic between workstations and the user's file server. As a result, users now have to learn about Unity keyboard shortcuts on every single login. [ Test Case ] On a non-fresh install, log in to the Unity desktop. The Shortcuts screen should ne be displayed. [ Regression Potential ] The regression potential in Ubuntu 14.04 LTS is nil since XDG_CONFIG_HOME is required to be writable in that distribution. [ Other Info ] The Ubuntu 14.04 LTS SRU was cherry-picked from Ubuntu 14.10 where the fix has been in production use for some time and has been stable. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1328677/+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
