[Dx-packages] [Bug 1055166] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... from

[Doug Smythies]

Yes, this has fixed my problem for one of my 14.04 Desktop VM running on my 
12.04 server host.
I have several other scenarios to check, it'll take me awhile. (I came here 
from bug 1282342 , which started 2104.02.17)

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

Title:
  compiz crashed with SIGSEGV in memmove() from
  drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator()
  from compiz::opengl::bindTexImageGLX() from ... from
  unity::UnityWindow::DrawWindowDecoration

Status in Compiz:
  Fix Committed
Status in Mesa:
  Invalid
Status in Unity:
  Invalid
Status in Unity 6.0 series:
  Won't Fix
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “mesa” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  See also bug 927168, which was resolved recently.

  Compiz crashed after installed something via Synaptic and just it
  installed that i want it crashed coz i want to see  the black
  installition screen

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity 6.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Sun Sep 23 21:36:37 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f031d57d73c:movntdq %xmm1,-0x10(%rdi)
   PC (0x7f031d57d73c) ok
   source "%xmm1" ok
   destination "-0x10(%rdi)" (0x108d5b170) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   gnome-session[1561]: WARNING: Application 'compiz.desktop' killed by signal 
11
   gnome-session[1561]: WARNING: App 'compiz.desktop' respawning too quickly
   gnome-session[1561]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1055166/+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 1184262] Re: times out too early, stuck in PrepareForSleep, causing network and other services to not resume

[Daniel Lombraña González]

This bugs keeps affecting me even with the latest version. Can I do
something to get this fixed?

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

Title:
  times out too early, stuck in PrepareForSleep, causing network and
  other services to not resume

Status in “systemd” package in Ubuntu:
  Invalid
Status in “systemd-shim” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Saucy:
  Invalid
Status in “systemd-shim” source package in Saucy:
  Fix Released
Status in “systemd” source package in Trusty:
  Invalid
Status in “systemd-shim” source package in Trusty:
  Fix Released

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  SRU INFORMATION:
  
  Reproducer:
  - Force suspend to take very long by adding a sleep:
    echo -e '#!/bin/sh\nsleep 15\nexit 1' | sudo tee 
/usr/lib/pm-utils/sleep.d/00break
    (this will also make suspend fail, which eases testing)
  - Suspend from the menu or with
    sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m 
org.freedesktop.login1.Manager.Suspend true
  - With the 13.10 final version, systemd-shim will (often) time out, and the 
next Suspend call from above will fail with "Operation already in progress" and 
the network does not come back up. With the fixed version, network should be 
back up and the Suspend() call can be issued many times.

  Fix:
https://github.com/desrt/systemd-shim/commit/136ed1143077d13c2
https://github.com/desrt/systemd-shim/commit/16a7fdc0652ad78f4

  Regression potential: Errors in this code could potentially break
  suspend/shutdown completely, so for verification both of these
  functionalities ought to be tested on real hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1
   169.254.0.0/16 dev wlan1  scope link  metric 1000
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:

  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9:
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   not running unknownunknown unknown   unknown 
unknownunknown unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+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 1281640] Re: Obscene content in music search results

[Mark Tully]

Both of these results appear to be coming from the Soundcloud scope, matching 
an artist named Rhy:
https://soundcloud.com/rhy-1/words-motherfucker-1
https://soundcloud.com/rhy-1/absolute-bullshit

** Also affects: unity-scope-soundcloud
   Importance: Undecided
   Status: New

** Changed in: unity-scope-soundcloud
   Status: New => Confirmed

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

Title:
  Obscene content in music search results

Status in Unity Music Lens:
  New
Status in Unity SoundCloud Scope:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Some search terms return obscene content in the dash

  To reproduce:
  1) Search for 'rhy' in the dash

  Expected results:
  Rhythmbox and other search results are returned, all of which I could show to 
a customer

  Actual results:
  The music scope returns offensive/obscene results, such as "WORDS 
MOTHERF*CKER" or "Absolute Bullsh*t" (see attached screenshot)

  I am not aware of any way to filter search results (similar to
  Google's "Safe Search"). If there is a way, it should be turned on by
  default.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20131106.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Tue Feb 18 10:50:44 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-02 (77 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-music-lens/+bug/1281640/+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 1287466] [NEW] compiz crashed with SIGSEGV in FT_Load_Glyph()

[JoshuaStrobl]

Public bug reported:

When I hit the super / windows key and started typing "terminal", compiz
crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140303-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar  4 03:45:13 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-03-01 (2 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f7b8723223a:  movswl 0x18(%rdx),%r12d
 PC (0x7f7b8723223a) ok
 source "0x18(%rdx)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%r12d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
UpgradeStatus: Upgraded to trusty on 2014-03-04 (0 days ago)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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


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

** Information type changed from Private to Public

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

Title:
  compiz crashed with SIGSEGV in FT_Load_Glyph()

Status in “unity” package in Ubuntu:
  New

Bug description:
  When I hit the super / windows key and started typing "terminal",
  compiz crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140303-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  4 03:45:13 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-03-01 (2 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f7b8723223a:movswl 0x18(%rdx),%r12d
   PC (0x7f7b8723223a) ok
   source "0x18(%rdx)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%r12d" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
  Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
  UpgradeStatus: Upgraded to trusty on 2014-03-04 (0 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1287466/+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 1281640] Re: Obscene content in music search results

[Treviño]

** Also affects: unity-music-lens
   Importance: Undecided
   Status: New

** 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/1281640

Title:
  Obscene content in music search results

Status in Unity Music Lens:
  New
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Some search terms return obscene content in the dash

  To reproduce:
  1) Search for 'rhy' in the dash

  Expected results:
  Rhythmbox and other search results are returned, all of which I could show to 
a customer

  Actual results:
  The music scope returns offensive/obscene results, such as "WORDS 
MOTHERF*CKER" or "Absolute Bullsh*t" (see attached screenshot)

  I am not aware of any way to filter search results (similar to
  Google's "Safe Search"). If there is a way, it should be turned on by
  default.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20131106.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Tue Feb 18 10:50:44 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-02 (77 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-music-lens/+bug/1281640/+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 1287464] [NEW] Fake decorations on spread flickers the first time they've been selected

[Treviño]

Public bug reported:

Selecting the first time a window in unity spread might cause some
flickering of the window decoration

** Affects: unity
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

** Affects: unity (Ubuntu)
 Importance: Undecided
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

** Also affects: unity
   Importance: Undecided
   Status: New

** Changed in: unity
   Status: New => In Progress

** Changed in: unity
   Importance: Undecided => Medium

** Changed in: unity
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity
Milestone: None => 7.2.0

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

Title:
  Fake decorations on spread flickers the first time they've been
  selected

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Selecting the first time a window in unity spread might cause some
  flickering of the window decoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1287464/+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 1055166] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... from

[Treviño]

** Changed in: unity (Ubuntu)
   Status: Triaged => 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/1055166

Title:
  compiz crashed with SIGSEGV in memmove() from
  drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator()
  from compiz::opengl::bindTexImageGLX() from ... from
  unity::UnityWindow::DrawWindowDecoration

Status in Compiz:
  Fix Committed
Status in Mesa:
  Invalid
Status in Unity:
  Invalid
Status in Unity 6.0 series:
  Won't Fix
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “mesa” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  See also bug 927168, which was resolved recently.

  Compiz crashed after installed something via Synaptic and just it
  installed that i want it crashed coz i want to see  the black
  installition screen

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity 6.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Sun Sep 23 21:36:37 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f031d57d73c:movntdq %xmm1,-0x10(%rdi)
   PC (0x7f031d57d73c) ok
   source "%xmm1" ok
   destination "-0x10(%rdi)" (0x108d5b170) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   gnome-session[1561]: WARNING: Application 'compiz.desktop' killed by signal 
11
   gnome-session[1561]: WARNING: App 'compiz.desktop' respawning too quickly
   gnome-session[1561]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1055166/+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 1283415] Re: 1px gap between launcher and dash on high-dpi screen

[Treviño]

** Changed in: unity
 Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)

** Changed in: unity
   Importance: Undecided => Medium

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

Title:
  1px gap between launcher and dash on high-dpi screen

Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  There is a 1px gap between the launcher and the dash.

  org.gnome.desktop.interface.scaling-factor = 2
  org.gnome.desktop.interface.text-scaling-factor = 1.0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Feb 22 12:41:11 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Feb 22 12:08:14 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970 
   vendor SDC
  xserver.version: 2:1.15.0-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1283415/+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 1282342] Re: compiz crashes with segfault after recent updates

[Treviño]

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

** This bug is no longer a duplicate of bug 1284536
   compiz crashed with SIGSEGV in two_way_long_needle()
** This bug has been marked a duplicate of bug 1055166
   compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from 
dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() 
from ... from unity::UnityWindow::DrawWindowDecoration

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

Title:
  compiz crashes with segfault after recent updates

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu Desktop 14.04 VM became unusable (unity shell) a few days ago, and 
after some significant updates.
  Things are fine after I log in and until I try to do something. Then compiz 
will crash and my system becomes unusable. I do have sshd running and can 
connect via ssh to re-boot or shurdown or get new updates are whatever.

  This bug report is being sent while logged on with GNOME shell, which
  also has been having issues since January 17th, ( see bug 1273276 )
  but there is a workaround that allows me to use it.

  For the last few days, I see log entries in both kern.log and syslog
  saying about compiz complaing about segfaults.

  Everything was working fine for unity log in until a few days ago.
  (well, and as expected during the development phase, there have been
  issues.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140218.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3
  Uname: Linux 3.13.0-10-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  CurrentDmesg: [  122.391354] init: plymouth-stop pre-start process (3894) 
terminated with status 1
  Date: Wed Feb 19 16:57:06 2014
  DistUpgraded: 2013-11-17 13:21:47,309 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2013-09-04 (168 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Bochs Bochs
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-10-generic 
root=UUID=4d6f0b17-9e14-4801-ab59-a7737cde6271 ro quiet splash
  Renderer: Software
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-17 (94 days ago)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
  dmi.product.name: Bochs
  dmi.sys.vendor: Bochs
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Feb 19 16:55:20 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputImExPS/2 Generic Explorer Mouse MOUSE, id 8
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/fb0: No such file or directory
   vmware(0): Failed to open drm.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1282342/+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 1283557] Re: compiz crashed with SIGSEGV in _wordcopy_fwd_dest_aligned()

[Treviño]

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

** This bug has been marked a duplicate of bug 1055166
   compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from 
dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() 
from ... from unity::UnityWindow::DrawWindowDecoration

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

Title:
  compiz crashed with SIGSEGV in _wordcopy_fwd_dest_aligned()

Status in “unity” package in Ubuntu:
  New

Bug description:
  running on Ubuntu 14.04 with current updates on a libvirt VM with 14.04 
updated, both 64 bit.
  Other issue that may be caused by this is that the terminal has all kinds of 
stripes in it and is thus almost unusable.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 22 22:13:02 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-02-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140214)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f64d2174514 <_wordcopy_fwd_dest_aligned+84>:
mov(%rsi),%r10
   PC (0x7f64d2174514) ok
   source "(%rsi)" (0x83e84f80) not located in a known VMA region (needed 
readable region)!
   destination "%r10" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   _wordcopy_fwd_dest_aligned (dstp=611212704, srcp=, 
len=40652993) at wordcopy.c:182
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in _wordcopy_fwd_dest_aligned()
  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/unity/+bug/1283557/+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 1285349] Re: While hovering indicator menus and crossing to a different monitor, the hover does does not continue on the second monitor

[Treviño]

Christopher, I actually did this on purpose, as I think it might cause
more troubles than gains: if you open menus in a monitor, then moving to
the other monitor (by mistake for example), shouldn't open the menus,
and the same thing should happen for menus imho.

Also, this fixed some other weird behaviors (like menus opened in a
monitor, but active indicator in the other).

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

Title:
  While hovering indicator menus and crossing to a different monitor,
  the hover does does not continue on the second monitor

Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  When hovering over indicator entries to reveal the menu and switching
  to different indicators and then crossing into a second monitor, the
  last indicator that was hovered on the first monitor stays open and
  the hovering will not continue on the second monitor.

  This is a regression found in the
  
