[Dx-packages] [Bug 761634] Re: compiz crashed with SIGSEGV in PanelView::~PanelView()

2016-08-31 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu laptop testing tracker.

A list of all reports related to this bug can be found here:
http://laptop.qa.ubuntu.com/qatracker/reports/bugs/761634

** Tags added: laptop-testing

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

Title:
  compiz crashed with SIGSEGV in PanelView::~PanelView()

Status in Nux:
  Fix Released
Status in Unity:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  After start of unity.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: libnux-0.9-0 0.9.44-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia wl
  Architecture: amd64
  CheckboxSubmission: 17a30fd74b8a2944babbcfe331de3cd9
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Fri Apr 15 10:25:29 2011
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=pl_PL:en
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4573a9c618:shl%cl
   PC (0x7f4573a9c618) in non-executable VMA region: 
0x7f4573a9b000-0x7f4573aa1000 rw-p None
   source "%cl" ok
  SegvReason: executing writable VMA None
  Signal: 11
  SourcePackage: nux
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   PanelView::~PanelView() () from /usr/lib/compiz/libunityshell.so
   PanelView::~PanelView() () from /usr/lib/compiz/libunityshell.so
   nux::Object::Destroy() () from /usr/lib/libnux-core-0.9.so.0
   nux::Object::UnReference() () from /usr/lib/libnux-core-0.9.so.0
  Title: compiz crashed with SIGSEGV in PanelView::~PanelView()
  UpgradeStatus: Upgraded to natty on 2011-04-01 (13 days ago)
  UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

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

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


[Dx-packages] [Bug 865122] Re: unity-panel-service crashed with SIGSEGV in g_type_check_instance()

2016-08-31 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu laptop testing tracker.

A list of all reports related to this bug can be found here:
http://laptop.qa.ubuntu.com/qatracker/reports/bugs/865122

** Tags added: laptop-testing

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

Title:
  unity-panel-service crashed with SIGSEGV in g_type_check_instance()

Status in Indicator Display Objects:
  Fix Released
Status in Unity:
  Fix Released
Status in ido package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in ido source package in Oneiric:
  Fix Released
Status in unity source package in Oneiric:
  Fix Released

Bug description:
  TEST CASE:
  1. Open the sound menu
  2. Press the mouse button on the volume slider and hold it down to initiate a 
drag
  3. Move the mouse pointer over another indicator (e.g Calendar)

  Result:
  This crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: unity-services 4.20.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu2
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CrashCounter: 1
  Date: Mon Oct  3 09:41:12 2011
  ExecutablePath: /usr/lib/unity/unity-panel-service
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
  ProcCmdline: /usr/lib/unity/unity-panel-service
  SegvAnalysis:
   Segfault happened at: 0x1fb588 :call   0x1d0df7 
<__i686.get_pc_thunk.bx>
   PC (0x001fb588) ok
   source "0x1d0df7" (0x001d0df7) ok
   destination "(%esp)" (0xbf684000) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   g_type_check_instance (type_instance=0x98df010) at 
/build/buildd/glib2.0-2.30.0/./gobject/gtype.c:4051
   g_signal_emit_valist (instance=0x98df010, signal_id=18, detail=0, 
var_args=0xbf68417c "") at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:2936
   g_signal_emit (instance=0x98df010, signal_id=18, detail=0) at 
/build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3060
   ?? () from /usr/lib/libgtk-3.so.0
   ?? () from /usr/lib/libgtk-3.so.0
  Title: unity-panel-service crashed with SIGSEGV in g_type_check_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XsessionErrors:
   (nautilus:1600): Gtk-CRITICAL **: gtk_action_set_visible: assertion 
`GTK_IS_ACTION (action)' failed
   (nautilus:1600): Gtk-CRITICAL **: gtk_action_set_visible: assertion 
`GTK_IS_ACTION (action)' failed
   (indicator-weather:1603): libappindicator-WARNING **: Unable to connect to 
the Notification Watcher: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.75 was not 
provided by any .service files

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

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


[Dx-packages] [Bug 845726] Re: indicator-datetime-service crashed with signal 5 in ffi_call_unix64()

2016-08-31 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/845726

** Tags added: iso-testing

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

Title:
  indicator-datetime-service crashed with signal 5 in ffi_call_unix64()

Status in Ubuntu Kylin:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid

Bug description:
  Apport popped up 10s after logging in. Up-to-date oneiric as of today.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: indicator-datetime 0.2.93-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Fri Sep  9 18:30:21 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/false
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
  Signal: 5
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with signal 5 in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Dx-packages] [Bug 1238737] Re: indicator-datetime-service crashed: "Unable to get bus connection to own name 'com.canonical.indicator.datetime'"

2016-08-31 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1238737

** Tags added: iso-testing

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

