[Dx-packages] [Bug 2063869] Re: Missing default cursor

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to dmz-cursor-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/2063869

Title:
  Missing default cursor

Status in Mutter:
  New
Status in dmz-cursor-theme package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  After upgrading from Ubuntu 23.10 to 24.04, the DMZ-White mouse
  pointer works correctly when the pointer is over a window, but shows a
  pale grey square when over the desktop or Ubuntu top bar. This appears
  to happen because the /usr/share/icons/DMZ-White/cursors/default file
  (or symlink) is missing. Doing the following appears to fix the
  problem:

  1. cd /usr/share/icons/DMZ-White/cursors
  2. ln -s left_ptr default
  3. In gnome-tweaks change to some other mouse pointer.
  4. In gnome-tweaks change back to DMZ-White.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: dmz-cursor-theme 0.4.5ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 18:39:40 2024
  Dependencies:
   
  InstallationDate: Installed on 2020-07-14 (1382 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: dmz-cursor-theme
  UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2063869/+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 1363277] Re: Indicator not shown in fallback mode when a subdir/file with the same name of icon exists in current work dir

[Bug Watch Updater]

** Changed in: solaar-unifying
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libappindicator in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1363277

Title:
  Indicator not shown in fallback mode when a subdir/file with the same
  name of icon exists in current work dir

Status in libappindicator:
  New
Status in Solaar:
  Fix Released
Status in libappindicator package in Ubuntu:
  Confirmed

Bug description:
  Take the attached python script and execute it in a non-unity desktop
  which does not support appindicators but can show gtk_status_icon (see
  at the end of the post under the "Tested on" paragraph).

  The attached script will fallback correctly to the old gtk_status_icon
  and will show the "battery-good" indicator icon on the system tray.

  Now exit from the script (with ^C).
  In your current directory create a subdir named "battery-good".
  Do not change directory and relaunch the script.

  The fallback mechanism will be unable to find the icon, and now the
  indicator will not be shown.

  The problem could be in app-indicator.c, near line 1641

  if (g_file_test(icon_name, G_FILE_TEST_EXISTS)) {
gtk_status_icon_set_from_file(icon, icon_name);
  }

  This code will find the subdir "battery-good" you created, and it will
  try to load it as a icon. But if it fails, as it does, it will never
  load an icon for your indicator.

  Tested on xubuntu 14.04.1 64bit  without indicator panel element and
  with indicator application removed from autostart. Tested also on
  Fedora 20 64bit with XFCE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libappindicator/+bug/1363277/+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] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_un

[Bug Watch Updater]

** Changed in: accountsservice
   Status: New => Fix Released

-- 
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 Released
Status in indicator-messages package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-messages.  This problem was most recently seen with package version 
13.10.1+18.10.20180918-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions


-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_un

[Bug Watch Updater]

** Changed in: accountsservice
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/2015962

Title:
  indicator-messages-service crashed with SIGSEGV in
  g_type_check_instance() from g_signal_handlers_disconnect_matched()
  from act_user_manager_finalize() from g_object_unref() from
  im_accounts_service_dispose()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  In Progress
Status in indicator-messages package in Ubuntu:
  Confirmed

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 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => Fix Released

-- 
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/1966905

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  free_fetch_user_request() [accountsservice]

Status in accountsservice:
  Fix Released
Status in gnome-control-center:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  This is now the #1 gnome-shell crasher in Ubuntu 23.04.

  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394
  https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114

  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now 

[Dx-packages] [Bug 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]

[Bug Watch Updater]

** Changed in: accountsservice
   Status: New => Fix Released

-- 
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/1966905

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  free_fetch_user_request() [accountsservice]

Status in accountsservice:
  Fix Released
Status in gnome-control-center:
  Unknown
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  This is now the #1 gnome-shell crasher in Ubuntu 23.04.

  https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394
  https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114

  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  

[Dx-packages] [Bug 422511] Re: problem with new scrollbar in Human theme - GtkRange::trough-border set to 2

[Bug Watch Updater]

** Changed in: firefox
   Importance: Medium => Unknown

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to human-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/422511

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  New
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/egtk/+bug/422511/+subscriptions


-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Bug Watch Updater]

** Changed in: dbus
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  New
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Released
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Released
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: 

[Dx-packages] [Bug 1966905] Re: Valgrind memory errors in gnome-shell 42 from accountsservice

[Bug Watch Updater]

** Changed in: accountsservice
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1966905

Title:
  Valgrind memory errors in gnome-shell 42 from accountsservice

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511== 
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: 

[Dx-packages] [Bug 1900068] Re: Upgrade to zeitgeist-1.0.3

[Bug Watch Updater]

** Changed in: zeitgeist (Debian)
   Status: Unknown => Fix Released

-- 
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/1900068

Title:
  Upgrade to zeitgeist-1.0.3

Status in zeitgeist package in Ubuntu:
  New
Status in zeitgeist package in Debian:
  Fix Released

Bug description:
  Please do upgrade zeitgeist from current 1.0.2 to 1.0.3.

  It is required for GNOME Activity Journal to work. GNOME Activity Journal has
  been ported to GTK3. It will be available in GNOME repos shortly.

  For more details:

  https://discourse.gnome.org/t/zeitgeist-gnome-activity-
  journal-1-0/4521

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1900068/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Confirmed
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel ModemManager[1308]:   Caught signal, 
shutting down...
  Apr 08 06:09:19 Keschdeichel systemd[1]: 

[Dx-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Bug Watch Updater]

** Changed in: accountsservice (Debian)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Released
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1832865] Re: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user

[Bug Watch Updater]

** Changed in: accountsservice
   Status: New => Fix Released

-- 
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/1832865

Title:
  gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index ->
  g_hash_table_lookup_node -> g_hash_table_lookup -> update_user

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.32.1-1ubuntu1~19.04.1, the problem page at 
https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 
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/1832865/+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 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Bug Watch Updater]

** Changed in: accountsservice
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Committed
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1695998] Re: geisview crash on Segmentation fault (17.04)

[Bug Watch Updater]

** Changed in: debian
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to geis in Ubuntu.
https://bugs.launchpad.net/bugs/1695998

Title:
  geisview crash on Segmentation fault (17.04)

Status in Geis:
  New
Status in geis package in Ubuntu:
  New
Status in Debian:
  Fix Released

Bug description:
  geisview from geis-tools_2.2.17+16.04.20160126-0ubuntu1_amd64 crash on 
segmentation fault on Ubuntu 17.04 with 4.10.0-21 kernel.
  Here the output:

  >> geisview
  /usr/lib/python3/dist-packages/geisview/classview.py:22: PyGIWarning: Gtk was 
imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
  Segmentation fault (core dumped)

  
  I'm new on this so please help me and tell me if I need to provide more 
information and how.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geis/+bug/1695998/+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 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Bug Watch Updater]

** Changed in: accountsservice (Debian)
   Status: Unknown => Confirmed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Bug Watch Updater]

** Changed in: accountsservice
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1855782] Re: Typo in the documentation: "systen" -> "system"

[Bug Watch Updater]

Launchpad has imported 2 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=786829.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-08-26T09:33:18+00:00 Laurent Bigonville wrote:

Hello,

There is apparently a typo in the dconf.7 manpage, the whatis entry
shows "A configuration systen"

should be "system"

The typo is in:
https://git.gnome.org/browse/dconf/tree/docs/dconf-overview.xml#n29

Original bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868233

Reply at:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1855782/comments/0


On 2017-08-29T01:19:51+00:00 Piotr Drąg wrote:

Thank you!

https://git.gnome.org/browse/dconf/commit/?id=9ac8f161962c8e2eeab2847caa036064d21e807f

Reply at:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1855782/comments/1


** Changed in: dconf
   Status: Unknown => Fix Released

** Changed in: dconf
   Importance: Unknown => Medium

** Bug watch added: Debian Bug tracker #868233
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868233

-- 
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/1855782

Title:
  Typo in the documentation: "systen" -> "system"

Status in dconf:
  Fix Released
Status in d-conf package in Ubuntu:
  Confirmed

Bug description:
  Found on 14.04, 16.04, and 18.04. 19.04 and later distributions have
  it fixed.

  The "NAME" section of dconf7
  manpage(http://manpages.ubuntu.com/manpages/bionic/man7/dconf.7.html)
  says "dconf - A configuration systen".

  "systen" should be a typo for "system".

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1855782/+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 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1222602

Title:
  [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class
  hardware and 943/945 graphics controllers

Status in Mesa:
  New
Status in Nux:
  Fix Released
Status in Release Notes for Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After the upgrade to Mesa 9.2.0 unity is barely usable.
  Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, 
using 100% cpu.

  A downgrade to mesa 9.1.6-2ubuntu2 restores full performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgl1-mesa-glx 9.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep  9 01:51:45 2013
  DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
  InstallationDate: Installed on 2013-09-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago)
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Sep  9 01:46:55 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1001 
   vendor HSD
  xserver.version: 2:1.14.2.901-2ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1222602/+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 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers

[Bug Watch Updater]

** Changed in: mesa
   Status: Confirmed => Unknown

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #727
   https://gitlab.freedesktop.org/mesa/mesa/issues/727

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1222602

Title:
  [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class
  hardware and 943/945 graphics controllers

Status in Mesa:
  Unknown
Status in Nux:
  Fix Released
Status in Release Notes for Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After the upgrade to Mesa 9.2.0 unity is barely usable.
  Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, 
using 100% cpu.

  A downgrade to mesa 9.1.6-2ubuntu2 restores full performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgl1-mesa-glx 9.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep  9 01:51:45 2013
  DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
  InstallationDate: Installed on 2013-09-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago)
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Sep  9 01:46:55 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1001 
   vendor HSD
  xserver.version: 2:1.14.2.901-2ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1222602/+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 1844158] Re: FTBFS using vala-0.46.1

[Bug Watch Updater]

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1736053.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-08-01T14:33:27+00:00 releng wrote:

libunity failed to build from source in Fedora rawhide/f31

https://koji.fedoraproject.org/koji/taskinfo?taskID=36635189


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix libunity at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
libunity will be orphaned. Before branching of Fedora 32,
libunity will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/comments/0


On 2019-08-01T14:33:30+00:00 releng wrote:

Created attachment 1597558
build.log

file build.log too big, will only attach last 32768 bytes

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/comments/1


On 2019-08-01T14:33:33+00:00 releng wrote:

Created attachment 1597559
root.log

file root.log too big, will only attach last 32768 bytes

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/comments/2


On 2019-08-01T14:33:35+00:00 releng wrote:

Created attachment 1597560
state.log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/comments/3


On 2019-08-13T18:26:50+00:00 bcotton wrote:

This bug appears to have been reported against 'rawhide' during the Fedora 31 
development cycle.
Changing version to 31.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/comments/4


On 2019-09-16T15:22:21+00:00 rdieter wrote:

Failure appears to be vala-related:

make[2]: Entering directory '/builddir/build/BUILD/libunity-7.1.4/src'
/usr/bin/valac -C -H unity.h -d . --gir=Unity-7.0.gir --library unity 
--internal-vapi=unity-internal.vapi --internal-header=unity-internal.h 
--target-glib=2.32 --thread --use-header --vapidir ../vapi --vapidir 
../protocol --vapidir . --pkg unity-protocol --pkg config --pkg unity-trace 
--pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 --pkg 
gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4  unity-appinfo-manager.vala 
unity-icon.vala unity-inspector.vala unity-io.vala unity-launcher.vala 
unity-category.vala unity-filters.vala unity-preferences-manager.vala 
unity-merge-strategy.vala unity-models.vala unity-search.vala 
unity-synchronizer.vala unity-previews.vala unity-result-activation.vala 
unity-scope-interface.vala unity-scope-dbus-connector.vala 
unity-scope-dbus-impl.vala unity-scope-channel.vala unity-deprecated-scope.vala 
unity-deprecated-scope-impl.vala unity-aggregator-scope.vala 
unity-aggregator-scope-private.vala unity-master-scope.vala 
unity-simple-scope.vala unity-scope-loader.vala unity-scope-tracker.vala 
unity-sound-menu.vala unity-sound-menu-mpris.vala unity-utils.vala
Command-line option `--thread` is deprecated and will be ignored
Compilation failed: 2 error(s), 0 warning(s)
BUILDSTDERR: unity-deprecated-scope.vala:64.3-64.28: error: Creation method of 
abstract class cannot be public.
BUILDSTDERR:   public DeprecatedScopeBase (string dbus_path_, string id_)
BUILDSTDERR:   ^^
BUILDSTDERR: unity-aggregator-scope.vala:54.3-54.24: error: Creation method of 
abstract class cannot be public.
BUILDSTDERR:   public AggregatorScope (string dbus_path_, string id_, MergeMode 
merge_mode = AggregatorScope.MergeMode.OWNER_SCOPE, bool proxy_filter_hints = 
false)
BUILDSTDERR:   ^^
BUILDSTDERR: make[2]: *** [Makefile:1389: libunity_la_vala.stamp] Error 1
make[2]: Leaving directory '/builddir/build/BUILD/libunity-7.1.4/src'
BUILDSTDERR: make[1]: *** [Makefile:571: all-recursive] Error 1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/comments/5


On 2019-09-16T15:24:42+00:00 mhroncok wrote:

*** Bug 1718302 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/comments/6


On 2019-09-16T15:32:25+00:00 rdieter wrote:

Reported 

[Dx-packages] [Bug 726033] Re: does not display icons until hovered

[Bug Watch Updater]

** Changed in: mesa
   Status: Confirmed => Unknown

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #334
   https://gitlab.freedesktop.org/mesa/mesa/issues/334

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/726033

Title:
  does not display icons until hovered

Status in Mesa:
  Unknown
Status in Nux:
  Fix Released
