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

2016-03-30 Thread Ł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 1317860] Re: the phone should switch itself off before completely draining battery

2016-03-30 Thread Xavi Garcia 
** Branch linked: lp:~xavi-garcia-mena/livecd-rootfs/bug-1317860-upower-
poweroff-phone-only

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

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

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

2016-03-30 Thread Nick Dedekind 
** Branch linked: lp:~nick-dedekind/ubuntu-settings-components/calendar-
freeze

-- 
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:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

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 1317860] Re: the phone should switch itself off before completely draining battery

2016-03-30 Thread Pat McGowan 
It was further suggested to make the changefrom comment #15  in ubuntu-
touch-settings

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

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

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

[Dx-packages] [Bug 1508438] Re: Do not notify for events marked as not attending

2016-03-30 Thread Renato Araujo Oliveira Filho 
** Branch linked: lp:~renatofilho/indicator-datetime/fix-1508438

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

Title:
  Do not notify for events marked as not attending

Status in Ubuntu Calendar App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-up from bug #1371871. While it was marked as Fix
  Released, it doesn't seem to have had any effect. I'm reporting it as
  two separate bugs to reopen it now.

  I've got a few events in my calendar for meetings where I'm marked as
  not going, which I still want to see in my calendar unless I
  explicitly delete them.

  An example is a recurring event which I've got on my work calendar. During my 
holiday:
  - I'll mark myself as not attending
  - I will not delete the event
  - I don't expect to be notified

  As I'm not marked as attending, I wouldn't expect to get a reminder
  notification, even less if I'm in a different timezone and it's 3:00
  a.m. :)

  See bug 1508440 for the "display events not being attended clearly"
  part.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1508438/+subscriptions

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

[Dx-packages] [Bug 1533681] Re: imported google calendar events sound when they shouldn't

2016-03-30 Thread Renato Araujo Oliveira Filho 
** Branch linked: lp:~renatofilho/indicator-datetime/fix-1533681

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

Title:
  imported google calendar events sound when they shouldn't

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

Bug description:
  I use the calendar-app with my work google calendar. For that calendar
  I have alarms setup to automatically send an email 24 hours, 4 hours
  and 30 minutes before any event and I choose email as the reminder (as
  opposed to popup) so that I wouldn't be bombarded with reminders all
  day. Unfortunately the calendar app does not make a distinction
  between email and popup and every event with an email reminder gets
  imported as an event that gets an event notification on the phone with
  an alarm sound. I have a lot of events in my calendar and so my phone
  is constantly making noise at all times of the day. This is
  particularly annoying at night time since I might get a reminder as
  early as 3am or 4am, which wakes me up. Of course, I could use silent
  mode at night, but, like last night, I forgot and was awoken at 6am.
  Plus, I don't necessarily want the phone in silent mode-- I'd like to
  be able to hear if a phone call comes in since that is likely an
  emergency call I need to take.

  There are a lot of different bugs related to calendar event
  notifications and if some of them were fixed, it would ameliorate this
  bug. For example, I've been hoping for a setting to disable sounds for
  just the calendar (whether via the app or system settings) but
  otherwise get calendar notifications. Being able to change the alarm
  sound to 'None' would work too. TBH at this point I don't care which
  bug is fixed, I need to get this phone to stop sounding off
  constantly.

  WORKAROUND:
  1. download https://commons.wikimedia.org/wiki/File:Silence.ogg to 
/home/phablet
  2. use gsettings to adjust the sound:
  $ DISPLAY=:0.0 gsettings get com.canonical.indicator.datetime 
calendar-default-sound
  '/usr/share/sounds/ubuntu/ringtones/Marimbach.ogg'
  $ DISPLAY=:0.0 gsettings set com.canonical.indicator.datetime 
calendar-default-sound /home/phablet/Silence.ogg 
  $ DISPLAY=:0.0 gsettings get com.canonical.indicator.datetime 
calendar-default-sound
  '/home/phablet/Silence.ogg'

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

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

[Dx-packages] [Bug 1510769] Re: totem's app icon is old

2016-03-30 Thread Kenichi Ito 
The current old icon of totem is no consistency with the new one showed
in gnome-software.

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

Title:
  totem's app icon is old

Status in humanity-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  New icon shows on Gnome.
  However, old icon shows on Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: totem 3.16.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 11:56:37 2015
  InstallationDate: Installed on 2015-09-23 (34 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: totem
  UpgradeStatus: Upgraded to wily on 2015-10-25 (3 days ago)

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

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

2016-03-30 Thread Rodney Dawes 
https://translations.launchpad.net/ubuntu-rtm/15.04/+source/indicator-
session/+pots/indicator-session has translations, so I presume this
should be marked invalid for indicator-session task?

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

2016-03-30 Thread Pat McGowan 
Can we get the new lang packas in the image

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

** Changed in: canonical-devices-system-image
 Assignee: Alejandro J. Cura (alecu) => Łukasz Zemczak (sil2100)

-- 
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:
  Fix Committed
Status in langpack-o-matic:
  Fix Released
Status in indicator-session package in Ubuntu:
  Invalid

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

2016-03-30 Thread Alejandro J. Cura 
** Changed in: indicator-session (Ubuntu)
   Status: Confirmed => Invalid

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

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

Title:
   Indicator session not localized

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

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 1564126] [NEW] scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()

2016-03-30 Thread siucdude 
Public bug reported:

Just started to happen on 16.04 beta 2

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 30 17:23:40 2016
Dependencies:
 
ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
InstallationDate: Installed on 2015-12-17 (103 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
files/gdrive.scope
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f5bbe04bbbe:  cmp(%rax),%rbp
 PC (0x7f5bbe04bbbe) ok
 source "(%rax)" (0x5) not located in a known VMA region (needed 
readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: libunity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
 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
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace xenial

** Information type changed from Private to Public

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

Title:
  scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()

Status in libunity package in Ubuntu:
  New

Bug description:
  Just started to happen on 16.04 beta 2

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 30 17:23:40 2016
  Dependencies:
   
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2015-12-17 (103 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
files/gdrive.scope
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f5bbe04bbbe:cmp(%rax),%rbp
   PC (0x7f5bbe04bbbe) ok
   source "(%rax)" (0x5) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libunity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
   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
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()
  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/libunity/+bug/1564126/+subscriptions

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

[Dx-packages] [Bug 1564126] Re: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()

2016-03-30 Thread Apport retracing service 
*** This bug is a duplicate of bug 1194465 ***
https://bugs.launchpad.net/bugs/1194465

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 #1194465, 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/1564126/+attachment/4617547/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1194465
   scope-runner-dbus.py crashed with SIGSEGV in 
auth_session_remote_object_destroyed_cb()

** Tags removed: need-amd64-retrace

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

Title:
  scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()

Status in libunity package in Ubuntu:
  New

Bug description:
  Just started to happen on 16.04 beta 2

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 30 17:23:40 2016
  Dependencies:
   
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2015-12-17 (103 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
files/gdrive.scope
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f5bbe04bbbe:cmp(%rax),%rbp
   PC (0x7f5bbe04bbbe) ok
   source "(%rax)" (0x5) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libunity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
   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
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()
  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/libunity/+bug/1564126/+subscriptions

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