unity.tests.test_panel.PanelCrossMonitorsTests.test_hovering_indicators_on_multiple_monitors
  Autopilot test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1285349/+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 1266464] Re: HUD "Super" and "Alt" shortcuts works through locked screen

[Treviño]

** Branch linked: lp:~andyrock/unity/lockscreen

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

Title:
  HUD "Super" and "Alt" shortcuts works through locked screen

Status in Unity:
  Confirmed
Status in “hud” package in Ubuntu:
  Invalid

Bug description:
  To reproduce:
  1. Lock screen (e.g. using Ctrl+Alt+L or corresponding option in menu).
  2. Press Super (or Alt) key.
  3. Enter password to unlock desktop.

  Expected behaviour: nothing on desktop should be changed.
  Observed behaviour: HUD menu pupped up, as if Alt or Super were pressed on 
desktop.

  I mark this bug report as security issue, because not sure is Super
  and Alt keys are only shortcuts that being passed to desktop, if other
  keys can be passed to desktop in any way it would be possible to run
  some command through HUD.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: hud 13.10.1+13.10.20131031-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CheckboxSubmission: 3d16077c4fdd6a017d47f6e3dc4f3c54
  CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
  Date: Mon Jan  6 17:18:05 2014
  InstallationDate: Installed on 2014-01-01 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1266464/+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 1283671] Re: 14.04 daily build (2014-02-21): unity desktop crashes on every application start

[Treviño]

Try to use latest compiz, it should be fixed.

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

Title:
  14.04 daily build (2014-02-21): unity desktop crashes on every
  application start

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I installed the 14.04 daily build from a CD image yesterday to help
  testing. Unfortunately, I cannot test anything because right upon
  booting, when the desktop appears, every app I start causes about a
  minute of freezing (even the mouse pointer freezes) and then a restart
  (or complete crash) of the unity top menubar and sidebar.

  The only thing in the desktop I customized was the Unity sidebar
  button size (in the settings app - to 16 pixels first, then to 24
  pixels). But even the settings app caused this crash before I could
  use it to change the settings.

  I am writing this in a 640x480 Firefox window without window manager
  from within the crashed Unity desktop.

  Is this a known bug? I sure hope so. ;)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Feb 23 09:58:45 2014
  InstallationDate: Installed on 2014-02-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140222)
  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/1283671/+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 1283611] Re: Unity launcher partially hidden after dragging files onto it

[Treviño]

** Summary changed:

- Unity panel partially hidden after dragging files onto it
+ Unity launcher partially hidden after dragging files onto it

** Description changed:

- When dragging a file/folder/shortcut and going over the panel (as in trying 
to drop it there) the panel shows, then hides and then doesn't fully show after 
that.
- After this, only about 80% of the panel is shown every time it is activated, 
with the left most 20% not showing (auto-hide enabled).
- Also, when opening Lenses, there is a gap the size of the missing part of the 
panel, between the panel and the lenses.
+ When dragging a file/folder/shortcut and going over the launcher (as in 
trying to drop it there) the launcher shows, then hides and then doesn't fully 
show after that.
+ After this, only about 80% of the launcher is shown every time it is 
activated, with the left most 20% not showing (auto-hide enabled).
+ Also, when opening Lenses, there is a gap the size of the missing part of the 
launcher, between the launcher and the lenses.
  The only way to work around it is by restarting unity (or lightdm or the 
computer) or by disabling and re-enabling the Unity Plugin in ccsm.
  Happy to help troubleshooting this issue, please explain how I can help.
  
  Thank you.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 13.10
+ ProblemType: BugDistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Feb 23 13:48:11 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.6, 3.11.0-15-generic, x86_64: installed
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company Device [103c:17ab]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Device [103c:17ab]
  InstallationDate: Installed on 2014-02-16 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP ProBook 6570b
  MarkForUpload: True
- ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/username--lp-lv_root ro quiet splash vt.handoff=7
- SourcePackage: unity
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic 
root=/dev/mapper/username--lp-lv_root ro quiet splash 
vt.handoff=7SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICE Ver. F.04
  dmi.board.name: 17AB
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICEVer.F.04:bd06/12/2012:svnHewlett-Packard:pnHPProBook6570b:pvrA1029D1103:rvnHewlett-Packard:rn17AB:rvrKBCVersion42.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 6570b
  dmi.product.version: A1029D1103
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Wed Feb 19 07:48:54 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id   12890 
-  vendor SEC
+  product id   12890
+  vendor SEC
  xserver.version: 2:1.14.5-1ubuntu2~saucy1

** Also affects: unity
   Importance: Undecided
   Status: New

** Changed in: unity
   Status: New => Triaged

** Changed in: unity
Milestone: None => 7.2.0

-- 
You received this bug notification because you are a member of DX
Packages, which is

[Dx-packages] [Bug 1055166] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... from

[Treviño]

** Changed in: compiz
   Status: In Progress => Fix Committed

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

Title:
  compiz crashed with SIGSEGV in memmove() from
  drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator()
  from compiz::opengl::bindTexImageGLX() from ... from
  unity::UnityWindow::DrawWindowDecoration

Status in Compiz:
  Fix Committed
Status in Mesa:
  Invalid
Status in Unity:
  Invalid
Status in Unity 6.0 series:
  Won't Fix
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “mesa” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  See also bug 927168, which was resolved recently.

  Compiz crashed after installed something via Synaptic and just it
  installed that i want it crashed coz i want to see  the black
  installition screen

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity 6.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Sun Sep 23 21:36:37 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f031d57d73c:movntdq %xmm1,-0x10(%rdi)
   PC (0x7f031d57d73c) ok
   source "%xmm1" ok
   destination "-0x10(%rdi)" (0x108d5b170) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   gnome-session[1561]: WARNING: Application 'compiz.desktop' killed by signal 
11
   gnome-session[1561]: WARNING: App 'compiz.desktop' respawning too quickly
   gnome-session[1561]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1055166/+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 1055166] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... from

[Launchpad Bug Tracker]

This bug was fixed in the package compiz -
1:0.9.11+14.04.20140303-0ubuntu1

---
compiz (1:0.9.11+14.04.20140303-0ubuntu1) trusty; urgency=low

  [ Marco Trevisan (Treviño) ]
  * Window: define proper cases when we need to resize a window when
decorating/undecorating Yeah, again here... So, now when setting the
window extents, we resize a window only in these cases: 1) We have a
normal window that has never been decorated (lp:1282304) 2) We're
(re)decorating a maximized or fullscreen window (lp:1282305) This
seems to work well in all the cases I tested, with no regressions
with nedit (that highlighted an issue with old code path) (LP:
#1282304, #1282305)
  * Opengl, Texture: don't try to create a texture of invalid (empty or
negative) size This seem to cause also a crash when using software
rendering. (LP: #1055166)
 -- Ubuntu daily releaseMon, 03 Mar 2014 
20:09:55 +

** Changed in: compiz (Ubuntu)
   Status: New => Fix Released

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

Title:
  compiz crashed with SIGSEGV in memmove() from
  drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator()
  from compiz::opengl::bindTexImageGLX() from ... from
  unity::UnityWindow::DrawWindowDecoration

Status in Compiz:
  In Progress
Status in Mesa:
  Invalid
Status in Unity:
  Invalid
Status in Unity 6.0 series:
  Won't Fix
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “mesa” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  See also bug 927168, which was resolved recently.

  Compiz crashed after installed something via Synaptic and just it
  installed that i want it crashed coz i want to see  the black
  installition screen

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity 6.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Sun Sep 23 21:36:37 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f031d57d73c:movntdq %xmm1,-0x10(%rdi)
   PC (0x7f031d57d73c) ok
   source "%xmm1" ok
   destination "-0x10(%rdi)" (0x108d5b170) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   gnome-session[1561]: WARNING: Application 'compiz.desktop' killed by signal 
11
   gnome-session[1561]: WARNING: App 'compiz.desktop' respawning too quickly
   gnome-session[1561]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1055166/+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 1055166] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... from

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/compiz

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

Title:
  compiz crashed with SIGSEGV in memmove() from
  drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator()
  from compiz::opengl::bindTexImageGLX() from ... from
  unity::UnityWindow::DrawWindowDecoration

Status in Compiz:
  In Progress
Status in Mesa:
  Invalid
Status in Unity:
  Invalid
Status in Unity 6.0 series:
  Won't Fix
Status in “compiz” package in Ubuntu:
  New
Status in “mesa” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  See also bug 927168, which was resolved recently.

  Compiz crashed after installed something via Synaptic and just it
  installed that i want it crashed coz i want to see  the black
  installition screen

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity 6.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Sun Sep 23 21:36:37 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f031d57d73c:movntdq %xmm1,-0x10(%rdi)
   PC (0x7f031d57d73c) ok
   source "%xmm1" ok
   destination "-0x10(%rdi)" (0x108d5b170) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   gnome-session[1561]: WARNING: Application 'compiz.desktop' killed by signal 
11
   gnome-session[1561]: WARNING: App 'compiz.desktop' respawning too quickly
   gnome-session[1561]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1055166/+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 1287411] [NEW] compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path()

[Deluxo]

Public bug reported:

tried 14.04 daily build. Installed it and ran updates.
Then, i installed google chrome browser and wanted to drag the icon to the 
launcher. compiz just froze, and only mouse could move. no further interaction 
was possible. Then i switched to tty6 and logged-in. Compiz restarted and asked 
to report this issue. Can't help more, sorry.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140228-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar  4 01:00:26 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-03-03 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140303)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f5dd2773341 :  
mov0x8(%rax),%edx
 PC (0x7f5dd2773341) ok
 source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 g_mount_spec_to_dbus_with_path () from 
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 g_file_load_contents () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


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

** Information type changed from Private to Public

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

Title:
  compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path()

Status in “unity” package in Ubuntu:
  New

Bug description:
  tried 14.04 daily build. Installed it and ran updates.
  Then, i installed google chrome browser and wanted to drag the icon to the 
launcher. compiz just froze, and only mouse could move. no further interaction 
was possible. Then i switched to tty6 and logged-in. Compiz restarted and asked 
to report this issue. Can't help more, sorry.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140228-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  4 01:00:26 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-03-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140303)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f5dd2773341 :
mov0x8(%rax),%edx
   PC (0x7f5dd2773341) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   g_mount_spec_to_dbus_with_path () from 
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
   g_file_load_contents () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path()
  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/unity/+bug/1287411/+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 902715] Re: [Precise] Sound indicator have a silent menu item with are not accessible for screen reader

[Luke Yelavich]

** Changed in: indicator-sound (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  [Precise] Sound indicator have a silent menu item with are not
  accessible for screen reader

Status in Indicator Display Objects:
  Fix Released
Status in Sound Menu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Confirmed
Status in “indicator-sound” source package in Precise:
  Fix Released

Bug description:
  Dear Developers,

  When I using Sound Indicator with Orca screen reader, I possible accessing 
the volume percent value, possible changing the mute status.
  Unfortunately, have a third menu item in the indicator with Orca nothing 
spokening. Possible this is an empty menu item?
  Can you investigate this problem?

  Attila

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-sound 0.8.0.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
  Uname: Linux 3.2.0-3-generic i686
  ApportVersion: 1.90-0ubuntu1
  Architecture: i386
  Date: Sun Dec 11 07:20:11 2011
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 
(20111202.1)
  ProcEnviron:
   LANGUAGE=hu_HU:en
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   LC_MESSAGES=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ido/+bug/902715/+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 1280759] Re: Shortcuts are defined via keyboard layout, not the keys

[Masoud Pourmoosa]

This bug still exists in Trusty after recent updates on the Unity
desktop.

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

Title:
  Shortcuts are defined via keyboard layout, not the keys

Status in “unity” package in Ubuntu:
  New