Status in Unity:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: unity-place-applications

  while unity-places-files and the unity launcher display their content
  on launching, unity-place-applications does not display anything until
  the respecting elements were activated (hovering, clicking). see
  screenshot for the look, where only a few icons were hovered.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity-place-applications 0.2.34-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Uname: Linux 2.6.38-5-generic i686
  Architecture: i386
  Date: Sun Feb 27 14:13:47 2011
  LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-place-applications
  --- 
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  CompositorRunning: compiz
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1400x1050 1400x1050 1280x1024 1280x1024 1280x960 1280x854 1280x800 
1280x720 1152x768 1024x768 1024x768 800x600 800x600 848x480 720x480 640x480 
640x480
   edid-base64: 
AP///wAwrkNPAQOAHhd46q8AmVhTjColUFQhCACBgAEBAQEBAQEBAQEBAQEBMCp4IFEaEEAwcBMAMeQQAAAYKCN4IFEaEEAwcBMAMeQQAAAYDwCQQzKQQygUBgAyDAAA/gBMUDE1MEUwNS1BMgogAJs=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroRelease: Ubuntu 11.04
  DistroVariant: ubuntu
  GdmLog1:
   
  GdmLog2:
   
  GraphicsCard:
   ATI Technologies Inc M66GL [ATI Mobility FireGL V5250] [1002:71d4] (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:20a4]
  LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  LiveMediaBuild_: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  LiveMediaBuild__: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227)
  MachineType: LENOVO 2007FVG
  Package: unity 3.4.6-0ubuntu1
  PackageArchitecture: i386
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  ProcVersionSignature_: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  ProcVersionSignature__: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Renderer: Unknown
  Tags: natty running-unity natty running-unity natty running-unity ubuntu 
compiz-0.9
  Uname: Linux 2.6.38-5-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 2007FVG
  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:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007FVG:pvrThinkPadT60p:rvnLENOVO:rn2007FVG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2007FVG
  dmi.product.version: ThinkPad T60p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.4-0ubuntu1
  version.libdrm2: libdrm2 2.4.23-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu8
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu11
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/726033/+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 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6

[Bug Watch Updater]

** Changed in: accountsservice
   Status: New => Fix Released

-- 
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/1841382

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup_node() / g_hash_table_lookup() from
  accountsservice 0.6.55-0ubuntu5/6

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d

  I do not know what triggered the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 25 20:45:09 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-24 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   ?? ()
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1841382/+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 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6

[Bug Watch Updater]

** Changed in: accountsservice
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1841382

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup_node() / g_hash_table_lookup() from
  accountsservice 0.6.55-0ubuntu5/6

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d

  I do not know what triggered the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 25 20:45:09 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-24 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   ?? ()
   ?? ()
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1841382/+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 1757594] Re: Please port your package away from Qt 4

[Bug Watch Updater]

** Changed in: appmenu-qt (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1757594

Title:
  Please port your package away from Qt 4

Status in appmenu-qt package in Ubuntu:
  Fix Released
Status in appmenu-qt package in Debian:
  Fix Released

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1757594/+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 1803808] Re: wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity

[Bug Watch Updater]

** Changed in: wireshark
   Status: Unknown => Fix Released

-- 
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/1803808

Title:
  wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity

Status in Wireshark:
  Fix Released
Status in appmenu-qt5 package in Ubuntu:
  Confirmed
Status in wireshark package in Ubuntu:
  Fix Released

Bug description:
  app crashed after close

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: wireshark-qt 2.6.3-1~ubuntu14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 16 13:16:50 2018
  ExecutablePath: /usr/bin/wireshark
  InstallationDate: Installed on 2015-07-27 (1177 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: wireshark
  Signal: 11
  SourcePackage: wireshark
  StacktraceTop:
   QIcon::~QIcon() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   QIcon::~QIcon() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: wireshark crashed with SIGSEGV in QIcon::~QIcon()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark

  (Reported originally as a private bug, this bug does not contain
  sensitive information)

  This is also reported as an error many times:
  https://errors.ubuntu.com/problem/ac9b86e48c6b6b5792c1128a836ba63213d62b44

To manage notifications about this bug go to:
https://bugs.launchpad.net/wireshark/+bug/1803808/+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 1803808] Re: wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity

[Bug Watch Updater]

** Changed in: wireshark
   Status: Won't Fix => Unknown

-- 
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/1803808

Title:
  wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity

Status in Wireshark:
  Unknown
Status in appmenu-qt5 package in Ubuntu:
  Confirmed
Status in wireshark package in Ubuntu:
  Fix Released

Bug description:
  app crashed after close

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: wireshark-qt 2.6.3-1~ubuntu14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 16 13:16:50 2018
  ExecutablePath: /usr/bin/wireshark
  InstallationDate: Installed on 2015-07-27 (1177 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: wireshark
  Signal: 11
  SourcePackage: wireshark
  StacktraceTop:
   QIcon::~QIcon() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   QIcon::~QIcon() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: wireshark crashed with SIGSEGV in QIcon::~QIcon()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark

  (Reported originally as a private bug, this bug does not contain
  sensitive information)

  This is also reported as an error many times:
  https://errors.ubuntu.com/problem/ac9b86e48c6b6b5792c1128a836ba63213d62b44

To manage notifications about this bug go to:
https://bugs.launchpad.net/wireshark/+bug/1803808/+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 1832865] Re: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user

[Bug Watch Updater]

** Changed in: accountsservice
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1832865

Title:
  gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index ->
  g_hash_table_lookup_node -> g_hash_table_lookup -> update_user

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.32.1-1ubuntu1~19.04.1, the problem page at 
https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 
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/1832865/+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 422511] Re: problem with new scrollbar in Human theme - GtkRange::trough-border set to 2

[Bug Watch Updater]

** Bug watch added: Mozilla Bugzilla #1552613
   https://bugzilla.mozilla.org/show_bug.cgi?id=1552613

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to human-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/422511

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  New
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/egtk/+bug/422511/+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 857651] Re: Unable to hide users from login screen / user switcher

[Bug Watch Updater]

** Changed in: sddm
   Status: Unknown => Fix Released

-- 
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/857651

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Unknown
Status in SDDM:
  Fix Released
Status in accountsservice package in Ubuntu:
  Triaged
Status in ceph package in Ubuntu:
  Triaged
Status in ifmail package in Ubuntu:
  Triaged
Status in libvirt package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in netqmail package in Ubuntu:
  Triaged
Status in sddm package in Ubuntu:
  Fix Released

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/857651/+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 390508] Re: notifyOSD ignores the expire timeout parameter

[Bug Watch Updater]

** Changed in: notify-osd (Debian)
   Status: Unknown => Confirmed

-- 
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/390508

Title:
  notifyOSD ignores the expire timeout parameter

Status in Ayatana Design:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Message Web:
  New
Status in notify-osd package in Ubuntu:
  Won't Fix
Status in notify-osd package in Arch Linux:
  New
Status in notify-osd package in Debian:
  Confirmed

Bug description:
  Binary package hint: libnotify-bin

  adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
  Description:  Ubuntu 9.04
  Release:  9.04
  adyroman@panther:~/libnotify-0.4.5/tools$ 

  adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
  libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
   *** 0.4.5-0ubuntu1 0
  500 http://ro.archive.ubuntu.com jaunty/universe Packages
  100 /var/lib/dpkg/status
  adyroman@panther:~/libnotify-0.4.5/tools$ 

  adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep 
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, _timeout,
notify_notification_set_timeout(notify, expire_timeout);
  adyroman@panther:~/libnotify-0.4.5/tools$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/390508/+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 528964] Re: toggle buttons look untoggled when the mouse is over them

[Bug Watch Updater]

** Changed in: murrine
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to human-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/528964

Title:
  toggle buttons look untoggled when the mouse is over them

Status in Murrine:
  Won't Fix
Status in gtk2-engines-murrine package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: human-theme

  A toggle button (such as the "QUESTION" button in the Lernid
  application when a chatroom is active) looks the same whether it is
  activated or not activated when the mouse is hovering over it.  It
  takes the pressed look while it is being clicked, but then takes the
  unpressed look as soon as the click is released, until the mouse moves
  away.  In the case I happened upon it, I didn't realize the button was
  a toggle at first because of this.  A related problem is that if a
  user toggles and untoggles the button repeatedly, until the mouse is
  moved there is no way to tell it is in the toggled or untoggled state.

  An active toggle button with the mouse over it should look different
  from an untoggled button.  Likewise, an untoggled button that is being
  pressed to toggle it should look different from a toggled button that
  is being pressed to untoggle it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/murrine/+bug/528964/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service

[Bug Watch Updater]

** Changed in: systemd-shim (Debian)
   Status: New => Fix Released

-- 
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/1359439

Title:
  [7.287663] systemd-logind[1057]: Failed to start unit
  user@126.service: Unknown unit: user@126.service

Status in NULL Project:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Utopic:
  Won't Fix
Status in systemd-shim source package in Utopic:
  Won't Fix
Status in systemd-shim package in Debian:
  Fix Released

