[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

[Łukasz Zemczak]

We have decided this is a zero-day SRU, we already tested it and we'll
release it as-is.

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

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

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Committed
Status in ayatana-indicator-messages package in Ubuntu:
  Incomplete
Status in indicator-messages package in Ubuntu:
  In Progress

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

[Łukasz Zemczak]

I accepted indicator-messages into lunar-proposed but, sadly, it didn't
build. The issue is on the binary-package level:

https://launchpad.net/ubuntu/+source/indicator-
messages/13.10.1+18.10.20180918-0ubuntu4

Basically what's happening is that indicator-messages and ayatana-
indicator-messages both build the libmessaging-menu* binary packages.
This is not right. Both are available in the archive for lunar. So
indicator-messages cannot be published as it tries to upload the new
binaries but it sees newer versioned ones (from ayatana) already - and
bails.

We probably need to drop the libmessaging-menu* packages from indicator-
messages.

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

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

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Committed
Status in 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 1898477] Proposed package removed from archive

[Łukasz Zemczak]

The version of indicator-applet in the proposed pocket of Focal that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

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

Title:
  Old indicator items are not removed, just hidden

Status in indicator-applet package in Ubuntu:
  Fix Released
Status in indicator-applet source package in Focal:
  Won't Fix

Bug description:
  [Impact]

  In Focal the indicator-applet (12.10.2+20.04.20200409-0ubuntu1)
  contains a bug that can cause duplicate icons to appear in the applet.
  When an application which creates a notification item is closed, then
  the indicator applet will just hide its item and not remove it. If the
  application is started again, a new item will be added to the applet,
  but the old item is still present (just hidden). When the panel is
  moved or otherwise refreshed, then all items will be made visible
  again, causing many duplicates.

  The required fix is included in https://bazaar.launchpad.net
  /~indicator-applet-developers/indicator-
  applet/trunk.14.04/revision/451 and needs to be back ported into the
  new SRU release.

  For more details see this merge request:
  
https://code.launchpad.net/~lanoxx/indicator-applet/fix-duplicate-icons/+merge/390344

  [Test Case]

   1. Open an application which adds a notification item to the indicator 
applet. Examples for such an applications are VLC, Network Manager Applet, or 
Skype.
   2. Close the application and reopen it.
   3. Hold Alt key, then move the panel which has the indicator applet to an 
different edge of the screen.
   4. Observe that new two icons of the respective application are visible 
(e.g. to VLC icons).

  [Regression Potential]

   * The regression potential is minimal. The only user of this package are the 
GNOME Flashback packages. The biggest impact this change could have is that 
indicator applet items behave incorrectly, which is not worse than the current 
situation.
   * I have tested this patch for several weeks now and not found any 
regressions.

  [racb] The code path being changed is the signal handler that fires
  when indicator items are removed. Regressions may manifest if this
  code path is exercised in some unexpected way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1898477/+subscriptions

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

[Dx-packages] [Bug 1898477] Proposed package removed from archive

[Łukasz Zemczak]

The version of indicator-applet in the proposed pocket of Focal that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

** Changed in: indicator-applet (Ubuntu Focal)
   Status: Fix Committed => Won't Fix

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

Title:
  Old indicator items are not removed, just hidden

Status in indicator-applet package in Ubuntu:
  Fix Released
Status in indicator-applet source package in Focal:
  Won't Fix

Bug description:
  [Impact]

  In Focal the indicator-applet (12.10.2+20.04.20200409-0ubuntu1)
  contains a bug that can cause duplicate icons to appear in the applet.
  When an application which creates a notification item is closed, then
  the indicator applet will just hide its item and not remove it. If the
  application is started again, a new item will be added to the applet,
  but the old item is still present (just hidden). When the panel is
  moved or otherwise refreshed, then all items will be made visible
  again, causing many duplicates.

  The required fix is included in https://bazaar.launchpad.net
  /~indicator-applet-developers/indicator-
  applet/trunk.14.04/revision/451 and needs to be back ported into the
  new SRU release.

  For more details see this merge request:
  
https://code.launchpad.net/~lanoxx/indicator-applet/fix-duplicate-icons/+merge/390344

  [Test Case]

   1. Open an application which adds a notification item to the indicator 
applet. Examples for such an applications are VLC, Network Manager Applet, or 
Skype.
   2. Close the application and reopen it.
   3. Hold Alt key, then move the panel which has the indicator applet to an 
different edge of the screen.
   4. Observe that new two icons of the respective application are visible 
(e.g. to VLC icons).

  [Regression Potential]

   * The regression potential is minimal. The only user of this package are the 
GNOME Flashback packages. The biggest impact this change could have is that 
indicator applet items behave incorrectly, which is not worse than the current 
situation.
   * I have tested this patch for several weeks now and not found any 
regressions.

  [racb] The code path being changed is the signal handler that fires
  when indicator items are removed. Regressions may manifest if this
  code path is exercised in some unexpected way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1898477/+subscriptions

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

[Dx-packages] [Bug 1898477] Re: Old indicator items are not removed, just hidden

[Łukasz Zemczak]

Hey Dmitry! You mentioned indicator-appmenu on Ubuntu groovy, even
though the SRU is targeting focal. Did you mean to say that the same fix
is also present in groovy and that there it seems to be causing invalid
behavior?

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

Title:
  Old indicator items are not removed, just hidden

Status in indicator-applet package in Ubuntu:
  Fix Released
Status in indicator-applet source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  In Focal the indicator-applet (12.10.2+20.04.20200409-0ubuntu1)
  contains a bug that can cause duplicate icons to appear in the applet.
  When an application which creates a notification item is closed, then
  the indicator applet will just hide its item and not remove it. If the
  application is started again, a new item will be added to the applet,
  but the old item is still present (just hidden). When the panel is
  moved or otherwise refreshed, then all items will be made visible
  again, causing many duplicates.

  The required fix is included in https://bazaar.launchpad.net
  /~indicator-applet-developers/indicator-
  applet/trunk.14.04/revision/451 and needs to be back ported into the
  new SRU release.

  For more details see this merge request:
  
https://code.launchpad.net/~lanoxx/indicator-applet/fix-duplicate-icons/+merge/390344

  [Test Case]

   1. Open an application which adds a notification item to the indicator 
applet. Examples for such an applications are VLC, Network Manager Applet, or 
Skype.
   2. Close the application and reopen it.
   3. Hold Alt key, then move the panel which has the indicator applet to an 
different edge of the screen.
   4. Observe that new two icons of the respective application are visible 
(e.g. to VLC icons).

  [Regression Potential]

   * The regression potential is minimal. The only user of this package are the 
GNOME Flashback packages. The biggest impact this change could have is that 
indicator applet items behave incorrectly, which is not worse than the current 
situation.
   * I have tested this patch for several weeks now and not found any 
regressions.

  [racb] The code path being changed is the signal handler that fires
  when indicator items are removed. Regressions may manifest if this
  code path is exercised in some unexpected way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1898477/+subscriptions

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

[Dx-packages] [Bug 1867996] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for libappindicator has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Segfault in app_indicator_set_icon_full [patch attached]

Status in libappindicator package in Ubuntu:
  Fix Released
Status in libappindicator source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

  Discord and several other applications using libappindicator are
  widely reported to have been crashing for several years. See:
  https://github.com/flathub/com.discordapp.Discord/issues/30 (and
  others)

  [ Test case ]

  - Run discord application
  - It must not crash in ubuntu (or when indicators are enabled)

  [ Regression potential ]

  Very low, icons might not appear in some cases, if any.

  -

  This is the backtrace:
  (gdb) bt full
  #0  0x7fe1d5d2e00e in  () at /app/lib/libappindicator.so
  #1  0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0
  #2  0x7fe1f5a813d2 in  () at /lib/libgobject-2.0.so.0
  #3  0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0
  #4  0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0
  #5  0x7fe1d5d2ed4f in app_indicator_set_icon_full () at 
/app/lib/libappindicator.so
  #6  0x0077851a in  ()
  #7  0x01de7123 in  ()
  #8  0x01e4bd4e in  ()
  #9  0x01e6e34c in  ()
  #10 0x01e6e668 in  ()
  #11 0x01e6e9cb in  ()
  #12 0x01df971a in  ()
  #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0
  #14 0x7fe1f354b430 in  () at /lib/libglib-2.0.so.0
  #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0
  #16 0x01df9606 in  ()
  #17 0x01e6e0e7 in  ()
  #18 0x01e29570 in  ()
  #19 0x00c37ec8 in  ()
  #20 0x00c37d15 in  ()
  #21 0x00c1da7d in  ()
  #22 0x00a9282e in  ()
  #23 0x007892d4 in  ()
  #24 0x007896e0 in  ()
  #25 0x03b830a3 in main ()

  Happens in all versions of libappindicator built from latest sources
  available on launchpad.

  I ran into the issue yesterday when installing Discord for the first
  time. I have tracked the problem down to libappindicator passing in an
  extra vararg item to g_signal_emit that the signal's definition in
  libappindicator was not declaring, causing the crash you see above in
  gobject's g_signal dispatch machinery.

  Patch is attached.

  I am presuming this is 'upstream' for libappindicator, whatever that
  may mean for what appears to be an unmaintained project. If it is not,
  and since it is an Ubuntu/Canonical-sourced project originally, I
  respectfully request that you assist in upstreaming it since this bug
  is causing severe breakage for users across all distros.

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

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

[Dx-packages] [Bug 1873678] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for accountsservice has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gnome-language-selector crashed with dbus.exceptions.DBusException in
  call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is
  not a valid locale name

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