Bug description:
  There are shortcuts to open lenses in Unity, for example "Super + A"
  for App Lens, or "Super + F" for Files Lens, etc. There are also
  shortcuts in the Launcher "Super + 1 to 9" to launch apps from the
  Launcher. These shortcuts don't work if the keyboard layout is set to
  a non-Latin layout, in my case Persian, where almost all the keys are
  mapped to new characters.

  HOW TO REPRODUCE:
  Add a new Persian keyboard layout to the system, in addition to English, via 
keyboard layout indicator --> Text Entry Settings.
  Switch to the Persian layout (by clicking on the keyboard layout indicator).
  Press "Super + F".

  WHAT HAPPENS:
  Dash is not open. Nothing happens.

  WHAT SHOULD HEPPEN:
  The Files Lens in the dash should open.
  The shortcuts should be associated with the keys on the keyboard, not to the 
characters they are associated with (which depends on the active keyboard 
layout).
  When I am typing something in Persian, and I want to search for a file, it is 
not reasonable that I should first switch back to the English layout before I 
can use a particular shortcut.

  
  This problem does not happen in some other apps like gedit or Firefox.

  COMPARE TO GEDIT:
  Open gedit text editor.
  Write something.
  Switch to the Persian layout.
  Press "Ctrl + S" (the shortcut to save the document).

  WHAT HAPPENS, AND WHAT SHOULD HAPPEN:
  The save dialoge box appears.

  
  I think this problem happens for all keyboard layouts that don't use Latin 
characters. 
  Layout-wise, when I press "Ctrl + S" while Persian layout is active, I am 
typing "Ctrl + س".
  But keyboard-wise, I am always pressing the same keyboard binding.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 16 12:04:10 2014
  InstallationDate: Installed on 2014-02-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211)
  SourcePackage: libunity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1280759/+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 1283798] Re: Keyboard layout switcher shortcuts stop working after reboot

[Masoud Pourmoosa]

I can no longer reproduce this bug. Keep up the great work :)

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

Title:
  Keyboard layout switcher shortcuts stop working after reboot

Status in “unity” package in Ubuntu:
  New

Bug description:
  HOW TO REPRODUCE
  - Add a new keyboard shortcut (in my case, Persian layout) from the keyboard 
indicator -> Text Entry Settings
  - Assign shortcuts for switching to next/previous source (in my case 
Shift+Alt L and Alt+Shift R)
  - Test the new layout and layout switcher shortcuts to check if they work (in 
my case, yes they do)
  - Reboot
  - Log back in
  - Press the layout switcher shortcuts

  WHAT HAPPENS
  Keyboard layout does not change upon pressing the shortcuts

  WHAT SHOULD HAPPEN
  Layout should change according to the shortcuts you press

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140218.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Feb 23 20:09:45 2014
  InstallationDate: Installed on 2014-02-15 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211)
  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/1283798/+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 1286605] Re: Unity global menu causes handlers of the "activate" signal of Gtk.Action to be emptied

[William Hua]

** Also affects: unity-gtk-module
   Importance: Undecided
   Status: New

** Also affects: unity-gtk-module (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unity global menu causes handlers of the "activate" signal of
  Gtk.Action to be emptied

Status in Unity GTK+ module:
  New
Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity-gtk-module” package in Ubuntu:
  New

Bug description:
  If you launch banshee 2.6.2 or banshee 2.9.0 in Ubuntu 14.04 and start
  playing a song, and then go to the "Edit" menu, you will not see an
  option to set up the rating of the song.

  The culprit of this is Unity's Global Menu, because the RatingSet menu
  appears fine when launching banshee with UBUNTU_MENUPROXY=0.

  Under the hood, the reason of why this menu is not attached when
  running inside unity is because adding a handler to the signal
  "activate" of a Gtk.Action has no effect (maybe Unity is removing all
  the handlers of this signal?).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Mar  1 21:23:34 2014
  InstallationDate: Installed on 2014-02-25 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-gtk-module/+bug/1286605/+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 1286605] Re: Unity global menu causes handlers of the "activate" signal of Gtk.Action to be emptied

[William Hua]

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

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

Title:
  Unity global menu causes handlers of the "activate" signal of
  Gtk.Action to be emptied

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  If you launch banshee 2.6.2 or banshee 2.9.0 in Ubuntu 14.04 and start
  playing a song, and then go to the "Edit" menu, you will not see an
  option to set up the rating of the song.

  The culprit of this is Unity's Global Menu, because the RatingSet menu
  appears fine when launching banshee with UBUNTU_MENUPROXY=0.

  Under the hood, the reason of why this menu is not attached when
  running inside unity is because adding a handler to the signal
  "activate" of a Gtk.Action has no effect (maybe Unity is removing all
  the handlers of this signal?).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Mar  1 21:23:34 2014
  InstallationDate: Installed on 2014-02-25 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
  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/1286605/+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 1283171] Re: Visual corruption on window buttons

[Treviño]

** Changed in: unity
   Status: In Progress => Fix Committed

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

Title:
  Visual corruption on window buttons

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  My window buttons have corruption...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Fri Feb 21 18:51:40 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-06-29 (601 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-20 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1283171/+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 1283453] Re: window spread with too narrow titlebars on hig-dpi screen

[Treviño]

** Changed in: unity
   Status: In Progress => Fix Committed

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

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

Title:
  window spread with too narrow titlebars on hig-dpi screen

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Committed

Bug description:
  Titlebars are currently cropped and don't completely display the text
  in spread mode, if the global scaling factor is set to 2.

  org.gnome.desktop.interface.scaling-factor = 2
  org.gnome.desktop.interface.text-scaling-factor = 1.0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Feb 22 15:04:07 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-02 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1283453/+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 1283410] Re: titlebar-font does not scale on high-dpi screen

[Treviño]

** Changed in: unity
   Status: In Progress => Fix Committed

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

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

Title:
  titlebar-font does not scale on high-dpi screen

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Committed

Bug description:
  The titlebar-font appears to small in window titlebars, application menu and 
indicators. Since all other fonts are consider the global scaling factor 
automatically, the individual font sizes should not need to be changed.
  In the screenshot I have 
org.gnome.desktop.wm.preferences.titlebar-font="Ubuntu Bold 11" (the default).
  When I change it to "Ubuntu Bold 22", most titlebars and the application 
title in the panel show the (originally) expected font size, but the 
application menu and indicators still show too small text.

  org.gnome.desktop.interface.scaling-factor = 2
  org.gnome.desktop.interface.text-scaling-factor = 1.0
  org.gnome.desktop.wm.preferences.titlebar-font="Ubuntu Bold 11"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Feb 22 12:33:14 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Feb 22 12:08:14 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970 
   vendor SDC
  xserver.version: 2:1.15.0-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1283410/+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 1283406] Re: top panel menus are offset on high-dpi screen

[Treviño]

** Changed in: unity
   Status: In Progress => Fix Committed

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

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

Title:
  top panel menus are offset on high-dpi screen

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Committed

Bug description:
  The position of the menus from the toppanel (application menus,
  indicators) take the scaling factor twice into account and appear
  offset to the bottom right.

  org.gnome.desktop.interface.scaling-factor = 2
  org.gnome.desktop.interface.text-scaling-factor = 1.0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Feb 22 12:17:55 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Feb 22 12:08:14 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970 
   vendor SDC
  xserver.version: 2:1.15.0-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1283406/+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 1283171] Re: Visual corruption on window buttons

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.1.2+14.04.20140303-0ubuntu1

---
unity (7.1.2+14.04.20140303-0ubuntu1) trusty; urgency=low

  [ Marco Trevisan (Treviño) ]
  * Panel, Decorations, Launcher, Quicklist, Tooltip: correctly scale
items based on the monitor settings Adapt elements to match their
monitor DPI scale settings. We mostly use
cairo_surface_set_device_scale to easily scale cairo-generated
textures. (LP: #1283171)
 -- Ubuntu daily releaseMon, 03 Mar 2014 
16:47:47 +

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

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

Title:
  Visual corruption on window buttons

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  My window buttons have corruption...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Fri Feb 21 18:51:40 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-06-29 (601 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-20 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1283171/+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 1287322] Re: ctrl+super keybindings broken in trusty

[Chow Loong Jin]

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

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

Title:
  ctrl+super keybindings broken in trusty

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

Bug description:
   affects unity
   status new

  Unity's handling of Ctrl+Super+X keybindings has regressed in trusty -- 
Control
  must be pressed before Super is pressed, or Unity hijacks the keybinding
  instead.

  For example:
  1. Press and hold Control
  2. Press and hold Super
  3. Press 1

  This activates the Ctrl+Super+1 keybinding, which for me is Zoom reset
  (from the ezoom plugin).

  However, if you reverse steps 1 and 2, so that Super is held down before
  Control, then the keybinding for Super+1 is activated instead, i.e. the first
  item in the launcher gets activated.

  This bug used to be present in older versions of Unity, but was fixed in 
Saucy,
  and reappeared in Trusty.

  -- 
  Kind regards,
  Loong Jin

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1287322/+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 1287343] [NEW] Application menu hijacks Alt+F, E, V, S, T, H keybindings in gnome-terminal

[Chow Loong Jin]

Public bug reported:

1. Enable the menubar in gnome-terminal
2. Go to Edit->Keyboard Shortcuts and uncheck "Enable menu access keys (such as 
Alt+F to open the File menu)
3. Type something in the shell, then go to the beginning of the line, and 
attempt to use Alt+F to navigate forward by word
4. Observe that the File menu triggers instead, even though it should have been 
disabled as per step 2.

Repeat the above steps running gnome-terminal like: "UBUNTU_MENUPROXY=0
gnome-terminal", and notice that the menu doesn't activate, and Alt+F
gets successfully handled by the shell.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-gtk3-module 0.0.0+14.04.20140213.2-0ubuntu1
Uname: Linux 3.13.4-hyper1 x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar  4 03:53:14 2014
SourcePackage: unity-gtk-module
UpgradeStatus: Upgraded to trusty on 2014-03-03 (0 days ago)

** Affects: unity-gtk-module (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  Application menu hijacks Alt+F,E,V,S,T,H keybindings in gnome-terminal

Status in “unity-gtk-module” package in Ubuntu:
  New

Bug description:
  1. Enable the menubar in gnome-terminal
  2. Go to Edit->Keyboard Shortcuts and uncheck "Enable menu access keys (such 
as Alt+F to open the File menu)
  3. Type something in the shell, then go to the beginning of the line, and 
attempt to use Alt+F to navigate forward by word
  4. Observe that the File menu triggers instead, even though it should have 
been disabled as per step 2.

  Repeat the above steps running gnome-terminal like:
  "UBUNTU_MENUPROXY=0 gnome-terminal", and notice that the menu doesn't
  activate, and Alt+F gets successfully handled by the shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-gtk3-module 0.0.0+14.04.20140213.2-0ubuntu1
  Uname: Linux 3.13.4-hyper1 x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  4 03:53:14 2014
  SourcePackage: unity-gtk-module
  UpgradeStatus: Upgraded to trusty on 2014-03-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1287343/+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 1274181] Re: notification-daemon crashed with signal 5 in g_source_remove()

[vulfgar]

Affects me every time I log in. The effect is that upper panel in Gnome
Flashback with Compiz  is blurred and I can't access the functions
placed there.

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

Title:
  notification-daemon crashed with signal 5 in g_source_remove()

Status in “notification-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Just rebooted and logged into Gnome Flashback with Compiz and
  immediately got this error notification.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: notification-daemon 0.7.6-1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Jan 29 11:37:58 2014
  ExecutablePath: /usr/lib/notification-daemon/notification-daemon
  InstallationDate: Installed on 2014-01-08 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108)
  ProcCmdline: /usr/lib/notification-daemon/notification-daemon
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: notification-daemon
  StacktraceTop:
   g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: notification-daemon crashed with signal 5 in g_source_remove()
  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/notification-daemon/+bug/1274181/+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 992789] Re: Unity shortcuts ignore current keyboard layout

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 771263
   Short-cuts in Unity do not use the appropriate keyboard layout
** This bug has been marked a duplicate of bug 1226962
   Hotkeys not functional in non-latin keyboard layout in 13.10 and 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/992789