Bug description:
  [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: 
Unknown unit: user@126.service
  [7.287677] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@126.service
  [7.293871] systemd-logind[1057]: New session c1 of user lightdm.
  [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/126/X11-display.
  [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team
  [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
  [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready
  [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec
  [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3)
  [9.920181] wlan0: authenticated
  [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3)
  [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 
status=0 aid=2)
  [9.927753] wlan0: associated
  [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [   12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope
  [   12.677122] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc1_2escope
  [   12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: 
Unknown unit: user@1000.service
  [   12.683912] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@1000.service
  [   12.685157] systemd-logind[1057]: New session c2 of user caravena.
  [   12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
  [  234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope
  [  234.494478] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc2_2escope
  [  235.514349] systemd-logind[1057]: New session c3 of user lightdm.
  [  244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope
  [  244.245923] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc3_2escope

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-7ubuntu4 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 20 18:26:06 2014
  InstallationDate: Installed on 2014-04-27 (115 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1359439/+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 1803808] Re: wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity

[Bug Watch Updater]

** Changed in: wireshark
   Status: Unknown => Won't Fix

-- 
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/1803808

Title:
  wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity

Status in Wireshark:
  Won't Fix
Status in appmenu-qt5 package in Ubuntu:
  New
Status in wireshark package in Ubuntu:
  Invalid

Bug description:
  app crashed after close

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: wireshark-qt 2.6.3-1~ubuntu14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 16 13:16:50 2018
  ExecutablePath: /usr/bin/wireshark
  InstallationDate: Installed on 2015-07-27 (1177 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: wireshark
  Signal: 11
  SourcePackage: wireshark
  StacktraceTop:
   QIcon::~QIcon() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   QIcon::~QIcon() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: wireshark crashed with SIGSEGV in QIcon::~QIcon()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark

  (Reported originally as a private bug, this bug does not contain
  sensitive information)

  This is also reported as an error many times:
  https://errors.ubuntu.com/problem/ac9b86e48c6b6b5792c1128a836ba63213d62b44

To manage notifications about this bug go to:
https://bugs.launchpad.net/wireshark/+bug/1803808/+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 820274] Re: [panel] Maximized window title switches to Arial font

[Bug Watch Updater]

** Changed in: gconf
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-2d in Ubuntu.
https://bugs.launchpad.net/bugs/820274

Title:
  [panel] Maximized window title switches to Arial font

Status in gconf:
  Won't Fix
Status in unity-2d:
  Fix Released
Status in unity-2d package in Ubuntu:
  Fix Released

Bug description:
  Window title switch to arial font after using Synaptic, so after have updated 
or installed some packages.
  Doesn't seem to happen in other occasions.
  Using unity-2d daily-ppa in Oneiric.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gconf/+bug/820274/+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 857651] Re: Unable to hide users from login screen / user switcher

[Bug Watch Updater]

** Changed in: accountsservice
   Status: Confirmed => Unknown

-- 
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/857651

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Unknown
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/857651/+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 941673] Re: performance of accounts-daemon is very poor

[Bug Watch Updater]

** Changed in: accountsservice
   Status: Confirmed => Unknown

-- 
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/941673

Title:
  performance of accounts-daemon is very poor

Status in accountsservice:
  Unknown
Status in accountsservice package in Ubuntu:
  In Progress
Status in accountsservice source package in Oneiric:
  Won't Fix
Status in accountsservice source package in Precise:
  In Progress

Bug description:
  Version 11.10

  
  The performance of accounts-daemon is unacceptable with large password and/or 
group files. We have appoximately 4 users in the passwords file and 16000 
lines in the group file. Having looked at the source, it appears to me the 
problem is that for each user is pulls from the password database (via 
getpwXXX)  its then calls getgroups to return the users list of groups.

  Getgroups must make a complete pass through the group file to determine the 
groups for the user. When initializing this results in
  reading the groups file 4 times.

  I think a better solution is to build a inverted group file map then first 
time getgroups is called by reading the entire group database and building a 
data structure indexed by username where a users group list can by found in a 
single lookup.
  Of couse, an even better solution would be for getgroups to do that itself, 
but that would require much larger code changes.

  I tried installed nscd to see if this would make a difference but no
  dice.

  At the moment, 11.10 is unusable for us because of this problem.

  Hope this is all the info you need.

  Regards, pdg

  p...@uow.edu.au

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/941673/+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 639891] Re: typing break should set status to 'busy' or 'away' in me menu

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-me in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/639891

Title:
  typing break should set status to 'busy' or 'away' in me menu

Status in gnome-control-center:
  Won't Fix
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-me package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-control-center

  I often have the typing break set to 10 mins during which time it
  would be useful for my status to be set to 'busy' or 'away' in
  Empathy/the Me Menu

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-control-center 1:2.31.91-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-25.43-generic-pae 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic-pae i686
  Architecture: i386
  Date: Wed Sep 15 20:50:11 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/639891/+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 406917] Re: Items in menus not selected when mouse against screen edge

[Bug Watch Updater]

** Changed in: murrine
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to human-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/406917

Title:
  Items in menus not selected when mouse against screen edge

Status in Murrine:
  Won't Fix
Status in human-theme package in Ubuntu:
  New

Bug description:
  Binary package hint: human-theme

  The 'Applications' and FUSA menus rest against the screen edges and
  yet when the mouse is against or very close to the edge the items in
  the menu are not highlighted and cannot be clicked.

  This is also an issue with the 'File' menu in maximised windows.

  This is not an issue in other themes, such as Dust.

  + encountered on ubuntu 9.04, jaunty jackalope
  + human-theme 0.28.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/murrine/+bug/406917/+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 1219898] Re: zeitgeist_event_constructv_full declaration makes impossible to compile with -Wunused-function

[Bug Watch Updater]

** Changed in: zeitgeist
   Status: Confirmed => Unknown

-- 
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/1219898

Title:
  zeitgeist_event_constructv_full declaration makes impossible to
  compile with -Wunused-function

Status in Vala:
  New
Status in Zeitgeist Framework:
  Unknown
Status in vala package in Ubuntu:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  The declaration of zeitgeist_event_constructv_full into zeitgeist-
  datamodel.h is static and this leads to a warning that makes
  impossible to compile with -Wunused-function.

  This seems mostly a Vala issue (maybe lead by
  https://bugzilla.gnome.org/show_bug.cgi?id=620675 ?), but the library
  should avoid to expose static symbols in a public header anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/vala/+bug/1219898/+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 970842] Re: zeitgeist-daemon memory/cpu leak when using privacy settings and dash search

[Bug Watch Updater]

** Changed in: zeitgeist
   Status: Confirmed => Unknown

-- 
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/970842

Title:
  zeitgeist-daemon memory/cpu leak when using privacy settings and dash
  search

Status in Activity Log Manager:
  Confirmed
Status in Zeitgeist Framework:
  Unknown
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  Reproduce the bug:
  

  - Open gnome control center
  - go to privacy settings
  - modify a setting (e.g. delete all history). Close it.
  - open dahsboard
  - search for anything

  The symptoms:
  

  - the temperature of CPU rises from 45 to 70 and the fan follows.
  - If you click 'delete history' on gnome center [privacy], you get this in 
terminal as stacktrace: [21:37:07.321048 CRITICAL] 
zeitgeist_engine_delete_events: assertion `_tmp0__length1 > 0' failed

  Workaround:
  ---

  - Kill zeitgeist-daemon  process
  or : user@pc:$~   zeitgeist-daemon --replace

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: zeitgeist 0.8.99~beta1-1
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  Date: Sun Apr  1 16:19:39 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: zeitgeist
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/activity-log-manager/+bug/970842/+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 422511] Re: problem with new scrollbar in Human theme - GtkRange::trough-border set to 2

[Bug Watch Updater]

** Changed in: firefox
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to human-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/422511

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  New
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/egtk/+bug/422511/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash

[Bug Watch Updater]

** Changed in: glib
   Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1506744

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Expired
Status in bamf package in Ubuntu:
  In Progress
Status in gnome-menus package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in gnome-menus source package in Xenial:
  Fix Released
Status in libunity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  I am running 15.10 development version fully up to date, I installed it a few 
days ago and I have an issue with newly installed applications not appearing in 
the dash when I search for them, they can be started via console but the 
icons/launchers of newly installed applications will only appear in the dash 
after session is restarted.

  [Test case]
  1. Install a new applicaiton (using apt-get or the software center)
  2. Make sure the application is listed in the Unity Dash

  [Possible Regressions]
  Unity fails to list all the applications, not just the newly installed ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 422511] Re: problem with new scrollbar in Human theme - GtkRange::trough-border set to 2

[Bug Watch Updater]

** Changed in: firefox
   Status: New => Unknown

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to human-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/422511

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  Unknown
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/egtk/+bug/422511/+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 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP

[Bug Watch Updater]

** Changed in: glib
   Status: Confirmed => Expired

-- 
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/1554878

Title:
  fix up usage of XDG_CURRENT_DESKTOP

Status in GLib:
  Expired
Status in Python XDG App:
  Confirmed
Status in empathy package in Ubuntu:
  Fix Released
Status in eog package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Fix Released

Bug description:
  Since being standardised XDG_CURRENT_DESKTOP supports specifying
  multiple Desktop Names seperated by a colon, however many of the
  patches in Ubuntu pre-date this change so don't correctly support the
  current format in some cases.

  These days XDG_CURRENT_DESKTOP will look something like
  Unity
  GNOME (gnome-shell)
  GNOME-Classic:GNOME (gnome-shell classic mode)
  GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use 
GNOME-Flashack:GNOME for this)

  Many of the patches only check for == "Unity" or == "GNOME", so
  misbehave for the latter cases in the list above.

  I suspect this will be more widespread than just nautilus, but fixing
  that would be a good start. Since most of this code is still Ubuntu
  specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc),
  probably taking the last value in the string would get the desired
  result of Unity vs GNOME3 behaviour

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Mar  9 15:04:36 2016
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1554878/+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 593003] Re: wishlist: Indicator-applet needs active chatrooms under "Chat"

[Bug Watch Updater]

** Changed in: empathy
   Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-applet in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/593003

Title:
  wishlist: Indicator-applet needs active chatrooms under "Chat"

Status in Empathy:
  Expired
Status in empathy package in Ubuntu:
  Triaged
Status in indicator-applet package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: indicator-applet

  I'm using Emapthy with IRC, and I'd really like to see the chatrooms I'm 
currently in listed below "Chat" in the messaging menu. That way, I would not 
need to have the chatroom windows open.
  Thanks!

  In my opinion, Empathy now has some inconsistency when it comes to clicking 
the X (close window):
  - X-ing away the main window (the one that lists contacts) leaves Empathy 
running
  - X-ing away chat windows closes the conversation(s), disconnecting chatrooms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/593003/+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 529229] Re: no buddy icon or incorrect buddy icon for facebook

[Bug Watch Updater]

** Changed in: empathy
   Status: New => Expired

-- 
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/529229

Title:
  no buddy icon or incorrect buddy icon for facebook

Status in Empathy:
  Expired
Status in empathy package in Ubuntu:
  Triaged
Status in notify-osd package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: empathy

  When a facebook contact becomes available, usually no buddy icon is
  displayed in the notification. Eventually an icon may be displayed
  after a long delay. Buddy icons should load from a cache for the
  notifications.

  When a facebook contact signs off, the wrong buddy icon may be shown,
  or it may show the correct icon initially, and then change to display
  the buddy icon of another contact. I think this is happening when
  multiple contacts sign off while the notification is still displayed.

  linux: Ubuntu 10.04 (Lucid) 64-bit
  empathy: 2.29.91-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/529229/+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 552543] Re: Empathy not showing notifications of a second user

[Bug Watch Updater]

** Changed in: empathy
   Status: New => Expired

-- 
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/552543

Title:
  Empathy not showing notifications of a second user

Status in Empathy:
  Expired
Status in empathy package in Ubuntu:
  Triaged
Status in notify-osd package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: empathy

  Steps to reproduce:

  1 - Open empathy as a certain user A and hide the chat window.
  2 - Make a first user B to send user A a couple of messages.
  3 - Immediately after, make a second user C send user A a message.

  User A should receive notifications for the messages of user B, but no
  notification for the messages of user C. But those notifications will
  afterwards appear whenever Empathy is interacted with somehow (opening
  a chat window, for example).

  According to investigation made by Nicolò Chieffo in Bug #476662, this
  is intended behavior in vanilla Empathy: the user is supposed to
  receive the remaining notifications only after clicking on the status
  icon. Empathy developers intend to keep it this way until there's a
  way to selectively open chat windows. Ubuntu Empathy, however, *does*
  have such a way already: the Messaging Menu.

  The code that "eats" notifications from the second user onwards should
  be modified to do so *only* if the regular status icon is being used
  (i.e. the messaging menu is not being used). Apparently, the logic is
  in empathy-status-icon.c.

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/552543/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

[Bug Watch Updater]

** Changed in: dconf
   Status: Confirmed => Fix Released

-- 
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/1735929

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Fix Released
Status in gnome-session:
  Fix Released
Status in d-conf package in Ubuntu:
  Fix Released
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Fix Released
Status in session-migration package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in d-conf source package in Bionic:
  Fix Released
Status in dconf source package in Bionic:
  Triaged
Status in gnome-session source package in Bionic:
  Fix Released
Status in session-migration source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Committed

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

[Bug Watch Updater]

** Changed in: gnome-session
   Status: Confirmed => Fix Released

-- 
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/1735929

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Fix Released
Status in d-conf package in Ubuntu:
  Fix Released
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  In Progress
Status in session-migration package in Ubuntu:
  Fix Released
Status in d-conf source package in Bionic:
  Fix Released
Status in dconf source package in Bionic:
  Triaged
Status in gnome-session source package in Bionic:
  In Progress
Status in session-migration source package in Bionic:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1735929/+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 1757594] Re: Please port your package away from Qt 4

[Bug Watch Updater]

** Changed in: appmenu-qt (Debian)
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1757594

Title:
  Please port your package away from Qt 4

Status in appmenu-qt package in Ubuntu:
  New
Status in appmenu-qt package in Debian:
  New

Bug description:
  Currently Qt 4 has been dead upstream and we are starting to have
  problems maintaining it, like for example in the OpenSSL 1.1 support
  case.

  Following in the footsteps of Debian[1], all packages directly or
  indirectly depending on qt4-x11 (like this one) must either get ported
  to Qt 5 and uploaded to the development release or get removed (by
  means of demotion to -proposed or removal of the package) before the
  19.04 release. If it is possible to port your package by the 18.10
  release, please do so.

  If you have any questions about porting or this transition, please ask
  in #ubuntu-qt (preferred) or directly ping me

  [1] https://wiki.debian.org/Qt4Removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1757594/+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 1068495] Re: Firefox 16.0.1 Crash Report [@ unity_webapps_available_application_get_application_domain ]

[Bug Watch Updater]

** Changed in: firefox
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity-webapps in Ubuntu.
https://bugs.launchpad.net/bugs/1068495

Title:
  Firefox 16.0.1 Crash Report [@
  unity_webapps_available_application_get_application_domain ]

Status in Mozilla Firefox:
  Won't Fix
Status in WebApps: libunity-webapps:
  Fix Released
Status in libunity-webapps package in Ubuntu:
  Fix Released
Status in libunity-webapps source package in Quantal:
  Fix Released
Status in libunity-webapps source package in Raring:
  Fix Released

Bug description:
  This has increased in frequency a lot since yesterday:

  https://crash-stats.mozilla.com/report/index/ea964fd9-9aca-
  41f8-a1b1-f9ca12121018

  Some comments:

  "Tried to use gmail integration with ubuntu 12.10 and firefox crashed"

  "opening a google calendar invite link from thunderbird"

  "I just opened facebook"

  "I click on view document in the gmail. What different: may be because
  I installed gmail plugin."

  Crashing thread:

  0 libunity-webapps-repository.so.0.0.0
unity_webapps_available_application_get_application_domain  
unity-webapps-available-application.c:65
  1 libxul.so   libxul.so@0x15cc717 
  2 libxul.so   ffi_callffi64.c:485
  3 libxul.so   js::ctypes::FunctionType::Call  CTypes.cpp:5576
  4 libxul.so   js::InvokeKerneljscntxtinlines.h:382
  5 libxul.so   js::Invoke  jsinterp.h:119
  6 libxul.so   js::IndirectProxyHandler::call  jsproxy.cpp:442
  7 libxul.so   js::DirectWrapper::call jswrapper.cpp:383
  8 libxul.so   js::CrossCompartmentWrapper::call   
jswrapper.cpp:777
  9 libxul.so   proxy_Call  jsproxy.cpp:1143
  10libxul.so   js::InvokeKerneljscntxtinlines.h:382
  11libxul.so   js::Interpret   jsinterp.cpp:2442
  12libxul.so   js::RunScript   jsinterp.cpp:301
  13libxul.so   js::InvokeKerneljsinterp.cpp:355
  14libxul.so   js::Invoke  jsinterp.h:119
  15libxul.so   js::IndirectProxyHandler::call  jsproxy.cpp:442
  16libxul.so   js::DirectWrapper::call jswrapper.cpp:383
  17libxul.so   js::CrossCompartmentWrapper::call   
jswrapper.cpp:777
  18libxul.so   proxy_Call  jsproxy.cpp:1143
  19libxul.so   js::InvokeKerneljscntxtinlines.h:382
  20libxul.so   js::Interpret   jsinterp.cpp:2442
  21libxul.so   js::RunScript   jsinterp.cpp:301
  22libxul.so   js::InvokeKerneljsinterp.cpp:355
  23libxul.so   js_fun_applyjsinterp.h:119
  24libxul.so   js::InvokeKerneljscntxtinlines.h:382
  25libxul.so   js::Interpret   jsinterp.cpp:2442
  26libxul.so   js::RunScript   jsinterp.cpp:301
  27libxul.so   js::InvokeKerneljsinterp.cpp:355
  28libxul.so   array_forEach   jsinterp.h:119
  29libxul.so   js::InvokeKerneljscntxtinlines.h:382
  30libxul.so   js::Interpret   jsinterp.cpp:2442
  31libxul.so   js::RunScript   jsinterp.cpp:301
  32libxul.so   js::InvokeKerneljsinterp.cpp:355
  33libxul.so   js_fun_applyjsinterp.h:119
  34libxul.so   js::InvokeKerneljscntxtinlines.h:382
  35libxul.so   js::Interpret   jsinterp.cpp:2442
  36libxul.so   js::RunScript   jsinterp.cpp:301
  37libxul.so   js::InvokeKerneljsinterp.cpp:355
  38libxul.so   js::Invoke  jsinterp.h:119
  39libxul.so   JS_CallFunctionValuejsapi.cpp:5604
  40libxul.so   nsXPCWrappedJSClass::CallMethod 
XPCWrappedJSClass.cpp:1436
  41libxul.so   nsXPCWrappedJS::CallMethod  XPCWrappedJS.cpp:580
  42libxul.so   PrepareAndDispatch  xptcstubs_x86_64_linux.cpp:121
  43libxul.so   libxul.so@0x10c1d02 
  44libxul.so   nsDocLoader::FireOnLocationChange   
nsDocLoader.cpp:1391
  45libxul.so   nsDocShell::CreateContentViewer 
nsDocShell.cpp:7698
  46libxul.so   nsDSURIContentListener::DoContent   
nsDSURIContentListener.cpp:119
  47libxul.so   nsDocumentOpenInfo::TryContentListener  
nsURILoader.cpp:678
  48libxul.so   nsDocumentOpenInfo::DispatchContent 
nsURILoader.cpp:375
  49libxul.so   nsDocumentOpenInfo::OnStartRequest  
nsURILoader.cpp:263
  50libxul.so   mozilla::net::nsHttpChannel::CallOnStartRequest 
nsHttpChannel.cpp:964
  51libxul.so   mozilla::net::nsHttpChannel::ContinueProcessNormal  
nsHttpChannel.cpp:1462
  52libxul.so   mozilla::net::nsHttpChannel::ProcessNormal  
nsHttpChannel.cpp:1397
  53libxul.so   mozilla::net::nsHttpChannel::ProcessResponse
nsHttpChannel.cpp:1310
  54libxul.so   mozilla::net::nsHttpChannel::OnStartRequest 

[Dx-packages] [Bug 798962] Re: g-c-c "automatic login" settings not working with lightdm

[Bug Watch Updater]

** Changed in: accountsservice
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/798962

Title:
  g-c-c "automatic login" settings not working with lightdm

Status in accountsservice:
  Won't Fix
Status in accountsservice package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Invalid
Status in accountsservice source package in Oneiric:
  Fix Released
Status in lightdm source package in Oneiric:
  Invalid

Bug description:
  Binary package hint: gnome-control-center

  sytem, user accounts, select user, unlock, enter sudo pw, change
  "Automatic Login" to Yes, close window.  drill into it,  "Automatic
  Login" is No.  Set to yes again, reboot, not logged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.0.2-1ubuntu4
  ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3
  Uname: Linux 3.0-1-generic x86_64
  Architecture: amd64
  Date: Fri Jun 17 16:01:44 2011
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANGUAGE=en_US:
   LANG=en_US
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/798962/+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 982499] Re: dconf-editor always prints warnings: "Unknown property on "

[Bug Watch Updater]

** Changed in: d-conf (Debian)
   Status: New => Incomplete

-- 
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/982499

Title:
  dconf-editor always prints warnings: "Unknown property on "

Status in d-conf package in Ubuntu:
  Confirmed
Status in d-conf package in Debian:
  Incomplete

Bug description:
  When I start dconf-editor, these four warnings are logged:

  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:330: Unknown 
property on , extends
  >
  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:330: Unknown 
property on , extends
  >
  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:401: Unknown tag 

  >
  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:401: Unknown tag 


  It doesn't seem to affect operations so I'm setting the initial
  importance to "Low".

  This is reproducible for me every time I start dconf-editor from the
  command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/982499/+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 727089] Re: indicator-datetime-preferences crashed with SIGSEGV in g_utf8_normalize()

[Bug Watch Updater]

** Changed in: gtk
   Status: New => Expired

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/727089

Title:
  indicator-datetime-preferences crashed with SIGSEGV in
  g_utf8_normalize()

Status in GTK+:
  Expired
Status in Indicator Date and Time:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-datetime source package in Natty:
  Fix Released

Bug description:
  Binary package hint: indicator-datetime

  I was trying to add more time location to be shown.

  I can't reproduce this bug

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: indicator-datetime 0.1.95-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Uname: Linux 2.6.38-5-generic i686
  Architecture: i386
  Date: Tue Mar  1 11:39:34 2011
  ExecutablePath: /usr/bin/indicator-datetime-preferences
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110212)
  ProcCmdline: indicator-datetime-preferences
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x1f3b37:  cmpb   $0x0,(%esi)
   PC (0x001f3b37) ok
   source "$0x0" ok
   destination "(%esi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? () from /lib/libglib-2.0.so.0
   g_utf8_normalize () from /lib/libglib-2.0.so.0
   gtk_entry_completion_complete () from /usr/lib/libgtk-x11-2.0.so.0
   ?? ()
   ?? ()
  Title: indicator-datetime-preferences crashed with SIGSEGV in 
g_utf8_normalize()
  UpgradeStatus: Upgraded to natty on 2011-02-24 (4 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XsessionErrors: (nautilus:1866): GConf-CRITICAL **: gconf_value_free: 
assertion `value != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/727089/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

[Bug Watch Updater]

** Changed in: gnome-session
   Status: Unknown => Confirmed

** Changed in: gnome-session
   Importance: Unknown => Medium

-- 
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/1735929

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Confirmed
Status in d-conf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Triaged
Status in session-migration package in Ubuntu:
  Confirmed

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

[Bug Watch Updater]

** Changed in: dconf
   Status: Unknown => Confirmed

** Changed in: dconf
   Importance: Unknown => Medium

-- 
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/1735929

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Unknown
Status in d-conf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Triaged
Status in session-migration package in Ubuntu:
  Confirmed

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1735929/+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 1071738] Re: Indicator scroll event says direction UP on 12.10 even when scrolling down

[Bug Watch Updater]

** Changed in: pygobject
   Status: Unknown => Expired

** Changed in: pygobject
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libappindicator in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1071738

Title:
  Indicator scroll event says direction UP on 12.10 even when scrolling
  down

Status in pygobject:
  Expired
Status in libappindicator package in Ubuntu:
  Fix Released
Status in libappindicator source package in Trusty:
  Fix Released
Status in libappindicator source package in Utopic:
  Fix Released

Bug description:
  * Impact
  Scrolling on indicators report the wrong scroll event

  * Test case
  run the program from comment #6, scroll on the indicator, check that the 
right direction information is outputed

  * Regression potentiel
  check that scrolling on indicators still work where it used to do something

  ---

  I am using AppIndicator via Python. On Ubuntu 12.10 (stock install,
  python-appindicator: Installed: 12.10.0-0ubuntu1) when I listen for
  scroll event signals, the direction is always reported as UP, never as
  DOWN - even when scrolling down. This was working on 12.04.

  My application variety depends on this functionality, here is the
  relevant bug report for it:
  https://bugs.launchpad.net/variety/+bug/1071598

  Here is sample code to demonstrate the problem (OK on 12.04, buggy on
  12.10):

  from gi.repository import Gtk, Gdk, AppIndicator3

  if __name__ == "__main__":
  menu = Gtk.Menu()
  quit = Gtk.MenuItem("Quit")
  quit.connect("activate", Gtk.main_quit)
  menu.append(quit)
  menu.show_all()

  def scroll(ind, steps, direction):
  print steps, direction
  if direction != Gdk.ScrollDirection.UP:
  print "Things seem ok"

  indicator = AppIndicator3.Indicator.new('testscroll', '', 
AppIndicator3.IndicatorCategory.APPLICATION_STATUS)
  indicator.set_status(AppIndicator3.IndicatorStatus.ACTIVE)
  indicator.set_icon("/usr/share/pixmaps/firefox.png")
  indicator.connect("scroll-event", scroll)
  indicator.set_menu(menu)
  Gtk.main()

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/1071738/+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 1259562] Re: Old guest users pollute accountsservice

[Bug Watch Updater]

** Changed in: accountsservice
   Status: Confirmed => Fix Released

-- 
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/1259562

Title:
  Old guest users pollute accountsservice

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  When you log out from a guest session, the temporary guest account is
  removed - but only almost. The folder /var/lib/AccountsService/users
  gets 'polluted' with files for previous guest users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1259562/+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 1233760] Re: Sure way to crash Gnome-Shell in Ubuntu 13.10 and Ubuntu Gnome 13.10

[Bug Watch Updater]

** Changed in: dconf (Fedora)
   Status: Unknown => Won't Fix

** Changed in: dconf (Fedora)
   Importance: Unknown => Undecided

-- 
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/1233760

Title:
  Sure way to crash Gnome-Shell in Ubuntu 13.10 and Ubuntu Gnome 13.10

Status in d-conf package in Ubuntu:
  Confirmed
Status in dconf package in Fedora:
  Won't Fix

Bug description:
  This affects Gnome-Shell 3.8 up to the latest build from
  Gnome3-Staging Gnome-Shell 3.10 on Ubuntu 13.10 and Ubuntu Gnome 13.10
  daily builds, as of today!

  1. Start gnome-terminal (has to be gnome-terminal - other term apps don't 
appear to produce this bug).
  2. run sudo su and enter your password
  3. run gedit or nautilus but definitely gedit is confirmed by 1 other person
  4. Flick your mouse up to Activities
  5. Gnome-Shell is dead

  ctrl+alt+f1 - login and run stop gdm or stop lightdm depending on your Ubuntu 
build
  start lightdm or gdm - attempt to login to gnome - no desktop will appear and 
if you switch back to the console you can see gnome-shell running like crazy.

  I've tried killing X, and confirmed all gnome service aren't running
  then tried start gdm or start lightdm and still nothing works.

  Have to restart PC to recover.

  Happy to test this and give you any logs you need.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1233760/+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 1017125] Re: [SRU quantal] boost::unordered_multimap<>::erase(iterator, iterator) broken in boost1.49

[Bug Watch Updater]

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=806236.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-03-23T09:43:09+00:00 Anton wrote:

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:/usr/lib64/libreoffice/program/soffice.bin --impress 
file:///home/anton/Customer%20Portal%20Internal_03202012.odp --splash-pipe=6
crash_function: std::list::begin
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 3.3.0-3.tip0.uprobes.fc17.x86_64
pid:18424
pwd:/home/anton
reason: Process /usr/lib64/libreoffice/program/soffice.bin was killed 
by signal 11 (SIGSEGV)
time:   Fri 23 Mar 2012 09:42:27 CET
uid:1000
username:   anton

backtrace:  Text file, 69241 bytes
dso_list:   Text file, 20606 bytes
maps:   Text file, 88339 bytes

environ:
:GIT_PS1_SHOWDIRTYSTATE=true
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=bandura.brq.redhat.com
:LC_MONETARY=en_GB.utf8
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:GIO_LAUNCHED_DESKTOP_FILE_PID=18410
:GPG_AGENT_INFO=/tmp/keyring-XLyyPc/gpg:0:1
:SHELL=/bin/bash
:TERM=xterm-256color
:DESKTOP_STARTUP_ID=nautilus-18399-bandura.brq.redhat.com-libreoffice-0_TIME6183650
:HISTSIZE=1000
:XDG_SESSION_COOKIE=140f39c967431aadf43a7e320010-1332485955.765921-668108218
:GJS_DEBUG_OUTPUT=stderr
:G_MESSAGES_DEBUG=all
:LC_NUMERIC=en_GB.utf8
:OLDPWD=/usr/lib64/libreoffice/program
:QTDIR=/usr/lib64/qt-3.3
:GNOME_KEYRING_CONTROL=/tmp/keyring-XLyyPc
:QTINC=/usr/lib64/qt-3.3/include
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:IMSETTINGS_MODULE=none
:USER=anton
:SSH_AUTH_SOCK=/tmp/keyring-XLyyPc/ssh
:USERNAME=anton
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1117,unix/unix:/tmp/.ICE-unix/1117
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/libreoffice-impress.desktop
:MAIL=/var/spool/mail/anton
:PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/anton/.local/bin:/home/anton/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/anton
:XMODIFIERS=@im=none
:EDITOR=vim
:KDE_IS_PRELINKED=1
:GNOME_KEYRING_PID=1109
:LANG=en_GB.utf8
:GDM_LANG=en_GB.utf8
:KDEDIRS=/usr
:LC_MEASUREMENT=en_GB.utf8
:GIT_PS1_SHOWUNTRACKEDFILES=true
:GDMSESSION=gnome
:SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
:HISTCONTROL=ignoredups
:XDG_SEAT=seat0
:HOME=/home/anton
:SHLVL=1
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SAL_ENABLE_FILE_LOCKING=1
:LOGNAME=anton
:PRINTER=brno1-3rd-cafe
:QTLIB=/usr/lib64/qt-3.3/lib
:CVS_RSH=ssh
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-7mbsOmI4UG,guid=a900ddf0010ccf66132eecc7003f
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:BROWSER=google-chrome
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/anton
:DISPLAY=:0.0
:LC_TIME=en_GB.utf8
:XAUTHORITY=/var/run/gdm/auth-for-anton-S0MDkT/database
:LD_LIBRARY_PATH=/usr/java/jre1.7.0_03/lib/amd64/client:/usr/java/jre1.7.0_03/lib/amd64/server:/usr/java/jre1.7.0_03/lib/amd64/native_threads:/usr/java/jre1.7.0_03/lib/amd64

var_log_messages:
:Mar 23 09:42:27 bandura kernel: [ 6247.104768] soffice.bin[18424]: segfault at 
a0 ip 003bc9fba958 sp 7fff1af30e50 error 4 in 
libvcllo.so[3bc9e0+7dd000]
:Mar 23 09:42:28 bandura abrt[18500]: Saved core dump of pid 18424 
(/usr/lib64/libreoffice/program/soffice.bin) to 
/var/spool/abrt/ccpp-2012-03-23-09:42:27-18424 (129572864 bytes)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1017125/comments/0


On 2012-03-23T09:43:14+00:00 Anton wrote:

Created attachment 572211
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1017125/comments/1


On 2012-03-23T09:43:16+00:00 Anton wrote:

Created attachment 572212
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1017125/comments/2


On 2012-03-23T09:43:19+00:00 Anton wrote:

Created attachment 572214
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1017125/comments/3


On 2012-03-23T12:29:54+00:00 Caolan wrote:

some kind of busted lifecycle.

Was this on closing an impress frame ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1017125/comments/4


On 2012-03-26T06:16:51+00:00 Anton wrote:

I can guess only, but IIRC it was on the close of impress.

Reply at:

[Dx-packages] [Bug 897212] Re: lightdm ignores session selection of ldap users

[Bug Watch Updater]

Launchpad has imported 45 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=617465.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-07-23T07:04:08+00:00 Karel wrote:

Description of problem:

GDM ignores user's default session, it is always set to GNOME no matter
what content is stored ~/.dmrc.


Version-Release number of selected component (if applicable):

gdm-2.30.2-1.fc13.x86_64.rpm,

How reproducible:

Always.


Steps to Reproduce:
1. Install other windows manager (I tried with xmonad and awesome), or simply 
create *.session representing raw X session.
2. Login to the newly created session using GDM
3. Log out
  
Actual results:

After logging out from Awesome the Awesome session should be selected as
default, but GNOME is selected as default session although the Awesome
is shown as default session in ~/.dmrc.

Expected results:

After logging out from Awesome window manager is selected as user's
default session.

Additional info:

This works on Fedora 12, with gdm-2.28.2.3.fc12, so it must be a
regression.

I'm using custom gnome-session configuration which launches special
Gnome session where Awesome replaces panel and window manager, however
the issue occurs even if Awesome is run in the standalone mode or an raw
Xsession is launched.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/897212/comments/0


On 2010-08-02T10:00:17+00:00 Tajidin wrote:

This bug has been triaged


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Reply at:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/897212/comments/1


On 2010-11-04T19:23:18+00:00 Andrew wrote:

I have run across this problem, too, on Fedora 14.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/897212/comments/2


On 2011-05-02T21:37:47+00:00 Andrew wrote:

I have confirmed that this is still a problem in Fedora 15.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/897212/comments/3


On 2011-05-02T21:46:44+00:00 Ray wrote:

we don't look at ~/.dmrc .  GDM now uses the account service to choose
default session.

Is

/var/lib/AccountsService/users

getting updated after you choose your session and log in?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/897212/comments/4


On 2011-05-02T22:02:34+00:00 Andrew wrote:

After logging in once, GDM "remembers" the session.  Unfortunately, if
you log in on a different machine in a computer lab or reinstall, it
"forgets" the session again.  I understand that GDM can't (and
shouldn't) write to users' home directories, but it should at least be
reading the file in the home directories and honoring their explicit
configuration.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/897212/comments/5


On 2011-06-21T15:31:44+00:00 Fedora wrote:

This package has changed ownership in the Fedora Package Database.
Reassigning to the new owner of this component.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/897212/comments/6


On 2011-06-21T15:33:46+00:00 Fedora wrote:

This package has changed ownership in the Fedora Package Database.
Reassigning to the new owner of this component.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/897212/comments/7


On 2011-06-21T15:36:33+00:00 Fedora wrote:

This package has changed ownership in the Fedora Package Database.
Reassigning to the new owner of this component.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/897212/comments/8


On 2011-06-21T15:39:47+00:00 Fedora wrote:

This package has changed ownership in the Fedora Package Database.
Reassigning to the new owner of this component.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/897212/comments/9


On 2011-06-21T15:49:13+00:00 Fedora wrote:

This package has changed ownership in the Fedora Package Database.
Reassigning to the new owner of this component.

Reply at:

[Dx-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

[Bug Watch Updater]

** Changed in: sddm (Ubuntu)
   Status: Invalid => Fix Released

-- 
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/1667113

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  Confirmed
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in ifmail package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Fix Released

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+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 1683516] Re: indicator-messages is not shown in mate-panel on Ubuntu 16.04 LTS MATE

[Bug Watch Updater]

** Changed in: indicator-messages
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-applet in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1683516

Title:
  indicator-messages is not shown in mate-panel on Ubuntu 16.04 LTS MATE

Status in Messaging Menu:
  New
Status in indicator-applet package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in mate-indicator-applet package in Ubuntu:
  New
Status in mate-panel package in Ubuntu:
  New

Bug description:
  it is known that messaging menu returned in Ubuntu MATE 16.10 (https
  ://ubuntu-mate.community/t/messaging-menu-is-making-a-return-
  in-16-10/7268/9), but there is no such menu in Ubuntu 16.04 LTS MATE
  even with ppa:ubuntu-mate-dev/xenial-mate enabled.

  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS MATE.
  2. Install 'indicator-applet-complete' and 'indicator-messages' packages
  3. Add Indicator Applet Complete to the mate-panel.
  4. Launch Thunderbird - this should enable Envelope/Letter icon in 
'mate-panel' and set corresponding config (check with "dconf read 
/com/canonical/indicator/messages/applications" = "['thunderbird.desktop']").

  Expected results:
  Envelope/Letter ('indicator-messages') icon is shown in 
'indicator-applet-complete' inside 'mate-panel' and is usable by Thunderbird or 
mailnag.

  Actual results:
  Envelope/Letter ('indicator-messages') is not shown and is not usable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-messages/+bug/1683516/+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 438868] Re: Numerous applications have focus issues after emerging from a screensaver or suspend

[Bug Watch Updater]

Launchpad has imported 14 comments from the remote bug at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=298261.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-12-19T21:17:22+00:00 5-seter-r wrote:

Build Identifier: M20090917-0800

When waking up after having gone into screen saver mode, Eclipse is 
unresponsive 
to keystrokes. Mouse still works.

Workaround 1:
- switch workspace and back. I mean X workspaces, not Eclipse workspaces. Eg. 
CTRL-ALT-RIGHTARROW followed by CTRL-ALT_LEFTARROW.

Workaround 2:
- restart Eclipse

Reproducible: Always

Steps to Reproduce:
1. Start Eclipse and work a bit, then leave it alone until the screen saver 
kicks in (simple screen fading to black in my case). Make sure you have eg. an 
editor open (in my case a java file, but I don't think it matters).
2. Wake it up again eg. by moving the mouse
3. Try typing: it doesn't work!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/52


On 2009-12-19T21:19:17+00:00 5-seter-r wrote:

Some additional system info:
- Ubuntu 9.10 64bit (x86_64)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/53


On 2009-12-19T21:32:49+00:00 Francis Upton wrote:

Might this be related to the GTK changes with Karmic (I'm on Jaunty and
have no trouble).

http://blog.export.be/2009/10/fixing-eclipse-for-ubuntu-karmic-koala-9-10/
https://bugs.eclipse.org/bugs/show_bug.cgi?id=287307

You might try the workaround suggested in the blog posting.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/54


On 2009-12-19T22:48:41+00:00 5-seter-r wrote:

I'm pretty confident it's not related to the GTK changes. I have the
GDK_NATIVE_WINDOWS workaround applied for over a month now, but that
didn't help this issue at all. Moreover, I already had this problem when
I was still on Jaunty and even before that. It's maybe x86_64 related?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/55


On 2009-12-19T23:09:17+00:00 Francis Upton wrote:

(In reply to comment #3)
>. It's maybe x86_64 related?
I'm on X86_64.  Have you tried a non-Eclipse application under the same 
circumstances?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/56


On 2010-01-04T18:15:42+00:00 Ob1-eclipse wrote:

Moving to SWT for comments.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/58


On 2010-04-07T18:35:46+00:00 Samuelwestbrook wrote:

I'm observing this running on Ubuntu 9.1 and Dell Optiplex 755. All
updates to OS and Eclipse have been applied. The problem also occurs if
"lcok screen" is chosen and then the screen unlocked for reuse. Clicking
to another progam and back makes Eclipse responsive again. No other
applications have shown the same effect.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/84


On 2010-05-31T01:33:56+00:00 Remy Chi Jian Suen wrote:

*** Bug 315010 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/114


On 2010-07-01T18:31:51+00:00 Pinnamur wrote:

*** Bug 318064 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/118


On 2010-07-02T13:54:44+00:00 Mikhail-zabaluev wrote:

(In reply to comment #6)
> No other applications have shown the same
> effect.

Firefox has a similar problem, which appeared at the same Ubuntu upgrade:
https://bugzilla.mozilla.org/show_bug.cgi?id=507269

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/119


On 2010-07-03T17:17:47+00:00 5-seter-r wrote:

It is somehow related to the compiz window manager. When using metacity
instead of compiz the problem seems to be gone.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/438868/comments/120


On 

[Dx-packages] [Bug 1605478] Re: supertux2 segfaults on native Mir with SDL_VIDEODRIVER=mir trying to call glXQueryVersion

[Bug Watch Updater]

** Changed in: glew
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to glew in Ubuntu.
https://bugs.launchpad.net/bugs/1605478

Title:
  supertux2 segfaults on native Mir with SDL_VIDEODRIVER=mir trying to
  call glXQueryVersion

Status in Glew:
  Fix Released
Status in glew package in Ubuntu:
  Triaged
Status in libsdl2 package in Ubuntu:
  Invalid
Status in supertux package in Ubuntu:
  Invalid

Bug description:
  supertux2 crashes on native Mir, trying to call GLX functions...

  Thread 1 "supertux2" received signal SIGSEGV, Segmentation fault.
  0x7519a95d in XQueryExtension ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  (gdb) bt
  #0  0x7519a95d in XQueryExtension ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #1  0x7518e4c2 in XInitExtension ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #2  0x76f8269c in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  #3  0x76f7e041 in glXQueryVersion ()
 from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  #4  0x76d2eb34 in glxewInit ()
 from /usr/lib/x86_64-linux-gnu/libGLEW.so.1.13
  #5  0x00560eeb in GLRenderer::GLRenderer() ()
  #6  0x0055e153 in GLVideoSystem::GLVideoSystem() ()
  #7  0x004f4b85 in VideoSystem::create(VideoSystem::Enum) ()
  #8  0x004ad662 in Main::launch_game() ()
  #9  0x004af0ad in Main::run(int, char**) ()
  #10 0x004a9f13 in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/glew/+bug/1605478/+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 789123] Re: Eclipse crashes/quits without any error messages

[Bug Watch Updater]

** Changed in: eclipse
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to overlay-scrollbar in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/789123

Title:
  Eclipse crashes/quits without any error messages

Status in Eclipse:
  Invalid
Status in overlay-scrollbar package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: eclipse

  Installed software:
CollabNet Merge Client  2.2.3   
com.collabnet.subversion.merge.feature.feature.group
Eclipse IDE for Java Developers 1.3.2.20110301-1807 epp.package.java
Eclipse Web Developer Tools 
3.2.3.v201102160541-7O7CFbWEMf84qYjGDyP3DNEwcgFU
org.eclipse.wst.web_ui.feature.feature.group
ERMaster1.0.0.v20101001-0024org.insightech.er.feature.feature.group
Google App Engine Java SDK 1.4.01.4.0.v201012021502 
com.google.appengine.eclipse.sdkbundle.e36.feature.1.4.0.feature.group
Google Plugin for Eclipse 3.6   2.3.0.r36v201104261928  
com.google.gdt.eclipse.suite.e36.feature.feature.group
Google Web Toolkit SDK 2.1.12.1.1.v201012170127 
com.google.gwt.eclipse.sdkbundle.e36.feature.2.1.1.feature.group
JNA Library 3.2.7   com.sun.jna.feature.group
Maven Integration for Eclipse (Required)0.12.1.20110112-1712
org.maven.ide.eclipse.feature.feature.group
Subversive Revision Graph (Optional) (Incubation)   0.7.9.I20110124-1700
org.eclipse.team.svn.revision.graph.feature.group
Subversive SVN Connectors   2.2.2.I20110124-1700
org.polarion.eclipse.team.svn.connector.feature.group
Subversive SVN Integration for the Mylyn Project (Optional) (Incubation)
0.7.9.I20110207-1700org.eclipse.team.svn.mylyn.feature.group
Subversive SVN JDT Ignore Extensions (Optional) (Incubation)
0.7.9.I20101203-1700
org.eclipse.team.svn.resource.ignore.rules.jdt.feature.group
Subversive SVN Team Provider (Incubation)   0.7.9.I20110207-1700
org.eclipse.team.svn.feature.group
SVNKit 1.3.5 Implementation (Optional)  2.2.2.I20110124-1700
org.polarion.eclipse.team.svn.connector.svnkit16.feature.group


  Problem:
  When working on Java-classes my Eclipse can suddenly decide to just quit. No 
"Saving workspace" or nothing, it just disappears just like that. This 
typically happens around twice per day. The latest crash today came when i was 
asking for code completion pop-up to appear for a class i was working on.

  I have not found any logs or anything that gives any information about
  these crashes, so please give me some tips for logs you want me to
  check. (This is not serious enough to get in the syslog/dmesg)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: eclipse (not installed)
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri May 27 14:59:00 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eclipse
  UpgradeStatus: Upgraded to natty on 2011-04-29 (28 days ago)
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 11.04
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  NonfreeKernelModules: nvidia
  Package: openjdk-6-jre-headless 6b22-1.10.1-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Tags:  natty
  Uname: Linux 2.6.38-8-generic x86_64
  UpgradeStatus: Upgraded to natty on 2011-04-29 (31 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/789123/+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 1645799] Re: Please remove google-mock, gtest (replaced by googletest)

[Bug Watch Updater]

** Changed in: gtest (Debian)
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to google-mock in Ubuntu.
https://bugs.launchpad.net/bugs/1645799

Title:
  Please remove google-mock,gtest (replaced by googletest)

Status in google-mock package in Ubuntu:
  New
Status in gtest package in Ubuntu:
  New
Status in gtest package in Debian:
  Fix Released

Bug description:
  The gtest and google-mock source packages have been replaced by the
  googletest source package in Debian.

  gtest produced one binary: libgtest-dev
  google-mock produced one binary: google-mock
  googletest produces both those binaries and googletest

  Please drop these source packages from Ubuntu zesty:
  google-mock
  gtest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-mock/+bug/1645799/+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

[Bug Watch Updater]

** Changed in: accountsservice (Debian)
   Status: Unknown => Fix Released

-- 
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 Committed
Status in accountsservice source package in Xenial:
  In Progress
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 1609793] Re: Unity tests crashes when compiling google-mocks with gcc-6

[Bug Watch Updater]

** Changed in: google-mock (Debian)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to google-mock in Ubuntu.
https://bugs.launchpad.net/bugs/1609793

Title:
  Unity tests crashes when compiling google-mocks with gcc-6

Status in google-mock package in Ubuntu:
  Fix Released
Status in google-mock package in Debian:
  Fix Released

Bug description:
  Ubuntu Unity tests fails when using gcc-6, because test-gtest causes a
  crash.

  Starting program: 
/tmp/unity-7.5.0+16.10.20160804/obj-x86_64-linux-gnu/tests/test-gtest 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffe0f1d700 (LWP 22778)]
  [New Thread 0x7fffdbfff700 (LWP 22779)]
  [New Thread 0x7fffdb7fe700 (LWP 22780)]
  [==] Running 1637 tests from 105 test cases.
  [--] Global test environment set-up.
  [--] 14 tests from TestActionLink
  [ RUN  ] TestActionLink.AligmentCorrectlySetDifferent

  Thread 1 "test-gtest" received signal SIGSEGV, Segmentation fault.
  testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> 
const&) (args=empty std::tuple, this=0x7fffdb08)
  at /usr/include/gmock/gmock-spec-builders.h:1530
  1530  this->UntypedInvokeWith())->GetValueAndDelete();


  #0  testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> 
const&) (args=empty std::tuple, this=0x7fffdb08)
  at /usr/include/gmock/gmock-spec-builders.h:1530
  No locals.
  #1  testing::internal::FunctionMocker::Invoke() 
(this=0x7fffdb08) at 
/usr/include/gmock/gmock-generated-function-mockers.h:76
  No locals.
  #2  unity::dash::ActionLinkMock::QueueDraw (this=0x7fffd3c0) at 
/tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:43
  No locals.
  #3  0x559ce574 in unity::dash::ActionLink::set_underline 
(this=0x7fffd3c0, underline=unity::StaticCairoText::NUX_UNDERLINE_NONE)
  at 
/tmp/unity-7.5.0+16.10.20160804/tests/../dash/previews/ActionLink.cpp:218
  No locals.
  #4  0x559d53bf in std::function::operator()(unity::StaticCairoText::UnderlineState const&) const 
(__args#0=, this=0x7fffda00) at 
/usr/include/c++/6/functional:2136
  No locals.
  #5  nux::RWProperty::Set 
(this=0x7fffd9c8, value=)
  at /usr/include/Nux-4.0/NuxCore/Property-inl.h:218
  No locals.
  #6  0x559d0c31 in 
unity::dash::TestActionLink_UnderlineCorrectlySetDifferent_Test::TestBody 
(this=)
  at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:116

  
  A fix is available at 
https://github.com/google/googletest/issues/705#issuecomment-235067917

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-mock/+bug/1609793/+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 1609793] Re: Unity tests crashes when compiling google-mocks with gcc-6

[Bug Watch Updater]

** Changed in: google-mock (Debian)
   Status: Unknown => Fix Committed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to google-mock in Ubuntu.
https://bugs.launchpad.net/bugs/1609793

Title:
  Unity tests crashes when compiling google-mocks with gcc-6

Status in google-mock package in Ubuntu:
  Fix Released
Status in google-mock package in Debian:
  Fix Committed

Bug description:
  Ubuntu Unity tests fails when using gcc-6, because test-gtest causes a
  crash.

  Starting program: 
/tmp/unity-7.5.0+16.10.20160804/obj-x86_64-linux-gnu/tests/test-gtest 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffe0f1d700 (LWP 22778)]
  [New Thread 0x7fffdbfff700 (LWP 22779)]
  [New Thread 0x7fffdb7fe700 (LWP 22780)]
  [==] Running 1637 tests from 105 test cases.
  [--] Global test environment set-up.
  [--] 14 tests from TestActionLink
  [ RUN  ] TestActionLink.AligmentCorrectlySetDifferent

  Thread 1 "test-gtest" received signal SIGSEGV, Segmentation fault.
  testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> 
const&) (args=empty std::tuple, this=0x7fffdb08)
  at /usr/include/gmock/gmock-spec-builders.h:1530
  1530  this->UntypedInvokeWith())->GetValueAndDelete();


  #0  testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> 
