date:20150310

[Dx-packages] [Bug 1245459] Re: Windows end up outside viewable area after disconnecting external monitor with higher resolution than laptop panel

2015-03-10 Thread Roland Bock

I am still experiencing this in 14.04

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

Title:
  Windows end up outside viewable area after disconnecting external
  monitor with higher resolution than laptop panel

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  I use a Dell XPS 13 laptop which I connect to an external 1920x1200
  dpi monitor at work through a displayport connection. In this
  configuration, the external display is set as primary display and the
  laptop panel is disabled. When I disconnect the monitor by unplugging
  the cable, the laptop panel (1366x768 dpi) switches on and becomes the
  new primary display. The problem is that any window that was displayed
  at a position that is beyond the resolution of the smaller panel (e.g.
  at a y-position greater than 800 pixels) now falls outside the
  viewable area of the laptop panel and is no longer visible.  Other
  windows that were larger than the viewable area on the smaller monitor
  tend to end up with their title bars under Unity's top menu bar. In
  the latter case, the windows can be moved back by ALT+mouse, but in
  the former case it becomes quite difficult to move the windows back to
  the viewport (selecting the window in the spread, then using
  ALT+space+m and arrow keys works, but is hardly a straightforward
  workaround).

  To reproduce:
  1. Connect an external monitor with higher resolution than the native laptop 
panel
  2. In display setup, set the external monitor to primary and disable the 
laptop panel
  3. On the external monitor, open a window (e.g. terminal or empathy chat) and 
move it to the bottom of the screen, at a Y-position greater than the 
Y-resolution of the laptop panel
  4. Disconnect the external monitor by unplugging the display cable
  5. Try to access the window you just opened

  Expected behavior:
  1. Windows outside the viewable area should be repositioned to fit inside the 
smaller display area
  2. Larger windows should be repositioned so that their title bar does not end 
up under the Unity menu bar

  It would be great if this could be fixed in the 12.04 LTS version.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-13.20~precise2-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,scale,place,mousepoll,gnomecompat,wall,animation,workarounds,grid,resize,vpswitch,imgpng,move,session,expo,unityshell]
  Date: Mon Oct 28 07:49:42 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1430241] Re: indicator-session-service crashed with SIGSEGV in _start()

2015-03-10 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1382654, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1430241/+attachment/4339780/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1430241/+attachment/4339782/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1430241/+attachment/4339783/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1430241/+attachment/4339784/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1430241/+attachment/4339785/+files/Registers.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1430241/+attachment/4339786/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1382654

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  indicator-session-service crashed with SIGSEGV in _start()

Status in indicator-session package in Ubuntu:
  New

Bug description:
  At startup (lightdm login screen)

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-session 12.10.5+15.04.20150228-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 10 21:09:35 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
  InstallationDate: Installed on 2015-01-31 (38 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x41243a <_start+1290>:movzbl (%r8),%eax
   PC (0x0041243a) ok
   source "(%r8)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-session
  Stacktrace:
   #0  0x0041243a in _start ()
   No symbol table info available.
  StacktraceTop: _start ()
  Title: indicator-session-service crashed with SIGSEGV in _start()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Dx-packages] [Bug 1430254] Re: indicator-session-service crashed with SIGSEGV in _start()

2015-03-10 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1290876, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1430254/+attachment/4339789/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1430254/+attachment/4339791/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1430254/+attachment/4339793/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1430254/+attachment/4339794/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1430254/+attachment/4339795/+files/Registers.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1430254/+attachment/4339796/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1290876
   indicator-session-service crashed with SIGSEGV in get_user_label()

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  indicator-session-service crashed with SIGSEGV in _start()

Status in indicator-session package in Ubuntu:
  New

Bug description:
  indicator-session-service crashed with SIGSEGV in _start()

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-session 12.10.5+15.04.20150228-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: i386
  Date: Tue Mar 10 13:54:05 2015
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  InstallationDate: Installed on 2015-03-10 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150306)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  SegvAnalysis:
   Segfault happened at: 0x8057453 <_start+1319>:   movzbl 0x0(%ebp),%eax
   PC (0x08057453) ok
   source "0x0(%ebp)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-session
  Stacktrace:
   #0  0x08057453 in _start ()
   No symbol table info available.
  StacktraceTop: _start ()
  Title: indicator-session-service crashed with SIGSEGV in _start()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Dx-packages] [Bug 1290876] Re: indicator-session-service crashed with SIGSEGV in get_user_label()