Title:
  Unity shortcuts ignore current keyboard layout

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  With normal QWERTY keyboard layout (ie) on Ubuntu, the keyboard
  shortcut to launch a terminal is CTRL + ALT + T.

  When I change to USA/Dvorak, I should expect to press CTRL + ALT + K
  on my physical keyboard, as 'K' corresponds to 'T' in Dvorak.

  However, I actually have to use the old QWERTY key combination with my
  Dvorak layout, which would print as CTRL + ALT + K, to launch a
  terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu1
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Tue May  1 19:27:33 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  ProcEnviron:
   LANGUAGE=en_IE:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IE.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/ubuntu/+source/unity/+bug/992789/+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 1228360] Re: No clock in menu bar and can't edit Clock settings

[Oleksandr]

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

** This bug has been marked a duplicate of bug 1244285
   Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 
13.10)

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

Title:
  No clock in menu bar and can't edit Clock settings

Status in “indicator-datetime” package in Ubuntu:
  Triaged

Bug description:
  The latest update broke the clock in several ways:

  * No clock shows up in the menu bar.

  * Open Time & Date settings.  You cannot edit anything in the Clock
  tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu38
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 20 15:51:55 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-07-12 (800 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to saucy on 2011-12-23 (637 days ago)
  usr_lib_gnome-control-center:
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20130913-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1228360/+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 771263] Re: Short-cuts in Unity do not use the appropriate keyboard layout

[Alberto Salvia Novella]

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

** This bug has been marked a duplicate of bug 1226962
   Hotkeys not functional in non-latin keyboard layout in 13.10 and 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/771263

Title:
  Short-cuts in Unity do not use the appropriate keyboard layout

Status in Gnome Settings Daemon:
  Confirmed
Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  What I did :

  1. install my computer, using azerty (french) keyboard layout 
  2. switch my computer to bépoè layout (it is like dvorak, but for french)
  3. remove the azerty layout (in the keyboard preferences windows
  4. press Ctrl-alt-t
  5. press Ctrl-alt-è (è is the key which was the t in the azerty layout)
  6. press Super-f
  7. press Super-t

  What I expected :
  at step 4 : unity open the terminal
  at step 5 : nothing
  at step 6 : unity open the files lens
  at step 7 : unity open the trash window

  What happened :
  at step 4 : nothing
  at step 5 : unity open the terminal
  at step 6 : unity open the files lens
  at step 7 : unity open the trash window

  Comments :
  So, it seems that with ctrl-alt, unity uses the old layout (which I removed), 
and with Super, it uses the correct layout.  Remark that if I uses ctrl-alt-f3, 
the computer uses the azerty layout.  So, it looks like switching keyboard 
layout and removing the previous one only applied to the graphical side (X 
server?), and that Unity, for some reason, uses different layout when I press 
ctrl-alt and super...

  Ubuntu version : Natty Narwhal, fully updated

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/771263/+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 1001185] Re: I can't lock screen by Ctrl+alt+L when current keyboard layout is non latin

[Alberto Salvia Novella]

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

** This bug is no longer a duplicate of bug 771263
   Short-cuts in Unity do not use the appropriate keyboard layout
** This bug has been marked a duplicate of bug 1226962
   Hotkeys not functional in non-latin keyboard layout in 13.10 and 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/1001185

Title:
  I can't lock screen by Ctrl+alt+L when current keyboard layout is non
  latin

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When current keyboard's layout is non latin, keyboard shortcut to lock
  screen doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.12-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,snap,colorfilter,text,workarounds,neg,copytex,annotate,clone,commands,gnomecompat,move,place,regex,resize,rotate,screenshot,imgpng,water,zoom,grid,imgsvg,unitymtgrabhandles,expo,winrules,kdecompat,session,vpswitch,mousepoll,shift,ezoom,resizeinfo,mag,switcher,thumbnail,wall,ring,fade,scale,unityshell,scaleaddon,opacify]
  Date: Fri May 18 13:06:28 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-04-27 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1001185/+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 1120358] Re: Reduce the dependency on the geoclue-ubuntu-geoip packages to a recommends

[Charles Kerr]

This was previously not practical because indicator-datetime needed
libgeoclue-dev to even build.

However, this  isn't true anymore in 14.04 and geoclue is not used by
default -- it's enabled if/when a user toggles the "show-auto-detected-
location" boolean via unity-control-center. So I think this decoupling
is at least possible now, though I'd prefer to have seb128 or cyphermox
weigh in whether or not that change is practical.

Lastly, this change is IMO a low priority because indicator-datetime
stopped unconditionally initializing GeoClue in 13.04.

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

Title:
  Reduce the dependency on the geoclue-ubuntu-geoip packages to a
  recommends

Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  Geoip check is currently used to determine if your timezone has
  changed. It connects to canonical servers on every boot. There is
  currently no way to remove the geoclue-ubuntu-geoip package without
  also removing indicator-datetime. Please reduce the dependency on the
  geoclue-ubuntu-geoip package to a recommends so users that do not need
  timezone adjustment or privacy-aware people can un-install it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1120358/+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 1120358] Re: Reduce the dependency on the geoclue-ubuntu-geoip packages to a recommends

[Charles Kerr]

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Reduce the dependency on the geoclue-ubuntu-geoip packages to a
  recommends

Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  Geoip check is currently used to determine if your timezone has
  changed. It connects to canonical servers on every boot. There is
  currently no way to remove the geoclue-ubuntu-geoip package without
  also removing indicator-datetime. Please reduce the dependency on the
  geoclue-ubuntu-geoip package to a recommends so users that do not need
  timezone adjustment or privacy-aware people can un-install it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1120358/+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 740817] Re: Mousing over date doesn't highlight it

[Charles Kerr]

** Changed in: ido
   Importance: Undecided => Wishlist

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

Title:
  Mousing over date doesn't highlight it

Status in Indicator Display Objects:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: indicator-datetime

  indicator-datetime 0.1.98-0ubuntu1, Ubuntu Natty

  1. Open the clock menu.
  2. Mouse over any of the dates in the calendar.

  What happens: Nothing (apart from bug 740350).
  What should happen: The date under the mouse should highlight like a normal 
menu item.

  : "All dates
  shown in the calendar should behave, and look, as normal grid-layout
  menu items."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ido/+bug/740817/+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 854497] Re: indicator-datetime-service crashed with SIGSEGV in geoclue_master_client_set_requirements_async()

[Charles Kerr]

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

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  geoclue_master_client_set_requirements_async()

Status in The Date and Time Indicator:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  Dell Inspiron 1150 Laptop without Hard Drive Running Ubuntu 11.10
  Oneric Ocelot Beta 1 off USB Drive with updates from Natty Narwhal
  11.04 Final

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: indicator-datetime 0.2.95-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic i686
  ApportVersion: 1.23-0ubuntu1
  Architecture: i386
  Date: Mon Sep 19 11:58:53 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
  ProcCwd: /
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x353419 
:mov0x0(%ebp),%edi
   PC (0x00353419) ok
   source "0x0(%ebp)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   geoclue_master_client_set_requirements_async () from /usr/lib/libgeoclue.so.0
   ?? ()
   ?? () from /usr/lib/libgeoclue.so.0
   ?? () from /usr/lib/libgeoclue.so.0
   ?? () from /usr/lib/i386-linux-gnu/libdbus-glib-1.so.2
  Title: indicator-datetime-service crashed with SIGSEGV in 
geoclue_master_client_set_requirements_async()
  UpgradeStatus: Upgraded to oneiric on 2011-09-12 (8 days ago)
  UserGroups: admin
  XsessionErrors:
   (unity-panel-service:1609): libindicator-WARNING **: IndicatorObject class 
does not have an accessible description.
   (unity-panel-service:1609): libindicator-WARNING **: IndicatorObject class 