Title:
  indicator-datetime-service crashed: "Unable to get bus connection to
  own name 'com.canonical.indicator.datetime'"

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  The time display in the menu bar crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Oct 11 17:11:22 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-01-20 (630 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  Signal: 5
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: indicator-datetime-service crashed with signal 5 in 
g_main_context_dispatch()
  UpgradeStatus: Upgraded to saucy on 2013-10-11 (0 days ago)
  UserGroups:

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

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


[Dx-packages] [Bug 1612767] Re: Drop appmenu-qt5 from default installations

2016-08-31 Thread Dmitry Shachnev
I have just been able to reproduce the tst_QStaticText failure in my
pbuilder (on amd64).

I gathered the debug images from that test and submitted upstream as
https://bugreports.qt.io/browse/QTBUG-55653 (see attached file there).

The tst_QAbstractPrintDialog test crashes for me with SIGPIPE in libcups
httpFlushWrite function. Will investigate that a bit later.

Note that I retried the builds in my PPA today, so there are new build
logs there which may be different from the previous ones.

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

Title:
  Drop appmenu-qt5 from default installations

Status in indicator-appmenu package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Currently we are using appmenu-qt5 as our platform theme on desktop,
  however it has many disadvantages, which make me want to get rid of
  it:

  1) Its design is a hack: instead of the using normal QPA API for
  getting the menu, it retrieves the menu bar using QWidget::findChild,
  and then casts the pointer to QMenu*. The normal methods (which are
  getting called by Qt) remain empty stubs.

  2) It is preventing applications from using GTK+ theme integration,
  such as dialogs (I reported this as bug 1378935, but there is no easy
  way to fix that).

  3) It is not working with Qt Quick applications (because it expects a
  QtWidgets window; see also bug 1323853). The standard implementation
  will work with i.e. Qt Quick Controls 2 using apps (implemented in
  https://codereview.qt-project.org/142733).

  4) It breaks other environments such as Plasma when installed: see bug
  1434516.

  5) Finally, it is mostly unmaintained: most patches since 2014 are
  authored by me, however I see no point continuing to develop that
  code.

  Recently, Shawn Rutledge and I have written a native implementation of
  what appmenu-qt5 provides (global menu and system tray), which is part
  of Qt. That code uses the normal API, is well maintained, and works
  better than appmenu-qt5 (or at least not worse).

  So I propose to drop appmenu-qt5 from default Ubuntu installations,
  and maybe later from archive too.

  Unfortunately we use Qt 5.6, and some of the needed patches are only
  in Qt 5.7, so I would like to backport them to our packaging:

  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 
5.6.2 / 5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 
5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 
5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 
5.7.0)

  Timo: if you have no objections, I will commit those patches to the
  packaging Git.

  After we do that, I will remove the appmenu-qt5 recommendation from
  indicator-appmenu (that is the only package referring to it).

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

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


[Dx-packages] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04

2016-08-31 Thread Chris J Arges
Hello Pascal, or anyone else affected,

Accepted accountsservice into xenial-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.40-2ubuntu11.2
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  Switch user feature has disappeared from GNOME Shell since upgrade
  from 15.10 to 16.04

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Fix Committed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Committed
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu 16.04's accountsservice was built without systemd support because 
systemd dropped libsystemd-login because that functionality was merged into 
libsystemd.

  At a minimum, this broke GNOME Shell's "Switch User" feature.

  Test Case
  =
  1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages.
  2. Add a user if necessary to ensure you have at least 2 user accounts 
configured.
  3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower 
case letter r. Or you can log out of all user accounts and log back in.
  4. Click the system status area in the top right of GNOME Shell.
  5. Click your user name. "Switch User" should appear in the list.

  Regression Potential
  
  None.
  The one-line change to accountsservice's configure check was made in Debian's 
accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was 
included in accountsservice 0.6.42 released in June.

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

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


[Dx-packages] [Bug 1618886] Re: unity-gtk-module.service is racy

2016-08-31 Thread Iain Lane
To restart everything when the session starts, add

  systemctl --user stop graphical-session.target

to the systemd-graphical-session.conf and run-systemd-session, after the
block where all failed units are reset.

For the unity-in-upstart case, we might want to not override unity-gtk-
module? Maybe it then becomes racy with setting environment variables
though.

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

Title:
  unity-gtk-module.service is racy

Status in unity-gtk-module package in Ubuntu:
  Triaged

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1618886/+subscriptions

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


[Dx-packages] [Bug 1618886] Re: unity-gtk-module.service is racy

2016-08-31 Thread Iain Lane
s/restart everything/stop everything from a previous graphical session/

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

Title:
  unity-gtk-module.service is racy

Status in unity-gtk-module package in Ubuntu:
  Triaged

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1618886/+subscriptions

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


[Dx-packages] [Bug 1618886] Re: unity-gtk-module.service is racy