Bug description:
  [Impact]

  accountsservice includes a function for checking the validity of
  locales, and it incorrectly considers "C.UTF-8" to be invalid. It
  leads to incorrect behavior under certain conditions and also a crash
  if the function was triggered from language-selector-gnome.

  Even if this only makes a difference in special corner cases, it
  happens often enough to justify this SRU:

  https://errors.ubuntu.com/?release=Ubuntu%2020.04=language-
  selector=year

  (It's the top ranked crash type in the list.)

  The version in focal-proposed fixes the issue.

  [Test case]

  Make a fresh install of Ubuntu 20.04 (a VM works fine)

  Once logged in:

  * Install accountsservice, gir1.2-accountsservice-1.0 and
libaccountsservice0 from focal-proposed

  * Open /etc/default/locale for editing, replace its contents with
the single line:

LANG=C.UTF-8

and reboot.

  Open Language Support and change language (drag any language above
  the "English" item)

  Open ~/.pam_environment and find that e.g. LANG is now the locale
  representing the language you selected, while e.g. LC_TIME is set to
  "C.UTF-8".

  [Regression risk]

  This is a oneliner which white list "C.UTF-8" as a valid locale name.
  I can't think of a case where this would cause unexpected behavior.

  [Original description]

  USB live disk (20.04 beta)

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: language-selector-gnome 0.203
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: MATE
  Date: Sun Apr 19 17:07:26 2020
  ExecutablePath: /usr/bin/gnome-language-selector
  InterpreterPath: /usr/bin/python3.8
  LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonArgs: ['/usr/bin/gnome-language-selector']
  PythonDetails: N/A
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a 
valid locale name
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~dx-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

[Łukasz Zemczak]

** Tags removed: rls-ff-incoming

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

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

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

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

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

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

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

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

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

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

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

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

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

[Łukasz Zemczak]

Ok, I think that the test case is thorough enough to cover the
regression risk here. Let's get it in.

** Changed in: accountsservice (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

  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 1843982] Please test proposed package

[Łukasz Zemczak]

Hello Hans-Petter, or anyone else affected,

Accepted accountsservice into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.55-0ubuntu12~20.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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:
  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.

  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

[Dx-packages] [Bug 1819103] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for indicator-application
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Indicator Application and indicator-applet does not show indicators

Status in indicator-application package in Ubuntu:
  Fix Released
Status in indicator-application source package in Bionic:
  Fix Released
Status in indicator-application source package in Cosmic:
  Fix Released

Bug description:
  [ Description ]

  When gnome-shell-extension-appindicator is installed and in use, and
  indicator-application is also in use, there is a race condition that
  means that Ubuntu sessions might not show any appindicators. They each
  try to claim a bus name, and only one thing may own the same bus name
  at a time.

  [ QA ]

  1. Install indicator-application.
  2. Enter an Ubuntu GNOME Shell session
  3. Start something which displays an appindicator, for example 
transmission-gtk (turn on "Show Transmission in the notification area" in 
Preferences -> Desktop.
  4. Make sure it displays
  5. This bug is a race, and sometimes the appindicator will win the race and 
so they will work anyway. Open `journalctl -b` and check that there are no 
messages mentioning "org.kde.StatusNotifier". If the bug was happening you'd 
have a message from either the extension or indicator-application mentioning 
this name.

  [ Fix ]

  Don't run indicator-application on ubuntu sessions.

  [ Regression potential ]

  If someone has a different session called 'ubuntu' then this will stop
  indicator-application running for them.

  [ Original description ]

  On an Ubuntu 18.10 system, the dropbox icon would not show in the
  system tray panel. After searching the internet and trying various
  fixes (which did not work as expected) I came across a link which said
  indicator-application should be removed. I removed it along with the
  indicator-applet app and things are working fine!.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: indicator-application (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 11:48:16 2019
  InstallationDate: Installed on 2018-12-20 (77 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1819103/+subscriptions

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

[Dx-packages] [Bug 1819103] Please test proposed package

[Łukasz Zemczak]

Hello pramathesh, or anyone else affected,

Accepted indicator-application into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/indicator-application/12.10.1+18.04.20190308.1-0ubuntu1 in a few hours,
and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Indicator Application and indicator-applet does not show indicators

Status in indicator-application package in Ubuntu:
  Fix Released
Status in indicator-application source package in Bionic:
  Fix Committed
Status in indicator-application source package in Cosmic:
  Fix Committed

Bug description:
  [ Description ]

  When gnome-shell-extension-appindicator is installed and in use, and
  indicator-application is also in use, there is a race condition that
  means that Ubuntu sessions might not show any appindicators. They each
  try to claim a bus name, and only one thing may own the same bus name
  at a time.

  [ QA ]

  1. Install indicator-application.
  2. Enter an Ubuntu GNOME Shell session
  3. Start something which displays an appindicator, for example 
transmission-gtk (turn on "Show Transmission in the notification area" in 
Preferences -> Desktop.
  4. Make sure it displays
  5. This bug is a race, and sometimes the appindicator will win the race and 
so they will work anyway. Open `journalctl -b` and check that there are no 
messages mentioning "org.kde.StatusNotifier". If the bug was happening you'd 
have a message from either the extension or indicator-application mentioning 
this name.

  [ Fix ]

  Don't run indicator-application on ubuntu sessions.

  [ Regression potential ]

  If someone has a different session called 'ubuntu' then this will stop
  indicator-application running for them.

  [ Original description ]

  On an Ubuntu 18.10 system, the dropbox icon would not show in the
  system tray panel. After searching the internet and trying various
  fixes (which did not work as expected) I came across a link which said
  indicator-application should be removed. I removed it along with the
  indicator-applet app and things are working fine!.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: indicator-application (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 11:48:16 2019
  InstallationDate: Installed on 2018-12-20 (77 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1819103/+subscriptions

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

[Dx-packages] [Bug 1819103] Re: Indicator Application and indicator-applet does not show indicators

[Łukasz Zemczak]

Hello pramathesh, or anyone else affected,

Accepted indicator-application into cosmic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/indicator-application/12.10.1+18.10.20190308.1-0ubuntu1 in a few hours,
and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: indicator-application (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: indicator-application (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Indicator Application and indicator-applet does not show indicators

Status in indicator-application package in Ubuntu:
  Fix Released
Status in indicator-application source package in Bionic:
  Fix Committed
Status in indicator-application source package in Cosmic:
  Fix Committed

Bug description:
  [ Description ]

  When gnome-shell-extension-appindicator is installed and in use, and
  indicator-application is also in use, there is a race condition that
  means that Ubuntu sessions might not show any appindicators. They each
  try to claim a bus name, and only one thing may own the same bus name
  at a time.

  [ QA ]

  1. Install indicator-application.
  2. Enter an Ubuntu GNOME Shell session
  3. Start something which displays an appindicator, for example 
transmission-gtk (turn on "Show Transmission in the notification area" in 
Preferences -> Desktop.
  4. Make sure it displays
  5. This bug is a race, and sometimes the appindicator will win the race and 
so they will work anyway. Open `journalctl -b` and check that there are no 
messages mentioning "org.kde.StatusNotifier". If the bug was happening you'd 
have a message from either the extension or indicator-application mentioning 
this name.

  [ Fix ]

  Don't run indicator-application on ubuntu sessions.

  [ Regression potential ]

  If someone has a different session called 'ubuntu' then this will stop
  indicator-application running for them.

  [ Original description ]

  On an Ubuntu 18.10 system, the dropbox icon would not show in the
  system tray panel. After searching the internet and trying various
  fixes (which did not work as expected) I came across a link which said
  indicator-application should be removed. I removed it along with the
  indicator-applet app and things are working fine!.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: indicator-application (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 11:48:16 2019
  InstallationDate: Installed on 2018-12-20 (77 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1819103/+subscriptions

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

[Dx-packages] [Bug 1773859] Please test proposed package

[Łukasz Zemczak]

Hello Kees, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Dx-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[Łukasz Zemczak]

Hello Kees, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial.

  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]
   
   * original bug report

  
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Dx-packages] [Bug 1768610] Please test proposed package

[Łukasz Zemczak]

Hello Martin, or anyone else affected,

Accepted nux into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nux/4.0.8+16.04.20180622.2-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: xorg (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Fix Committed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Łukasz Zemczak]

Hello Martin, or anyone else affected,

Accepted nux into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nux/4.0.8+18.04.20180622.2-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nux (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic

** Changed in: xorg (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Fix Committed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  

[Dx-packages] [Bug 1768610] Please test proposed package

[Łukasz Zemczak]

Hello Martin, or anyone else affected,

Accepted xorg into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/xorg/1:7.7+19ubuntu7.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Fix Committed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 

[Dx-packages] [Bug 1768610] Please test proposed package

[Łukasz Zemczak]

Hello Martin, or anyone else affected,

Accepted xorg into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/xorg/1:7.7+13ubuntu3.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Fix Committed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 

[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Łukasz Zemczak]

** Changed in: xorg (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  In Progress
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Won't Fix
Status in nux source package in Bionic:
  Fix Released
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ]

  · Install xenial
  · Upgrade (nux-tools) and ensure that unity is still properly running after
a logout/login cycle.
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
    printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
    in an environment with no 3d support (VMs are easy tests)

  [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND
  REMOVED UNITY ]

   · remove nux-tools from artful/bionic-release (pre-sru), upgrade,
 reinstall nux-tools (no prompt)
   · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall
 nux-tools (nothing should be prompted)
   · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should 
prompt)
   · install nux-tools, upgrade, no prompt

  You end up with either no /etc/X11/Xsession.d/50_check_unity_support,
  its new contents or you are asked what to do if you've changed it
  before. Never the old content.

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Dx-packages] [Bug 1747814] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for libunity has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Snapped applications using ubuntu launcher integration needs desktop
  update

Status in libunity package in Ubuntu:
  Fix Released
Status in libunity source package in Xenial:
  Fix Released

Bug description:
  [ Impact ]

  Launching a snapped application with ubuntu launcher icon integration
  doesn't properly work as the desktop ID does not use the proper
  namespace.

  Also, a snapped app could decorate other apps outside the snap scope.

  [ Test case ]

  git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git
  cd ubuntu-launcher-integration-snap
  snapcraft prime
  snap try prime

  Then launch those (you might do it from dash/activities to get proper 
matching):
   ubuntu-launcher-integration-snap.ubuntu-launcher
   ubuntu-launcher-integration-snap.ubuntu-launcher-2nd
   ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded

  All these apps should get an icon in the launcher with emblems (of
  different values when they're launched together).

  [ Regression potential ]

  Application with SNAP environments could point to wrong desktop-file
  to decorate

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

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

[Dx-packages] [Bug 1747814] Please test proposed package

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

Accepted libunity into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libunity/7.1.4+16.04.20180209.1-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Snapped applications using ubuntu launcher integration needs desktop
  update

Status in libunity package in Ubuntu:
  Fix Released
Status in libunity source package in Xenial:
  Fix Committed

Bug description:
  [ Impact ]

  Launching a snapped application with ubuntu launcher icon integration
  doesn't properly work as the desktop ID does not use the proper
  namespace.

  Also, a snapped app could decorate other apps outside the snap scope.

  [ Test case ]

  git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git
  cd ubuntu-launcher-integration-snap
  snapcraft prime
  snap try prime

  Then launch those (you might do it from dash/activities to get proper 
matching):
   ubuntu-launcher-integration-snap.ubuntu-launcher
   ubuntu-launcher-integration-snap.ubuntu-launcher-2nd
   ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded

  All these apps should get an icon in the launcher with emblems (of
  different values when they're launched together).

  [ Regression potential ]

  Application with SNAP environments could point to wrong desktop-file
  to decorate

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

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

[Dx-packages] [Bug 1747814] Re: Snapped applications using ubuntu launcher integration needs desktop update

[Łukasz Zemczak]

I'm wondering if it makes sense to also get this released for artful?
Unity is not the default experience but the package is still available,
so in theory someone upgrading from xenial to artful and insisting on
staying with Unity as his shell might experience a regression.

What do you think? I'll accept it for now, but maybe it's worth
considering?

** Also affects: libunity (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: libunity (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Snapped applications using ubuntu launcher integration needs desktop
  update

Status in libunity package in Ubuntu:
  Fix Released
Status in libunity source package in Xenial:
  Fix Committed

Bug description:
  [ Impact ]

  Launching a snapped application with ubuntu launcher icon integration
  doesn't properly work as the desktop ID does not use the proper
  namespace.

  Also, a snapped app could decorate other apps outside the snap scope.

  [ Test case ]

  git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git
  cd ubuntu-launcher-integration-snap
  snapcraft prime
  snap try prime

  Then launch those (you might do it from dash/activities to get proper 
matching):
   ubuntu-launcher-integration-snap.ubuntu-launcher
   ubuntu-launcher-integration-snap.ubuntu-launcher-2nd
   ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded

  All these apps should get an icon in the launcher with emblems (of
  different values when they're launched together).

  [ Regression potential ]

  Application with SNAP environments could point to wrong desktop-file
  to decorate

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

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

[Dx-packages] [Bug 1747814] Please test proposed package

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

Accepted libunity into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libunity/7.1.4+16.04.20180207-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Snapped applications using ubuntu launcher integration needs desktop
  update

Status in libunity package in Ubuntu:
  Fix Released
Status in libunity source package in Xenial:
  Fix Committed

Bug description:
  [ Impact ]

  Launching a snapped application with ubuntu launcher icon integration
  doesn't properly work as the desktop ID does not use the proper
  namespace.

  Also, a snapped app could decorate other apps outside the snap scope.

  [ Test case ]

  git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git
  cd ubuntu-launcher-integration-snap
  snapcraft prime
  snap try prime

  Then launch those (you might do it from dash/activities to get proper 
matching):
   ubuntu-launcher-integration-snap.ubuntu-launcher
   ubuntu-launcher-integration-snap.ubuntu-launcher-2nd
   ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded

  All these apps should get an icon in the launcher with emblems (of
  different values when they're launched together).

  [ Regression potential ]

  Application with SNAP environments could point to wrong desktop-file
  to decorate

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

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

[Dx-packages] [Bug 1664205] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for nux has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Copy-paste and text selection doesn't work when caps-lock is on

Status in nux package in Ubuntu:
  Fix Released
Status in nux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps 
Lock is on

  [Test case]
  0) Set Caps-Lock on in your keyboard
  1) Open dash, and write something
  2) Ctrl+A should select all the text, Ctrl+C should copy,
     Ctrl+V should paste and Ctrl+X should cut

  Currently they don't work unless caps-lock is turned off

  [Possible regression]
  Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling 
won't work anymore

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

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

[Dx-packages] [Bug 1644323] Change of SRU verification policy

[Łukasz Zemczak]

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions

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

[Dx-packages] [Bug 1302084] Re: Menu in the global title bar is missing after a window child in Qt5 applications

[Łukasz Zemczak]

** Changed in: appmenu-qt5 (Ubuntu)
   Status: In Progress => Confirmed

** Changed in: appmenu-qt5
   Status: In Progress => Triaged

** Changed in: appmenu-qt5 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Menu in the global title bar is missing after a window child in Qt5
  applications

Status in appmenu-qt5:
  Triaged
Status in Application Menu Indicator:
  New
Status in Unity:
  Invalid
Status in appmenu-qt5 package in Ubuntu:
  Triaged

Bug description:
  steps to get this behavior

  1. "Settings | Appearance | Behavior" set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu "Open Help | 
About QtCreator..."
  4. Close Window "About Qt Creator".
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+subscriptions

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

[Dx-packages] [Bug 1435348] Re: qtcreator recently used file/project submenu empty

[Łukasz Zemczak]

** Changed in: appmenu-qt5 (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  qtcreator recently used file/project submenu empty

Status in appmenu-qt5 package in Ubuntu:
  Confirmed
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Invalid

Bug description:
  Using current vivid, with integrated menu (appmenu-qt5), the qtcreator
  files-> recent files/projects submenus are empty, they work fine if
  the qt theme env variable is empty (use local menus instead)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1435348/+subscriptions

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

[Dx-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Łukasz Zemczak]

** Also affects: libertine-scope (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: pay-service (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qtmir (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-app-launch (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-push (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-system-settings-online-accounts (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-click (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: url-dispatcher (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1681870/+subscriptions

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

[Dx-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Łukasz Zemczak]

** Also affects: content-hub (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: indicator-transfer (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: keeper (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1681870/+subscriptions

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

[Dx-packages] [Bug 1622686] Please test proposed package

[Łukasz Zemczak]

Hello Dave, or anyone else affected,

Accepted humanity-icon-theme into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/humanity-icon-theme/0.6.11.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Committed
Status in ubiquity source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  Fix Committed
Status in ubiquity source package in Yakkety:
  New

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions

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

[Dx-packages] [Bug 1622686] Re: double header in 16.10

[Łukasz Zemczak]

Hello Dave, or anyone else affected,

Accepted humanity-icon-theme into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/humanity-icon-theme/0.6.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: humanity-icon-theme (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: humanity-icon-theme (Ubuntu Yakkety)
   Status: New => Fix Committed

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Committed
Status in ubiquity source package in Xenial:
  New
Status in humanity-icon-theme source package in Yakkety:
  Fix Committed
Status in ubiquity source package in Yakkety:
  New

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions

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

[Dx-packages] [Bug 1657863] Please test proposed package

[Łukasz Zemczak]

Hello David, or anyone else affected,

Accepted humanity-icon-theme into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/humanity-icon-theme/0.6.11.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Icons are too big or the wrong icon is shown on hidpi screens

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Committed
Status in humanity-icon-theme source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  Humanity icons are sometimes displayed too big on hidpi screens in
  16.04.  On both 16.04 and 16.10, different icons are used on hidpi
  screens than non-hidpi screens.  Sometimes the icons look similar but
  with much thinner strokes, while other times an icon with a different
  metaphor is used.  Users on hidpi screens will notice that icons in
  applications like Nautilus, Transmission, etc. look different (not
  just clearer) on hidpi screens.

  The fix here is to add support for @2 icons to the Humanity theme by
  adding symbolic links for @2 icons and updating the index.theme files
  accordingly.

  We should backport the fix to 16.04 and 16.10, so Humanity icons look
  the same on hidpi screens as non-hidpi screens.

  
  [Test Case]

  Here are a few test cases: 
  1) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi 
screen are much larger.  (This applies to icons on the desktop as well.)
  -The fix should result in icons being the same size on both hidpi and 
lowdpi.
  
  2) Using a computer with a hidpi screen and one with a lowdpi screen running 
Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the 
toolbar uses an icon with a different metaphor on hidpi screens (an up arrow 
emerging from a folder) than on lowdpi screens (a sheet of paper emerging from 
a folder).
  - The fix should result in the "sheet of paper emerging from a folder" 
icon being used here on both hidpi and lowdpi screens.

  3) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons 
look sutbly different.  The strokes in icons on the hidpi screen will be 
visibly thinner on the hidpi screen because icons for bigger scale are used 
(say 48 on hidpi instead of 24) rather than rendering the original size icon at 
a larger resolution.
  - The fix should result in icons that have the same stroke width on hidpi 
and lowdpi screens.  The icons will still be sharper on the hidpi screen, but 
the lines won't be thinner.
  

  [Regression Potential]

  The patch is designed for compatibility where @2 support is not
  available by listing the @2 directories under "ScaledDirectories="
  rather than "Directories=".  However it's possible there could be
  other kinds of issues not found in testing.  If there are any
  omissions or errors in the index.theme, this could cause rendering
  issues for some categories of icons.  Comparing icons on a broad range
  of applications and systems should catch this class of issues.

  Hidpi users may find that their machine looks different after the
  update than it did before.  This is not a regression, but a fix to a
  bug that's been present all along.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions

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

[Dx-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens

[Łukasz Zemczak]

Hello David, or anyone else affected,

Accepted humanity-icon-theme into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/humanity-icon-theme/0.6.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: humanity-icon-theme (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: humanity-icon-theme (Ubuntu Yakkety)
   Status: New => Fix Committed

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

Title:
  Icons are too big or the wrong icon is shown on hidpi screens

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Committed
Status in humanity-icon-theme source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  Humanity icons are sometimes displayed too big on hidpi screens in
  16.04.  On both 16.04 and 16.10, different icons are used on hidpi
  screens than non-hidpi screens.  Sometimes the icons look similar but
  with much thinner strokes, while other times an icon with a different
  metaphor is used.  Users on hidpi screens will notice that icons in
  applications like Nautilus, Transmission, etc. look different (not
  just clearer) on hidpi screens.

  The fix here is to add support for @2 icons to the Humanity theme by
  adding symbolic links for @2 icons and updating the index.theme files
  accordingly.

  We should backport the fix to 16.04 and 16.10, so Humanity icons look
  the same on hidpi screens as non-hidpi screens.

  
  [Test Case]

  Here are a few test cases: 
  1) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi 
screen are much larger.  (This applies to icons on the desktop as well.)
  -The fix should result in icons being the same size on both hidpi and 
lowdpi.
  
  2) Using a computer with a hidpi screen and one with a lowdpi screen running 
Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the 
toolbar uses an icon with a different metaphor on hidpi screens (an up arrow 
emerging from a folder) than on lowdpi screens (a sheet of paper emerging from 
a folder).
  - The fix should result in the "sheet of paper emerging from a folder" 
icon being used here on both hidpi and lowdpi screens.

  3) Using a computer with hidpi screen and a computer with a lowdpi screen 
both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons 
look sutbly different.  The strokes in icons on the hidpi screen will be 
visibly thinner on the hidpi screen because icons for bigger scale are used 
(say 48 on hidpi instead of 24) rather than rendering the original size icon at 
a larger resolution.
  - The fix should result in icons that have the same stroke width on hidpi 
and lowdpi screens.  The icons will still be sharper on the hidpi screen, but 
the lines won't be thinner.
  

  [Regression Potential]

  The patch is designed for compatibility where @2 support is not
  available by listing the @2 directories under "ScaledDirectories="
  rather than "Directories=".  However it's possible there could be
  other kinds of issues not found in testing.  If there are any
  omissions or errors in the index.theme, this could cause rendering
  issues for some categories of icons.  Comparing icons on a broad range
  of applications and systems should catch this class of issues.

  Hidpi users may find that their machine looks different after the
  update than it did before.  This is not a regression, but a fix to a
  bug that's been present all along.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions

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

[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Łukasz Zemczak]

** Changed in: dbus (Ubuntu Xenial)
   Status: Fix Committed => Confirmed

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Fix Released
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions

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

[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

[Łukasz Zemczak]

** Changed in: dbus (Ubuntu Xenial)
   Status: Fix Released => Fix Committed

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Fix Released
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions

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

[Dx-packages] [Bug 1569293] Re: enable mono bindings on arm64 and ppc64el

[Łukasz Zemczak]

** Changed in: libappindicator (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

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

Title:
  enable mono bindings on arm64 and ppc64el

Status in libappindicator package in Ubuntu:
  New

Bug description:
  mono is now available on arm64 and ppc64el. please enable the bindings

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

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

[Dx-packages] [Bug 1566341] Re: ``Tomorrow'' appears untranslated

[Łukasz Zemczak]

As already mentioned on the mailing list, looking at the language-pack
we're using for OTA-10 the string seems to be properly translated:

#: ../src/utils.c:278
msgid "Tomorrow"
msgstr "Holnap"

The same with any other occurrences of the same string.

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

Title:
  ``Tomorrow'' appears untranslated

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Reported in the ubuntu-phone mailing list's ``Landing team 31.03.16''
  thread:

  Richard Somlói:
  >  "Tomorrow" should be "Holnap" in Hungarian, and it worked well with the 
previous images. Could somebody confirm it with another language?

  sil2100:
  > I just checked the indicator-datetime language pack and see Tomorrow as 
translated in all possible places there, so at least it's not a problem with 
the langpack itself. I would recommend filling in a bug against 
indicator-datetime so that the developers can take a look what's wrong.
  > But there is certainly something wrong since I get the same issue with the 
Polish locale.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1566341/+subscriptions

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

[Dx-packages] [Bug 954079] Re: right-click crashes graphical environment

[Łukasz Zemczak]

** Changed in: compiz-shift-plugin
 Assignee: Łukasz Zemczak (sil2100) => (unassigned)

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

Title:
  right-click crashes graphical environment

Status in Compiz Main Plugins:
  Fix Released
Status in Compiz Shift Switcher Plugin:
  Fix Committed
Status in compiz-plugins-main package in Ubuntu:
  Fix Released

Bug description:
  When i right-click, on any app it crashes the GUI
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,compiztoolbox,move,dbus,mousepoll,grid,resize,shift,place,gnomecompat,regex,wobbly,session,vpswitch,imgpng,blur,animation,fade,workarounds,cube,rotate,scale,expo,unitymtgrabhandles,unityshell]
  CompositorRunning: compiz
  DistUpgraded: Log time: 2012-02-28 12:06:54.300615
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Device [1019:9959]
 Subsystem: Elitegroup Computer Systems Device [1019:9959]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
  Package: unity 5.6.0-0ubuntu3
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae 
root=UUID=35b26662-ff31-495a-8d87-8ab507f5064d ro vga=792 splash quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  Tags:  precise precise precise precise ubuntu reproducible compiz-0.9
  Uname: Linux 3.2.0-18-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-03-13 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 09/30/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 1.04JPSA
  dmi.board.asset.tag: Tag 12345
  dmi.chassis.type: 10
  dmi.modalias: 
dmi:bvnPhoenix:bvr1.04JPSA:bd09/30/2009:svn:pn:pvr:rvn:rn:rvr:cvn:ct10:cvr:
  version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.6.99.901+git20120126-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz-plugins-main/+bug/954079/+subscriptions

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

[Dx-packages] [Bug 1563213] Re: Indicator session not localized

[Łukasz Zemczak]

** Changed in: langpack-o-matic
   Status: In Progress => Fix Released

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

Title:
   Indicator session not localized

Status in Canonical System Image:
  Confirmed
Status in langpack-o-matic:
  Fix Released
Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Flash the device.
  - Switch to Spanish.
  - Open indicator session.

  Expected result.
  - Indicator session is translated to Spanish.

  Actual result.
  - Indicator session is shown in English.

  current build number: 66
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  device name: frieza

  There are no indicator-session.mo files shipped in the system. Is
  indicator-session configured to export the translations to langpacks?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563213/+subscriptions

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

[Dx-packages] [Bug 1563213] Re: Indicator session not localized

[Łukasz Zemczak]

** Branch linked: lp:~sil2100/langpack-o-matic/add_session_touch

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

Title:
   Indicator session not localized

Status in Canonical System Image:
  Confirmed
Status in langpack-o-matic:
  In Progress
Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Flash the device.
  - Switch to Spanish.
  - Open indicator session.

  Expected result.
  - Indicator session is translated to Spanish.

  Actual result.
  - Indicator session is shown in English.

  current build number: 66
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  device name: frieza

  There are no indicator-session.mo files shipped in the system. Is
  indicator-session configured to export the translations to langpacks?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563213/+subscriptions

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

[Dx-packages] [Bug 1563213] Re: Indicator session not localized

[Łukasz Zemczak]

I don't see indicator-session templates/translations on
https://translations.launchpad.net/ubuntu-rtm/15.04 , so the project
probably needs to be re-configured to automatically export those to LP.
The other step would be to add the new package to langpack-o-matic -
this I will do on my side.

** Also affects: langpack-o-matic
   Importance: Undecided
   Status: New

** Changed in: langpack-o-matic
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

** Changed in: langpack-o-matic
   Importance: Undecided => Critical

** Changed in: langpack-o-matic
   Status: New => In Progress

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

Title:
   Indicator session not localized

Status in Canonical System Image:
  Confirmed
Status in langpack-o-matic:
  In Progress
Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Flash the device.
  - Switch to Spanish.
  - Open indicator session.

  Expected result.
  - Indicator session is translated to Spanish.

  Actual result.
  - Indicator session is shown in English.

  current build number: 66
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  device name: frieza

  There are no indicator-session.mo files shipped in the system. Is
  indicator-session configured to export the translations to langpacks?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563213/+subscriptions

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

[Dx-packages] [Bug 1560188] Re: unity8 hang w/ CPU pegged

[Łukasz Zemczak]

** Tags added: lt-blocker

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

Title:
  unity8 hang w/ CPU pegged

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  To trigger:
  1. Wipe (or freshly flash) rc-proposed on a krillin or mako
  2. Log in, configure time zone
  3. Tilt the phone to make the screen rotate

  At this point, the UI stopped responding and 'top' showed 100% CPU
  being used by unity8.

  I tried to get data from gdb, but it wasn't very helpful:
  (gdb) bt
  #0  0xa803cce2 in ?? ()
  #1  0xa803cb98 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  More details are needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560188/+subscriptions

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

[Dx-packages] [Bug 1539202] Re: please multiarchify the library packages

[Łukasz Zemczak]

** Changed in: libunity-webapps (Ubuntu)
   Status: New => In Progress

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

Title:
  please multiarchify the library packages

Status in libunity-webapps package in Ubuntu:
  In Progress

Bug description:
  please multiarchify the library packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1539202/+subscriptions

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

[Dx-packages] [Bug 1539202] Re: please multiarchify the library packages

[Łukasz Zemczak]

** Branch linked: lp:~sil2100/libunity-webapps/multi-arch

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

Title:
  please multiarchify the library packages

Status in libunity-webapps package in Ubuntu:
  New

Bug description:
  please multiarchify the library packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1539202/+subscriptions

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

[Dx-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher

[Łukasz Zemczak]

This bug was fixed in the package mediaplayer-app
0.20.5+15.04.20160106.1-0ubuntu1 in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/stable-phone-overlay

---

mediaplayer-app (0.20.5+15.04.20160106.1-0ubuntu1) vivid; urgency=medium

  [ Arthur Mello ]
  * Add X-Ubuntu-Touch=true to desktop file (LP: #1521773)
  * Translate app title (LP: #1521186)

mediaplayer-app (0.20.5+15.10.20150701-0ubuntu2~gcc5.1) wily;
urgency=medium

  * No-change test rebuild for g++5 ABI transition

mediaplayer-app (0.20.5+15.10.20150701-0ubuntu1) wily; urgency=medium

  [ Bill Filler ]
  * use OnlyShowIn=Old to hide from Apps scope (LP: #1387691)

  [ Renato Araujo Oliveira Filho ]
  * Fixed slider positioning. (LP: #1470331)

mediaplayer-app (0.20.5+15.10.20150630-0ubuntu1) wily; urgency=medium

  [ Renato Araujo Oliveira Filho ]
  * Updated app icon. (LP: #1457424)

mediaplayer-app (0.20.5+15.10.20150522-0ubuntu1) wily; urgency=medium

  [ Jim Hodapp ]
  * Quit playback after fatal playback error. (LP: #1435088)

 -- Bill Filler   Wed, 06 Jan 2016 17:11:48
+


** Changed in: mediaplayer-app (Ubuntu RTM)
   Status: Triaged => Fix Released

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

Title:
  Media Player should not be visible in the app scope and launcher

Status in Canonical System Image:
  Fix Released
Status in Ubuntu UX:
  Fix Committed
Status in mediaplayer-app package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  Triaged
Status in mediaplayer-app package in Ubuntu RTM:
  Fix Released
Status in url-dispatcher package in Ubuntu RTM:
  Invalid

Bug description:
  The mediaplayer is an 'auxiliary app' in the current design approach.
  That means that its purpouse it playback media launched by other apps
  (e.g Messaging) or scopes (e.g. Videos). It should not be launched
  from the App scopes.

  However, the 'Update' section System Settings should still display it
  when an update to mediaplayer is available.

  Current behaviour
  - Mediaplayer app displayed in App Scope, Launcher and Settings

  Desired behaviour
  - Mediaplayer app not displayed in App Scope or Launcher
  - Mediaplayer displayed in Settings > Update

  --- --- --- --- ---

  UX Comment:

  Fix appears partially released.

  Implemented:
  - Mediaplayer app not displayed in App Scope/ Ubuntu Store

  Not implemented:
  - Mediaplayer app not displayed in Launcher (still visible in launcher, can 
be 'pinned' to launcher, etc).
  - Mediaplayer displayed in Settings > Update

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+subscriptions

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

[Dx-packages] [Bug 1505688] Re: Alerts like for calendar events should use a default sound different from alarms

[Łukasz Zemczak]

** Tags removed: lt-blocker lt-category-visible

** Changed in: indicator-datetime (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Alerts like for calendar events should use a default sound different
  from alarms

Status in Canonical System Image:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Currently the new default alarm suond is used and it is not
  appropriate for calendar events

  Choose something like Marimbach

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505688/+subscriptions

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

[Dx-packages] [Bug 1338820] Re: Preview icon is pointing to the wrong location

[Łukasz Zemczak]

** Also affects: unity-lens-music (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  Preview icon is pointing to the wrong location

Status in Music Lens:
  Fix Committed
Status in unity-lens-music package in Ubuntu:
  Fix Released
Status in unity-lens-music source package in Trusty:
  New

Bug description:
  The unity "album_missing.png" icon has been moved to a different
  location, so we get this error and a missing image:

  WARN  2014-07-08 00:44:29 unity.iconloader IconLoader.cpp:755 Unable
  to load icon file:///usr/share/unity/6/album_missing.png at size
  96x96: Error opening file: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-music/+bug/1338820/+subscriptions

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

[Dx-packages] [Bug 1451946] Re: Menu disappears if a window is hidden and then shown again

[Łukasz Zemczak]

** Changed in: indicator-appmenu (Ubuntu)
 Assignee: Łukasz Zemczak (sil2100) => (unassigned)

** Changed in: indicator-appmenu (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Menu disappears if a window is hidden and then shown again

Status in appmenu-qt5 package in Ubuntu:
  In Progress
Status in indicator-appmenu package in Ubuntu:
  Invalid

Bug description:
  If a Qt 5 application window becomes hidden (QWidget::hide()) and then
  shown again, it loses its global menu.

  I have attached a simple application to show the problem. It occurs on
  Ubuntu 14.04 LTS with stock Qt 5.2.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1451946/+subscriptions

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

[Dx-packages] [Bug 1451946] Re: Menu disappears if a window is hidden and then shown again

[Łukasz Zemczak]

** Changed in: indicator-appmenu (Ubuntu)
   Status: Invalid => New

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

Title:
  Menu disappears if a window is hidden and then shown again

Status in appmenu-qt5 package in Ubuntu:
  In Progress
Status in indicator-appmenu package in Ubuntu:
  New

Bug description:
  If a Qt 5 application window becomes hidden (QWidget::hide()) and then
  shown again, it loses its global menu.

  I have attached a simple application to show the problem. It occurs on
  Ubuntu 14.04 LTS with stock Qt 5.2.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1451946/+subscriptions

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

[Dx-packages] [Bug 1505688] Re: Alerts like for calendar events should use a default sound different from alarms

[Łukasz Zemczak]

** Tags added: lt-blocker lt-category-visible

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

Title:
  Alerts like for calendar events should use a default sound different
  from alarms

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Currently the new default alarm suond is used and it is not
  appropriate for calendar events

  Choose something like Marimbach

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505688/+subscriptions

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

[Dx-packages] [Bug 1313248] Re: Ctrl+[Key] Shortcuts Assigned in QtCreator Do Not Work

[Łukasz Zemczak]

*** This bug is a duplicate of bug 1380702 ***
https://bugs.launchpad.net/bugs/1380702

Hello everyone,

I will mark this bug as a duplicate of another one (a newer one
actually) since that one is more 'generic'. It's an issue with appmenu-
qt5 and Qt5... more details in bug #1380702.

** This bug has been marked a duplicate of bug 1380702
   No keyboards shortcuts in QT apps

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

Title:
  Ctrl+[Key] Shortcuts Assigned in QtCreator Do Not Work

Status in appmenu-qt5 package in Ubuntu:
  Confirmed

Bug description:
  I recompiled one of my Qt applications tonight on Ubuntu 14.04. This
  application uses QActions that are are set up in the mainwindow.ui
  file. (I originally did this with QtDesigner some two year ago, but
  have updated the application for Qt 5 in the mean time.)

  When appmenu-qt5 is installed, the Ctrl+[key] shortcuts of the actions
  on the main menubar do not work. If I remove appment-qt5, they do work
  as expected.

  Oddly enough, the edit actions on the edit dialog do work, but they
  are disabled and enabled multiple times.

  I tried disabling and enabling the actions on the main menubar in code
  which didn't help. I also tried assigning the short cut keys via code
  and that did not help.

  I am using 14.04 LTS, appmenu-qt5 0.3.0+14.04.20140415-0ubuntu1, and
  the Qt program found at https://github.com/Dyrcona/omiquji

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1313248/+subscriptions

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

[Dx-packages] [Bug 1302084] Re: Menu in the global title bar is missing after a window child in Qt5 applications

[Łukasz Zemczak]

Can anyone try to reproduce this issue indeed? Would be good to know if
it got fixed with the past changes in the distribution.

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

Title:
  Menu in the global title bar is missing after a window child in Qt5
  applications

Status in appmenu-qt5:
  In Progress
Status in Application Menu Indicator:
  New
Status in Unity:
  Invalid
Status in appmenu-qt5 package in Ubuntu:
  In Progress

Bug description:
  steps to get this behavior

  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+subscriptions

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

[Dx-packages] [Bug 1451946] Re: Menu disappears if a window is hidden and then shown again

[Łukasz Zemczak]

Thanks for looking into that Marco! I think the problem might be indeed
something with indicator-appmenu. I checked appmenu-qt5 and everything
seems fine there: appmenu-qt5 fetches the related QMenu and exports it
through DBus. During the hide/show the menu stays the same, the window
stays the same, so appmenu-qt5 has no reason to re-export it again as
all the previous contents are valid - and appmenu-qt5 really doesn't do
much more. It only re-exports menus when the menu parent changes, or the
menu itself. Here it has no reason to do that as none of the important
bits (the winId or the QMenu) changed. But somehow, the once exported
menu is invalidated/lost somewhere.

Adding indicator-appmenu to the investigation.

** Also affects: indicator-appmenu (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: indicator-appmenu (Ubuntu)
 Assignee: (unassigned) = Łukasz Zemczak (sil2100)

** Changed in: indicator-appmenu (Ubuntu)
   Status: New = In Progress

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

Title:
  Menu disappears if a window is hidden and then shown again

Status in appmenu-qt5 package in Ubuntu:
  In Progress
Status in indicator-appmenu package in Ubuntu:
  In Progress

Bug description:
  If a Qt 5 application window becomes hidden (QWidget::hide()) and then
  shown again, it loses its global menu.

  I have attached a simple application to show the problem. It occurs on
  Ubuntu 14.04 LTS with stock Qt 5.2.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1451946/+subscriptions

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

[Dx-packages] [Bug 1056108] Re: Week 39 - No image for dash icon

[Łukasz Zemczak]

** Changed in: unity-2d
   Status: Fix Committed = Fix Released

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

Title:
  Week 39 - No image for dash icon

Status in Unity 2D:
  Fix Released
Status in unity-2d package in Ubuntu:
  Fix Released

Bug description:
  [Test Case]
  1. Start unity-2d
 - Verify that the Dash icon in the launcher looks normally and is 
available

  [Regression Potential]
  No regression potential.

  Original description:

  Unity 2D tests - Ubuntu 12.04 Precise with ppa:unity-team/sru

  Issue: Dash icon on launcher has no image, instead has a ?
  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.14.0+bzr2401ubuntu0+706 [origin: LP-PPA-unity-team-sru]
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CrashDB: unity
  CurrentDmesg:
   [   25.904643] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   36.029755] eth0: no IPv6 routers present
  Date: Tue Sep 25 12:01:16 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:1507]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  MachineType: FUJITSU LIFEBOOK E780
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic-pae 
root=UUID=4aaa0a72-55cd-4939-a8f4-29a94a0238d1 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2011
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.20
  dmi.board.name: FJNB210
  dmi.board.vendor: FUJITSU
  dmi.board.version: CP477721-02
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: E78__
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.20:bd01/24/2011:svnFUJITSU:pnLIFEBOOKE780:pvr:rvnFUJITSU:rnFJNB210:rvrCP477721-02:cvnFUJITSU:ct10:cvrE78__:
  dmi.product.name: LIFEBOOK E780
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.4
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-2d/+bug/1056108/+subscriptions

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

[Dx-packages] [Bug 1081610] Re: Autopilot ibus tests failing due to different expected values

[Łukasz Zemczak]

** Changed in: unity
   Status: In Progress = Won't Fix

** Changed in: unity (Ubuntu)
   Status: In Progress = Won't Fix

** Changed in: unity
 Assignee: Łukasz Zemczak (sil2100) = (unassigned)

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

Title:
  Autopilot ibus tests failing due to different expected values

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix

Bug description:
  Some ibus autopilot tests fail if ibus returns different results in
  the lookup table than expected.

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

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

[Dx-packages] [Bug 1066764] Re: Unity fails to load on old hardware (compiz enabling LLVMpipe has no effect and Mesa tries to use hardware still)

[Łukasz Zemczak]

** Changed in: compiz
 Assignee: Łukasz Zemczak (sil2100) = (unassigned)

** Changed in: nux
 Assignee: Łukasz Zemczak (sil2100) = (unassigned)

** Changed in: nux (Ubuntu)
 Assignee: Łukasz Zemczak (sil2100) = (unassigned)

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

Title:
  Unity fails to load on old hardware (compiz enabling LLVMpipe has no
  effect and Mesa tries to use hardware still)

Status in Compiz:
  Triaged
Status in Nux:
  Triaged
Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Triaged

Bug description:
  Following the removal of unity-2d, Unity will not run on some hardware that 
does not support 3d. On login I get the background image but no launcher or 
panel.
  .xsession-errors attached

  If I add to /etc/environment the line
  LIBGL_ALWAYS_SOFTWARE=1
  then unity start ok

  This problem appeared after the fix to bug #1039155 (Unity fails to
  load on old hardware (blank desktop; only wallpaper). Missing
  automatic fallback to LLVMpipe when unity_support_test fails) was
  released.

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

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

[Dx-packages] [Bug 1126205] Re: [FFe] Bring Unity appmenu / HUD integration to Qt5

[Łukasz Zemczak]

** Changed in: indicator-appmenu (Ubuntu)
   Status: In Progress = Invalid

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

Title:
  [FFe] Bring Unity appmenu / HUD integration to Qt5

Status in Application menu for Qt4:
  Fix Committed
Status in libdbusmenu-qt:
  Fix Committed
Status in appmenu-qt package in Ubuntu:
  Fix Released
Status in indicator-appmenu package in Ubuntu:
  Invalid
Status in libdbusmenu-qt package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  We're currently lacking patches in Qt5 that would enable appmenu / HUD
  support in Qt5.

  == CHANGE ==

  https://code.launchpad.net/~sil2100/ubuntu/raring/qtbase-opensource-
  src/enable-appmenu - the added patch
  debian/patches/enable_appmenu_support.diff

  The patch re-adds appmenu support as it was in Qt4 - it's based on the
  approved Qt4 upstream changes we had landed. It's a direct port of the
  same changes.

  == TESTS ==

  The packages (and Qt5 with the patch) builds and works, as tested on
  the ppa:sil2100/qt PPA by some users.

  == WHY? ==

  Since the release of the Ubuntu SDK, our distro started directly
  depending on Qt5. In the current form, Qt5 has no global menu support
  - all Qt5 compiled applications have menus in windows. HUD support for
  those applications is also non-existent. We think this is
  unacceptable, especially that we're advertising development using our
  Ubuntu SDK (Qt5).

  Note that this also blocks fix for bug 1126210 (see
  https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
  src/+bug/1126210/comments/9).

  As mentioned in the comments, this is a distro-only fix for now, as
  upstream support does require more time to be done (see bug LP:
  #1157213). This distro patch would be essentially removed and replaced
  by the QPA support upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt/+bug/1126205/+subscriptions

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

[Dx-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher

[Łukasz Zemczak]

This bug was fixed in the package mediaplayer-app
0.20.5+15.04.20150701-0ubuntu1 in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/stable-phone-overlay

---

mediaplayer-app (0.20.5+15.04.20150701-0ubuntu1) vivid; urgency=medium

  [ Bill Filler ]
  * use OnlyShowIn=Old to hide from Apps scope (LP: #1387691)

  [ Renato Araujo Oliveira Filho ]
  * Fixed slider positioning. (LP: #1470331)

mediaplayer-app (0.20.5+15.10.20150630-0ubuntu1) wily; urgency=medium

  [ Renato Araujo Oliveira Filho ]
  * Updated app icon. (LP: #1457424)

mediaplayer-app (0.20.5+15.10.20150522-0ubuntu1) wily; urgency=medium

  [ Jim Hodapp ]
  * Quit playback after fatal playback error. (LP: #1435088)

mediaplayer-app (0.20.5+15.04.20150428-0ubuntu1) vivid; urgency=medium

  [ CI Train Bot ]
  * Resync trunk.

  [ Ricardo Mendoza ]
  * Bug #1417006 Performance/Rendering fixes:  * Remove clipping on
video loader  * Remove unused rectangles (overdraw) (LP: #1417006)

 -- CI Train Bot ci-train-...@canonical.com  Wed, 01 Jul 2015 21:53:38
+


** Changed in: mediaplayer-app (Ubuntu RTM)
   Status: Invalid = Fix Released

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

Title:
  Media Player should not be visible in the app scope and launcher

Status in the base for Ubuntu mobile products:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in mediaplayer-app package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  Fix Released
Status in mediaplayer-app package in Ubuntu RTM:
  Fix Released
Status in url-dispatcher package in Ubuntu RTM:
  Invalid

Bug description:
  The mediaplayer is an 'auxiliary app' in the current design approach.
  That means that its purpouse it playback media launched by other apps
  (e.g Messaging) or scopes (e.g. Videos). It should not be launched
  from the App scopes.

  However, the 'Update' section System Settings should still display it
  when an update to mediaplayer is available.

  Current behaviour
  - Mediaplayer app displayed in App Scope, Launcher and Settings

  Desired behaviour
  - Mediaplayer app not displayed in App Scope or Launcher
  - Mediaplayer displayed in Settings  Update

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+subscriptions

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

[Dx-packages] [Bug 1451946] Re: Menu disappears if a window is hidden and then shown again

[Łukasz Zemczak]

** Changed in: appmenu-qt5 (Ubuntu)
   Status: Triaged = In Progress

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

Title:
  Menu disappears if a window is hidden and then shown again

Status in appmenu-qt5 package in Ubuntu:
  In Progress

Bug description:
  If a Qt 5 application window becomes hidden (QWidget::hide()) and then
  shown again, it loses its global menu.

  I have attached a simple application to show the problem. It occurs on
  Ubuntu 14.04 LTS with stock Qt 5.2.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1451946/+subscriptions

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

[Dx-packages] [Bug 1451946] Re: Menu disappears if a window is hidden and then shown again

[Łukasz Zemczak]

** Changed in: appmenu-qt5 (Ubuntu)
 Assignee: (unassigned) = Łukasz Zemczak (sil2100)

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

Title:
  Menu disappears if a window is hidden and then shown again

Status in appmenu-qt5 package in Ubuntu:
  New

Bug description:
  If a Qt 5 application window becomes hidden (QWidget::hide()) and then
  shown again, it loses its global menu.

  I have attached a simple application to show the problem. It occurs on
  Ubuntu 14.04 LTS with stock Qt 5.2.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1451946/+subscriptions

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

[Dx-packages] [Bug 1451946] Re: Menu disappears if a window is hidden and then shown again

[Łukasz Zemczak]

Also reproduced on 15.04, seems to be an overall problem with our
approach in Qt 5. I'll try to find some free cycles to take a closer
look into this ASAP.

** Changed in: appmenu-qt5 (Ubuntu)
   Status: New = Triaged

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

Title:
  Menu disappears if a window is hidden and then shown again

Status in appmenu-qt5 package in Ubuntu:
  Triaged

Bug description:
  If a Qt 5 application window becomes hidden (QWidget::hide()) and then
  shown again, it loses its global menu.

  I have attached a simple application to show the problem. It occurs on
  Ubuntu 14.04 LTS with stock Qt 5.2.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1451946/+subscriptions

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

[Dx-packages] [Bug 1435348] Re: qtcreator recently used file/project submenu empty

[Łukasz Zemczak]

** Changed in: appmenu-qt5 (Ubuntu)
 Assignee: (unassigned) = Łukasz Zemczak (sil2100)

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

Title:
  qtcreator recently used file/project submenu empty

Status in appmenu-qt5 package in Ubuntu:
  New
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  New

Bug description:
  Using current vivid, with integrated menu (appmenu-qt5), the qtcreator
  files- recent files/projects submenus are empty, they work fine if
  the qt theme env variable is empty (use local menus instead)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1435348/+subscriptions

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

[Dx-packages] [Bug 1435348] Re: qtcreator recently used file/project submenu empty

[Łukasz Zemczak]

I just sat down to it once again. I probably found what specific thing
in qtcreator causes the unwanted behaviour. It seems those two sub-menus
are the only places where the creator is doing menu()-clear(); which I
think might be what results in those issues in either appmenu-qt5 or the
menu exporter itself. I'll prepare a stand-alone test-case and try
debugging it. For now I'll set the appmenu-qt5 task as In Progress and
then change it to the root cause itself.

I actually wonder if we didn't have the same problems in previous
series?

** Changed in: appmenu-qt5 (Ubuntu)
   Status: New = In Progress

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

Title:
  qtcreator recently used file/project submenu empty

Status in appmenu-qt5 package in Ubuntu:
  In Progress
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  New

Bug description:
  Using current vivid, with integrated menu (appmenu-qt5), the qtcreator
  files- recent files/projects submenus are empty, they work fine if
  the qt theme env variable is empty (use local menus instead)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1435348/+subscriptions

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

[Dx-packages] [Bug 1435348] Re: qtcreator recently used file/project submenu empty

[Łukasz Zemczak]

Interesting - I can reproduce it as well. This must be caused by those
entries being added differently which makes appmenu-qt5 confused. In
theory appmenu should handle all cases as we're basically fetching the
QMenuBar's pointer from the application and just exporting things as
they go, so in theory there should be no issue with getting out-of-sync.

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

Title:
  qtcreator recently used file/project submenu empty

Status in appmenu-qt5 package in Ubuntu:
  New
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  New

Bug description:
  Using current vivid, with integrated menu (appmenu-qt5), the qtcreator
  files- recent files/projects submenus are empty, they work fine if
  the qt theme env variable is empty (use local menus instead)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1435348/+subscriptions

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

[Dx-packages] [Bug 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Łukasz Zemczak]

I was just wondering: is this also causing issues in vivid as well? We
have an Ubuntu task for this bug here and this change didn't land in
vivid, which is a requirement in case of reproducibility.

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

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+subscriptions

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

[Dx-packages] [Bug 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Łukasz Zemczak]

Ok, so I'm leaving it on our issue list for Ubuntu until the situation
gets cleared up - this way it will stay on our radar. Thanks!

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

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+subscriptions

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

[Dx-packages] [Bug 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Łukasz Zemczak]

** Tags added: lt-category-visible

** Tags added: lt-blocker

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

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  New

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+subscriptions

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

[Dx-packages] [Bug 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

[Łukasz Zemczak]

** Also affects: indicator-datetime (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  New

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+subscriptions

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

[Dx-packages] [Bug 1209106] Re: system tray icon is next to launcher

[Łukasz Zemczak]

** Changed in: appmenu-qt5
   Status: New = In Progress

** Changed in: appmenu-qt5 (Ubuntu)
   Status: New = In Progress

** Changed in: appmenu-qt5
 Assignee: (unassigned) = Dmitry Shachnev (mitya57)

** Changed in: appmenu-qt5 (Ubuntu)
 Assignee: (unassigned) = Dmitry Shachnev (mitya57)

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

Title:
  system tray icon is next to launcher

Status in Application menu for Qt5:
  In Progress
Status in Qt:
  New
Status in Qt StatusNotifierItem plugin:
  Confirmed
Status in appmenu-qt5 package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Confirmed

Bug description:
  The system tray icon is next to the launcher in the latest verion of
  Qt Creator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1209106/+subscriptions

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

[Dx-packages] [Bug 1378935] Re: appmenu-qt5 prevents apps from using native Gtk+ dialogs

[Łukasz Zemczak]

Yeah, this is a known issue. When I was first creating appmenu-qt5 there
simply was no gtk2 platformtheme, so extending QGnomeTheme was enough.
Now indeed we might need to find a solution to actually use the gtk2
theme somehow, too bad only one theme can be loaded by default. Well,
nothing we cannot work around.

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

Title:
  appmenu-qt5 prevents apps from using native Gtk+ dialogs

Status in Application menu for Qt5:
  New
Status in appmenu-qt5 package in Ubuntu:
  New

Bug description:
  Hi,

  QtBase ships with a platform theme called gtk2, which enables native
  file dialog, color dialog and font dialog on Gtk-based environments
  (such as Unity and GNOME).

  
https://qt.gitorious.org/qt/qtbase/source/5.3:src/platformsupport/themes/genericunix/qgenericunixthemes.cpp#L593

  However, when appmenu-qt5 is installed, the platform theme is forcibly
  set to appmenu-qt5 (via /etc/profile.d/appmenu-qt5.sh). Thus, the
  advantages of gtk2 theme like native dialogs are not available.

  Test case:

  0) Install qtcreator and appmenu-qt5;
  1) Launch qtcreator and select Open Project;
  2) Launch QT_QPA_PLATFORMTHEME= qtcreator and select Open Project.

  In case 1), the standard Qt file dialog will be used (looking a stranger in 
Gtk environment).
  In case 2), the native Gtk+ file dialog will be used (looking nice).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1378935/+subscriptions

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

[Dx-packages] [Bug 1209106] Re: system tray icon is next to launcher

[Łukasz Zemczak]

** Also affects: appmenu-qt5
   Importance: Undecided
   Status: New

** Also affects: appmenu-qt5 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  system tray icon is next to launcher

Status in Application menu for Qt5:
  New
Status in Qt:
  New
Status in Qt StatusNotifierItem plugin:
  Confirmed
Status in appmenu-qt5 package in Ubuntu:
  New
Status in sni-qt package in Ubuntu:
  Confirmed

Bug description:
  The system tray icon is next to the launcher in the latest verion of
  Qt Creator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1209106/+subscriptions

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

[Dx-packages] [Bug 1394887] Re: appmenu-qt5 fails to build against Qt 5.4.0 beta

[Łukasz Zemczak]

** Changed in: appmenu-qt5
   Status: In Progress = Won't Fix

** Changed in: appmenu-qt5
   Status: Won't Fix = 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/1394887

Title:
  appmenu-qt5 fails to build against Qt 5.4.0 beta

Status in Application menu for Qt5:
  Fix Released
Status in appmenu-qt5 package in Ubuntu:
  Fix Released

Bug description:
  appmenu-qt5 fails to build against Qt 5.4.0 beta:

  https://launchpad.net/~canonical-
  qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4580920/+listing-
  archive-extra

  appmenuplatformmenubar.cpp:304:36: error: no matching function for call to 
'QKdeTheme::QKdeTheme(const QString, int)'
   : QKdeTheme(kdeHome, kdeVersion)

  More information about Qt testing versions at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1394887/+subscriptions

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

[Dx-packages] [Bug 1394887] Re: appmenu-qt5 fails to build against Qt 5.4.0 beta

[Łukasz Zemczak]

Ouch, not looking good I'm afraid. Need to see if they moved/renamed the
QKdeTheme by any chance. If they didn't and completely removed it,
things might get hairy. But I suppose we anyway will be able to get the
menu decorations one way or another.

** Changed in: appmenu-qt5
 Assignee: (unassigned) = Łukasz Zemczak (sil2100)

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

Title:
  appmenu-qt5 fails to build against Qt 5.4.0 beta

Status in Application menu for Qt5:
  New
Status in “appmenu-qt5” package in Ubuntu:
  New

Bug description:
  appmenu-qt5 fails to build against Qt 5.4.0 beta:

  https://launchpad.net/~canonical-
  qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4580920/+listing-
  archive-extra

  appmenuplatformmenubar.cpp:304:36: error: no matching function for call to 
'QKdeTheme::QKdeTheme(const QString, int)'
   : QKdeTheme(kdeHome, kdeVersion)

  More information about Qt testing versions at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1394887/+subscriptions

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

[Dx-packages] [Bug 1394887] Re: appmenu-qt5 fails to build against Qt 5.4.0 beta

[Łukasz Zemczak]

I just briefly checked and it seems I read the error wrong, it seems
that the constructor simply changed its parameters. Let's fix that then.

** Changed in: appmenu-qt5
   Status: New = In Progress

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

Title:
  appmenu-qt5 fails to build against Qt 5.4.0 beta

Status in Application menu for Qt5:
  In Progress
Status in “appmenu-qt5” package in Ubuntu:
  New

Bug description:
  appmenu-qt5 fails to build against Qt 5.4.0 beta:

  https://launchpad.net/~canonical-
  qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4580920/+listing-
  archive-extra

  appmenuplatformmenubar.cpp:304:36: error: no matching function for call to 
'QKdeTheme::QKdeTheme(const QString, int)'
   : QKdeTheme(kdeHome, kdeVersion)

  More information about Qt testing versions at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1394887/+subscriptions

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

[Dx-packages] [Bug 1394887] Re: appmenu-qt5 fails to build against Qt 5.4.0 beta

[Łukasz Zemczak]

** Branch linked: lp:~sil2100/appmenu-qt5/fix_ftbfs_5.4.0

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

Title:
  appmenu-qt5 fails to build against Qt 5.4.0 beta

Status in Application menu for Qt5:
  In Progress
Status in “appmenu-qt5” package in Ubuntu:
  New

Bug description:
  appmenu-qt5 fails to build against Qt 5.4.0 beta:

  https://launchpad.net/~canonical-
  qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4580920/+listing-
  archive-extra

  appmenuplatformmenubar.cpp:304:36: error: no matching function for call to 
'QKdeTheme::QKdeTheme(const QString, int)'
   : QKdeTheme(kdeHome, kdeVersion)

  More information about Qt testing versions at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1394887/+subscriptions

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

[Dx-packages] [Bug 1394621] Re: Test bug #2 - ignore this one, will be removed

[Łukasz Zemczak]

** Changed in: appmenu-qt5
   Status: New = Invalid

** Changed in: appmenu-qt5 (Ubuntu)
   Status: New = Invalid

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

Title:
  Test bug #2 - ignore this one, will be removed

Status in Application menu for Qt5:
  Invalid
Status in “appmenu-qt5” package in Ubuntu:
  Invalid

Bug description:
  Test bug #2 - ignore this one, will be removed

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1394621/+subscriptions

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

[Dx-packages] [Bug 1394620] Re: Test bug #1 - ignore this one, will be removed

[Łukasz Zemczak]

** Changed in: appmenu-qt5
   Status: New = Invalid

** Changed in: appmenu-qt5 (Ubuntu)
   Status: New = Invalid

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

Title:
  Test bug #1 - ignore this one, will be removed

Status in Application menu for Qt5:
  Invalid
Status in “appmenu-qt5” package in Ubuntu:
  Invalid

Bug description:
  Test bug #1 - ignore this one, will be removed

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1394620/+subscriptions

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

[Dx-packages] [Bug 1340952] Re: Video and Music scopes should provide non-file:/// based URIs

[Łukasz Zemczak]

** Tags added: lt-age-20140911 lt-blocker lt-category-visible lt-prio-
high

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

Title:
  Video and Music scopes should provide non-file:/// based URIs

Status in Media Player App:
  In Progress
Status in Unity Media Scanner Scope:
  Confirmed
Status in QML plugin for Scopes:
  Confirmed
Status in “url-dispatcher” package in Ubuntu:
  In Progress

Bug description:
  There are some mp4 videos found/indexed by mediascanner-service-2.0 from 
~/Pictures. The thumbnails of those are shown in the Video scope but can not be 
played. If the video is moved over to ~/Videos, the videos are played just fine.
  mako utopic r119

To manage notifications about this bug go to:
https://bugs.launchpad.net/mediaplayer-app/+bug/1340952/+subscriptions

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

[Dx-packages] [Bug 1323853] Re: No menubar for QtQuick.Controls based applications

[Łukasz Zemczak]

** Changed in: appmenu-qt5 (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: appmenu-qt5
   Status: New = Triaged

** Changed in: appmenu-qt5
   Importance: Undecided = Medium

** Changed in: appmenu-qt5 (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  No menubar for QtQuick.Controls based applications

Status in Application menu for Qt5:
  Triaged
Status in “appmenu-qt5” package in Ubuntu:
  Triaged

Bug description:
  For QtQuick.Controls based applications no menubars are shown. The
  following message is printed to the console instead:

  appmenu-qt: handleReparent 128 The given QWindow has no QMenuBar
  assigned

  Apparently this is because QtQuick.Controls menus are built upon
  QQuickMenuBar and
  QGuiApplicationPrivate::platformTheme()-createPlatformMenuBar();
  instead of QMenuBar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1323853/+subscriptions

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

[Dx-packages] [Bug 1354406] Re: PIN-locked phone becomes unresponsive after simultaneous alarms

[Łukasz Zemczak]

** Tags added: lt-blocker lt-category-visible lt-prio-high

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

Title:
  PIN-locked phone becomes unresponsive after simultaneous alarms

Status in “indicator-datetime” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1. Run recent image (I'm on #178 on mako)
  2. Setup pin lock in system settings
  3. Enter two events for the same time, soon, in your google calendar
  4. Have your phone sync your google calendar using system settings - accounts
  5. Lock screen
  6. Wait for the events

  What happens

  * Multiple alarms go off, notification on screen. You can hear two rings at 
once (separate bug)
  * Tap notification to make it go away
  * Sound continues, but there's no notification on screen.

  At this point you cannot unlock the phone. You can swipe away the
  welcome screen, but the display dims a bit once you do, and nothing is
  clickable - can't click numbers in pin unlock, can't swipe down
  indicators..

  You have to reboot the phone to get past this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+subscriptions

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

[Dx-packages] [Bug 1341603] Re: Missing menus in ubuntu-sdk when appmenu-qt5 is installed

[Łukasz Zemczak]

** Changed in: appmenu-qt5 (Ubuntu)
 Assignee: (unassigned) = Łukasz Zemczak (sil2100)

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

Title:
  Missing menus in ubuntu-sdk when appmenu-qt5 is installed

Status in “appmenu-qt5” package in Ubuntu:
  New

Bug description:
  The menu bar in ubuntu-sdk is completely missing when appmenu-qt5 is
  installed.

  This has been tested in both Ubuntu(Default) and AwesomeWM.

  When using Ubuntu(Default) I pressed alt to open the menu search
  dialog but was unable to find any menu items.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140415-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Mon Jul 14 16:23:36 2014
  InstallationDate: Installed on 2014-02-13 (150 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1341603/+subscriptions

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

[Dx-packages] [Bug 1302084] Re: Menu in the global title bar is missing after a window child in Qt5 applications

[Łukasz Zemczak]

** Changed in: unity
   Status: New = Invalid

** Also affects: indicator-appmenu
   Importance: Undecided
   Status: New

** Changed in: appmenu-qt5
   Status: In Progress = Invalid

** Changed in: appmenu-qt5 (Ubuntu)
   Status: In Progress = Invalid

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

Title:
  Menu in the global title bar is missing after a window child in Qt5
  applications

Status in Application menu for Qt5:
  In Progress
Status in The Application Menu:
  New
Status in Unity:
  Invalid
Status in “appmenu-qt5” package in Ubuntu:
  In Progress

Bug description:
  steps to get this behavior

  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+subscriptions

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

[Dx-packages] [Bug 1302084] Re: Menu in the global title bar is missing after a window child in Qt5 applications

[Łukasz Zemczak]

So, sorry for meddling with the projects here, but Trevinho first
thought it's an old indicator-appmenu issue, but we see it still might
be related to appmenu-qt5. LIM is not prepared for us still exporting a
menu when the child window is opened. Not sure if we can fix this from
our side - we might need a tweak in indicator-appmenu...

** Changed in: appmenu-qt5
   Status: Invalid = In Progress

** Changed in: appmenu-qt5 (Ubuntu)
   Status: Invalid = In Progress

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

Title:
  Menu in the global title bar is missing after a window child in Qt5
  applications

Status in Application menu for Qt5:
  In Progress
Status in The Application Menu:
  New
Status in Unity:
  Invalid
Status in “appmenu-qt5” package in Ubuntu:
  In Progress

Bug description:
  steps to get this behavior

  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+subscriptions

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

[Dx-packages] [Bug 1302084] Re: Menu in title bar is missing after a modal window child

[Łukasz Zemczak]

** Changed in: appmenu-qt5
   Status: New = Confirmed

** Changed in: appmenu-qt5 (Ubuntu)
   Importance: Undecided = Medium

** Changed in: appmenu-qt5
   Importance: Undecided = Medium

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

Title:
  Menu in title bar is missing after a modal window child

Status in Application menu for Qt5:
  Confirmed
Status in “appmenu-qt5” package in Ubuntu:
  Confirmed

Bug description:
  steps to get this behavior

  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+subscriptions

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

[Dx-packages] [Bug 1302084] Re: Menu in title bar is missing after a modal window child

[Łukasz Zemczak]

Thank you for reporting the issue! I will be looking into it shortly.

** Changed in: appmenu-qt5
 Assignee: (unassigned) = Łukasz Zemczak (sil2100)

** Changed in: appmenu-qt5 (Ubuntu)
 Assignee: (unassigned) = Łukasz Zemczak (sil2100)

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

Title:
  Menu in title bar is missing after a modal window child

Status in Application menu for Qt5:
  Confirmed
Status in “appmenu-qt5” package in Ubuntu:
  Confirmed

Bug description:
  steps to get this behavior

  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+subscriptions

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

[Dx-packages] [Bug 1302084] Re: Menu in title bar is missing after a modal window child

[Łukasz Zemczak]

So, I had a look at the bug briefly. I can reproduce it easily - some first 
hand observations: 
- this only happens with the menus are in the window title-bar - everything 
works correctly with the global menu
- once the modal window is opened and then closed, HUD works normally
- when using HUD in the broken state to open up any modal window (like the 
about one that caused the failure), the menu appears on the modal window instead

Some first thoughts based on those observations: first of all, I'm not
sure if it's really a problem in appmenu-qt5. Since it seems that
appmenu exports the menu correctly through DBus, making it accessible by
unity7 and hud. The problem seems to be with parent identification. The
application is still the parent of the menu, but not the correct window.
I will check if all is correct from our appmenu's perspective.

** Changed in: appmenu-qt5 (Ubuntu)
   Status: Confirmed = In Progress

** Changed in: appmenu-qt5
   Status: Confirmed = In Progress

** Changed in: appmenu-qt5
   Importance: Medium = High

** Changed in: appmenu-qt5 (Ubuntu)
   Importance: Medium = High

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

Title:
  Menu in title bar is missing after a modal window child

Status in Application menu for Qt5:
  In Progress
Status in “appmenu-qt5” package in Ubuntu:
  In Progress

Bug description:
  steps to get this behavior

  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+subscriptions

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

[Dx-packages] [Bug 1302084] Re: Menu in title bar is missing after a modal window child

[Łukasz Zemczak]

And something else - it seems that modeless dialogs also cause the
problem.

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

Title:
  Menu in title bar is missing after a modal window child

Status in Application menu for Qt5:
  In Progress
Status in “appmenu-qt5” package in Ubuntu:
  In Progress

Bug description:
  steps to get this behavior

  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+subscriptions

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

[Dx-packages] [Bug 1302084] Re: Menu in the global title bar is missing after a window child

[Łukasz Zemczak]

** Summary changed:

- Menu in title bar is missing after a modal window child 
+ Menu in the global title bar is missing after a window child

** Changed in: appmenu-qt5
   Importance: High = Critical

** Changed in: appmenu-qt5 (Ubuntu)
   Importance: High = Critical

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

Title:
  Menu in the global title bar is missing after a window child

Status in Application menu for Qt5:
  In Progress
Status in “appmenu-qt5” package in Ubuntu:
  In Progress

Bug description:
  steps to get this behavior

  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+subscriptions

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

[Dx-packages] [Bug 1302084] Re: Menu in the global title bar is missing after a window child

[Łukasz Zemczak]

Ok, so... all seems to look ok from the side of appmenu-qt5 here. I will
be looking more on Monday, but I have also added unity as a possible
culprit since there is some probability it's not appmenu-qt5 fault.
Trevisan is not around today, so we'll know more next week. Bumped the
bug to critical as basically opening ANY dialogish window in the
application with LIM enabled causes the menu to malfunction. And this is
a serious issue.

** Also affects: unity
   Importance: Undecided
   Status: New

** Summary changed:

- Menu in the global title bar is missing after a window child
+ Menu in the global title bar is missing after a window child in Qt5 
applications

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

Title:
  Menu in the global title bar is missing after a window child in Qt5
  applications

Status in Application menu for Qt5:
  In Progress
Status in Unity:
  New
Status in “appmenu-qt5” package in Ubuntu:
  In Progress

Bug description:
  steps to get this behavior

  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+subscriptions

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

[Dx-packages] [Bug 1306472] Re: QToolBar Icons not loaded properly.

[Łukasz Zemczak]

** Changed in: appmenu-qt5
   Status: In Progress = Fix Released

** Changed in: appmenu-qt5 (Ubuntu)
 Assignee: (unassigned) = Łukasz Zemczak (sil2100)

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

Title:
  QToolBar Icons not loaded properly.

Status in Application menu for Qt5:
  Fix Released
Status in “appmenu-qt5” package in Ubuntu:
  Fix Released

Bug description:
  When using a QToolBar with a basic Qt application, the icons can be
  populated from a theme. Either using QIcon::FromTheme(), or setting
  them in the associated action using the forms designer in Qt. (The
  name given for the icon is the freedesktop.org standard naming
  convention)

  Under appmenu-qt5 these icons do not appear to be being loaded
  correctly, resulting in a toolbar populated with just the action text.

  A minimal example illustrates the problem here:
  https://github.com/GilesBathgate/appmenu-bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1306472/+subscriptions

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

[Dx-packages] [Bug 1273306] Re: python3.3 crashed with SIGSEGV in QWidget::destroy()

[Łukasz Zemczak]

** Branch linked: lp:~sil2100/kubuntu-packaging/qtbase-opensource-
src_5.0.2_qapp_fix

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

Title:
  python3.3 crashed with SIGSEGV in QWidget::destroy()

Status in Window Mocker:
  New
Status in “appmenu-qt” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress

Bug description:
  This happens when trying to run window-mocker with python3:

  $ bzr branch lp:~coreygoldberg/window-mocker/py3
  $ cd py3
  $ PYTHONPATH=. python3 bin/window-mocker -t Qt5

  When merely closing the window it cleanly exits for me; but when
  resizing the window I get this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: python3.3-minimal 3.3.3-6
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 27 17:23:52 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/python3.3
  ExecutableTimestamp: 1389422324
  InstallationDate: Installed on 2013-10-14 (105 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131013)
  ProcCmdline: python3 bin/window-mocker -t Qt5
  ProcCwd: /home/martin/ubuntu/tmp/py3
  SegvAnalysis:
   Segfault happened at: 0x7ff6f44b994d _ZN7QWidget7destroyEbb+637:   mov
0x8(%rax),%rdi
   PC (0x7ff6f44b994d) ok
   source 0x8(%rax) (0x0008) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: python3.3
  StacktraceTop:
   QWidget::destroy (this=this@entry=0x239d360, 
destroyWindow=destroyWindow@entry=true, 
destroySubWindows=destroySubWindows@entry=true) at kernel/qwidget_qpa.cpp:172
   QWidget::~QWidget (this=0x239d360, __in_chrg=optimized out) at 
kernel/qwidget.cpp:1478
   QMenu::~QMenu (this=0x239d360, __in_chrg=optimized out) at 
widgets/qmenu.cpp:1362
   MenuBarAdapter::~MenuBarAdapter() () from 
/tmp/apport_sandbox_qceHPQ/usr/lib/x86_64-linux-gnu/qt5/plugins/menubar/libappmenu-qt.so
   AppMenuPlatformMenuBar::destroyMenuBar() () from 
/tmp/apport_sandbox_qceHPQ/usr/lib/x86_64-linux-gnu/qt5/plugins/menubar/libappmenu-qt.so
  Title: python3.3 crashed with SIGSEGV in QWidget::destroy()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/window-mocker/+bug/1273306/+subscriptions

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

[Dx-packages] [Bug 1273306] Re: python3.3 crashed with SIGSEGV in QWidget::destroy()

[Łukasz Zemczak]

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New = In Progress

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) = Łukasz Zemczak (sil2100)

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

Title:
  python3.3 crashed with SIGSEGV in QWidget::destroy()

Status in Window Mocker:
  New
Status in “appmenu-qt” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress

Bug description:
  This happens when trying to run window-mocker with python3:

  $ bzr branch lp:~coreygoldberg/window-mocker/py3
  $ cd py3
  $ PYTHONPATH=. python3 bin/window-mocker -t Qt5

  When merely closing the window it cleanly exits for me; but when
  resizing the window I get this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: python3.3-minimal 3.3.3-6
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 27 17:23:52 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/python3.3
  ExecutableTimestamp: 1389422324
  InstallationDate: Installed on 2013-10-14 (105 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131013)
  ProcCmdline: python3 bin/window-mocker -t Qt5
  ProcCwd: /home/martin/ubuntu/tmp/py3
  SegvAnalysis:
   Segfault happened at: 0x7ff6f44b994d _ZN7QWidget7destroyEbb+637:   mov
0x8(%rax),%rdi
   PC (0x7ff6f44b994d) ok
   source 0x8(%rax) (0x0008) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: python3.3
  StacktraceTop:
   QWidget::destroy (this=this@entry=0x239d360, 
destroyWindow=destroyWindow@entry=true, 
destroySubWindows=destroySubWindows@entry=true) at kernel/qwidget_qpa.cpp:172
   QWidget::~QWidget (this=0x239d360, __in_chrg=optimized out) at 
kernel/qwidget.cpp:1478
   QMenu::~QMenu (this=0x239d360, __in_chrg=optimized out) at 
widgets/qmenu.cpp:1362
   MenuBarAdapter::~MenuBarAdapter() () from 
/tmp/apport_sandbox_qceHPQ/usr/lib/x86_64-linux-gnu/qt5/plugins/menubar/libappmenu-qt.so
   AppMenuPlatformMenuBar::destroyMenuBar() () from 
/tmp/apport_sandbox_qceHPQ/usr/lib/x86_64-linux-gnu/qt5/plugins/menubar/libappmenu-qt.so
  Title: python3.3 crashed with SIGSEGV in QWidget::destroy()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/window-mocker/+bug/1273306/+subscriptions

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

[Dx-packages] [Bug 1273306] Re: python3.3 crashed with SIGSEGV in QWidget::destroy()

[Łukasz Zemczak]

Looking into it right now. Due to the small number of Qt5 applications
available for our platform, the new appmenu-qt5 might still have some
bugs in it. I never tested it with python qt5 before, so I might have
missed something there. Let me see what's up.

** Changed in: appmenu-qt (Ubuntu)
 Assignee: (unassigned) = Łukasz Zemczak (sil2100)

** Changed in: appmenu-qt (Ubuntu)
   Status: New = In Progress

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

Title:
  python3.3 crashed with SIGSEGV in QWidget::destroy()

Status in Window Mocker:
  New
Status in “appmenu-qt” package in Ubuntu:
  In Progress

Bug description:
  This happens when trying to run window-mocker with python3:

  $ bzr branch lp:~coreygoldberg/window-mocker/py3
  $ cd py3
  $ PYTHONPATH=. python3 bin/window-mocker -t Qt5

  When merely closing the window it cleanly exits for me; but when
  resizing the window I get this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: python3.3-minimal 3.3.3-6
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 27 17:23:52 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/python3.3
  ExecutableTimestamp: 1389422324
  InstallationDate: Installed on 2013-10-14 (105 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131013)
  ProcCmdline: python3 bin/window-mocker -t Qt5
  ProcCwd: /home/martin/ubuntu/tmp/py3
  SegvAnalysis:
   Segfault happened at: 0x7ff6f44b994d _ZN7QWidget7destroyEbb+637:   mov
0x8(%rax),%rdi
   PC (0x7ff6f44b994d) ok
   source 0x8(%rax) (0x0008) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: python3.3
  StacktraceTop:
   QWidget::destroy (this=this@entry=0x239d360, 
destroyWindow=destroyWindow@entry=true, 
destroySubWindows=destroySubWindows@entry=true) at kernel/qwidget_qpa.cpp:172
   QWidget::~QWidget (this=0x239d360, __in_chrg=optimized out) at 
kernel/qwidget.cpp:1478
   QMenu::~QMenu (this=0x239d360, __in_chrg=optimized out) at 
widgets/qmenu.cpp:1362
   MenuBarAdapter::~MenuBarAdapter() () from 
/tmp/apport_sandbox_qceHPQ/usr/lib/x86_64-linux-gnu/qt5/plugins/menubar/libappmenu-qt.so
   AppMenuPlatformMenuBar::destroyMenuBar() () from 
/tmp/apport_sandbox_qceHPQ/usr/lib/x86_64-linux-gnu/qt5/plugins/menubar/libappmenu-qt.so
  Title: python3.3 crashed with SIGSEGV in QWidget::destroy()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/window-mocker/+bug/1273306/+subscriptions

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

[Dx-packages] [Bug 1273306] Re: python3.3 crashed with SIGSEGV in QWidget::destroy()

[Łukasz Zemczak]

Ok, I checked briefly the code and I see the problem, but I wonder if I
can fix it in appmenu-qt or will have to do it otherwise. appmenu-qt is
deprecated anyway, so the fix will have to be a distro-patch anyway. Let
me finish this up tomorrow morning.

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

Title:
  python3.3 crashed with SIGSEGV in QWidget::destroy()

Status in Window Mocker:
  New
Status in “appmenu-qt” package in Ubuntu:
  In Progress

Bug description:
  This happens when trying to run window-mocker with python3:

  $ bzr branch lp:~coreygoldberg/window-mocker/py3
  $ cd py3
  $ PYTHONPATH=. python3 bin/window-mocker -t Qt5

  When merely closing the window it cleanly exits for me; but when
  resizing the window I get this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: python3.3-minimal 3.3.3-6
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 27 17:23:52 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/python3.3
  ExecutableTimestamp: 1389422324
  InstallationDate: Installed on 2013-10-14 (105 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131013)
  ProcCmdline: python3 bin/window-mocker -t Qt5
  ProcCwd: /home/martin/ubuntu/tmp/py3
  SegvAnalysis:
   Segfault happened at: 0x7ff6f44b994d _ZN7QWidget7destroyEbb+637:   mov
0x8(%rax),%rdi
   PC (0x7ff6f44b994d) ok
   source 0x8(%rax) (0x0008) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: python3.3
  StacktraceTop:
   QWidget::destroy (this=this@entry=0x239d360, 
destroyWindow=destroyWindow@entry=true, 
destroySubWindows=destroySubWindows@entry=true) at kernel/qwidget_qpa.cpp:172
   QWidget::~QWidget (this=0x239d360, __in_chrg=optimized out) at 
kernel/qwidget.cpp:1478
   QMenu::~QMenu (this=0x239d360, __in_chrg=optimized out) at 
widgets/qmenu.cpp:1362
   MenuBarAdapter::~MenuBarAdapter() () from 
/tmp/apport_sandbox_qceHPQ/usr/lib/x86_64-linux-gnu/qt5/plugins/menubar/libappmenu-qt.so
   AppMenuPlatformMenuBar::destroyMenuBar() () from 
/tmp/apport_sandbox_qceHPQ/usr/lib/x86_64-linux-gnu/qt5/plugins/menubar/libappmenu-qt.so
  Title: python3.3 crashed with SIGSEGV in QWidget::destroy()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/window-mocker/+bug/1273306/+subscriptions

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