does not have an accessible description.
   (unity-panel-service:1609): GLib-CRITICAL **: g_error_free: assertion `error 
!= NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/854497/+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 1076434] Re: Day names for all day events use day names rather than Today/Tomorrow

[Charles Kerr]

Full-day events now use the strings "Today" and "Tomorrow" as specified.

http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/utils.c#L238

** Changed in: indicator-datetime
   Status: Triaged => Fix Released

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

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: indicator-datetime
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Changed in: indicator-datetime
Milestone: 13.04.0 => None

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

Title:
  Day names for all day events use day names rather than Today/Tomorrow

Status in The Date and Time Indicator:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  All day events which occur on the current day, or the day following
  it, are using the full day names such as 'Thursday' or 'Friday' when
  they should be displayed as 'Today' and 'Tomorrow' instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: indicator-datetime 12.10.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-18.18-lowlatency 3.5.7
  Uname: Linux 3.5.0-18-lowlatency x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Thu Nov  8 10:47:50 2012
  InstallationDate: Installed on 2012-10-21 (17 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1076434/+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 729056] Re: Date setting in the preferences should be not be shown in ISO format

[Charles Kerr]

Reassigning to unity-control-center, which is where the code for that
panel now resides.

** Project changed: indicator-datetime => unity-control-center

** Package changed: indicator-datetime (Ubuntu) => unity-control-center
(Ubuntu)

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

Title:
  Date setting in the preferences should be not be shown in ISO format

Status in Unity Control Center:
  Confirmed
Status in “unity-control-center” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: indicator-datetime

  Right now, on starting the time & date settings dialog to change the
  date, the date itself is shown in ISO 8601 format.

  This is confusing for users not used to that format. As an example a
  user in Spain will not be able to tell between the day and the month
  by just looking at the date shown there in most cases.

  The date should be shown in a way that is more locale-friendly or that
  is locale-independant but it is not subject to confusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-control-center/+bug/729056/+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 771263] Re: Short-cuts in Unity do not use the appropriate keyboard layout

[Ivan Larionov]

Fix link: https://bugs.launchpad.net/unity/+bug/1226962

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

Title:
  Short-cuts in Unity do not use the appropriate keyboard layout

Status in Gnome Settings Daemon:
  Confirmed
Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  What I did :

  1. install my computer, using azerty (french) keyboard layout 
  2. switch my computer to bépoè layout (it is like dvorak, but for french)
  3. remove the azerty layout (in the keyboard preferences windows
  4. press Ctrl-alt-t
  5. press Ctrl-alt-è (è is the key which was the t in the azerty layout)
  6. press Super-f
  7. press Super-t

  What I expected :
  at step 4 : unity open the terminal
  at step 5 : nothing
  at step 6 : unity open the files lens
  at step 7 : unity open the trash window

  What happened :
  at step 4 : nothing
  at step 5 : unity open the terminal
  at step 6 : unity open the files lens
  at step 7 : unity open the trash window

  Comments :
  So, it seems that with ctrl-alt, unity uses the old layout (which I removed), 
and with Super, it uses the correct layout.  Remark that if I uses ctrl-alt-f3, 
the computer uses the azerty layout.  So, it looks like switching keyboard 
layout and removing the previous one only applied to the graphical side (X 
server?), and that Unity, for some reason, uses different layout when I press 
ctrl-alt and super...

  Ubuntu version : Natty Narwhal, fully updated

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/771263/+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 1218136] Re: trafficserver

[Charles Kerr]

Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but it is better to raise problems you are having in the
support tracker at https://answers.launchpad.net/ubuntu if you are
uncertain if they are bugs. You can also find help with your problem in
the support forum of your local Ubuntu community http://loco.ubuntu.com/
or asking at http://askubuntu.com or http://ubuntuforums.org. For help
on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.

** Package changed: indicator-datetime (Ubuntu) => trafficserver
(Ubuntu)

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

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

Title:
  trafficserver

Status in “trafficserver” package in Ubuntu:
  Invalid

Bug description:
  how to configure trafficserver server.ports  8080:tr-in:bind??

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/trafficserver/+bug/1218136/+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 1215003] Re: indicator-datetime-service crashed with SIGSEGV in g_date_time_to_unix()

[Charles Kerr]

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

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_date_time_to_unix()

Status in The Date and Time Indicator:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  This crash happened on startup.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 12.10.3+13.10.20130731-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Wed Aug 21 12:12:06 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-08-12 (9 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130811)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe78418a764:mov0x10(%rdi),%esi
   PC (0x7fe78418a764) ok
   source "0x10(%rdi)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_date_time_to_unix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   indicator_datetime_planner_get_appointments ()
   ?? ()
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_date_time_to_unix()
  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/indicator-datetime/+bug/1215003/+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 771263] Re: Short-cuts in Unity do not use the appropriate keyboard layout

[Ivan Larionov]

Looks like tracked here: #1226962

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

Title:
  Short-cuts in Unity do not use the appropriate keyboard layout

Status in Gnome Settings Daemon:
  Confirmed
Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  What I did :

  1. install my computer, using azerty (french) keyboard layout 
  2. switch my computer to bépoè layout (it is like dvorak, but for french)
  3. remove the azerty layout (in the keyboard preferences windows
  4. press Ctrl-alt-t
  5. press Ctrl-alt-è (è is the key which was the t in the azerty layout)
  6. press Super-f
  7. press Super-t

  What I expected :
  at step 4 : unity open the terminal
  at step 5 : nothing
  at step 6 : unity open the files lens
  at step 7 : unity open the trash window

  What happened :
  at step 4 : nothing
  at step 5 : unity open the terminal
  at step 6 : unity open the files lens
  at step 7 : unity open the trash window

  Comments :
  So, it seems that with ctrl-alt, unity uses the old layout (which I removed), 
and with Super, it uses the correct layout.  Remark that if I uses ctrl-alt-f3, 
the computer uses the azerty layout.  So, it looks like switching keyboard 
layout and removing the previous one only applied to the graphical side (X 
server?), and that Unity, for some reason, uses different layout when I press 
ctrl-alt and super...

  Ubuntu version : Natty Narwhal, fully updated

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/771263/+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 1222245] Re: /usr/lib/x86_64-linux-gnu/indicator-datetime-service:11:g_date_time_to_instant:g_date_time_to_unix:my_get_appointments:indicator_datetime_planner_get_appointments:get_a

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1215003
   indicator-datetime-service crashed with SIGSEGV in g_date_time_to_unix()

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

Title:
  /usr/lib/x86_64-linux-gnu/indicator-datetime-
  
service:11:g_date_time_to_instant:g_date_time_to_unix:my_get_appointments:indicator_datetime_planner_get_appointments:get_all_appointments_this_month

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-datetime.  This problem was most recently seen
  with version 13.10.0+13.10.20130903-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/daa92ecd1f29cb86f5a38bc50b8b8d28d2203d04
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/145/+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 1287280] [NEW] Unity UI lost middle mouse click in title bar function

[James Lewis]

Public bug reported:

As of the Locally Integrated Menu's release, Unity is no-longer
honouring a middle click in the title bar... unless the window is
maximised.

This appears to be a regressions since it has worked up until this
release, and indeed still works for maximised windows...

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140228-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Mon Mar  3 12:49:35 2014
InstallationDate: Installed on 2013-10-25 (128 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-01-17 (45 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Unity UI lost middle mouse click in title bar function

Status in “unity” package in Ubuntu:
  New

Bug description:
  As of the Locally Integrated Menu's release, Unity is no-longer
  honouring a middle click in the title bar... unless the window is
  maximised.

  This appears to be a regressions since it has worked up until this
  release, and indeed still works for maximised windows...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140228-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Mar  3 12:49:35 2014
  InstallationDate: Installed on 2013-10-25 (128 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1287280/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

[Ivan Larionov]

14:04. Unity hotkeys (cmd+a/f/m/c/v) still doesn't work in non-latin
layout.

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “indicator-keyboard” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-settings-daemon” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+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 1279490] Re: Global menu searching obvious matches don't match

[Pete Woods]

** Branch linked: lp:~jpakkane/libcolumbus/hud-rework

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

Title:
  Global menu searching obvious matches don't match

Status in Unity HUD:
  In Progress
Status in Libcolumbus, a small, fast, error tolerant matcher:
  In Progress
Status in “hud” package in Ubuntu:
  In Progress

Bug description:
  Hi,

  I'm trying, in Gimp, to press Alt and then select the `Image -> Crop
  to Selection` item by matching against 'crop to selection' but that
  doesn't bring up that result.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20131106.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb 12 21:53:49 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-10-12 (1219 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-26 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/1279490/+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 829967] Re: indicator-datetime leaks memory

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version. When you test
it and it is still an issue, kindly upload the updated logs by running
apport-collect  and any other logs that are relevant for this
particular issue.

For what it's worth, I'm not seeing these leaks in my own testing when
running valgrind on the latest version of indicator-datetime,
13.10.0+14.04.20140227.1-0ubuntu1

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  indicator-datetime leaks memory

Status in “indicator-datetime” package in Ubuntu:
  Incomplete

Bug description:
  While monitoring some processes to find another leak, I found
  indicator-datetime to constantly use more (resident) memory over time
  (see screenshot). Over 10 hours of the system idling, the process
  gained 5MB which is kind of unacceptable on long running systems
  (given that stays linear while the system is in use - I'm checking
  that today).

  Will add valgrind information shortly.

  This bug seems to be different from bug 782468, as I don't see that
  much of an increase. I've not added any additional timezones or
  anything like that.

  Using indicator-application 0.2.93-0ubuntu1 on up-to-date Oneiric.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/829967/+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 1098812] Re: indicator-datetime-service crashed with SIGSEGV in update_appointment_menu_items()

[Charles Kerr]

This is caused by the same problems that caused bug #1197645.

For more information on this, see the change description at
https://code.launchpad.net/~charlesk/indicator-
datetime/lp-1204532/+merge/184155

** Changed in: indicator-datetime
   Status: New => Fix Released

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

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  update_appointment_menu_items()

Status in The Date and Time Indicator:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily12.11.23-0ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Jan 12 06:06:05 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-10-20 (83 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x4064ff:  mov0x0(%rbp),%rdi
   PC (0x004064ff) ok
   source "0x0(%rbp)" (0x) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2012-12-09 (33 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1098812/+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 1197851] Re: indicator-datetime-service crashed with SIGSEGV

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
your system at the time of the report. Please upgrade your system to the
latest package versions. If you still encounter the crash, please file a
new report.

Thank you for your understanding, and sorry for the inconvenience!

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

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

Title:
  indicator-datetime-service crashed with SIGSEGV

Status in “indicator-datetime” package in Ubuntu:
  Invalid

Bug description:
  After a reboot of Ubuntu, it crashed with this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 12.10.3+13.10.20130703.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Jul  4 16:51:14 2013
  Disassembly: => 0x7f81f6d15040:   Cannot access memory at address 
0x7f81f6d15040
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-01-06 (179 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f81f6d15040:Cannot access memory at address 
0x7f81f6d15040
   PC (0x7f81f6d15040) ok
   SP (0x7fff382c0b40) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: indicator-datetime
  Stacktrace:
   #0  0x7f81f6d15040 in ?? ()
   No symbol table info available.
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   ?? ()
   ?? ()
  Title: indicator-datetime-service crashed with SIGSEGV
  UpgradeStatus: Upgraded to saucy on 2013-07-01 (3 days ago)
  UserGroups: adm audio cdrom dip disk libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1197851/+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 1239701] Re: indicator-datetime-service crashed with signal 5 in ffi_call_SYSV()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1238621
   indicator-datetime-service crashed with signal 5 in ffi_call_SYSV()
** This bug has been marked a duplicate of bug 1238737
   indicator-datetime-service crashed: "Unable to get bus connection to own 
name 'com.canonical.indicator.datetime'"

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

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

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Upon first boot after upgrading to 13.10 (beta)

  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 i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Mon Oct 14 14:32:17 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-06-18 (482 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  Signal: 5
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
  Title: indicator-datetime-service crashed with signal 5 in ffi_call_SYSV()
  UpgradeStatus: Upgraded to saucy on 2013-10-14 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1239701/+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 1238621] Re: indicator-datetime-service crashed with signal 5 in ffi_call_SYSV()

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1238737
   indicator-datetime-service crashed: "Unable to get bus connection to own 
name 'com.canonical.indicator.datetime'"

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

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

Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  Just rebooted from an update on Saucy today and got this crash.

  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 i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Fri Oct 11 07:44:21 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-10-01 (9 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta i386 (20131001)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 5
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
  Title: indicator-datetime-service crashed with signal 5 in ffi_call_SYSV()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1238621/+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 1072887] Re: indicator-datetime-service crashed with SIGSEGV in update_appointment_menu_items()

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  update_appointment_menu_items()

Status in The Date and Time Indicator:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  erro popped up after restart after todays upgrade

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: indicator-datetime 12.10.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Mon Oct 29 14:04:14 2012
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2012-05-16 (166 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x804d966: mov(%esi),%eax
   PC (0x0804d966) ok
   source "(%esi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to quantal on 2012-10-06 (22 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1072887/+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 1087410] Re: indicator-datetime-service crashed with SIGSEGV in update_appointment_menu_items()

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  update_appointment_menu_items()

Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  Get a lot of errors with datetime.
  I use evolution for adding my google agenda to the datetime-service.

  Have these on two different setups (pc and laptop)

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: indicator-datetime 12.10.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Thu Dec  6 20:32:36 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2012-02-02 (307 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANGUAGE=nl_BE:nl
   LANG=nl_BE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x406897:  mov0x8(%rax),%rcx
   PC (0x00406897) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to quantal on 2012-10-18 (48 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1087410/+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 1073076] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1072887
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Indicator-datetime-service crashed after startup.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: indicator-datetime 12.10.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Tue Oct 30 12:47:00 2012
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2010-03-20 (955 days ago)
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
  MarkForUpload: True
  ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804dd7f: mov0x8(%eax),%eax
   PC (0x0804dd7f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to quantal on 2012-09-23 (36 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev 
nopasswdlogin plugdev sambashare tape video
  XsessionErrors:
   (gnome-settings-daemon:1800): common-plugin-WARNING **: Key 0xff6a 
(keycodes:  146)  with state 0x0 (resolved to 0x0)  has no usable modifiers 
(usable modifiers are 0x14ed)
   (unity-mail:1978): libunity-WARNING **: unity-launcher.vala:373: Schema 
"com.canonical.Unity.Launcher" is not installed!
   (gnome-terminal:2237): Vte-2.90-WARNING **: Не удалось преобразовать символы 
из набора текущая в набор X-VTE-GUNICHAR.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1073076/+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 1088799] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1072887
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
   I see the date and time crash report on starting ubuntu

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: indicator-datetime 12.10.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.5.0-20.31-generic 3.5.7.1
  Uname: Linux 3.5.0-20-generic i686
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  Date: Tue Dec 11 07:48:05 2012
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2011-06-09 (550 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804dd5f: mov0x8(%eax),%eax
   PC (0x0804dd5f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to quantal on 2012-09-08 (93 days ago)
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1088799/+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 1092857] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1087410
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  This happens quite frequently, but I don't know what triggers the bug.
  I have the "Show upcoming events i the Evolution calendar" enabled, Evolution 
is linked to my gCal. Everything seems to work as usual, even after apport 
offers sending the error report.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: indicator-datetime 12.10.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Dec 21 11:48:45 2012
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2012-10-04 (77 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x406897:  mov0x8(%rax),%rcx
   PC (0x00406897) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to quantal on 2012-10-17 (64 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (nvidia-settings:2690): Gtk-WARNING **: Kunne ikke finne temamotor i 
module_path: «oxygen-gtk».
   (Tomboy:2692): Gtk-WARNING **: Kunne ikke finne temamotor i module_path: 
«oxygen-gtk».
   (dropbox:2711): Gtk-WARNING **: Kunne ikke finne temamotor i module_path: 
«oxygen-gtk».
   (gtk-window-decorator:2846): Gtk-WARNING **: Kunne ikke finne temamotor i 
module_path: «oxygen-gtk».
   (gnome-settings-daemon:2653): libappindicator-CRITICAL **: 
app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1092857/+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 1106377] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  apport showed up for no reason

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.01.25-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic i686
  ApportVersion: 2.8-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Sat Jan 26 22:04:37 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2011-11-11 (442 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d8e6: mov(%esi),%eax
   PC (0x0804d8e6) ok
   source "(%esi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-01-24 (2 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sbuild 
vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1106377/+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 1101000] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1087410
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Restart lightdm

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: indicator-datetime 12.10.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Jan 17 23:42:04 2013
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2012-11-02 (76 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x4064ff:  mov0x0(%rbp),%rdi
   PC (0x004064ff) ok
   source "0x0(%rbp)" (0x0026) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv (closure=0x21e9530, return_value=, instance=0x7f59c0003510, args=, marshal_data=, n_params=, param_types=0x21e13c0) at 
/build/buildd/glib2.0-2.34.1/./gobject/gmarshal.c:1312
   _g_closure_invoke_va (closure=0x21e9530, return_value=0x0, 
instance=0x7f59c0003510, args=0x7fffc7086058, n_params=1, 
param_types=0x21e13c0) at /build/buildd/glib2.0-2.34.1/./gobject/gclosure.c:840
   g_signal_emit_valist (instance=0x7f59c0003510, signal_id=, 
detail=0, var_args=var_args@entry=0x7fffc7086058) at 
/build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3211
   g_signal_emit (instance=, signal_id=, 
detail=) at /build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3356
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk kismet libvirtd lpadmin plugdev sambashare src 
sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1101000/+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 1159868] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  I started the computer, and some thing crashed.

  Regards,
  Pankaj Pal

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: i386
  Date: Mon Mar 25 21:26:59 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-11-22 (122 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d97f: mov0x8(%eax),%eax
   PC (0x0804d97f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-01-22 (61 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  XsessionErrors:
   gnome-session[1911]: WARNING: Failed to start app: Unable to start 
application: Failed to execute child process "dropbox" (No such file or 
directory)
   (process:2495): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1159868/+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 1156700] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  It bug report was generated automatically.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
  Uname: Linux 3.8.0-030800-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Mon Mar 18 18:55:03 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-09-30 (169 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d97f: mov0x8(%eax),%eax
   PC (0x0804d97f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
  XsessionErrors:
   gnome-session[2931]: WARNING: Failed to start app: Unable to start 
application: Не удалось выполнить процесс-потомок «nemo» (Нет такого файла или 
каталога)
   (indicator-multiload:3086): GLib-GIO-CRITICAL **: GApplication subclass 
'Main' failed to chain up on ::startup (from start of override function)
   gnome-session[2931]: WARNING: Could not launch application 
'evolution-alarm-notify.desktop': Unable to start application: Не удалось 
выполнить процесс-потомок «/usr/lib/evolution/3.6/evolution-alarm-notify» (Нет 
такого файла или каталога)
   (gnome-terminal:3416): Vte-2.90-WARNING **: Не удалось преобразовать символы 
из набора текущая в набор X-VTE-GUNICHAR.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1156700/+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 1119131] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1087410
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when I boot the computer it crash.

  I use gnome-classic or gnome-session-fallback with 3D (compiz).

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: indicator-datetime 12.10.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Feb  8 08:06:21 2013
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2012-11-02 (97 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x4064ff:  mov0x0(%rbp),%rdi
   PC (0x004064ff) ok
   source "0x0(%rbp)" (0x0026) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv (closure=0x10ce8b0, return_value=, instance=0x10b8ec0, args=, marshal_data=, 
n_params=, param_types=0x10cc990) at 
/build/buildd/glib2.0-2.34.1/./gobject/gmarshal.c:1312
   _g_closure_invoke_va (closure=0x10ce8b0, return_value=0x0, 
instance=0x10b8ec0, args=0x7fff83060808, n_params=1, param_types=0x10cc990) at 
/build/buildd/glib2.0-2.34.1/./gobject/gclosure.c:840
   g_signal_emit_valist (instance=0x10b8ec0, signal_id=, 
detail=0, var_args=var_args@entry=0x7fff83060808) at 
/build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3211
   g_signal_emit (instance=, signal_id=, 
detail=) at /build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3356
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk kismet libvirtd lpadmin plugdev sambashare src 
sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1119131/+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 1152821] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Crash occurred after loging into my account.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.06-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic i686
  ApportVersion: 2.9-0ubuntu2
  Architecture: i386
  Date: Fri Mar  8 19:29:25 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-10-25 (134 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x804d97f: mov0x8(%eax),%eax
   PC (0x0804d97f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-02-22 (14 days ago)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1152821/+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 1158028] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  on startup

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu1
  Architecture: i386
  Date: Thu Mar 21 00:33:30 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-12-22 (88 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x804d97f: mov0x8(%eax),%eax
   PC (0x0804d97f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-03-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1158028/+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 1156392] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Hello,

  Just end to upgrade my system,

  While launching session or accessing to my online calendar

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
  Uname: Linux 3.8.0-13-generic i686
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  CheckboxSubmission: 1008879e0fce49bb78f6ea764f9356d6
  CheckboxSystem: ed86e29ffba809c116a39e33fa9fc45c
  Date: Sun Mar 17 20:34:45 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-03-17 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha i386 
(20130316)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d566: mov(%esi),%eax
   PC (0x0804d566) ok
   source "(%esi)" (0x0026) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  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-datetime/+bug/1156392/+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 1114143] Re: indicator-datetime-service crashed with SIGSEGV in update_appointment_menu_items()

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  update_appointment_menu_items()

Status in The Date and Time Indicator:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  indicator-datetime-service crashed right after system startup.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.01.25-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
  Uname: Linux 3.8.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu3
  Architecture: amd64
  Date: Sun Feb  3 12:38:20 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-02-05 (363 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120201.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x406837:  mov0x8(%rax),%rcx
   PC (0x00406837) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv (closure=0x68d0a0, return_value=, instance=, args=, marshal_data=, n_params=, param_types=0x68b550) at 
/build/buildd/glib2.0-2.35.4/./gobject/gmarshal.c:1312
   _g_closure_invoke_va (closure=0x68d0a0, return_value=0x0, instance=0x673d70, 
args=0x7fffc139a728, n_params=1, param_types=0x68b550) at 
/build/buildd/glib2.0-2.35.4/./gobject/gclosure.c:840
   g_signal_emit_valist (instance=0x673d70, signal_id=, 
detail=0, var_args=var_args@entry=0x7fffc139a728) at 
/build/buildd/glib2.0-2.35.4/./gobject/gsignal.c:3225
   g_signal_emit (instance=, signal_id=, 
detail=) at /build/buildd/glib2.0-2.35.4/./gobject/gsignal.c:3370
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2012-11-15 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (nautilus:2485): Nautilus-Python-WARNING **: g_module_open libpython failed: 
/usr/lib/libpython2.7.so.1.0: невозможно открыть разделяемый объектный файл: 
Нет такого файла или каталога
   (nautilus:2485): Nautilus-Python-WARNING **: pygobject initialization failed
   (nautilus:2485): Nautilus-Python-WARNING **: nautilus_python_init_python 
failed
   (process:3009): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1114143/+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 1162017] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  On boot

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  CrashCounter: 1
  Date: Fri Mar 29 20:23:13 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-12-22 (97 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d98f: mov0x8(%eax),%eax
   PC (0x0804d98f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-03-20 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1162017/+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 1158171] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  I dont know

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic i686
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: i386
  Date: Thu Mar 21 15:01:31 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-03-17 (4 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130316)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d97f: mov0x8(%eax),%eax
   PC (0x0804d97f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (gnome-settings-daemon:3794): color-plugin-WARNING **: failed to get edid: 
unable to get EDID for output
   (gnome-settings-daemon:3794): color-plugin-WARNING **: unable to get EDID 
for xrandr-LVDS: unable to get EDID for output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1158171/+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 1160983] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  This bug report was created automatically.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  Uname: Linux 3.8.0-030800-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  Date: Wed Mar 27 17:50:55 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-09-30 (177 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d98f: mov0x8(%eax),%eax
   PC (0x0804d98f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
  XsessionErrors:
   gnome-session[3017]: WARNING: Failed to start app: Unable to start 
application: Не удалось выполнить процесс-потомок «nemo» (Нет такого файла или 
каталога)
   (indicator-multiload:3202): GLib-GIO-CRITICAL **: GApplication subclass 
'Main' failed to chain up on ::startup (from start of override function)
   gnome-session[3017]: WARNING: Could not launch application 
'evolution-alarm-notify.desktop': Unable to start application: Не удалось 
выполнить процесс-потомок «/usr/lib/evolution/3.6/evolution-alarm-notify» (Нет 
такого файла или каталога)
   (process:3543): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed
   (process:3637): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1160983/+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 1161007] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()
** This bug has been marked a duplicate of bug 1098812
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  I started the system and got this alert.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  CrashCounter: 1
  Date: Wed Mar 27 22:05:57 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-11-22 (125 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d98f: mov0x8(%eax),%eax
   PC (0x0804d98f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-01-22 (63 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  XsessionErrors:
   gnome-session[1915]: WARNING: Failed to start app: Unable to start 
application: Failed to execute child process "dropbox" (No such file or 
directory)
   (process:2504): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed
   (thunderbird:2504): GLib-CRITICAL **: g_variant_new_string: assertion 
`string != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1161007/+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 979314] Re: indicator-applet-complete crashed with signal 7

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 852899
   [Oneiric b1] unity-panel-service crashed with signal 7 in g_object_newv()

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