2015-03-10 Thread Apport retracing service

** Tags added: vivid

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

Title:
  indicator-session-service crashed with SIGSEGV in get_user_label()

Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-session 12.10.5+14.04.20140214-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Mar 11 14:48:23 2014
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  InstallationDate: Installed on 2014-03-05 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140304)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  SegvAnalysis:
   Segfault happened at: 0x8056643 <_start+945>:movzbl (%edi),%eax
   PC (0x08056643) ok
   source "(%edi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-session
  Stacktrace:
   #0  0x08056643 in _start ()
   No symbol table info available.
  StacktraceTop: _start ()
  Title: indicator-session-service crashed with SIGSEGV in _start()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1430380] [NEW] wrong default icon size with user interface scaling

2015-03-10 Thread Andreas E.

Public bug reported:

When using user interface scaling (like on high-dpi screens) with scale
factor 2, gtk3 application toolbars show the icon resource of twice the
correct size. The icons are not upsampled, just the too big resource
file is chosen (that would fit a scale factor of 4).

This was tested with default settings (15.04 iso). This issue did not
occur in default settings of older releases (14.10).

Ubuntu 15.04 from vivid-desktop-amd64.iso 06-Mar-2015 08:00

** Affects: unity (Ubuntu)
Importance: Undecided
Status: New

** Attachment added: "screenshot. Note: the screen's resolution was bigger than
the image's resolution."

https://bugs.launchpad.net/bugs/1430380/+attachment/4340095/+files/vivid%20icon%20size.png

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

Title:
wrong default icon size with user interface scaling

Status in unity package in Ubuntu:
New

Bug description:
When using user interface scaling (like on high-dpi screens) with
scale factor 2, gtk3 application toolbars show the icon resource of
twice the correct size. The icons are not upsampled, just the too big
resource file is chosen (that would fit a scale factor of 4).

This was tested with default settings (15.04 iso). This issue did not
occur in default settings of older releases (14.10).

Ubuntu 15.04 from vivid-desktop-amd64.iso 06-Mar-2015 08:00

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

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

[Dx-packages] [Bug 1425078] Re: Cannot callback/send messages from Notifications

2015-03-10 Thread Ted Gould

I think this was fixed with a recent indicator-messages landing that
fixed message actions.

** Changed in: indicator-messages (Ubuntu)
   Status: New => Fix Released

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

Title:
  Cannot callback/send messages from Notifications

Status in indicator-messages package in Ubuntu:
  Fix Released
Status in unity-notifications package in Ubuntu:
  New

Bug description:
  1. Create an incoming call to your Ubuntu phone from another device
  2. Don't pickup the call so that missed call notification appears in the 
'Notifications' menu
  3. Open Notifications and tap on the missed call entry for it to expand
  4. press the 'Call back' button

  What happens: Nothing

  What should happen:
  Dialer app should open with the relevant number already in the input box.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-messages 13.10.1+15.04.20150219-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Tue Feb 24 18:36:59 2015
  InstallationDate: Installed on 2015-02-24 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150224-020204)
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1430412] Re: indicator-session-service crashed with SIGSEGV in _start()

2015-03-10 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1382654, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1430412/+attachment/4340172/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1430412/+attachment/4340174/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1430412/+attachment/4340175/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1430412/+attachment/4340176/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1430412/+attachment/4340177/+files/Registers.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1430412/+attachment/4340178/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1382654

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  indicator-session-service crashed with SIGSEGV in _start()

Status in indicator-session package in Ubuntu:
  New

Bug description:
  Upon dist-upgrade in vivid channel

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-session 12.10.5+15.04.20150228-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 10 11:45:59 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
  InstallationDate: Installed on 2013-12-06 (458 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x41243a <_start+1290>:movzbl (%r8),%eax
   PC (0x0041243a) ok
   source "(%r8)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-session
  Stacktrace:
   #0  0x0041243a in _start ()
   No symbol table info available.
  StacktraceTop: _start ()
  Title: indicator-session-service crashed with SIGSEGV in _start()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Dx-packages] [Bug 778054] Re: Packages shouldn't depend on the transitional package python-gobject

2015-03-10 Thread Launchpad Bug Tracker

This bug was fixed in the package zeitgeist - 0.9.14-2.2ubuntu3

---
zeitgeist (0.9.14-2.2ubuntu3) vivid; urgency=medium

  * Depend on python-gobject-2 and python-gi instead of python-gobject,
