[Dx-packages] [Bug 1332947] Re: HDPI: unity randomly turns on large text in universal access

2014-07-19 Thread Andrey Konstantinov
It's not limited to very high DPI either. I have an Acer Aspire V5-573
with 15.6 inch 1920x1080 screen and this happens. However, it does *not*
happen on my Asus N550JV with same screen specs. Both are running Ubuntu
14.04 64 bit. The only difference is that I used icon scaling settings
on the Acer (in Displays settings).

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

Title:
  HDPI: unity randomly turns on large text in universal access

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

Bug description:
  I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every
  couple of reboots, the 'large text' option in Universal Access gets
  switched on upon login. It happens in roughly 1 out of 5 reboots for 1
  or more users on the computer.

  It appears to happen to people with small HighDPI screens. In my case, it's 
13 inch at 2560x1600.
  Another example is 13 inch at 1080p -  
http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0

  unity:
Installed: 7.2.1+14.04.20140513-0ubuntu2
Candidate: 7.2.1+14.04.20140513-0ubuntu2
Version table:
   *** 7.2.1+14.04.20140513-0ubuntu2 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  unity-control-center:
Installed: 14.04.3+14.04.20140410-0ubuntu1
Candidate: 14.04.3+14.04.20140410-0ubuntu1
Version table:
   *** 14.04.3+14.04.20140410-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  intel iris pro graphics (lspci -vvv):

  00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) 
(prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device 011a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 66
Region 0: Memory at b000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at a000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 1000 [size=64]
Expansion ROM at unassigned [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1332947/+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 1223699] Re: klipper hangs after launch in Unity

2014-07-19 Thread Dmitriy Simplehuman Fedorov
Is is still actual for Ubuntu 14.04 x64 and 14.10 x64

** Description changed:

+ Still actual for Ubuntu 14.10 x64
+ 
  klipper hangs after launch in Unity.
  
  I am getting this output in terminal:
  
  klipper
  QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.
  QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.
  klipper(20151) Klipper::loadHistory: Failed to load history resource. 
Clipboard history cannot be read. :  History file does not exist
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: klipper 4:4.11.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0
  Uname: Linux 3.11.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Wed Sep 11 10:31:02 2013
  InstallationDate: Installed on 2013-07-31 (41 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  SourcePackage: kde-workspace
  UpgradeStatus: No upgrade log present (probably fresh install)

** Tags added: trusty utopic

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

Title:
  klipper hangs after launch in Unity

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Still actual for Ubuntu 14.10 x64

  klipper hangs after launch in Unity.

  I am getting this output in terminal:

  klipper
  QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.
  QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.
  klipper(20151) Klipper::loadHistory: Failed to load history resource. 
Clipboard history cannot be read. :  History file does not exist

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: klipper 4:4.11.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0
  Uname: Linux 3.11.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Wed Sep 11 10:31:02 2013
  InstallationDate: Installed on 2013-07-31 (41 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730)
  MarkForUpload: True
  SourcePackage: kde-workspace
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1223699/+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 1310200] Re: Indicators disappear at the panel (clementine, dropbox, skype etc)

2014-07-19 Thread Rabotyahoff
Skype and clementine are work fine.
Thank you.

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

Title:
  Indicators disappear at the panel (clementine, dropbox, skype etc)

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  Some indicators icons (such as skype, clementine, dropbox) disappear from 
panel when changing graphical state.

  [Test case]
  1. Run one of the affected software (i.e. skype)
  2. The skype icon should show in the unity panel
  3. Change your status in skype to something else (i.e. Away)
  4. The skype icon in the panel should change without disappearing

  [Regression potential]
  Nothing known, the icons database is reloaded for safety checks and this does 
nothing but updating the icons.

  

  
  Unconstant indicators (which are changig their graphical state during work of 
the app, for example skype, clemetine) disappears on the panel. They appear 
again if you click the mouse on th closest rightest indicator and pull it into 
left side or they appear after some time.

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr 20 12:26:14 2014
  InstallationDate: Installed on 2014-01-14 (95 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1310200/+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

2014-07-19 Thread Alberto Salvia Novella
** No longer affects: sublime-text (Ubuntu)

-- 
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 Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
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 MonoDevelop:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” 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.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  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/aptana-studio-installer/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

2014-07-19 Thread orions.belts1
Same config as #231, #234 steps seems to fix the problem. :)
 At least until the next update... !

-- 
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 Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
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 MonoDevelop:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” 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.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  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/aptana-studio-installer/+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 1344990] [NEW] Volume control jumps back and forth

2014-07-19 Thread Jussi Lind
Public bug reported:

Steps to reproduce:

1) Listen to music via Audacious
2) Open volume control from Unity's panel
3) Try to change the volume

What happens:

- The volume control doesn't follow mouse properly and jumps back and
forth

What should happen:

- The obvious thing

I believe this is regression as didn't notice anything weird in 13.10
with exactly same setup.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Sat Jul 19 19:51:32 2014
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug package-from-proposed 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/1344990

Title:
  Volume control jumps back and forth

Status in “unity” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1) Listen to music via Audacious
  2) Open volume control from Unity's panel
  3) Try to change the volume

  What happens:

  - The volume control doesn't follow mouse properly and jumps back and
  forth

  What should happen:

  - The obvious thing

  I believe this is regression as didn't notice anything weird in 13.10
  with exactly same setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Jul 19 19:51:32 2014
  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/1344990/+subscriptions

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


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

2014-07-19 Thread Yanpas
I suppose that problem is invisible for developers. Any ideas how to UP
topic?

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

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

Status in NetworkManager:
  New
Status in wicd:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Confirmed

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

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

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

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

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

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

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


[Dx-packages] [Bug 1331873] Re: the Ubuntu Help should be Ubuntu Kylin Help

2014-07-19 Thread Charles Kerr
** Changed in: indicator-session
   Status: In Progress = Fix Released

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

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

Title:
  the Ubuntu Help should be Ubuntu Kylin Help

Status in The Session Menu:
  Fix Released
Status in Ubuntu Kylin:
  Fix Committed
Status in “indicator-session” package in Ubuntu:
  Fix Released

Bug description:
  the Ubuntu Helpshould be Ubuntu Kuliy Help in the indicator ,since
  this is ubuntuKylin system.

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

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


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

2014-07-19 Thread Aron Xu
** Changed in: ubuntukylin
   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/845726

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

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

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

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

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

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