const&) (args=empty std::tuple, this=0x7fffdb08)
  at /usr/include/gmock/gmock-spec-builders.h:1530
  No locals.
  #1  testing::internal::FunctionMocker::Invoke() 
(this=0x7fffdb08) at 
/usr/include/gmock/gmock-generated-function-mockers.h:76
  No locals.
  #2  unity::dash::ActionLinkMock::QueueDraw (this=0x7fffd3c0) at 
/tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:43
  No locals.
  #3  0x559ce574 in unity::dash::ActionLink::set_underline 
(this=0x7fffd3c0, underline=unity::StaticCairoText::NUX_UNDERLINE_NONE)
  at 
/tmp/unity-7.5.0+16.10.20160804/tests/../dash/previews/ActionLink.cpp:218
  No locals.
  #4  0x559d53bf in std::function::operator()(unity::StaticCairoText::UnderlineState const&) const 
(__args#0=, this=0x7fffda00) at 
/usr/include/c++/6/functional:2136
  No locals.
  #5  nux::RWProperty::Set 
(this=0x7fffd9c8, value=)
  at /usr/include/Nux-4.0/NuxCore/Property-inl.h:218
  No locals.
  #6  0x559d0c31 in 
unity::dash::TestActionLink_UnderlineCorrectlySetDifferent_Test::TestBody 
(this=)
  at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:116

  
  A fix is available at 
https://github.com/google/googletest/issues/705#issuecomment-235067917

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-mock/+bug/1609793/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1443052] Re: User accounts login history showing incorrect history

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Confirmed => Unknown

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1443052

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 982499] Re: dconf-editor always prints warnings: "Unknown property on "