Title:
  indicator-applet-complete crashed with signal 7

Status in Indicator Applet:
  Confirmed
Status in “indicator-applet” package in Ubuntu:
  Confirmed

Bug description:
  I was using bleachbit when the error occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: indicator-applet-complete 0.5.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.0.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr 11 22:18:03 2012
  ExecutablePath: /usr/lib/indicator-applet/indicator-applet-complete
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  ProcCmdline: /usr/lib/indicator-applet/indicator-applet-complete
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  Signal: 7
  SourcePackage: indicator-applet
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: indicator-applet-complete crashed with signal 7
  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/indicator-applet/+bug/979314/+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 1050174] Re: indicator-datetime-service crashed with "Settings schema 'org.gnome.Evolution.DefaultSources' is not installed"

[Charles Kerr]

** Summary changed:

- indicator-datetime-service crashed with signal 5 in g_object_newv()
+ indicator-datetime-service crashed with "Settings schema 
'org.gnome.Evolution.DefaultSources' is not installed"

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

Title:
  indicator-datetime-service crashed with "Settings schema
  'org.gnome.Evolution.DefaultSources' is not installed"

Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  Crash happened upon boot just after logging in. I did nothing specific
  with the date/time applet to cause this.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: indicator-datetime 12.10.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
  Uname: Linux 3.5.0-14-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  Date: Wed Sep 12 20:25:03 2012
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120814.1)
  ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
  Signal: 5
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with signal 5 in g_object_newv()
  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-datetime/+bug/1050174/+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 1243586] Re: dpkg-source: warning: unknown information field 'Pre-Depends'

[William Hua]

Hi Angel, thanks for the bug report, the warning itself should have been
fixed here: http://bazaar.launchpad.net/~indicator-applet-developers
/unity-gtk-module/trunk.14.04/revision/311.

But I can't replicate the error (on 64-bit). Does it still happen for
you?

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

Title:
  dpkg-source: warning: unknown information field 'Pre-Depends'

Status in “unity-gtk-module” package in Ubuntu:
  New

Bug description:
  I trying to build a .deb from source code of unity-gtk-module since
  there are not instructions for build or install, I am running the
  following command:

  apt-get source unity-gtk-module
  sudo apt-get build-dep unity-gtk-module
  cd unity-gtk-module-*
  LANG=C dpkg-buildpackage -rfakeroot -b

  Running the last dpkg-buildpackage command I get:

  dpkg-buildpackage: host architecture i386
   dpkg-source --before-build unity-gtk-module-0.0.0+13.10.20130716.1
  dpkg-source: warning: unknown information field 'Pre-Depends' in input data 
in general section of control info file
   fakeroot debian/rules clean

  And the build fails for dh_install:

  dh_install --fail-missing
  
/home/myuser/unity-gtk-module-0.0.0+13.10.20130716.1/debian/libunity-gtk-parser-dev-common.install:
 1: 