2016-08-31 Thread Martin Pitt
Without the PPA this is because upstart runs unity and there is no
synchronization between unity-gtk-module.service and unity7.conf.

With the PPA (i. e. converted services) this happens because unity-gtk-
module.service stays running after killing X (systemctl restart lightdm)
if there is another login. We need to restart it on login, or even
better, ensure that it stops when X gets killed.

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

Title:
  unity-gtk-module.service is racy

Status in unity-gtk-module package in Ubuntu:
  Triaged

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1618886/+subscriptions

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


[Dx-packages] [Bug 1618886] Re: unity-gtk-module.service is racy

2016-08-31 Thread Treviño
More than this unit, it seems related to the fact that it doesn't get 
deactivated on events such as Xorg being killed.
And this is not the only module with this issue. Also gnome-keyring-ssh.

In general any script which is on graphical-session doesn't get stopped.
And in fact:

sudo killall -9 Xorg 
marco@ubuntu-vmware:~:0$ systemctl --user status graphical-session.target 
● graphical-session.target - Current graphical user session
   Loaded: loaded (/usr/lib/systemd/user/graphical-session.target; static; 
vendor preset: enabled)
   Active: active since mer 2016-08-31 13:48:21 CEST; 54s ago
 Docs: man:systemd.special(7)

ago 31 13:48:21 ubuntu-vmware systemd[6159]: Reached target Current
graphical user session.

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

Title:
  unity-gtk-module.service is racy

Status in unity-gtk-module package in Ubuntu:
  Triaged

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1618886/+subscriptions

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


[Dx-packages] [Bug 1618886] [NEW] unity-gtk-module.service is racy

2016-08-31 Thread Martin Pitt
Public bug reported:

Sometimes on session start unity-gtk-module.service runs too late or
something, and $GTK_MODULES does not include "unity". It is in
"systemctl --user show-environment" but not in a terminal bash.

** Affects: unity-gtk-module (Ubuntu)
 Importance: High
 Assignee: Martin Pitt (pitti)
 Status: Triaged

** Changed in: unity-gtk-module (Ubuntu)
   Status: New => Triaged

** Changed in: unity-gtk-module (Ubuntu)
   Importance: Undecided => Medium

** Changed in: unity-gtk-module (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: unity-gtk-module (Ubuntu)
   Importance: Medium => High

** Changed in: unity-gtk-module (Ubuntu)
Milestone: None => ubuntu-16.09

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

Title:
  unity-gtk-module.service is racy

Status in unity-gtk-module package in Ubuntu:
  Triaged

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1618886/+subscriptions

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


[Dx-packages] [Bug 1612767] Re: Drop appmenu-qt5 from default installations

2016-08-31 Thread Timo Jyrinki
I used a clean pbuilder too by manually logging in inside and apt build-
dep:ing and building, and couldn't reproduce it. I'm not sure what could
explain the difference.

I have now a successful build with those tests disabled, but it would be
useful to file a bug against the package change that causes this
regression, if only it would be known. Meanwhile, the previous qtbase
landing hasn't migrated to release pocket still so this is pending.

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

Title:
  Drop appmenu-qt5 from default installations

Status in indicator-appmenu package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Currently we are using appmenu-qt5 as our platform theme on desktop,
  however it has many disadvantages, which make me want to get rid of
  it:

  1) Its design is a hack: instead of the using normal QPA API for
  getting the menu, it retrieves the menu bar using QWidget::findChild,
  and then casts the pointer to QMenu*. The normal methods (which are
  getting called by Qt) remain empty stubs.

  2) It is preventing applications from using GTK+ theme integration,
  such as dialogs (I reported this as bug 1378935, but there is no easy
  way to fix that).

  3) It is not working with Qt Quick applications (because it expects a
  QtWidgets window; see also bug 1323853). The standard implementation
  will work with i.e. Qt Quick Controls 2 using apps (implemented in
  https://codereview.qt-project.org/142733).

  4) It breaks other environments such as Plasma when installed: see bug
  1434516.

  5) Finally, it is mostly unmaintained: most patches since 2014 are
  authored by me, however I see no point continuing to develop that
  code.

  Recently, Shawn Rutledge and I have written a native implementation of
  what appmenu-qt5 provides (global menu and system tray), which is part
  of Qt. That code uses the normal API, is well maintained, and works
  better than appmenu-qt5 (or at least not worse).

  So I propose to drop appmenu-qt5 from default Ubuntu installations,
  and maybe later from archive too.

  Unfortunately we use Qt 5.6, and some of the needed patches are only
  in Qt 5.7, so I would like to backport them to our packaging:

  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 
5.6.2 / 5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 
5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 
5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 
5.7.0)

  Timo: if you have no objections, I will commit those patches to the
  packaging Git.

  After we do that, I will remove the appmenu-qt5 recommendation from
  indicator-appmenu (that is the only package referring to it).

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

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