[Bug Watch Updater]

** Changed in: d-conf (Debian)
   Status: Unknown => 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/982499

Title:
  dconf-editor always prints warnings: "Unknown property on "

Status in d-conf package in Ubuntu:
  Confirmed
Status in d-conf package in Debian:
  New

Bug description:
  When I start dconf-editor, these four warnings are logged:

  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:330: Unknown 
property on , extends
  >
  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:330: Unknown 
property on , extends
  >
  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:401: Unknown tag 

  >
  > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:401: Unknown tag 


  It doesn't seem to affect operations so I'm setting the initial
  importance to "Low".

  This is reproducible for me every time I start dconf-editor from the
  command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/982499/+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 1512002] Re: Annoying dialog "Authentication is required to change your own user data"

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=94895.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-04-11T17:14:30+00:00 Alkis Georgopoulos wrote:

Currently, data/org.freedesktop.accounts.policy.in specifies that a user
must be active in order to set his own data.

X2go, LTSP etc users are considered remote, i.e. inactive, and they are not 
allowed to change their own user data without authentication.
This results in a different behaviour when they e.g. try to change their 
language in the `gnome-control-center user-accounts`.

Furthermore, in some distributions it has been observed that change-own-
user-data authentication dialogs popup when changing VTs or when
switching users or sometimes even with just gnome-screensaver, possibly
because the distribution is trying to update the user data (e.g. to
notify the UI that he has new mails) when the user's vt was not active.