because it's a transitional package (LP: #778054)
 -- Mathew HodsonTue, 10 Mar 2015 08:55:16 -0700

** Changed in: zeitgeist (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Packages shouldn't depend on the transitional package python-gobject

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in desktopcouch package in Ubuntu:
  Invalid
Status in eglibc package in Ubuntu:
  Invalid
Status in gnome-utils package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in wine1.4 package in Ubuntu:
  Fix Released
Status in zeitgeist package in Ubuntu:
  Fix Released
Status in aptdaemon source package in Trusty:
  Fix Released
Status in desktopcouch source package in Trusty:
  Invalid
Status in eglibc source package in Trusty:
  Invalid
Status in gnome-utils source package in Trusty:
  Invalid
Status in libreoffice source package in Trusty:
  Fix Released
Status in openoffice.org source package in Trusty:
  Invalid
Status in system-config-printer source package in Trusty:
  Fix Released
Status in wine1.4 source package in Trusty:
  Invalid
Status in zeitgeist source package in Trusty:
  In Progress

Bug description:
  [Impact]

  python-zeitgeist depends on python-gobject, which means python-gobject
  cannot be removed from the system. python-gobject is a transitional
  package, and packages should be updated to no longer depend on it.

  [Test Case]

  * Install python-zeitgeist, and verify that python-gobject is not
  installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing python-zeitgeist.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

  ---

  [Impact]

  system-config-printer-gnome depends on python-gobject, which means
  python-gobject cannot be removed from the system. python-gobject is a
  transitional package, and packages should be updated to no longer
  depend on it.

  [Test Case]

  * Install system-config-printer-gnome, and verify that python-gobject
  is not installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing system-config-printer-gnome.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

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

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

[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2015-03-10 Thread Pablo180

Spoke too soon, just hibernated and then resumed with Ethernet cable
plugged in and the problem occurred. Killing or restarting Network
Manager just caused nm-applet to crash so I had to restart that - which
is probably why the workaround no longer works.

I haven't noticed this problem in the week or so since the reinstall,
although I have been using wifi and not ethernet all that time - my wifi
was disabled via Network Manager before hibernating this time., so that
may be related.

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  Invalid
Status in systemd-shim package in Ubuntu:
  Confirmed
Status in systemd-shim source package in Saucy:
  Won't Fix
Status in systemd-shim source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions

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

[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2015-03-10 Thread Yanpas

@Pablo have you tried disabling ACPI HPET Table in BIOS? Maybe you don't
have such option in BIOS/UEFI.

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  Invalid
Status in systemd-shim package in Ubuntu:
  Confirmed
Status in systemd-shim source package in Saucy:
  Won't Fix
Status in systemd-shim source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions

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

[Dx-packages] [Bug 1385331] Re: Notification LED stays on when no messages in notification center

2015-03-10 Thread Pat McGowan

** Changed in: canonical-devices-system-image
Milestone: ww09-2015 => ww11-2015

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

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

Title:
  Notification LED stays on when no messages in notification center

Status in the base for Ubuntu mobile products:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in qmenumodel package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in qmenumodel package in Ubuntu RTM:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  Fix Released

Bug description:
  Observed the notification LED staying on even though there were no
  notifications in the indicators and the notification icon was greyed
  out.

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

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

[Dx-packages] [Bug 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged

2015-03-10 Thread Marc Deslauriers

Devices that report a wrong time remaining need to be blacklisted, just
like any other misbehaving hardware device. The fact that such devices
exist is not a valid reason to get rid of a sane and elegant
notification system.

Do you own a mouse with an incorrect "time remaining" estimate?

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

Title:
  Mouse with no time remaining estimate showing in preference to battery
  being charged

Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  When my laptop battery is in a charging state, but is not fully
  charged, I expect it to be displayed in preference to my mouse, which
  has no time remaining estimate.

  The spec here:

  https://wiki.ubuntu.com/Power

  says:

  "If anything is discharging, the menu title should represent the
  component (not battery, but component) that is estimated to lose power
  first. For example, if your notebook battery is estimated to discharge
  in 1 hour 47 minutes, and your wireless mouse battery is estimated to
  discharge in 27 minutes, the menu title should represent the mouse. "

  but there doesn't seem to be any guideline to what happens when a
  battery is being charged.

  I suggest the time remaining to charge a battery should be displayed
  in preference to the power level in a wireless mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 11:50:36 2014
  InstallationDate: Installed on 2013-11-26 (156 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago)

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

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

[Dx-packages] [Bug 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged

2015-03-10 Thread Ernesto Alejo

My mouse is always 90% or 5% (no intermediate values) and it changes
~4-5 times a week; mostly when the laptop suspends. The mouse uses
batteries and it's always the one showed in the notifications area. In
fact I think the mouse does not even report the remaining time (it's not
present in the dialog)

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

Title:
  Mouse with no time remaining estimate showing in preference to battery
  being charged

Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  When my laptop battery is in a charging state, but is not fully
  charged, I expect it to be displayed in preference to my mouse, which
  has no time remaining estimate.

  The spec here:

  https://wiki.ubuntu.com/Power

  says:

  "If anything is discharging, the menu title should represent the
  component (not battery, but component) that is estimated to lose power
  first. For example, if your notebook battery is estimated to discharge
  in 1 hour 47 minutes, and your wireless mouse battery is estimated to
  discharge in 27 minutes, the menu title should represent the mouse. "

  but there doesn't seem to be any guideline to what happens when a
  battery is being charged.

  I suggest the time remaining to charge a battery should be displayed
  in preference to the power level in a wireless mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 11:50:36 2014
  InstallationDate: Installed on 2013-11-26 (156 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago)

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

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

[Dx-packages] [Bug 1430542] [NEW] Indicator doesn't use weighted average with different-sized batteries

2015-03-10 Thread Ryan Lortie

Public bug reported:

The indicator implements the spec:

  https://wiki.ubuntu.com/Power#Handling_multiple_batteries

which states:

  "Their percentages should be averaged."

Apparently this was taken to mean the simple arithmetic mean, and not
the weighted average (by the capacity of each battery).

  http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
power/trunk.15.04/view/head:/src/service.c#L1316

shows:

  const double percent = sum_percent / n_batteries;

This means that if one battery is twice as large as another, then after
that battery is discharged, 50% would be reported.  I'd expect 33%.

The spec needs to be updated to be less ambiguous about the intended
meaning of the word "average" and the code needs to be fixed.

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Indicator doesn't use weighted average with different-sized batteries

Status in indicator-power package in Ubuntu:
  New

Bug description:
  The indicator implements the spec:

https://wiki.ubuntu.com/Power#Handling_multiple_batteries

  which states:

"Their percentages should be averaged."

  Apparently this was taken to mean the simple arithmetic mean, and not
  the weighted average (by the capacity of each battery).

http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
  power/trunk.15.04/view/head:/src/service.c#L1316

  shows:

const double percent = sum_percent / n_batteries;

  This means that if one battery is twice as large as another, then
  after that battery is discharged, 50% would be reported.  I'd expect
  33%.

  The spec needs to be updated to be less ambiguous about the intended
  meaning of the word "average" and the code needs to be fixed.

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

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

[Dx-packages] [Bug 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged

2015-03-10 Thread Jochen Fahrner

It's very funny to see how Canonical justifies this stupid new
"feature". In the meantime I switched to Debian Wheezy (one of the
reasons was this "feature") and now I'm on FreeBSD (because of systemd
taking over control of the whole linux world).

Good luck to all that stay on Ubuntu. ;-)

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

Title:
  Mouse with no time remaining estimate showing in preference to battery
  being charged

Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  When my laptop battery is in a charging state, but is not fully
  charged, I expect it to be displayed in preference to my mouse, which
  has no time remaining estimate.

  The spec here:

  https://wiki.ubuntu.com/Power

  says:

  "If anything is discharging, the menu title should represent the
  component (not battery, but component) that is estimated to lose power
  first. For example, if your notebook battery is estimated to discharge
  in 1 hour 47 minutes, and your wireless mouse battery is estimated to
  discharge in 27 minutes, the menu title should represent the mouse. "

  but there doesn't seem to be any guideline to what happens when a
  battery is being charged.

  I suggest the time remaining to charge a battery should be displayed
  in preference to the power level in a wireless mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 11:50:36 2014
  InstallationDate: Installed on 2013-11-26 (156 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago)

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

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

[Dx-packages] [Bug 1429670] Re: Desktop reverts to defaults, can't be changed

2015-03-10 Thread James Ferguson

Looks like my ~/.config/dconf files were corrupted somehow.  I removed
them with:

mv ~/.config/dconf/ ~/.config/dconf.bak

And now at least I can re-create my old settings.

** Changed in: unity (Ubuntu)
   Status: New => Invalid

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

Title:
  Desktop reverts to defaults, can't be changed

Status in unity package in Ubuntu:
  Invalid

Bug description:
  All of a sudden my launcher icons, wallpaper image etc, reverted to
  default, and when I "unlock from launcher" on the defaults, they
  disappear after about a second, and then reappear when I tried to re-
  arrange the icon order.

  I think there's perhaps something screwy with gconf (? - isn't that
  where the personal launcher app list is?) because another setting went
  away and can't be restored (I use caps lock as another control).
  However, I don't know how to test this or where to look for logs, and
  the *symptoms* turn up in Unity.

  If anyone can help with places to look for diagnostics etc., I'd
  appreciate it.  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.4+14.04.20141217-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale]
  CurrentDesktop: Unity
  Date: Sun Mar  8 18:06:28 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-21 (290 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140310)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1429670] Re: Desktop reverts to defaults, can't be changed

2015-03-10 Thread James Ferguson

I marked it Invalid since it's (probably) nothing to do with Unity.

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

Title:
  Desktop reverts to defaults, can't be changed

Status in unity package in Ubuntu:
  Invalid

Bug description:
  All of a sudden my launcher icons, wallpaper image etc, reverted to
  default, and when I "unlock from launcher" on the defaults, they
  disappear after about a second, and then reappear when I tried to re-
  arrange the icon order.

  I think there's perhaps something screwy with gconf (? - isn't that
  where the personal launcher app list is?) because another setting went
  away and can't be restored (I use caps lock as another control).
  However, I don't know how to test this or where to look for logs, and
  the *symptoms* turn up in Unity.

  If anyone can help with places to look for diagnostics etc., I'd
  appreciate it.  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.4+14.04.20141217-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale]
  CurrentDesktop: Unity
  Date: Sun Mar  8 18:06:28 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-21 (290 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140310)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1429670] Re: Desktop reverts to defaults, can't be changed