/home/myuser/unity-gtk-module-0.0.0+13.10.20130716.1/debian/libunity-gtk-parser-dev-common.install:
 usr/include/unity-gtk-parser/*: not found
  
/home/myuser/unity-gtk-module-0.0.0+13.10.20130716.1/debian/libunity-gtk-parser-dev-common.install:
 2: 
/home/myuser/unity-gtk-module-0.0.0+13.10.20130716.1/debian/libunity-gtk-parser-dev-common.install:
 usr/share/gtk-doc/html/unity-gtk-module/*: not found
  dh_install: problem reading debian/libunity-gtk-parser-dev-common.install: 
  make[1]: *** [override_dh_install] Error 127
  make[1]: se sale del directorio 
«/home/myuser/unity-gtk-module-0.0.0+13.10.20130716.1»
  make: *** [binary] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1243586/+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 1199976] Re: indicator-datetime-service crashed with SIGSEGV

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
your system at the time of the report. Please upgrade your system to the
latest package versions. If you still encounter the crash, please file a
new report.

Thank you for your understanding, and sorry for the inconvenience!

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

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

Title:
  indicator-datetime-service crashed with SIGSEGV

Status in “indicator-datetime” package in Ubuntu:
  Invalid

Bug description:
  crash reported at start-up

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 12.10.3+13.10.20130708-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jul 10 11:48:18 2013
  Disassembly: => 0x7f77d6c38040:   Cannot access memory at address 
0x7f77d6c38040
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-10-21 (261 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f77d6c38040:Cannot access memory at address 
0x7f77d6c38040
   PC (0x7f77d6c38040) ok
   SP (0x7fff73f62560) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: indicator-datetime
  Stacktrace:
   #0  0x7f77d6c38040 in ?? ()
   No symbol table info available.
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   ?? ()
   ?? ()
  Title: indicator-datetime-service crashed with SIGSEGV
  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-datetime/+bug/1199976/+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 1159868] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of private bug 1132174
** This bug has been marked a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  I started the computer, and some thing crashed.

  Regards,
  Pankaj Pal

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: i386
  Date: Mon Mar 25 21:26:59 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-11-22 (122 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d97f: mov0x8(%eax),%eax
   PC (0x0804d97f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-01-22 (61 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  XsessionErrors:
   gnome-session[1911]: WARNING: Failed to start app: Unable to start 
application: Failed to execute child process "dropbox" (No such file or 
directory)
   (process:2495): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1159868/+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 1223389] Re: indicator-datetime-service crashed with SIGSEGV

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
your system at the time of the report. Please upgrade your system to the
latest package versions. If you still encounter the crash, please file a
new report.

Thank you for your understanding, and sorry for the inconvenience!

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

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

Title:
  indicator-datetime-service crashed with SIGSEGV

Status in “indicator-datetime” package in Ubuntu:
  Invalid

Bug description:
  The Time and Date is not displayed in the Panel  after upgrading vom
  13.04 to 13.10...

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20130903-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Sep 10 16:25:35 2013
  Disassembly: => 0x7f7a7c32ff90:   Cannot access memory at address 
0x7f7a7c32ff90
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-04-05 (158 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=de_DE
   LANG=de_DE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f7a7c32ff90:Cannot access memory at address 
0x7f7a7c32ff90
   PC (0x7f7a7c32ff90) ok
   SP (0x7fffb7c0e910) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: indicator-datetime
  Stacktrace:
   #0  0x7f7a7c32ff90 in ?? ()
   No symbol table info available.
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   ?? ()
   ?? ()
  Title: indicator-datetime-service crashed with SIGSEGV
  UpgradeStatus: Upgraded to saucy on 2013-09-07 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1223389/+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 1106377] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of private bug 1105995
** This bug has been marked a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  apport showed up for no reason

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.01.25-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic i686
  ApportVersion: 2.8-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Sat Jan 26 22:04:37 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2011-11-11 (442 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d8e6: mov(%esi),%eax
   PC (0x0804d8e6) ok
   source "(%esi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-01-24 (2 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sbuild 
vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1106377/+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 1156392] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of private bug 1132174
** This bug has been marked a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Hello,

  Just end to upgrade my system,

  While launching session or accessing to my online calendar

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
  Uname: Linux 3.8.0-13-generic i686
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  CheckboxSubmission: 1008879e0fce49bb78f6ea764f9356d6
  CheckboxSystem: ed86e29ffba809c116a39e33fa9fc45c
  Date: Sun Mar 17 20:34:45 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-03-17 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha i386 
(20130316)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d566: mov(%esi),%eax
   PC (0x0804d566) ok
   source "(%esi)" (0x0026) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  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-datetime/+bug/1156392/+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 1161007] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of private bug 1132174
** This bug has been marked a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  I started the system and got this alert.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  CrashCounter: 1
  Date: Wed Mar 27 22:05:57 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-11-22 (125 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d98f: mov0x8(%eax),%eax
   PC (0x0804d98f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-01-22 (63 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  XsessionErrors:
   gnome-session[1915]: WARNING: Failed to start app: Unable to start 
application: Failed to execute child process "dropbox" (No such file or 
directory)
   (process:2504): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed
   (thunderbird:2504): GLib-CRITICAL **: g_variant_new_string: assertion 
`string != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1161007/+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 1156700] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of private bug 1132174
** This bug has been marked a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  It bug report was generated automatically.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
  Uname: Linux 3.8.0-030800-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Mon Mar 18 18:55:03 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-09-30 (169 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d97f: mov0x8(%eax),%eax
   PC (0x0804d97f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
  XsessionErrors:
   gnome-session[2931]: WARNING: Failed to start app: Unable to start 
application: Не удалось выполнить процесс-потомок «nemo» (Нет такого файла или 
каталога)
   (indicator-multiload:3086): GLib-GIO-CRITICAL **: GApplication subclass 
'Main' failed to chain up on ::startup (from start of override function)
   gnome-session[2931]: WARNING: Could not launch application 
'evolution-alarm-notify.desktop': Unable to start application: Не удалось 
выполнить процесс-потомок «/usr/lib/evolution/3.6/evolution-alarm-notify» (Нет 
такого файла или каталога)
   (gnome-terminal:3416): Vte-2.90-WARNING **: Не удалось преобразовать символы 
из набора текущая в набор X-VTE-GUNICHAR.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1156700/+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 1160983] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of private bug 1132174
** This bug has been marked a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  This bug report was created automatically.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  Uname: Linux 3.8.0-030800-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  Date: Wed Mar 27 17:50:55 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-09-30 (177 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d98f: mov0x8(%eax),%eax
   PC (0x0804d98f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
  XsessionErrors:
   gnome-session[3017]: WARNING: Failed to start app: Unable to start 
application: Не удалось выполнить процесс-потомок «nemo» (Нет такого файла или 
каталога)
   (indicator-multiload:3202): GLib-GIO-CRITICAL **: GApplication subclass 
'Main' failed to chain up on ::startup (from start of override function)
   gnome-session[3017]: WARNING: Could not launch application 
'evolution-alarm-notify.desktop': Unable to start application: Не удалось 
выполнить процесс-потомок «/usr/lib/evolution/3.6/evolution-alarm-notify» (Нет 
такого файла или каталога)
   (process:3543): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed
   (process:3637): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1160983/+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 1152821] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of private bug 1132174
** This bug has been marked a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Crash occurred after loging into my account.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.06-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic i686
  ApportVersion: 2.9-0ubuntu2
  Architecture: i386
  Date: Fri Mar  8 19:29:25 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-10-25 (134 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x804d97f: mov0x8(%eax),%eax
   PC (0x0804d97f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-02-22 (14 days ago)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1152821/+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 1158028] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of private bug 1132174
** This bug has been marked a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  on startup

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu1
  Architecture: i386
  Date: Thu Mar 21 00:33:30 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-12-22 (88 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x804d97f: mov0x8(%eax),%eax
   PC (0x0804d97f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-03-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1158028/+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 1162017] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of private bug 1132174
** This bug has been marked a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  On boot

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  CrashCounter: 1
  Date: Fri Mar 29 20:23:13 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2012-12-22 (97 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d98f: mov0x8(%eax),%eax
   PC (0x0804d98f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: Upgraded to raring on 2013-03-20 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1162017/+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 1158171] Re: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Charles Kerr]

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

** This bug is no longer a duplicate of private bug 1132174
** This bug has been marked a duplicate of bug 1114143
   indicator-datetime-service crashed with SIGSEGV in 
update_appointment_menu_items()

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_cclosure_marshal_VOID__OBJECTv()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  I dont know

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic i686
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: i386
  Date: Thu Mar 21 15:01:31 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-03-17 (4 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130316)
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x804d97f: mov0x8(%eax),%eax
   PC (0x0804d97f) ok
   source "0x8(%eax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__OBJECTv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (gnome-settings-daemon:3794): color-plugin-WARNING **: failed to get edid: 
unable to get EDID for output
   (gnome-settings-daemon:3794): color-plugin-WARNING **: unable to get EDID 
for xrandr-LVDS: unable to get EDID for output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1158171/+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 1238192] Re: indicator-datetime-service crashed with SIGSEGV in g_type_check_instance()

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1238737
   indicator-datetime-service crashed: "Unable to get bus connection to own 
name 'com.canonical.indicator.datetime'"

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

Title:
  indicator-datetime-service crashed with SIGSEGV in
  g_type_check_instance()

Status in The Date and Time Indicator:
  New
Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Clicked on system settings icon in unity toolbar and system went
  straight to restart

  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Thu Oct 10 11:12:42 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  InstallationDate: Installed on 2013-10-08 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64+mac 
(20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f66eca905ad : mov
(%rdi),%rax
   PC (0x7f66eca905ad) ok
   source "(%rdi)" (0x0021) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_handler_disconnect () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   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
  Title: indicator-datetime-service crashed with SIGSEGV in 
g_type_check_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1238192/+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 1287205] [NEW] hud does not work with the global menu on desktop

[krishnan sampath]

Public bug reported:

Pre 13.04, the HUD could access anything on the global menu. For eg, hitting 
alt and typing shutdown brought up the shutdown option, it could be used to 
open applications integrated into the sound and messenger menu like rhythmbox, 
banshee and thunderbird. From 13.04 onwards, on any fresh installation and 
upgrade, i find this feature does not work. I atleast think its a bug and 
should be fixed soon.
Thanks for reading and have a nice day :)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: hud 13.10.1+14.04.20140218.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar  3 20:24:22 2014
InstallationDate: Installed on 2014-03-02 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
SourcePackage: hud
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.window-stack-bridge.log:
 QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was 
':1.7'
 QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was 
':1.5'

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


** Tags: amd64 apport-bug trusty

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

Title:
  hud does not work with the global menu on desktop

Status in “hud” package in Ubuntu:
  New

Bug description:
  Pre 13.04, the HUD could access anything on the global menu. For eg, hitting 
alt and typing shutdown brought up the shutdown option, it could be used to 
open applications integrated into the sound and messenger menu like rhythmbox, 
banshee and thunderbird. From 13.04 onwards, on any fresh installation and 
upgrade, i find this feature does not work. I atleast think its a bug and 
should be fixed soon.
  Thanks for reading and have a nice day :)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hud 13.10.1+14.04.20140218.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  3 20:24:22 2014
  InstallationDate: Installed on 2014-03-02 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.window-stack-bridge.log:
   QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was 
':1.7'
   QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was 
':1.5'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1287205/+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 1247671] Re: indicator time does not update upon location change

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1244680
   Clock freezes after changing timezone
** This bug has been marked a duplicate of bug 1271484
   Clock doesn't update after changing time zone

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

Title:
  indicator time does not update upon location change

Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  I recently travelled from my home area of Los Angeles to Hong Kong.
  While the time zone correctly was changed in settings, the indicator
  itself froze at the old time. killing the indicator-datetime-service
  process resulted in the correct local time being displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20131016.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov  4 05:12:32 2013
  InstallationDate: Installed on 2013-01-14 (293 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac 
(20121017.3)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to saucy on 2013-10-23 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1247671/+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 1258121] Re: indicator time does not update time zone change

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1244680
   Clock freezes after changing timezone
** This bug has been marked a duplicate of bug 1271484
   Clock doesn't update after changing time zone

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

Title:
   indicator time does not update time zone change

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Indicator time does not update when I change time zone in "Date & Time
  Settings".

  To reproduce:
  1. Open "Date & Time Settings..." in time indicator.
  2. Change "Location" to other time zone (e.g. I change from "Saint 
Petersburg" to "London").

  Expected behaviour: time in time indicator should change.
  Observed behaviour: time in time indicator shown in old time zone.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Dec  5 11:01:48 2013
  InstallationDate: Installed on 2013-10-16 (49 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to saucy on 2013-11-07 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1258121/+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 1244680] Re: Clock freezes after changing timezone

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1271484
   Clock doesn't update after changing time zone

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

Title:
  Clock freezes after changing timezone

Status in “indicator-datetime” package in Ubuntu:
  Triaged

Bug description:
  The time in the datetime indicator freezes when you change the
  timezone.

  To reproduce:
  1) Note the current time in the datetime indicator
  2) Change the system timezone, such as by clicking a different timezone in 
the datetime indicator menu or changing timezone in the date/time system 
settings app

  Expected results:
  The clock in the datetime indicator updates to show the current time in the 
new timezone. The clock continues to function normally, updating the 
minutes/hours as time progresses

  Actual results:
  The clock in the datetime indicator freezes. It does not update to the new 
timezone and no longer updates the minutes/hours - it stays frozen at the time 
it displayed when you updated the timezone.

  The system time is not affected; running 'date' from a terminal
  displays the correct time. The menu in the datetime indicator will
  display the correct time. It's just the clock in the panel that is
  broken.

  This is 100% reproducible on my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20131016.2-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-0ubuntu2.1
  Architecture: amd64
  Date: Fri Oct 25 10:07:03 2013
  InstallationDate: Installed on 2010-09-17 (1134 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to saucy on 2013-08-07 (78 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1244680/+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 993540] Re: Initially empty menu not shown in wxwidget program under Unity

[William Hua]

** Changed in: unity-gtk-module
   Status: New => Confirmed

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

Title:
  Initially empty menu not shown in wxwidget program under Unity

Status in Unity GTK+ module:
  Confirmed
Status in “unity” package in Ubuntu:
  New

Bug description:
  If a wxwidget program creates an initially empty menu (that will later
  be dynamically filled at run-time) that menu is not shown when Unity
  is used in Ubuntu 12.04. It shows up fine in Xubuntu or in Ubuntu
  10.10, equally if another window manager is used it shows up fine.

  Tested with Ubuntu 12.04 LTS. Attached is a program adapted from
  wxwidget menu examples that will show the issue (file menu.cpp
  compiles with: g++ -o menu menu.cpp `wx-config --libs --cxxflags
  --cppflags`)

  Result of running the program is that the "Demo" menu is shown but not
  the "Empty" menu. Expected result is that the Empty menu should be
  shown as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-gtk-module/+bug/993540/+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 1113008] Re: F10 or Alt+ opens the window menus within the window

[William Hua]

** Changed in: unity-gtk-module
   Status: Triaged => Fix Released

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

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

Title:
  F10 or Alt+ opens the window menus within the window

Status in Unity:
  Fix Committed
Status in Unity GTK+ module:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-gtk-module” package in Ubuntu:
  Fix Released

Bug description:
  Attempting to activate the menu bar using F10 or Alt+F causes the menu
  to pop open within the menu instead of from the panel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1113008/+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 1242550] Re: indicator-sound keyboard controls with left/right ARROW keys broken

[Sebastien Bacher]

** Changed in: ido
   Status: Fix Committed => Fix Released

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

Title:
  indicator-sound keyboard controls with left/right ARROW keys broken

Status in Indicator Display Objects:
  Fix Released
Status in “ido” package in Ubuntu:
  Fix Released

Bug description:
  In raring I used to be able to focus indicator-sound and then down-
  arrow to the volume, and then left/right arrow the volume up and down.

  In saucy the left/right arrows, instead of adjusting the volume, moves
  to the indicator to the right (clock) or left (battery) of the volume
  indicator.

  Now I am getting RSI from reaching for the far-away and difficult-to-
  press volume adjusting keys on the Dell Latitude E5400.

  The left/right arrow keys should only switch indicators if I have not
  descended into the indicator submenu with the down arrow.

  Note in the clock indicator, going with the down arrow into the
  monthly calendar, the left/right arrows correctly move through the
  calendar days, instead of switching to another indicator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ido/+bug/1242550/+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 1192646] Re: shouldn't list inactive items

[Sebastien Bacher]

** Changed in: hud/13.10
   Status: In Progress => Fix Released

** Changed in: hud
   Status: Fix Committed => Fix Released

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

Title:
  shouldn't list inactive items

Status in Unity HUD:
  Fix Released
Status in Unity HUD 13.10 series:
  Fix Released
Status in “hud” package in Ubuntu:
  Fix Released
Status in “hud” source package in Saucy:
  Fix Released

Bug description:
  [Impact]
  All Ubuntu users using Unity and the HUD.

  [Test case]
  - start gedit
  - open the hud
  - look for "undo"

  It lists the "undo" item from the edit menu, it shouldn't since there
  is nothing to undo and the menu item is greyed out.

  [Regression potential]
  Since this changes how menu items are identified on whether or not they need 
to be shown, there could be unforeseen issues where menu items that should be 
appearing and used to be appearing are now hidden and considered unavailable. 
Items that just recently became available may not be visible in the hud.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/1192646/+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 1246536] Re: segfault in menu_hidden()

[Sebastien Bacher]

** Changed in: indicator-sound
   Status: Fix Committed => Fix Released

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

Title:
  segfault in menu_hidden()

Status in Sound Menu:
  Fix Released
Status in “ido” package in Ubuntu:
  Fix Released
Status in “ido” source package in Saucy:
  Fix Released

Bug description:
  Impact: indicator-sound is segfaulting the unity-panel-service
  sometimes

  Test Case:
  - install the current GTK version from saucy-proposed
  - use the indicator-sound slider and the play multimedia key to start/stop 
rhythmbox
  - the indicator should be stable

  Regression potential: try desktop indicators and make sure they keep
  working

  ---

  Using saucy stable, happened a few times today while using the slider,
  muting/unmuting, using play multimedia key/mpris to start/stop
  rhythmbox

  "#0  menu_hidden (menu=0x96882c0, scale=0x97b8110) at idoscalemenuitem.c:640
  #1  0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x97b5818,
  return_value=0x0, n_param_values=1, param_values=0xbff2e970,
  invocation_hint=0xbff2e91c, marshal_data=0x0)
  at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85
  #2  0xb6e438ae in g_closure_invoke (closure=0x97b5818,
  return_value=return_value@entry=0x0, n_param_values=1,
  param_values=param_values@entry=0xbff2e970,
  invocation_hint=invocation_hint@entry=0xbff2e91c)
  at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777
  #3  0xb6e55df9 in signal_emit_unlocked_R (node=node@entry=0x9562ec8, detail=0,
  instance=0x96882c0, emission_return=emission_return@entry=0x0,
  instance_and_params=0xbff2e970)
  at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3586
  #4  0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0,
  signal_id=signal_id@entry=5, detail=detail@entry=0,
  var_args=var_args@entry=0xbff2eaac "h\027;\267")
  at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330
  #5  0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0,
  signal_id=5, detail=detail@entry=0)
  at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386
  #6  0xb73b1820 in gtk_widget_hide (widget=widget@entry=0x96882c0)
  at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkwidget.c:4268
  #7  0xb7278678 in gtk_menu_popdown (menu=menu@entry=0x96882c0)
  at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:1848
  #8  0xb727877d in gtk_menu_deactivate (menu_shell=0x96882c0)
  at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:4546
  #9  0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x956c640,
  return_value=0x0, n_param_values=1, param_values=0xbff2ec90,
  invocation_hint=0xbff2ec3c, marshal_data=0xb7278700 )
  at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85
  #10 0xb6e423d4 in g_type_class_meta_marshal (closure=0x956c640,
  return_value=0x0, n_param_values=1, param_values=0xbff2ec90,
  invocation_hint=0xbff2ec3c, marshal_data=0x1ec)
  at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:970
  #11 0xb6e438ae in g_closure_invoke (closure=closure@entry=0x956c640,
  return_value=return_value@entry=0x0, n_param_values=1,
  param_values=param_values@entry=0xbff2ec90,
  invocation_hint=invocation_hint@entry=0xbff2ec3c)
  at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777
  #12 0xb6e5549c in signal_emit_unlocked_R (node=node@entry=0x956d3b8, detail=0,
  instance=0x96882c0, emission_return=emission_return@entry=0x0,
  instance_and_params=0xbff2ec90)
  at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3516
  #13 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0,
  signal_id=signal_id@entry=82, detail=detail@entry=0,
  var_args=var_args@entry=0xbff2edcc "")
  at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330
  #14 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0,
  signal_id=82, detail=detail@entry=0)
  at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386
  #15 0xb7282923 in gtk_menu_shell_deactivate (menu_shell=0x96882c0)
  at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:616
  #16 0xb7283202 in gtk_menu_shell_activate_item (
  menu_shell=menu_shell@entry=0x96882c0,
  menu_item=menu_item@entry=0x962a0b8,
  force_deactivate=force_deactivate@entry=1)
  at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:1433
  #17 0xb7283626 in gtk_menu_shell_button_release (widget=0x96882c0,
  event=0x9648650)
  at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:842
  #18 0xb7276ce9 in gtk_menu_button_release (widget=0x96882c0, event=0x9648650)
  at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:3391
  #19 0xb7267ee6 in _gtk_marshal_BOOLEAN__BOXEDv (closure=0x9563f18,
  return_value=0xbff2efa8, instance=0x96882c0,
  args=0xbff

[Dx-packages] [Bug 1247898] Re: /usr/lib/i386-linux-gnu/hud/hud-service:11:hud_menu_model_collector_add_window:hud_application_source_context_add_window:hud_application_source_add_window:view_opened:f

[Sebastien Bacher]

** Changed in: hud/14.04
   Status: Fix Committed => Fix Released

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

Title:
  /usr/lib/i386-linux-gnu/hud/hud-
  
service:11:hud_menu_model_collector_add_window:hud_application_source_context_add_window:hud_application_source_add_window:view_opened:ffi_call_SYSV

Status in Unity HUD:
  Fix Released
Status in Unity HUD 13.10 series:
  In Progress
Status in Unity HUD 14.04 series:
  Fix Released
Status in “hud” package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding hud.  This problem was most recently seen with version
  13.10.1+13.10.20131024-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5af5f02229aef3cf6e93ddb9f7aaaf35a1124842
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/1247898/+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 1243413] Re: unity-gtk-module uses a hard-coded blacklist

[Sebastien Bacher]

** Changed in: unity-gtk-module
   Status: Fix Committed => Fix Released

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

Title:
  unity-gtk-module uses a hard-coded blacklist

Status in Unity GTK+ module:
  Fix Released
Status in “unity-gtk-module” package in Ubuntu:
  Fix Released

Bug description:
  Many applications don't work well with unity-gtk-module's menu
  exporting behaviour. Currently we disable menu exportation using a
  blacklist directly in the source code... it would be better to use a
  better solution like a GSettings key with good defaults.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-gtk-module/+bug/1243413/+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 1255719] Re: Upstart job keeps respawing indicator-sync on the greeter

[Sebastien Bacher]

** Changed in: indicator-sync
   Status: Fix Committed => Fix Released

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

Title:
  Upstart job keeps respawing indicator-sync on the greeter

Status in The Sync Menu:
  Fix Released
Status in “indicator-sync” package in Ubuntu:
  Fix Released

Bug description:
  Using trusty, /var/lib/lightdm/.cache/upstart/indicator-sync.log
  indicates that upstart keeps trying spawning indicator-sync which exit
  with "No watchers, service time out."

  The indicator is not supposed to be used on the greeter, the upstart
  job there seems like it should be smarter...

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sync/+bug/1255719/+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