Therefore I'd like to ask you to consider setting
yes for change-own-user-data.

Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1512002

Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/1512002/comments/37


** Changed in: accountsservice
   Status: Unknown => Confirmed

** Changed in: accountsservice
   Importance: Unknown => Medium

-- 
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/1512002

Title:
  Annoying dialog "Authentication is required to change your own user
  data"

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Confirmed
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in policykit-1-gnome package in Ubuntu:
  Confirmed

Bug description:
  Every few days a dialog pops up saying "Authentication is required to change 
your own user data" with an entry field for a password. If I type my user's 
password the dialog will reappear with an empty entry field. If I click on the 
cross to close the window many times it will be gone, but reappear a few days 
later. I don't know what this window is for and it makes no difference whether 
I close it or leave it. I don't use the gnome keyring.
  This started with Ubuntu 15.04 or maybe with an earlier release, and is still 
there in Ubuntu 15.10, also on machines I did a fresh install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1512002/+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 422511] Re: problem with new scrollbar in Human theme - GtkRange::trough-border set to 2

[Bug Watch Updater]

** Changed in: gtk
   Status: New => Expired

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to human-theme in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/422511

Title:
  problem with new scrollbar in Human theme - GtkRange::trough-border
  set to 2

Status in elementary Stylesheet:
  Won't Fix
Status in Mozilla Firefox:
  New
Status in GTK+:
  Expired
Status in human-theme:
  New
Status in LibGTK:
  New
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in human-theme package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  New

Bug description:
  The new scrollbar in Karmic's Human theme has a usability bug:
  To reproduce, open nautilus, maximize the window, then open a directory with 
enough files to cause the scrollbar to appear (e.g. /lib). Now move your mouse 
to the right edge of the screen, and left click. Instead of grabbing the scroll 
bar, the mouse will behave as if you had clicked the scrollbar background, i.e. 
the bar will jump to that position (in Firefox, nothing happens). The problem 
is that the bar doesn't extend to the right edge, leaving a two pixel margin, 
but because of Fitts' law, it's much easier to click on the screen edge than 
the few pixels to the left of it.

  The cause of this is GtkRange::trough-border being set to 2. Setting
  it to 0 removes the margin around the bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/egtk/+bug/422511/+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 1389336] Re: Use geoclue-2.0

[Bug Watch Updater]

** Changed in: qtlocation-opensource-src (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity-webapps in Ubuntu.
https://bugs.launchpad.net/bugs/1389336

Title:
  Use geoclue-2.0

Status in empathy package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in libunity-webapps package in Ubuntu:
  Confirmed
Status in qtlocation-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-geoip package in Ubuntu:
  Confirmed
Status in webkitgtk package in Ubuntu:
  Confirmed
Status in qtlocation-opensource-src package in Debian:
  Fix Released

Bug description:
  Geoclue2 (source package geoclue-2.0) is a separate, parallel-
  installable version of geoclue1 (source package geoclue).  We will
  likely shortly have both in main (see MIR bug 1388294) and it would be
  great to be able to demote geoclue1 to universe and only support one
  version of the service.

  The packages associated with this bug all have a reverse depends on
  geoclue1 in some form or patches to remove support for geoclue-2.0
  because it wasn't in main yet (e.g. gnome-settings-daemon).

  Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial.
  But we have at least six months to do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 1389336] Re: Use geoclue-2.0

[Bug Watch Updater]

** Changed in: qtlocation-opensource-src (Debian)
   Status: Unknown => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity-webapps in Ubuntu.
https://bugs.launchpad.net/bugs/1389336

Title:
  Use geoclue-2.0

Status in empathy package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in libunity-webapps package in Ubuntu:
  Confirmed
Status in qtlocation-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-geoip package in Ubuntu:
  Confirmed
Status in webkitgtk package in Ubuntu:
  Confirmed
Status in qtlocation-opensource-src package in Debian:
  New

Bug description:
  Geoclue2 (source package geoclue-2.0) is a separate, parallel-
  installable version of geoclue1 (source package geoclue).  We will
  likely shortly have both in main (see MIR bug 1388294) and it would be
  great to be able to demote geoclue1 to universe and only support one
  version of the service.

  The packages associated with this bug all have a reverse depends on
  geoclue1 in some form or patches to remove support for geoclue-2.0
  because it wasn't in main yet (e.g. gnome-settings-daemon).

  Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial.
  But we have at least six months to do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 1488344] Re: dbus rejected send messages

[Bug Watch Updater]

** Changed in: glib
   Status: Confirmed => Fix Released

-- 
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/1488344

Title:
  dbus rejected send messages

Status in GLib:
  Fix Released