2015-03-10 Thread James Ferguson

Seems my ~/.config/dconf/user file was empty, somehow, FWIW.

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

Title:
  Desktop reverts to defaults, can't be changed

Status in unity package in Ubuntu:
  Invalid

Bug description:
  All of a sudden my launcher icons, wallpaper image etc, reverted to
  default, and when I "unlock from launcher" on the defaults, they
  disappear after about a second, and then reappear when I tried to re-
  arrange the icon order.

  I think there's perhaps something screwy with gconf (? - isn't that
  where the personal launcher app list is?) because another setting went
  away and can't be restored (I use caps lock as another control).
  However, I don't know how to test this or where to look for logs, and
  the *symptoms* turn up in Unity.

  If anyone can help with places to look for diagnostics etc., I'd
  appreciate it.  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.4+14.04.20141217-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale]
  CurrentDesktop: Unity
  Date: Sun Mar  8 18:06:28 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-21 (290 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140310)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1055478] Re: Launcher, make Alt-Tab behavior configurable: Raise all app windows or just the most recently focused

2015-03-10 Thread Juan

+1 on this bug. It's very annoying to have two terms or file managers
open and not be able to see them.  Should work as on MacOS

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

Title:
   Launcher, make Alt-Tab behavior configurable: Raise all app windows
  or just the most recently focused

Status in Ayatana Design:
  New
Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Feature request as suggested in http://askubuntu.com/questions/127143:

  Please add a configuration option somewhere to toggle between behaviors when 
clicking on a launcher item or selecting an app in Alt-Tab:
   - Raise the most recently focused window
  or
   - Raise all app windows

  See also: https://bugs.launchpad.net/unity/+bug/959339

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1055478/+subscriptions

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

[Dx-packages] [Bug 1430601] Re: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct()

2015-03-10 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1426706, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1430601/+attachment/4340677/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1430601/+attachment/4340679/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1430601/+attachment/4340681/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1430601/+attachment/4340682/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1430601/+attachment/4340683/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1430601/+attachment/4340684/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1430601/+attachment/4340685/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1426706

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  indicator-sound-service crashed with signal 5 in
  indicator_sound_service_construct()

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  came up after restart

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Mar 11 02:09:48 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2015-02-06 (32 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop:
   indicator_sound_service_construct ()
   main ()
  Title: indicator-sound-service crashed with signal 5 in 
indicator_sound_service_construct()
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (13 days ago)
  UserGroups:

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

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

1 2 >

1 - 100 of 127 matches

Mail list logo