Status in accountsservice package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Seeing these log entries in the syslog

  Aug 24 18:26:36 M1 dbus[783]: [system] Rejected send message, 9 matched
  rules; type="method_return", sender=":1.5" (uid=0 pid=733
  comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)"
  member="(unset)" error name="(unset)" requested_reply="0"
  destination=":1.59" (uid=1000 pid=4326
  comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic")

  Hope the attached info helps locating the issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Tue Aug 25 18:30:51 2015
  InstallationDate: Installed on 2014-10-31 (298 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1488344/+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 1488344] Re: dbus rejected send messages

[Bug Watch Updater]

** Changed in: glib
   Status: Unknown => Confirmed

** Changed in: glib
   Importance: Unknown => Medium

-- 
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/1488344

Title:
  dbus rejected send messages

Status in GLib:
  Confirmed
Status in accountsservice package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Seeing these log entries in the syslog

  Aug 24 18:26:36 M1 dbus[783]: [system] Rejected send message, 9 matched
  rules; type="method_return", sender=":1.5" (uid=0 pid=733
  comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)"
  member="(unset)" error name="(unset)" requested_reply="0"
  destination=":1.59" (uid=1000 pid=4326
  comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic")

  Hope the attached info helps locating the issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Tue Aug 25 18:30:51 2015
  InstallationDate: Installed on 2014-10-31 (298 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1488344/+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 1103833] Re: Wine's icon and description appears for all Windows applications

[Bug Watch Updater]

Launchpad has imported 11 comments from the remote bug at
https://bugs.winehq.org/show_bug.cgi?id=32699.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-01-10T18:00:32+00:00 Simon K wrote:

See launchpad bug here: https://bugs.launchpad.net/unity/+bug/702452

In Ubuntu Unity applications run via wine have the default wine-icon (the 
wine-bottle) in the "Running Program-Icons"-bar (The Task-bar).
Thus all applications are getting "stacked" under one icon.

To stop this behavior you have to write in each (generated) .desktop-file the 
Line:
StartupWMClass=

Example Firefox:
StartupWMClass=firefox.exe

Wine should do this automatically after I installed my program, so the
users would get the expected Icons and "Stacking-Mechanism" in Unity.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1103833/comments/0


On 2013-04-13T15:33:11+00:00 Rgcjonas-c wrote:

This bug is a huge usability problem nowadays (in both Gnome Shell and Unity). 
The current solution matches all wine applications to a single desktop file, 
because every wine window has a WM_CLASS of "Wine" and the desktop file a 
StartupWMClass=Wine . I'd consider this incorrect, because
* Every wine application is now grouped to the same .desktop file, even though 
they're completely different applications
* You can't start the application the window belongs to by clicking the 
.desktop file (<-- this is the real problem)

Furthermore, this leads to the following problems in both Unity and gnome shell:
* Every wine window is grouped to the same icon
* The description "Wine windows program launcher" doesn't help when identifying 
the application
* You can pin the icon to the launcher, but it will never start anything.

Luckily, windows 7 can also group and pin apps on the taskbar, and AFAIK 
(correct me if I'm wrong) they match windows to launchers as follows:
* If the process set a AppUserModelID for the process or the window, then 
windows 7 searches for a shortcut file with the matching property 
System.AppUserModel.ID
* In case that fails, it falls back to searching a shortcut that specifies the 
running exe file.
* If that doesn't work either, the 'pinning' feature is disabled for that 
window, and it will be grouped by the process exe file.

The only way to correctly solve our problem is by replicating windows 7's 
method. I'd suggest the following implementation:
* Set the StartupWMClass of every .desktop file to the System.AppUserModel.ID 
property of the windows shortcut (if it exists) or the (case sensitive) name of 
the launched .exe file.
* Let every wine window have a WM_CLASS (res_class, because gnome shell ignores 
res_name) of the explicit AppUserModelID, if the application has set it, or the 
name of the running .exe file (the value that is set to res_name as of now).

This would then show the following behaviour (which IMHO is the one the user 
will probably expect):
* If the application correctly set an AppUserModelID and specified it in the 
shortcut, the desktop will match the windows with the correct .desktop file. It 
will be pinnable.
* If the application displays the window from the same process that is started 
with the shortcut, it will also be matched (because of the .exe file name in 
wm_class).
* If the window does not belong to any shortcut, the desktop environment won't 
match it. The app will not be pinnable in that case. I don't know how Unity or 
Gnome Shell would handle grouping in that case.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1103833/comments/4


On 2013-05-28T12:46:57+00:00 Damjan Jovanovic wrote:

Anything running under any runtime or custom loader (Java, Mono, Python,
Perl, Ruby, even running an application with strace or gdb) will exhibit
exactly the same stacking problem. Wow the Linux desktop is really
owning.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1103833/comments/5


On 2013-05-28T12:58:09+00:00 Rgcjonas-c wrote:

The same problem microsoft was facing when they introduced windows 7. They
developed a solution (AppUserModelIDs) which maps quite cleanly to the linux
solution (WMClass). We just need to implement that AppUserModelID stuff and
export it as WM Classes.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1103833/comments/6


On 2013-05-28T17:21:52+00:00 Vincent Povirk wrote:

AppUserModelID is the way to go in the long run, but it requires some
missing architecture (which I've been 

[Dx-packages] [Bug 702452] Re: [launcher] Wine applications are wrongly matched

[Bug Watch Updater]

** Changed in: wine
   Status: Confirmed => Unknown

-- 
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/702452

Title:
  [launcher] Wine applications are wrongly matched

Status in BAMF:
  Confirmed
Status in libwnck:
  Fix Released
Status in Unity:
  Confirmed
Status in Wine:
  Unknown
Status in bamf package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  After launching a Wine app from terminal or via gnome-do, it appears in the 
launcher with the Wine icon, instead of its own icon. The title is "Wine Window 
Program Loader" instead of the proper application name.
  It can't be favorited since it will favorite the wine executable itself.
  And obviously different wine apps are all grouped under the same launcher 
icon.

  See also bug #635223 about Wine applications not showing up in the
  dash.

  
-

  A way to fix this is to make all the Wine generated .desktop file to
  include a StartupWMClass value that matches the instance name of the
  related program (generally the .exe file name to be executed).

  So for example, a "Mozilla Firefox.desktop" file can be easily fixed adding 
this parameter:
   StartupWMClass=firefox.exe

  Wine should try to add this information at file generation time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/702452/+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 844081] Re: Unity Greeter - Background of the Unity Greeter should reflect the background chosen by the user that is currently selected

[Bug Watch Updater]

** Changed in: accountsservice
   Status: Confirmed => Fix Released

-- 
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/844081

Title:
  Unity Greeter - Background of the Unity Greeter should reflect the
  background chosen by the user that is currently selected

Status in accountsservice:
  Fix Released
Status in Ayatana Design:
  Fix Released
Status in Light Display Manager:
  Fix Released
Status in Unity Greeter:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Fix Released

Bug description:
  Background of the Unity Greeter should reflect the background chosen
  by the user that is currently selected.

  e.g. the background the user has selected on their desktop should be
  displayed in the greeter.  See the attached animation
  login_screen_v02_WP.mov to understand exactly how the backgrounds
  should crossfade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/844081/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

[Bug Watch Updater]

** Bug watch added: Eclipse bugs #461311
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=461311

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1475623] Re: zeitgeist ftbfs with GCC 5

[Bug Watch Updater]

** Changed in: zeitgeist
   Status: Confirmed = Fix Released

-- 
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/1475623

Title:
  zeitgeist ftbfs with GCC 5

Status in Zeitgeist Framework:
  Fix Released
Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  see
  
https://launchpadlibrarian.net/211752996/buildlog_ubuntu-wily-amd64.zeitgeist_0.9.14-2.2ubuntu6~gcc5.1_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist/+bug/1475623/+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 1475623] Re: zeitgeist ftbfs with GCC 5

[Bug Watch Updater]

Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=91443.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-07-24T04:18:11+00:00 Robert Ancell wrote:

The tests were using a c_str() result from a std::string that had gone out of
scope. GCC 5.1 seems to be more agressive in freeing the string data before
the tests checked against it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1475623/comments/8


On 2015-07-24T04:19:03+00:00 Robert Ancell wrote:

Created attachment 117327
Fix tests crashing with GCC 5.1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1475623/comments/9


** Changed in: zeitgeist
   Status: Unknown = Confirmed

** Changed in: zeitgeist
   Importance: Unknown = Medium

-- 
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/1475623

Title:
  zeitgeist ftbfs with GCC 5

Status in Zeitgeist Framework:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  see
  
https://launchpadlibrarian.net/211752996/buildlog_ubuntu-wily-amd64.zeitgeist_0.9.14-2.2ubuntu6~gcc5.1_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist/+bug/1475623/+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 1333158] Re: scaling doesn't affect firefox and thunderbird

[Bug Watch Updater]

** Changed in: firefox
   Status: Unknown = Fix Released

** Changed in: firefox
   Importance: Unknown = Medium

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1333158

Title:
  scaling doesn't affect firefox and thunderbird

Status in The Mozilla Firefox Browser:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in ubufox package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  If you use Scale for menu and title bars in the Displays Tab, this
  doesn't affect Firefox.

  please add this to the Unity Desktop Integration:

  about:config in Firefox and search for 
  layout.css.devPixelsPerPx
  set this value to the same scale factor as in unity-control-center

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1333158/+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 1199221] Re: Package zeitgeist-python for python3 aka make package python3-zeitgeist

[Bug Watch Updater]

** Changed in: zeitgeist
   Status: Confirmed = Fix Released

-- 
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/1199221

Title:
  Package zeitgeist-python for python3 aka make package
  python3-zeitgeist

Status in Zeitgeist Framework:
  Fix Released
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  At the moment the package python-zeitgeist installs in python2.7
  location and does not have a python3.x installation which makes
  python3 migration tougher.

  Expectation: Have a second package python3-zeitgeist which installs in
  python3.x location

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist/+bug/1199221/+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 1440373] Re: please build a python3-zeitgeist package and let zeitgeist depend on it

[Bug Watch Updater]

** Changed in: zeitgeist
   Status: Confirmed = Fix Released

-- 
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/1440373

Title:
  please build a python3-zeitgeist package and let zeitgeist depend on
  it

Status in Zeitgeist Framework:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build a python3-zeitgeist package and let
  zeitgeist depend on it

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist/+bug/1440373/+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 1422163] Re: Unity crashing while watching youtube videos using chrome

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=90802.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-06-01T16:14:22+00:00 mikbini wrote:

Created attachment 116207
Boot dmesg output

Hello,

on my old MacBook4,1, using Ubuntu 14.10, it seems that the llvmpipe
driver is chosen instead of i965.

I'm attaching the boot dmesg output.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1422163/comments/12


On 2015-06-01T16:15:14+00:00 mikbini wrote:

Created attachment 116208
Output of lspci -vvnn

Adding also the output of lspci -vvnn

Reply at:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1422163/comments/13


On 2015-06-01T16:17:20+00:00 mikbini wrote:

Created attachment 116209
Output of unity_support_test -p

And of unity_support_test -p , in case you need it

Reply at:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1422163/comments/14


On 2015-06-01T16:31:07+00:00 Mattst88 wrote:

What makes you think it's using llvmpipe instead of i965? The
unity_support_test output says:

 OpenGL vendor string:   Intel Open Source Technology Center
 OpenGL renderer string: Mesa DRI Intel(R) 965GM x86/MMX/SSE2
 OpenGL version string:  2.1 Mesa 10.3.2

which shows the i965 driver in use.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1422163/comments/15


On 2015-06-01T16:50:24+00:00 mikbini wrote:

Created attachment 116210
Output for an older run of unity_support_test -p

Interesting.

I'm attaching the unity_support_test that made me (or rather a helpful
guy on launchpad, see
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1422163) think that
it was llvmpipe.

It was generated on on February. As far as my (limited) understanding
goes it looked like the i965 driver failed to load for some unknown
reason and llvmpipe was picked up as a fallback.

I re-generated the one I attached when I opened this ticket a few
minutes ago, on the same hardware.

Likely something changed in between in ubuntu, you are right, it looks
like the right driver is picked up now.

Sorry for the noise.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1422163/comments/16


On 2015-06-01T17:14:32+00:00 Mattst88 wrote:

Cool, thanks for confirming.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1422163/comments/17


** Changed in: mesa
   Status: Unknown = Invalid

** Changed in: mesa
   Importance: Unknown = Medium

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1422163

Title:
  Unity crashing while watching youtube videos using chrome

Status in Mesa:
  Invalid
Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Triaged

Bug description:
  I recently upgraded to ubuntu 14.10 and started experiencing
  repeatable unity crashes while watching youtube videos using current
  chrome. It doesn't always crash at the first attempt but most
  definitely it will crash sooner or later.

  Once unity crashes it is respawn but again crashes immediately, the PC
  becomes unusable until I kill X from the console or reboot. From my
  .xsession-errors:

  upstart: unity7 main process (9627) terminated with status 1
  upstart: unity7 main process ended, respawning
  upstart: unity7 main process (9998) terminated with status 1
  upstart: unity7 main process ended, respawning
  upstart: unity7 main process (10017) terminated with status 1
  upstart: unity7 main process ended, respawning
  upstart: unity7 main process (10041) terminated with status 1
  upstart: unity7 main process ended, respawning
  upstart: unity7 main process (10054) terminated with status 1
  upstart: unity7 main process ended, respawning
  [you got the point]

  Unity support test results are not reassuring:

  
  $ /usr/lib/nux/unity_support_test -p
  libGL error: failed to open drm device: Permission denied
  libGL error: failed to load driver: i965
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
  OpenGL version string: 3.0 Mesa 10.3.2

  Not software rendered: no
  Not blacklisted: yes
  GLX fbconfig: yes
  GLX texture from pixmap: yes
  GL npot or rect textures: yes
  GL vertex program: yes
  GL fragment program: yes
  GL 

[Dx-packages] [Bug 1268673] Re: Unity Dash should propose terminal app when taping cmd

[Bug Watch Updater]

** Changed in: gnome-terminal
   Status: Unknown = Fix Released

** Changed in: gnome-terminal
   Importance: Unknown = Wishlist

-- 
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/1268673

Title:
  Unity Dash should propose terminal app when taping cmd

Status in GNOME Terminal:
  Fix Released
Status in Unity:
  New
Status in gnome-terminal package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  New

Bug description:
  Hi

  This is not a pure bug, but an idea to made life of lot of people
  simpler. More of that I'm not sure this is more related to Gnome
  Terminal than Unity). But it's for me an ergonomy bug. I explain :

  In my job I have to use Windows terminal a lot. As I do with 'term' in
  unity, to open it I usually press Windows / Super Key and enter
  'CMD'. Here is the problem : each time (very often) I come back on
  Ubuntu I try to search 'CMD' in the dash to open gnome-terminal. Of
  course : no result ! The idea is to have Gnome terminal (and probably
  other terminal app installed on the system) being found when searching
  cmd. This would avoid people like me to every time make the mistake,
  and newcomers to Ubuntu (student in Network/Telecoms/Programming...)
  would find what they search instantly what they search : better first
  impression of being home when first days on the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Jan 13 18:46:16 2014
  InstallationDate: Installed on 2014-01-12 (1 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_FR.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/gnome-terminal/+bug/1268673/+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 1440373] Re: please build a python3-zeitgeist package and let zeitgeist depend on it

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=66722.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-07-09T04:59:08+00:00 Manish Sinha (मनीष सिन्हा) wrote:

At the moment zeitgeist-python builds against whatever python version is
default.

A lot of systems are using python2.7 and not python3.x

Add support for explicit python2 and python3

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1440373/comments/0


** Changed in: zeitgeist
   Status: Unknown = Confirmed

** Changed in: zeitgeist
   Importance: Unknown = High

-- 
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/1440373

Title:
  please build a python3-zeitgeist package and let zeitgeist depend on
  it

Status in Zeitgeist Framework:
  Confirmed
Status in zeitgeist package in Ubuntu:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build a python3-zeitgeist package and let
  zeitgeist depend on it

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist/+bug/1440373/+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 1329089] Re: g++-4.9 binary incompatibilities with libraries built with g++-4.8

[Bug Watch Updater]

** Changed in: debian
   Status: New = Fix Released

-- 
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/1329089

Title:
  g++-4.9 binary incompatibilities with libraries built with g++-4.8

Status in Mir:
  Fix Released
Status in Mir 0.4 series:
  Won't Fix
Status in dbus-cpp package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  New
Status in gcc-4.9 package in Ubuntu:
  Fix Released
Status in gcc-defaults package in Ubuntu:
  Fix Released
Status in location-service package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in process-cpp package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  New
Status in Debian GNU/Linux:
  Fix Released

Bug description:
  The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic,
  when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built
  with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the
  default), fails the package build in its test suite.

   2/14 Test  #2: acceptance_tests ..***Failed   30.54 sec
  DBus daemon: 
unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b
  task-0: Started with PID: 13031
  task-0: [==] Running 2 tests from 1 test case.
  task-0: [--] Global test environment set-up.
  task-0: [--] 2 tests from LocationServiceStandalone
  task-0: [ RUN  ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus

  ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of
  30 seconds.

  (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: 
assertion 'all_tasks(service, all_tasks_finished_helper)' failed
  task-0: Shutting down
  DBus daemon: Shutdown

  This test suite does *not* fail if either dbus-cpp is rebuilt with
  g++-4.9, or if location-service is built with g++-4.8.

  This implies a binary compatibility problem for C++ libraries in g++
  4.9, which is critical to resolve.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1329089/+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 1314587] Re: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 (14.04 and 14.10)

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=89893.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-04-03T16:05:11+00:00 d❤vid seaward wrote:

Steps to reproduce:

 * Launch Unity desktop session
 * Minimize current window or alt-tab between windows
 * Reveal launcher to click on application
 * Click `Super` to bring up Dash
 * Hold `Super` to bring up Keyboard Shortcuts

What should happen:

Action completes smoothly and quickly.

What happens instead:

 * Action may be slow / animation jerky.
 * Action may stall (animation frozen on given frame, e.g. window partially 
minimized) - initiating another action cancels first action and second action 
may succeed (most often calling Guake with F12 seems to solve the issue)
 * Action may freeze - cursor no longer moves - a soft reboot 
(Alt+PrtScr+REISUB) usually works, otherwise a hard reboot

Notes:

This occurs on Ubuntu 14.04 and 14.10. See
https://bugs.launchpad.net/bugs/1314587 for a downstream bug report. It
was suggested there that an upstream report would be helpful.

I'm not sure which X.org component this applies to, if there is any
additional info I can provide please let me know (also see downstream
bug, linked above).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314587/comments/12


** Changed in: xorg-server
   Status: Unknown = Confirmed

** Changed in: xorg-server
   Importance: Unknown = Medium

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1314587

Title:
  Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7
  (14.04 and 14.10)

Status in Unity:
  Incomplete
Status in X.Org X server:
  Confirmed
Status in unity package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

   * Minimize current window or alt-tab between windows
   * Reveal launcher to click on application
   * Click `Super` to bring up Dash
   * Hold `Super` to bring up Keyboard Shortcuts

  What should happen:

  Action completes smoothly and quickly.

  What happens instead:

   * Action may be slow / animation jerky.
   * Action may stall (animation frozen on given frame, e.g. window partially 
minimized) - initiating another action cancels first action and second action 
may succeed (most often calling Guake with F12 seems to solve the issue)
   * Action may freeze - cursor no longer moves - a soft reboot 
(Alt+PrtScr+REISUB) usually works, otherwise a hard reboot

  Notes:

   * Not application specific. Minimizing is reliably slow/stalls with 
minimizing Firefox (including 29, I do not have a lot of bookmarks) or Pidgin, 
but I use those programs more often.
   * I am using an Nvidia Optimus machine with the default Nouveau driver - no 
`nvidia-prime`, no Bumblebee. I temporarily installed the latest stable Nvidia 
driver (including `nvidia-prime`) and it made no difference.
   * I did not experience this issue on the same machine running 13.10 (with 
Bumblebee).
   * I am running Maximus.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  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: Wed Apr 30 12:53:15 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04b6]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:04b6]
  InstallationDate: Installed on 2014-04-24 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=3a8fb3f3-1054-45a0-8ec0-0cbeba33da00 ro quiet splash vt.handoff=7
  

[Dx-packages] [Bug 425823] Re: Notifications not always visible

[Bug Watch Updater]

** Changed in: metacity
   Status: New = Fix Released

-- 
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/425823

Title:
  Notifications not always visible

Status in The Metacity Window Manager:
  Fix Released
Status in notify-osd package in Ubuntu:
  Invalid

Bug description:
  Sometimes, part of, or the whole notifiction does not show up, while
  hoovering over it, it becomes clearly visible.

  Howto reproduce: to be honest: I have no idea
  What seems to work (sometimes): 
  use notify-send to display a big image (in the screenshot a jpg of 40.5 kb 
with res 600x600px) and before it loads load a long loading page in firefox

  on terminal : sleep 4  notify-send Title Body text -i
  /path/to/big/image, go to firefox and load planet.ubuntu.com (for
  example)

  I'm using metacity with compositor, notify-osd 0.9.20-0ubuntu1, latest
  karmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/metacity/+bug/425823/+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 1284017] Re: gnome-shell crashed with SIGABRT in g_thread_abort()

[Bug Watch Updater]

** Changed in: d-conf (Ubuntu)
   Status: New = Invalid

** Changed in: dconf
   Status: Unknown = Invalid

** Changed in: dconf
   Importance: Unknown = Critical

-- 
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/1284017

Title:
  gnome-shell crashed with SIGABRT in g_thread_abort()

Status in A simple key-based configuration system:
  Invalid
Status in d-conf package in Ubuntu:
  Invalid

Bug description:
  gnome-shell crashed on system restart.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-shell 3.10.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb 24 12:24:40 2014
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-02-09 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121.1)
  ProcCmdline: gnome-shell --mode=gdm
  ProcEnviron:
   SHELL=/bin/false
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  Title: gnome-shell crashed with SIGABRT in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1284017/+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

[Bug Watch Updater]

** Changed in: nss-pam-ldapd (Debian)
   Status: Unknown = Fix Released

-- 
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:
  Confirmed
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Confirmed
Status in nss-pam-ldapd package in Debian:
  Fix Released

Bug 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:

  Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement 
user ingroup nopasswdlogin not met by user user
  Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication 
failure; logname= uid=0 euid=0 tty=:2 ruser= rhost=  user=user
  Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user 
(user)
  Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication 
failure; logname= uid=1001 euid=1001 tty= ruser= rhost=  user=user
  Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement 
user ingroup nopasswdlogin not met by user user

  cat /etc/pam.d/common-auth 
  account requiredpam_unix.so
  authrequiredpam_group.so
  auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure
  auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200
  authrequisite   pam_deny.so
  authrequiredpam_permit.so

  authoptionalpam_afs_session.so minimum_uid=200
  authoptionalpam_ecryptfs.so unwrap
  authoptionalpam_cap.so

  cat /etc/pam.d/common-account 
  account requiredpam_unix.so

  cat /etc/pam.d/lightdm
  authrequisite   pam_nologin.so
  authsufficient  pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  authoptionalpam_gnome_keyring.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  authoptionalpam_group.so
  session requiredpam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optionalpam_gnome_keyring.so auto_start
  session requiredpam_env.so readenv=1
  session requiredpam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale
  @include common-password

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1314095/+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 1415374] Re: Log: Loop not properly cleaned up on failures in Log constructor

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=88846.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-01-28T08:46:57+00:00 Albert Astals Cid wrote:

If the lambda fails the code leaves a MainLoop around that breaks things
(i.e. the Qt main glib loop).

I'm attaching the patch that fixes the problem, the generated code with
and the patch.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1415374/comments/0


On 2015-01-28T08:48:09+00:00 Albert Astals Cid wrote:

Created attachment 112905
The patch

Add finally {} to try {} catch {}

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1415374/comments/1


On 2015-01-28T08:49:14+00:00 Albert Astals Cid wrote:

Created attachment 112906
Generated .c code if unpatched

Note that there's some return; error conditions where the loop is not
exited correctly with g_main_loop_quit (_data1_-mainloop);

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1415374/comments/2


On 2015-01-28T08:49:52+00:00 Albert Astals Cid wrote:

Created attachment 112907
Generated .c code if patched

Note that all the exit paths properly have a g_main_loop_quit
(_data1_-mainloop);

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1415374/comments/3


On 2015-01-28T08:51:06+00:00 Albert Astals Cid wrote:

Please if possible credit this to Albert Astals Cid
albert.ast...@canonical.com and not to Albert Astals Cid
aa...@kde.org I'm just using my kde.org account since I didn't feel
like creating a new one just for this.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1415374/comments/4


On 2015-01-29T15:29:55+00:00 Albert Astals Cid wrote:

Created attachment 112950
The patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1415374/comments/6


On 2015-01-29T15:35:56+00:00 Albert Astals Cid wrote:

It's been commited.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1415374/comments/7


** Changed in: zeitgeist
   Status: Unknown = Fix Released

** Changed in: zeitgeist
   Importance: Unknown = Medium

-- 
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/1415374

Title:
  Log: Loop not properly cleaned up on failures in Log constructor

Status in Zeitgeist Framework:
  Fix Released
Status in zeitgeist package in Ubuntu:
  New

Bug description:
  If the lambda fails the code leaves a MainLoop around that breaks
  things (i.e. the Qt main glib loop).

  Patches and stuff at
  https://bugs.freedesktop.org/show_bug.cgi?id=88846

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist/+bug/1415374/+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 1257505] Re: Create Unity Control Center so can remain on old GNOME Control Center version

[Bug Watch Updater]

** Changed in: gnome-media
   Status: New = Expired

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages, dx-packages, dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1257505

Title:
  Create Unity Control Center so can remain on old GNOME Control Center
  version

Status in Chat app, and Telepathy user interface:
  Fix Released
Status in Eye of GNOME:
  Fix Released
Status in GNOME Color Manager:
  Incomplete
Status in GNOME Media Utilities:
  Expired
Status in The Gnome Thumbnail Image Viewer:
  Fix Released
Status in Nautilus:
  Fix Released
Status in Unity:
  Fix Released
Status in activity-log-manager package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in compiz package in Ubuntu:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in empathy package in Ubuntu:
  Fix Released
Status in eog package in Ubuntu:
  Fix Released
Status in gnome-color-manager package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in gnome-media package in Ubuntu:
  Fix Released
Status in gthumb package in Ubuntu:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-session package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in landscape-client package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in ubuntuone-control-panel package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in webaccounts-browser-extension package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu/Unity uses GNOME Control Center as the application to configure
  the Unity session. We've made a lot of changes appropriate for Ubuntu
  and Unity (61 patches) which makes it hard to maintain and creates a
  conflict for Ubuntu GNOME to use the control center. Unity 7 will be
  replaced by Unity 8 in the future which has a new settings interface.

  So we can continue to remain on the current version of GNOME Control
  Center but allow Ubuntu GNOME to continue to update we will create a
  new project lp:unity-control-center which is a copy of GNOME Control
  Center 3.6 but with appropriate renaming so both can be installed.

  A number of packages that refer to gnome-control-center need to be
  updated to refer to unity-control-center (see bug tasks).

  A PPA for testing is https://launchpad.net/~ubuntu-desktop/+archive
  /unity-control-center

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/1257505/+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 1315369] Re: Log in not available after lock screen with multi-monitor

[Bug Watch Updater]

** Changed in: xserver-xorg-video-intel
   Status: Incomplete = Invalid

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1315369

Title:
  Log in not available after lock screen with multi-monitor

Status in Unity:
  Invalid
Status in X.org xf86-video-intel:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed
Status in unity source package in Trusty:
  Confirmed

Bug description:
  After the screen locks I am unable to log back in because the screen
  with the login prompt is black, and the screen on my laptop just shows
  the Ubuntu logo.

  Furthermore, if I then unplug the external monitor (in an attempt to
  force the log in option to be displayed on the laptop)  the laptop
  screen then goes black and I can't do anything at all.

  I can't reproduce this if I select lock screen from the UI, but it
  happens reliably if it locks due to inactivity.

  Other info:
  - I am running a fresh install of 14.04
  - I have it set to lock after 5 min of inactivity, and require login after 
lock
  - I have an external monitor, configured to be on the left side of the laptop 
screen
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jane   2184 F pulseaudio
   /dev/snd/controlC0:  jane   2184 F pulseaudio
  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]
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec
  InstallationDate: Installed on 2014-05-01 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: Dell Inc. Dell System XPS L321X
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  PackageArchitecture: i386
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty trusty
  Uname: Linux 3.13.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 085X6F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L321X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1315369/+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 1023588] Re: Extra notify-osd bubble pops up when using Xfce

[Bug Watch Updater]

** Changed in: xfce4-volumed (Ubuntu)
   Status: Confirmed = Won't Fix

-- 
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/1023588

Title:
  Extra notify-osd bubble pops up when using Xfce

Status in Indicator Applet:
  Confirmed
Status in notify-osd package in Ubuntu:
  Confirmed
Status in xfce4-volumed package in Ubuntu:
  Won't Fix

Bug description:
  Using Xfce, Xfce's indicator applet plugin, and the gtk2-based sound
  indicator and using the scroll wheel on the volume bar pops up two
  NotifyOSD notifications instead of one. I attached a screenshot. I
  don't know if the bug is in Xfce, indicator, or notify-osd, though, or
  maybe my setup somehow.

  Worth noting is that everything works as expected when clicking on the
  icon and changing the audio that way or using my notebook's audio
  controls - the problem only occurs when using the mouse wheel with the
  mouse on top of the icon, having not clicked it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-applet/+bug/1023588/+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