[Dx-packages] [Bug 1170366] Re: Broken handling of All-Day events

2014-04-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Broken handling of All-Day events

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

Bug description:
  All-day events are not being shown on the day they occur, when that
  date is selected in the calendar, and all-day events which occur on
  Fridays seem to not be appearing at all. Furthermore, it also seems
  that all-day events which span multiple days are also handled poorly,
  listed as starting at 00:00 on the first day, and not appearing on the
  other days.

  In Online Services we have a few calendars for hours, meetings, and
  for the client engineering subteam we have review days, which we
  specify in a calendar. I have these calendars subscribed to in
  Evolution. The all-day events used to appear on the day they occurred,
  so this seems to be a regression.

  Some examples:

  All-day events; To see who is on call for reviews today, I must select
  the previous day. The event for Friday however, does not show up at
  all, so selecting Thursday dates on the calendar do not show me any
  future all-day events that occur on the Friday.

  Multi-day all-day event: I will be on holiday May 06-10, but this does
  not show correctly in the events list when I select any of those days.
  Instead, when I select the preceding Sunday May 05 in the calendar,
  the event shows as starting Monday at 00:00, rather than being an all-
  day event which spans multiple days.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu Apr 18 10:01:40 2013
  InstallationDate: Installed on 2012-10-21 (178 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to raring on 2012-12-24 (114 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1170366/+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 1193360] Re: Can't type diacritics with AltGr+letter in Dash or HUD

2014-04-03 Thread QkiZ
HI, I'm also from Poland and this problem is appeared in 13.10 and
14.04. Just log off and log on again helps.

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

Title:
  Can't type diacritics with AltGr+letter in Dash or HUD

Status in One Hundred Papercuts:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  In the default polish keyboard layout, diacritics are written using
  AltGr (right Alt) + letter, i.e. AltGr+l gives ł. This is now broken
  in unity, Compose key still works, though.

  To test, english layout has ł under AltGr+w.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.0daily13.06.19-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Jun 21 14:55:27 2013
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1193360/+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 1290997] Re: click crashed with gi._glib.GError in run(): Child process exited with code 139

2014-04-03 Thread hermelo
I got this error at the system start. I am using Gnome instead of Unity
as it is reported in the bug description.

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

Title:
  click crashed with gi._glib.GError in run(): Child process exited with
  code 139

Status in “url-dispatcher” package in Ubuntu:
  Triaged

Bug description:
  after update and logout  login again

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: click 0.4.17.2
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 11 19:47:29 2014
  ExecutablePath: /usr/bin/click
  InstallationDate: Installed on 2013-12-11 (89 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131211)
  InterpreterPath: /usr/bin/python3.4
  ProcCmdline: /usr/bin/python3 /usr/bin/click hook run-user
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/click', 'hook', 'run-user']
  SourcePackage: click
  Title: click crashed with gi._glib.GError in run(): Child process exited with 
code 139
  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/url-dispatcher/+bug/1290997/+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


Re: [Dx-packages] [Bug 1236720] Re: unity-panel-service crashed with SIGABRT

2014-04-03 Thread TenLeftFingers
Thank you!


On Thu, Apr 3, 2014 at 2:56 AM, Stephen M. Webb
stephen.w...@canonical.comwrote:

 Fix Released in Unity Unity 7.2.0.

 ** Changed in: unity
Status: Fix Committed = Fix Released

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1237546).
 https://bugs.launchpad.net/bugs/1236720

 Title:
   unity-panel-service crashed with SIGABRT

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


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

Title:
  unity-panel-service crashed with SIGABRT

Status in The Application Menu:
  New
Status in Unity:
  Fix Released
Status in Unity 7.1 series:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Saucy:
  Confirmed

Bug description:
  Crash at login. 
  Ubuntu 13.10 daily build fresh install

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity-services 7.1.1+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Oct  8 09:17:33 2013
  Disassembly: = 0xb7782424:   Cannot access memory at address 0xb7782424
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/unity/unity-panel-service
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Technology Solutions Device [1734:10b0]
  InstallationDate: Installed on 2013-10-07 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta i386 (20131007)
  MachineType: FUJITSU SIEMENS AMILO Pi 1536
  MarkForUpload: True
  ProcCmdline: /usr/lib/unity/unity-panel-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=it
   XDG_RUNTIME_DIR=set
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic 
root=UUID=b2533600-b3b2-4a53-9e01-1734bcba7662 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: unity
  Stacktrace:
   #0  0xb7782424 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0xbfffb044
  StacktraceTop: ?? ()
  ThreadStacktrace:
   .
   Thread 4 (LWP 9353):
   #0  0xb7782424 in ?? ()
   No symbol table info available.
   Cannot access memory at address 0xac94108c
  Title: unity-panel-service crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/16/2007
  dmi.bios.vendor: FUJITSU SIEMENS
  dmi.bios.version: 1.23
  dmi.board.name: AMILO Pi 1536
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: Not Applicable
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS:bvr1.23:bd03/16/2007:svnFUJITSUSIEMENS:pnAMILOPi1536:pvrNotApplicable:rvnFUJITSUSIEMENS:rnAMILOPi1536:rvrNotApplicable:cvnFUJITSUSIEMENS:ct10:cvrNotApplicable:
  dmi.product.name: AMILO Pi 1536
  dmi.product.version: Not Applicable
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.10+13.10.20131004-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Tue Oct  8 09:17:38 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.3-3ubuntu1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-appmenu/+bug/1236720/+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 1301813] [NEW] Firefox pop-up window gets under upper panel and window buttons cannot be accessed

2014-04-03 Thread Walter Garcia-Fontes
Public bug reported:

Steps to reproduce:

1) Open A Firefox page that has a link that open a pop-up window
2) Click on the pop-up window

What should happen?
Window upper part should be accessible (close/max/min buttons and so on).

What happens?
The upper part of the window opens below the upper panel and the window is not 
maximized, the window cannot be managed before moving it down.

I attach a video with the issue. This is a setup with two screens, it
happens in both screens (when the pop-up opens in the second screen
after clicking a pop-up link in the main screen it also gets under the
Unity upper panel).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140402-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
Uname: Linux 3.13.0-21-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-17ubuntu2)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,decor,grid,snap,regex,mousepoll,place,imgpng,gnomecompat,move,unitymtgrabhandles,compiztoolbox,wall,vpswitch,animation,resize,fade,session,expo,workarounds,ezoom,scale,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Apr  3 10:37:06 2014
DistUpgraded: 2014-03-07 13:54:13,979 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G84GL [Quadro FX 1700] [10de:040f] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation Device [10de:049a]
InstallationDate: Installed on 2010-10-25 (1255 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
MachineType: Dell Inc. Precision WorkStation T3400
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic 
root=UUID=dadc68cb-c217-4aef-a751-ba0b61137c4a ro quiet splash
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-03-07 (26 days ago)
dmi.bios.date: 06/04/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0TP412
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd06/04/2009:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T3400
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11+14.04.20140328-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-4ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
9.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
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-1ubuntu3
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: Thu Apr  3 08:31:46 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputgspca_zc3xx  KEYBOARD, id 8
 inputDell Dell USB Keyboard KEYBOARD, id 9
 inputLogitech USB Optical Mouse MOUSE, id 10
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.0-1ubuntu7

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


** Tags: amd64 apport-bug compiz-0.9 trusty 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/1301813

Title:
  Firefox pop-up window gets under upper panel and window buttons cannot
  be accessed

Status in “unity” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1) Open A Firefox page that has a link that open a pop-up window
  2) Click on the pop-up window

  What should happen?
  Window upper part should be accessible (close/max/min buttons and so on).

  What happens?
  The upper part of the window opens below the upper panel and the window is 
not maximized, the window cannot be managed before moving it down.

  I attach a video with the issue. This is a setup with two screens, it
  happens in both screens (when the pop-up opens in the second screen
  after clicking a pop-up link in the main screen it also gets under the
  

[Dx-packages] [Bug 1301812] Re: compiz crashed with SIGSEGV in FT_Load_Glyph()

2014-04-03 Thread Apport retracing service
*** This bug is a duplicate of bug 1199571 ***
https://bugs.launchpad.net/bugs/1199571

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1301812/+attachment/4062459/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1301812/+attachment/4062461/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1301812/+attachment/4062463/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1301812/+attachment/4062464/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1301812/+attachment/4062465/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1301812/+attachment/4062466/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1301812/+attachment/4062467/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1199571
   compiz crashed with SIGSEGV in af_latin_hints_compute_edges()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in FT_Load_Glyph()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Crashed directly after typing one character in the dash

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
  Uname: Linux 3.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  3 10:38:35 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-03-31 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f18ec206860:mov%rdx,0x10(%rax)
   PC (0x7f18ec206860) ok
   source %rdx ok
   destination 0x10(%rax) (0x0010) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing 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: 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/1301812/+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 1193360] Re: Can't type diacritics with AltGr+letter in Dash or HUD

2014-04-03 Thread Michał Sawicz
Actually this seems to be fixed for me in current 14.04:

⟫ LANG=C apt-cache policy unity
unity:
  Installed: 7.2.0+14.04.20140402-0ubuntu1
  Candidate: 7.2.0+14.04.20140402-0ubuntu1
  Version table:
 *** 7.2.0+14.04.20140402-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  Can't type diacritics with AltGr+letter in Dash or HUD

Status in One Hundred Papercuts:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  In the default polish keyboard layout, diacritics are written using
  AltGr (right Alt) + letter, i.e. AltGr+l gives ł. This is now broken
  in unity, Compose key still works, though.

  To test, english layout has ł under AltGr+w.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.0daily13.06.19-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Jun 21 14:55:27 2013
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1193360/+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 1301813] Re: Firefox pop-up window gets under upper panel and window buttons cannot be accessed

2014-04-03 Thread Walter Garcia-Fontes
Video with the issue

** Attachment added: out.ogv
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1301813/+attachment/4062496/+files/out.ogv

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

Title:
  Firefox pop-up window gets under upper panel and window buttons cannot
  be accessed

Status in “unity” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1) Open A Firefox page that has a link that open a pop-up window
  2) Click on the pop-up window

  What should happen?
  Window upper part should be accessible (close/max/min buttons and so on).

  What happens?
  The upper part of the window opens below the upper panel and the window is 
not maximized, the window cannot be managed before moving it down.

  I attach a video with the issue. This is a setup with two screens, it
  happens in both screens (when the pop-up opens in the second screen
  after clicking a pop-up link in the main screen it also gets under the
  Unity upper panel).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
  Uname: Linux 3.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-17ubuntu2)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,grid,snap,regex,mousepoll,place,imgpng,gnomecompat,move,unitymtgrabhandles,compiztoolbox,wall,vpswitch,animation,resize,fade,session,expo,workarounds,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr  3 10:37:06 2014
  DistUpgraded: 2014-03-07 13:54:13,979 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 1700] [10de:040f] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:049a]
  InstallationDate: Installed on 2010-10-25 (1255 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  MachineType: Dell Inc. Precision WorkStation T3400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic 
root=UUID=dadc68cb-c217-4aef-a751-ba0b61137c4a ro quiet splash
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-07 (26 days ago)
  dmi.bios.date: 06/04/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0TP412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd06/04/2009:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3400
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140328-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-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
9.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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-1ubuntu3
  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: Thu Apr  3 08:31:46 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputgspca_zc3xx  KEYBOARD, id 8
   inputDell Dell USB Keyboard KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1301813/+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-04-03 Thread Norbert
@Stephen M. Webb (bregma) 
I do not think that this bug is fixed in Unity since the dependent bug 1280759 
(Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - 
shortcuts are defined via keyboard layout, not the keys) is not fixed.
So bug 1226962 is not fixed in Unity.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/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 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:
  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 1301455] Re: Remove src+bin packages due to U1 shutdown

2014-04-03 Thread Sebastien Bacher
** Changed in: magicicada (Ubuntu)
   Importance: Undecided = High

** Changed in: ubuntuone-storage-protocol (Ubuntu)
   Importance: Undecided = High

** Changed in: ubuntuone-file-storage-api (Ubuntu)
   Importance: Undecided = High

** Changed in: indicator-sync (Ubuntu)
   Importance: Undecided = High

** Changed in: ubuntuone-client (Ubuntu)
   Importance: Undecided = High

** Changed in: ubuntuone-control-panel (Ubuntu)
   Importance: Undecided = High

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

Title:
  Remove src+bin packages due to U1 shutdown

Status in “indicator-sync” package in Ubuntu:
  Fix Released
Status in “magicicada” package in Ubuntu:
  Fix Released
Status in “ubuntuone-client” package in Ubuntu:
  Fix Released
Status in “ubuntuone-control-panel” package in Ubuntu:
  Confirmed
Status in “ubuntuone-file-storage-api” package in Ubuntu:
  Fix Released
Status in “ubuntuone-storage-protocol” package in Ubuntu:
  Fix Released

Bug description:
  Remove src+bin packages due to U1 shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sync/+bug/1301455/+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: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys

2014-04-03 Thread Norbert
I have tested Ubuntu 12.04 about this bug. I can use Super+A/F/M/T/S/W
on qwerty and йцукен (english and russian) layouts.

So this bug is a regression which should be fixed before Ubuntu 14.04
final release.

-- 
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:
  Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in
  Trusty - shortcuts are defined via keyboard layout, not the keys

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

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/unity-settings-daemon/+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 1280759] Re: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys

2014-04-03 Thread Norbert
The comment is for comparison between Ubuntu 12.04 and 14.04.

Below is a text table for Unity shortcuts, non-latin layout selected.
 12.04 14.04
Super+T+ +
Super+A+ -
Super+F+ -
Super+M+ -
Super+C   n/a-
Super+V+ -
Super+L   n/a+
Super+W+ +
Super+S+ +

So Super+T/L/W/S work on Ubuntu 14.04 and Super+A/F/M/C/V do not work on
Ubuntu 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/1280759

Title:
  Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in
  Trusty - shortcuts are defined via keyboard layout, not the keys

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

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/unity-settings-daemon/+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 1301835] [NEW] unity's new window decoration does not follow any thing from org.compiz.gwd

2014-04-03 Thread Mark Enriquez
Public bug reported:

I usually change the title bars' transparency on org.compiz.gwd
specifically on metacity-theme-acitive-opacity and metacity-theme-
acitive-opacity. After some updates on ubuntu trusty, this modification
does not work. Changing any of these values doesn't change its
transparency. It does work on other de's with compiz enabled like xfce.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
Uname: Linux 3.13.2-pf-pf x86_64
ApportVersion: 2.14-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]
CurrentDesktop: Unity
Date: Thu Apr  3 09:32:32 2014
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 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/1301835

Title:
  unity's new window decoration does not follow any thing from
  org.compiz.gwd

Status in “unity” package in Ubuntu:
  New

Bug description:
  I usually change the title bars' transparency on org.compiz.gwd
  specifically on metacity-theme-acitive-opacity and metacity-theme-
  acitive-opacity. After some updates on ubuntu trusty, this
  modification does not work. Changing any of these values doesn't
  change its transparency. It does work on other de's with compiz
  enabled like xfce.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  Uname: Linux 3.13.2-pf-pf x86_64
  ApportVersion: 2.14-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]
  CurrentDesktop: Unity
  Date: Thu Apr  3 09:32: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/1301835/+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 1295981] Re: unity-panel-service crashed with SIGSEGV in gtk_menu_tracker_remove_items()

2014-04-03 Thread Michael Blennerhassett
Was able to reproduce this.  The app needs to stop responding before it
creates its menus (say for example shotwell, when trying to import
photos from a camera)

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

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

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

Bug description:
  1. get an app to stop responding  (ie the window gets dimmed)
  2. wait for it to recover
  3. notice that it has no menus now (is there a bug somewhere for that?)
  4. close the app
  5. crash

  (Note: I think this is chain of events, I haven't been able to
  reproduce)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-services 7.1.2+14.04.20140320.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Mar 22 19:09:26 2014
  ExecutablePath: /usr/lib/unity/unity-panel-service
  InstallationDate: Installed on 2013-06-22 (273 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621)
  ProcCmdline: /usr/lib/unity/unity-panel-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=set
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff2bf1b3ffc:mov(%rdi),%rbx
   PC (0x7ff2bf1b3ffc) ok
   source (%rdi) (0x) not located in a known VMA region (needed 
readable region)!
   destination %rbx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.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
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: Upgraded to trusty on 2013-12-05 (106 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

2014-04-03 Thread Jens
It works here now (in Virtualbox) - so I think it is fixed.

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

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

Status in “unity” package in Ubuntu:
  Fix Released

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 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager

2014-04-03 Thread Martin Pitt
I think we should completely disable powerbtn.sh if logind is running;
that's much safer than trying to cover all session managers, and much
more correct too as logind itself handles the power button unless a
session manager inhibits it.

** Changed in: acpid (Ubuntu)
 Assignee: (unassigned) = Martin Pitt (pitti)

** Summary changed:

- Pressing power button turns off the PC ignoring the presence of another 
session manager
+ powerbtn.sh conflicts with logind

** Changed in: acpid (Ubuntu)
Milestone: None = ubuntu-14.04

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

Title:
  powerbtn.sh conflicts with logind

Status in “acpid” package in Ubuntu:
  Triaged
Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd-shim” package in Ubuntu:
  Invalid

Bug description:
  In saucy the PC powers down as soon as I press the power button, it
  seems that systemd is calling poweroff, but I'm not sure if it's
  doing that in response of some other event (i.e. as callback of a dbus
  call):

  root  4998  0.0  0.0 177932  2104 ?Sl   20:41   0:00 
/usr/lib/x86_64-linux-gnu/systemd-shim
  root  5012  0.0  0.0   4440   624 ?S20:41   0:00  \_ sh -c 
/sbin/poweroff
  root  5013  0.0  0.0   4440   628 ?S20:41   0:00  \_ 
/bin/sh /sbin/shutdown -h -P now

  In any case the caller or systemd itself should be aware that there's
  a session-manager running and that it shouldn't actually directly
  power off the system then.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+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 1299596] Re: The content of the display are briefly shown when resuming from sleep, before lock screen is displayed

2014-04-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  The content of the display are briefly shown when resuming from sleep,
  before lock screen is displayed

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I attach a video showing the problem.

  As you can see, when suspending the PC the transition between the
  desktop and the lock screen is no finished before suspending. It seems
  the process is finished on resume. The result is that the content of
  the desktop are briefly shown before the lock screen is displayed.

  I think this is a rather serious issue, as the content of the PC can
  be seen by non authorized people when one lefts the PC suspended and
  password protected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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 Mar 29 18:37:41 2014
  DistUpgraded: 2014-03-28 16:07:01,468 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.6, 3.13.0-19-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-20-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1436]
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobility Radeon HD 5650 [103c:1436]
  InstallationDate: Installed on 2013-09-23 (187 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130923.1)
  MachineType: Hewlett-Packard HP ENVY 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=ca667e96-4f50-4077-8344-88c49b0769a2 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-28 (1 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1436
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 59.24
  dmi.chassis.asset.tag: CNU03538DZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.26:bd12/01/2011:svnHewlett-Packard:pnHPENVY14NotebookPC:pvr0492102419162:rvnHewlett-Packard:rn1436:rvr59.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 14 Notebook PC
  dmi.product.version: 0492102419162
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140328-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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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-1ubuntu3
  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 Mar 29 14:23:06 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id3593 
   vendor LCD
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1299596/+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 1301655] Re: Buttons on the Shutdown/logout dialogs lacks click feedback

2014-04-03 Thread Stephen M. Webb
** Changed in: unity (Ubuntu)
   Status: New = Triaged

** Changed in: unity (Ubuntu)
   Importance: Undecided = Medium

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

** Changed in: unity
   Status: New = Triaged

** Changed in: unity
   Importance: Undecided = Medium

** Changed in: unity
Milestone: None = 7.2.1

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

Title:
  Buttons on the Shutdown/logout dialogs lacks click feedback

Status in One Hundred Papercuts:
  New
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  On the Shutdown and the Logout modal dialogs, buttons have a rollover effect, 
but they don't have any feedback effect when clicking or touching them.
  Sometimes you have a delay until the system visually starts the shutdown or 
logout action, and as an user, the overall impression is the dialog being 
unresponsive.

  Just a small feedback like the button flashing a couple of times could
  be welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140321-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Apr  2 22:10:19 2014
  LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1301655/+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 1300864] Re: Duplicate webapps launcher confuses bamf

2014-04-03 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/trusty-proposed/unity-webapps-qml

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

Title:
  Duplicate webapps launcher confuses bamf

Status in BAMF Application Matching Framework:
  New
Status in WebApps: libunity:
  Fix Committed
Status in Unity WebApps QML component:
  New
Status in “libunity-webapps” package in Ubuntu:
  In Progress
Status in “unity-webapps-qml” package in Ubuntu:
  New

Bug description:
  Even with the recent fixes to bamf, I can still be in cases where my
  webapp launcher does not associate correctly on the launcher.

  It happens for no particular webapp. However it stops occuring as soon
  as I suppress the duplicate desktop file we generate in
  ~/.local/share/applications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1300864/+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 1300864] Re: Duplicate webapps launcher confuses bamf

2014-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-webapps-qml -
0.1+14.04.20140401.1-0ubuntu1

---
unity-webapps-qml (0.1+14.04.20140401.1-0ubuntu1) trusty; urgency=low

  [ Alexandre Abreu ]
  * Add some missing files striclty for doc generation for the runtime-
api
  * There is currently an issue on Ubuntu Desktop with webapps running
in the container and bamf/unity that when a local desktop file
exists (and a webapp icon has been pinned to the launcher through
its global /usr/share desktop file), the webapp icons are duplicated
in the launcher. Various fixes have been made to mitigate the issue
in bamf but it seems to still be around. This is voluntarily
discarded for now and left around to get to the bottom of the issue
in a timely fashion. (LP: #1300864)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Tue, 01 Apr 2014 
18:28:51 +

** Changed in: unity-webapps-qml (Ubuntu)
   Status: New = Fix Released

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

Title:
  Duplicate webapps launcher confuses bamf

Status in BAMF Application Matching Framework:
  New
Status in WebApps: libunity:
  Fix Committed
Status in Unity WebApps QML component:
  New
Status in “libunity-webapps” package in Ubuntu:
  In Progress
Status in “unity-webapps-qml” package in Ubuntu:
  Fix Released

Bug description:
  Even with the recent fixes to bamf, I can still be in cases where my
  webapp launcher does not associate correctly on the launcher.

  It happens for no particular webapp. However it stops occuring as soon
  as I suppress the duplicate desktop file we generate in
  ~/.local/share/applications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1300864/+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 1292446] Re: lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume

2014-04-03 Thread Adolfo Jayme
** Tags added: rls-t-incoming

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

Title:
  lockscreen: on autolock on suspend the fade does not complete before
  suspend leaving desktop partially visible for a short period on resume

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

Bug description:
  When auto-locking as part of a suspend operation the lock screen still
  fades to opaque, this takes seconds and mid fade the suspend occurs.
  This means that on waking the machine the fade is still occurring and
  the desktop is partially visible potentially exposing information
  protected by the lock.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140313-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Mar 14 10:02:52 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-06-20 (266 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1292446/+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 1301655] Re: Buttons on the Shutdown/logout dialogs lacks click feedback

2014-04-03 Thread Dario Ruellan
** Changed in: hundredpapercuts
   Importance: Undecided = Medium

** Changed in: hundredpapercuts
   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/1301655

Title:
  Buttons on the Shutdown/logout dialogs lacks click feedback

Status in One Hundred Papercuts:
  Confirmed
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  On the Shutdown and the Logout modal dialogs, buttons have a rollover effect, 
but they don't have any feedback effect when clicking or touching them.
  Sometimes you have a delay until the system visually starts the shutdown or 
logout action, and as an user, the overall impression is the dialog being 
unresponsive.

  Just a small feedback like the button flashing a couple of times could
  be welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140321-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Apr  2 22:10:19 2014
  LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1301655/+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 1285614] Re: Mouse click offset

2014-04-03 Thread Lucas Silveira Melo
Hello guys the problem persists.
there is no solution?

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

Title:
  Mouse click offset

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

Bug description:
  In trusty, I have seen an old bug coming back: my mouse clicks suffer
  from an offset compared to what I see on screen.

  This is very similar to 
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/772612 but happening now 
in Trusty.
  This seems to happen after compiz somehow restarts spontaneously...

  I am conscious this is not a very usable bug report, but I have seen
  this happening 3 or 4 times in the last 2 days on my system, so I
  though it was worth reporting...

  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: Thu Feb 27 12:12:41 2014
  InstallationDate: Installed on 2013-02-16 (375 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1285614/+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 1293548] Re: Indicator disappears when switching to non default layout

2014-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package libindicator -
12.10.2+14.04.20140402-0ubuntu1

---
libindicator (12.10.2+14.04.20140402-0ubuntu1) trusty; urgency=low

  [ William Hua ]
  * Don't load using the icon info structure if it's a GBytesIcon. (LP:
#1293548)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Wed, 02 Apr 2014 
14:50:52 +

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

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

Title:
  Indicator disappears when switching to non default layout

Status in Libindicator:
  New
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed
Status in “libindicator” package in Ubuntu:
  Fix Released

Bug description:
  I am experiencing this problem with a non-default icon theme (Numix
  icons).

  I have two layouts: English and Latin American. When I switch layouts
  (with Shift+Shift_R) from English to Spanish, the indicator
  disappears. When I switch back to English, the indicator reappears.

  I've checked with adding a third layout, but the indicator won't show
  unless the layout is set to English (my default layout).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-keyboard 0.0.0+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 17 08:31:59 2014
  InstallationDate: Installed on 2014-03-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316)
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libindicator/+bug/1293548/+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 1295413] Re: new unity lock screen doesn't appear after resume

2014-04-03 Thread Lázaro Zarê
James Troup
Same here!
Sometimes I see the Gnome-Lockscreen + Unity lockscreen too

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

Title:
  new unity lock screen doesn't appear after resume

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

Bug description:
  New lock screen is awesome.  Unfortunately, for me, whenever I resume,
  I get a blank screen.  I can switch VTs but switching to a text VT and
  back to X doesn't help.  If I unplug and/or re-plug my external
  display, I'll sometimes get a black screen with a mouse, sometimes a
  lock screen that doesn't appear to be accepting keyboard input.

  This has happened twice now, running current trusty and I've ended up
  rebooting each time.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  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]
  CurrentDesktop: Unity
  Date: Thu Mar 20 23:26:52 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-20 (882 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-19 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1295413/+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 1300916] Re: Shutting down Ubuntu One file services

2014-04-03 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu-docs

-- 
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, dx-packages
https://bugs.launchpad.net/bugs/1300916

Title:
  Shutting down Ubuntu One file services

Status in “deja-dup” package in Ubuntu:
  Fix Released
Status in “indicator-applet” package in Ubuntu:
  Fix Released
Status in “thunderbird” package in Ubuntu:
  New
Status in “ubiquity” package in Ubuntu:
  Fix Committed
Status in “ubiquity-slideshow-ubuntu” package in Ubuntu:
  Fix Released
Status in “ubuntu-docs” package in Ubuntu:
  Fix Committed
Status in “ubuntu-gnome-meta” package in Ubuntu:
  Fix Released
Status in “ubuntu-meta” package in Ubuntu:
  Fix Released
Status in “ubuntu-sso-client” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  In Progress
Status in “webapps-applications” package in Ubuntu:
  Fix Released
Status in “deja-dup” source package in Precise:
  New
Status in “indicator-applet” source package in Precise:
  New
Status in “thunderbird” source package in Precise:
  New
Status in “ubiquity” source package in Precise:
  Invalid
Status in “ubiquity-slideshow-ubuntu” source package in Precise:
  New
Status in “ubuntu-docs” source package in Precise:
  New
Status in “ubuntu-gnome-meta” source package in Precise:
  New
Status in “ubuntu-meta” source package in Precise:
  New
Status in “ubuntu-sso-client” source package in Precise:
  New
Status in “unity” source package in Precise:
  New
Status in “webapps-applications” source package in Precise:
  New
Status in “deja-dup” source package in Trusty:
  Fix Released
Status in “indicator-applet” source package in Trusty:
  Fix Released
Status in “thunderbird” source package in Trusty:
  New
Status in “ubiquity” source package in Trusty:
  Fix Committed
Status in “ubiquity-slideshow-ubuntu” source package in Trusty:
  Fix Released
Status in “ubuntu-docs” source package in Trusty:
  Fix Committed
Status in “ubuntu-gnome-meta” source package in Trusty:
  Fix Released
Status in “ubuntu-meta” source package in Trusty:
  Fix Released
Status in “ubuntu-sso-client” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  In Progress
Status in “webapps-applications” source package in Trusty:
  Fix Released

Bug description:
  Shutting down Ubuntu One file services

  http://blog.canonical.com/2014/04/02/shutting-down-ubuntu-one-file-
  services/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1300916/+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 1300916] Re: Shutting down Ubuntu One file services

2014-04-03 Thread Gunnar Hjalmarsson
** Changed in: ubuntu-docs (Ubuntu Trusty)
   Status: In Progress = Fix Committed

-- 
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, dx-packages
https://bugs.launchpad.net/bugs/1300916

Title:
  Shutting down Ubuntu One file services

Status in “deja-dup” package in Ubuntu:
  Fix Released
Status in “indicator-applet” package in Ubuntu:
  Fix Released
Status in “thunderbird” package in Ubuntu:
  New
Status in “ubiquity” package in Ubuntu:
  Fix Committed
Status in “ubiquity-slideshow-ubuntu” package in Ubuntu:
  Fix Released
Status in “ubuntu-docs” package in Ubuntu:
  Fix Committed
Status in “ubuntu-gnome-meta” package in Ubuntu:
  Fix Released
Status in “ubuntu-meta” package in Ubuntu:
  Fix Released
Status in “ubuntu-sso-client” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  In Progress
Status in “webapps-applications” package in Ubuntu:
  Fix Released
Status in “deja-dup” source package in Precise:
  New
Status in “indicator-applet” source package in Precise:
  New
Status in “thunderbird” source package in Precise:
  New
Status in “ubiquity” source package in Precise:
  Invalid
Status in “ubiquity-slideshow-ubuntu” source package in Precise:
  New
Status in “ubuntu-docs” source package in Precise:
  New
Status in “ubuntu-gnome-meta” source package in Precise:
  New
Status in “ubuntu-meta” source package in Precise:
  New
Status in “ubuntu-sso-client” source package in Precise:
  New
Status in “unity” source package in Precise:
  New
Status in “webapps-applications” source package in Precise:
  New
Status in “deja-dup” source package in Trusty:
  Fix Released
Status in “indicator-applet” source package in Trusty:
  Fix Released
Status in “thunderbird” source package in Trusty:
  New
Status in “ubiquity” source package in Trusty:
  Fix Committed
Status in “ubiquity-slideshow-ubuntu” source package in Trusty:
  Fix Released
Status in “ubuntu-docs” source package in Trusty:
  Fix Committed
Status in “ubuntu-gnome-meta” source package in Trusty:
  Fix Released
Status in “ubuntu-meta” source package in Trusty:
  Fix Released
Status in “ubuntu-sso-client” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  In Progress
Status in “webapps-applications” source package in Trusty:
  Fix Released

Bug description:
  Shutting down Ubuntu One file services

  http://blog.canonical.com/2014/04/02/shutting-down-ubuntu-one-file-
  services/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1300916/+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: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys

2014-04-03 Thread Masoud Pourmoosa
With Persian layout in 14.04, I can confirm your last comment:
Super+T/L/W/S work, Super+A/F/M/C/V do not work. Great job.

-- 
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:
  Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in
  Trusty - shortcuts are defined via keyboard layout, not the keys

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

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/unity-settings-daemon/+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 1285614] Re: Mouse click offset

2014-04-03 Thread Christopher Townsend
Sorry, I cannot reproduce this issue.  Could you please provide exact
steps on how to reproduce?

Also, what graphics card and driver are being used?

** Changed in: unity
   Status: New = Incomplete

** Changed in: unity (Ubuntu)
   Status: Triaged = Incomplete

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

Title:
  Mouse click offset

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

Bug description:
  In trusty, I have seen an old bug coming back: my mouse clicks suffer
  from an offset compared to what I see on screen.

  This is very similar to 
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/772612 but happening now 
in Trusty.
  This seems to happen after compiz somehow restarts spontaneously...

  I am conscious this is not a very usable bug report, but I have seen
  this happening 3 or 4 times in the last 2 days on my system, so I
  though it was worth reporting...

  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: Thu Feb 27 12:12:41 2014
  InstallationDate: Installed on 2013-02-16 (375 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1285614/+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 1201180] Re: powerbtn.sh conflicts with logind

2014-04-03 Thread Martin Pitt
** Changed in: acpid (Ubuntu)
   Status: Triaged = Fix Committed

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

Title:
  powerbtn.sh conflicts with logind

Status in “acpid” package in Ubuntu:
  Fix Committed
Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd-shim” package in Ubuntu:
  Invalid

Bug description:
  In saucy the PC powers down as soon as I press the power button, it
  seems that systemd is calling poweroff, but I'm not sure if it's
  doing that in response of some other event (i.e. as callback of a dbus
  call):

  root  4998  0.0  0.0 177932  2104 ?Sl   20:41   0:00 
/usr/lib/x86_64-linux-gnu/systemd-shim
  root  5012  0.0  0.0   4440   624 ?S20:41   0:00  \_ sh -c 
/sbin/poweroff
  root  5013  0.0  0.0   4440   628 ?S20:41   0:00  \_ 
/bin/sh /sbin/shutdown -h -P now

  In any case the caller or systemd itself should be aware that there's
  a session-manager running and that it shouldn't actually directly
  power off the system then.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+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 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked

2014-04-03 Thread Rodney Dawes
I'm pretty sure this is unity-greeter and has nothing to do with unity
itself.

** Package changed: unity (Ubuntu) = unity-greeter (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/1292451

Title:
  screensaver re-locks itself after unlocking if the configured screen-
  off timer goes off while screen is locked

Status in Unity:
  New
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed
Status in “unity-greeter” package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Set screen-off timeout to 1 minute
  2. Configure screen to lock immediately when screen goes off.
  3. Lock screen manually (Ctrl+Alt+L)
  4. Wait for 1 minute
  5. Notice that screen doesn't turn off
  6. Unlock screen
  7. Wait a couple of seconds (~10 or so)
  8. Notice that screen re-locks itself.
  9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this 
time.

  There are two bugs described here: 
  1. Screen does not shut off if the screen is locked manually before the idle 
timer (see step 5).
  2. Screen re-locks itself after unlocking if the idle timer goes off while 
the screen is locked (see step 7).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu11
  Uname: Linux 3.13.4-hyper1 x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 14 18:19:26 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1292451/+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 1300916] Re: Shutting down Ubuntu One file services

2014-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.2.0+14.04.20140403-0ubuntu1

---
unity (7.2.0+14.04.20140403-0ubuntu1) trusty; urgency=low

  [ Stephen M. Webb ]
  * remove libsyncindicator from services/panel-service.c

  [ Dimitri John Ledkov ]
  * Drop U1 default shortcuts  indicator-sync recommendation. (LP:
#1300916) (LP: #1300916)

  [ Marco Trevisan (Treviño) ]
  * Launcher: hide the launcher window when in auto-hide mode if it's
not presented (LP: #1301394)
  * ApplicationLauncherIcon: recompute pips when the screen geometry
changes (LP: #1024101)
  * UnityScreen: reset decoration::DataPool on destruction, otherwise we
won't have a valid screen ptr (LP: #1291243)
  * DecorationsGrabEdge: Only perform tookit actions on right-click (LP:
#1301459)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 03 Apr 2014 
11:10:36 +

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

-- 
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, dx-packages
https://bugs.launchpad.net/bugs/1300916

Title:
  Shutting down Ubuntu One file services

Status in “deja-dup” package in Ubuntu:
  Fix Released
Status in “indicator-applet” package in Ubuntu:
  Fix Released
Status in “thunderbird” package in Ubuntu:
  New
Status in “ubiquity” package in Ubuntu:
  Fix Committed
Status in “ubiquity-slideshow-ubuntu” package in Ubuntu:
  Fix Released
Status in “ubuntu-docs” package in Ubuntu:
  Fix Committed
Status in “ubuntu-gnome-meta” package in Ubuntu:
  Fix Released
Status in “ubuntu-meta” package in Ubuntu:
  Fix Released
Status in “ubuntu-sso-client” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “webapps-applications” package in Ubuntu:
  Fix Released
Status in “deja-dup” source package in Precise:
  New
Status in “indicator-applet” source package in Precise:
  New
Status in “thunderbird” source package in Precise:
  New
Status in “ubiquity” source package in Precise:
  Invalid
Status in “ubiquity-slideshow-ubuntu” source package in Precise:
  New
Status in “ubuntu-docs” source package in Precise:
  New
Status in “ubuntu-gnome-meta” source package in Precise:
  New
Status in “ubuntu-meta” source package in Precise:
  New
Status in “ubuntu-sso-client” source package in Precise:
  New
Status in “unity” source package in Precise:
  New
Status in “webapps-applications” source package in Precise:
  New
Status in “deja-dup” source package in Trusty:
  Fix Released
Status in “indicator-applet” source package in Trusty:
  Fix Released
Status in “thunderbird” source package in Trusty:
  New
Status in “ubiquity” source package in Trusty:
  Fix Committed
Status in “ubiquity-slideshow-ubuntu” source package in Trusty:
  Fix Released
Status in “ubuntu-docs” source package in Trusty:
  Fix Committed
Status in “ubuntu-gnome-meta” source package in Trusty:
  Fix Released
Status in “ubuntu-meta” source package in Trusty:
  Fix Released
Status in “ubuntu-sso-client” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Released
Status in “webapps-applications” source package in Trusty:
  Fix Released

Bug description:
  Shutting down Ubuntu One file services

  http://blog.canonical.com/2014/04/02/shutting-down-ubuntu-one-file-
  services/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1300916/+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 1291243] Re: compiz crashed with SIGSEGV in TfpTexture::releaseTexImage()

2014-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.2.0+14.04.20140403-0ubuntu1

---
unity (7.2.0+14.04.20140403-0ubuntu1) trusty; urgency=low

  [ Stephen M. Webb ]
  * remove libsyncindicator from services/panel-service.c

  [ Dimitri John Ledkov ]
  * Drop U1 default shortcuts  indicator-sync recommendation. (LP:
#1300916) (LP: #1300916)

  [ Marco Trevisan (Treviño) ]
  * Launcher: hide the launcher window when in auto-hide mode if it's
not presented (LP: #1301394)
  * ApplicationLauncherIcon: recompute pips when the screen geometry
changes (LP: #1024101)
  * UnityScreen: reset decoration::DataPool on destruction, otherwise we
won't have a valid screen ptr (LP: #1291243)
  * DecorationsGrabEdge: Only perform tookit actions on right-click (LP:
#1301459)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 03 Apr 2014 
11:10:36 +

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

Title:
  compiz crashed with SIGSEGV in TfpTexture::releaseTexImage()

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

Bug description:
  Spread wasn't working anymore, so I performed compiz --replace, then
  shut the terminal again, then this error came up.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 12 09:50:25 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2011-10-08 (885 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111007.1)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f20ec8d596e 
_ZN10TfpTexture15releaseTexImageEv+30:mov(%rdi),%rax
   PC (0x7f20ec8d596e) ok
   source (%rdi) (0x) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   TfpTexture::releaseTexImage() () from /usr/lib/compiz/libopengl.so
   TfpTexture::~TfpTexture() () from /usr/lib/compiz/libopengl.so
   TfpTexture::~TfpTexture() () from /usr/lib/compiz/libopengl.so
   GLTexture::List::clear() () from /usr/lib/compiz/libopengl.so
   unity::PluginAdapter::InitiateScale(std::string const, int) () from 
/usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in TfpTexture::releaseTexImage()
  UpgradeStatus: Upgraded to trusty on 2014-03-09 (2 days ago)
  UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare saned 
scanner

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1291243/+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 1301459] Re: It's possible to maximize a window by quickly left-right clicking

2014-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.2.0+14.04.20140403-0ubuntu1

---
unity (7.2.0+14.04.20140403-0ubuntu1) trusty; urgency=low

  [ Stephen M. Webb ]
  * remove libsyncindicator from services/panel-service.c

  [ Dimitri John Ledkov ]
  * Drop U1 default shortcuts  indicator-sync recommendation. (LP:
#1300916) (LP: #1300916)

  [ Marco Trevisan (Treviño) ]
  * Launcher: hide the launcher window when in auto-hide mode if it's
not presented (LP: #1301394)
  * ApplicationLauncherIcon: recompute pips when the screen geometry
changes (LP: #1024101)
  * UnityScreen: reset decoration::DataPool on destruction, otherwise we
won't have a valid screen ptr (LP: #1291243)
  * DecorationsGrabEdge: Only perform tookit actions on right-click (LP:
#1301459)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 03 Apr 2014 
11:10:36 +

** Changed in: unity (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/1301459

Title:
  It's possible to maximize a window by quickly left-right clicking

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

Bug description:
  - Open restored window
  - Quickly left and then right click on it

  Expected behavior:
   - The window menu opens, and the window stays restored

  Actuual behavior:
   - The window menu opens, but the window gets maximized.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1301459/+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 1301394] Re: Launcher damange the left-monitor area also if it's hidden

2014-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.2.0+14.04.20140403-0ubuntu1

---
unity (7.2.0+14.04.20140403-0ubuntu1) trusty; urgency=low

  [ Stephen M. Webb ]
  * remove libsyncindicator from services/panel-service.c

  [ Dimitri John Ledkov ]
  * Drop U1 default shortcuts  indicator-sync recommendation. (LP:
#1300916) (LP: #1300916)

  [ Marco Trevisan (Treviño) ]
  * Launcher: hide the launcher window when in auto-hide mode if it's
not presented (LP: #1301394)
  * ApplicationLauncherIcon: recompute pips when the screen geometry
changes (LP: #1024101)
  * UnityScreen: reset decoration::DataPool on destruction, otherwise we
won't have a valid screen ptr (LP: #1291243)
  * DecorationsGrabEdge: Only perform tookit actions on right-click (LP:
#1301459)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 03 Apr 2014 
11:10:36 +

** Changed in: unity (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/1301394

Title:
  Launcher damange the left-monitor area also if it's hidden

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

Bug description:
  When in auto-hide mode the launcher damages the area that it would
  fill when shown, also when hidden.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1301394/+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 1024101] Re: Pips show incorrect status after attaching or detatching second screen

2014-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.2.0+14.04.20140403-0ubuntu1

---
unity (7.2.0+14.04.20140403-0ubuntu1) trusty; urgency=low

  [ Stephen M. Webb ]
  * remove libsyncindicator from services/panel-service.c

  [ Dimitri John Ledkov ]
  * Drop U1 default shortcuts  indicator-sync recommendation. (LP:
#1300916) (LP: #1300916)

  [ Marco Trevisan (Treviño) ]
  * Launcher: hide the launcher window when in auto-hide mode if it's
not presented (LP: #1301394)
  * ApplicationLauncherIcon: recompute pips when the screen geometry
changes (LP: #1024101)
  * UnityScreen: reset decoration::DataPool on destruction, otherwise we
won't have a valid screen ptr (LP: #1291243)
  * DecorationsGrabEdge: Only perform tookit actions on right-click (LP:
#1301459)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 03 Apr 2014 
11:10:36 +

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

Title:
  Pips show incorrect status after attaching or detatching second screen

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

Bug description:
  Intel based laptop in docking bay. Two screens connected and enabled. Some 
applications spread over both screens.
  Detach the second screen (in my case, pull the laptop out of the docking bay).

  Notice that the pips show empty triangles as if the applications are
  on another workspace when in fact they're on workspace 1 (current)

  Move to another (empty) workspace and back, and note the triangles
  fill back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.12+bzr2384ubuntu0+702 [origin: LP-PPA-unity-team-sru]
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  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]
  CrashDB: unity
  Date: Thu Jul 12 22:19:06 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1024101/+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 1302004] [NEW] Indicator-datetime still doesn't list all events for today's date (Trusty)

2014-04-03 Thread Khurshid Alam
Public bug reported:

This bug is related to this bug: Bug #1293646 (Which is marked as fix
released)

With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
lists all events for all past selected dates properly (which is fixed in
bug Bug #1293646) except today's date. When I click on any past date in
calendar it shows:

1. all all-day events for the day.
2. all events with time for the day
3. upcoming (future) all-day events
4. upcoming (future) events with time

But when I click on today's date it only shows:

1. future all day events
2. future events with time


I still have to click on previous day's date to find out all all-day events for 
today.

The behavior(showing all events for a day) should be same for any date,
including today's date.

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


** Tags: trusty

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

Title:
  Indicator-datetime still doesn't list all events for today's date
  (Trusty)

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

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which is fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  
  I still have to click on previous day's date to find out all all-day events 
for today.

  The behavior(showing all events for a day) should be same for any
  date, including today's date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1302004/+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 1283236] Re: Alarms are triggered in UTC tz despite saving in local tz

2014-04-03 Thread Nekhelesh Ramananthan
** Changed in: ubuntu-clock-app
   Status: Confirmed = Invalid

** Changed in: ubuntu-clock-app
 Assignee: Nekhelesh Ramananthan (nik90) = (unassigned)

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

Title:
  Alarms are triggered in UTC tz despite saving in local tz

Status in The Date and Time Indicator:
  In Progress
Status in Clock application for Ubuntu devices:
  Invalid
Status in Ubuntu UI Toolkit:
  In Progress
Status in “indicator-datetime” package in Ubuntu:
  Confirmed
Status in “qtorganizer5-eds” package in Ubuntu:
  Confirmed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New

Bug description:
  Setting an alarm in the local timezone is not respected by the system
  since the alarms is triggered in the equivalent UTC timezone.

  Mako build 200, 205

  Steps to reproduce: 
  1. Ensure that phone timezone is something other than UTC. For instance 
eastern tz (UTC-5)
  2. Set an alarm for 3:00 PM in the ubuntu clock app.
  3. Indicator shows a pending alarm for 3:00 PM
  4. Check a minute or so later, indicator shows an alarm pending for 8:00 PM

  What happens:
  The alarm does not go off at 3:00 PM. Instead it triggers at 8:00 PM

  What should happen:
  The alarm is triggered at 3:00 PM

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1283236/+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 1299596] Re: The content of the display are briefly shown when resuming from sleep, before lock screen is displayed

2014-04-03 Thread Matthias Niess
This looks like a security issue and there are already multiple users
confirming it (here and on reddit). I subscribed the security team to
this bug. If I'm wrong, please forgive me and just unsubscribe.

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

Title:
  The content of the display are briefly shown when resuming from sleep,
  before lock screen is displayed

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I attach a video showing the problem.

  As you can see, when suspending the PC the transition between the
  desktop and the lock screen is no finished before suspending. It seems
  the process is finished on resume. The result is that the content of
  the desktop are briefly shown before the lock screen is displayed.

  I think this is a rather serious issue, as the content of the PC can
  be seen by non authorized people when one lefts the PC suspended and
  password protected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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 Mar 29 18:37:41 2014
  DistUpgraded: 2014-03-28 16:07:01,468 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.6, 3.13.0-19-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-20-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1436]
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobility Radeon HD 5650 [103c:1436]
  InstallationDate: Installed on 2013-09-23 (187 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130923.1)
  MachineType: Hewlett-Packard HP ENVY 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=ca667e96-4f50-4077-8344-88c49b0769a2 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-28 (1 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1436
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 59.24
  dmi.chassis.asset.tag: CNU03538DZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.26:bd12/01/2011:svnHewlett-Packard:pnHPENVY14NotebookPC:pvr0492102419162:rvnHewlett-Packard:rn1436:rvr59.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 14 Notebook PC
  dmi.product.version: 0492102419162
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140328-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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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-1ubuntu3
  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 Mar 29 14:23:06 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id3593 
   vendor LCD
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1299596/+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 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken

2014-04-03 Thread Treviño
** Changed in: unity (Ubuntu)
   Status: Triaged = Invalid

** Changed in: unity
   Status: Triaged = Invalid

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

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

** Changed in: compiz
   Importance: Undecided = High

** Changed in: compiz
Milestone: None = 0.9.11.0

** Changed in: compiz
   Status: New = In Progress

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

Title:
  Launcher, Window management - Switching between spreads when dragging
  a file over the Launcher is broken

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  In Progress
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  To reproduce:

  Open two Chrome windows and two Firefox windows.  Drag a .html file
  over the Chrome icon in the Launcher.  A spread of the two Chrome
  windows should appear.  Then continue the same drag, and drag the file
  over the Firefox icon in the Launcher.  Nothing happens, the Chrome
  spread is still displayed.

  Desired behaviour;

  After a spread appears as a result of the user dragging a file over a
  application icon in the Launcher, if the user then drags the file over
  a different application icon (where the application is also a valid
  drop receptacle for the file type) the spread should switch to the
  newly selected application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/727904/+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-04-03 Thread Ivan Larionov
I can confirm Super+A/F/M/C/V still doesn't work in unity.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/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 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:
  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 1256590] Re: J. Random User Showing In Session Indicator

2014-04-03 Thread Sebastien Bacher
** Changed in: indicator-session (Ubuntu)
   Importance: Undecided = Low

** Changed in: indicator-session (Ubuntu)
   Status: Confirmed = In Progress

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

Title:
  J. Random User Showing In Session Indicator

Status in “indicator-session” package in Ubuntu:
  In Progress

Bug description:
  Yesterday I encountered an issue that was very concerning, at least
  until I investigated a bit more, and found that it may only be due to
  debug/test code that's still be present in released software. The
  search I made brought me here. Please redirect me if I'm in the wrong
  place.

  J. Random User appeared in the Ubuntu 13.10 (x86_64) Unity Power
  indicator list, below 'Lock' and above '{my user name}'.

  This was only noticed as I was about to lock the screen, which I do a
  number of times per day, however, this time J. Random User was
  visible.

  There was no User Account for that entry in System Settings  User Accounts.
  There was no one else logged onto the machine except my own username (checked 
by '$ w').
  There seemed to be no rogue processes running (checked in log and current 
processes).

  From a security point of view, it was very concerning. But after my
  searches on the matter, I belive the machine not to be compromised,
  but tickled by 'developer test code'.

  Restarting the computer removed the issue.

  It could be coincidence, but the only bit of new software I tried (for
  the first time ever) was the Remmina Remote Desktop Client to see if
  was interested to remotely connect to another computer on the home
  network. After restarting my computer and running that software again,
  it did not cause a J. Random User to appear in the indicator, so it
  could be a red-herring.

  It could also be related to this? :
  https://code.launchpad.net/~larsu/ido/custom-menu-items/+merge/165498

  Hope you know something about it, or can redirect this bug report
  elsewhere.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1256590/+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 1299596] Re: The content of the display are briefly shown when resuming from sleep, before lock screen is displayed

2014-04-03 Thread Nicolás Abel Carbone
I agree this is a potential security issue.

On reddit, some user have reported a similar problem when using multiple
monitors. As my notebook is using PRIME-based switchable graphics and
two screen are detected, maybe the problem is related to this.

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

Title:
  The content of the display are briefly shown when resuming from sleep,
  before lock screen is displayed

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I attach a video showing the problem.

  As you can see, when suspending the PC the transition between the
  desktop and the lock screen is no finished before suspending. It seems
  the process is finished on resume. The result is that the content of
  the desktop are briefly shown before the lock screen is displayed.

  I think this is a rather serious issue, as the content of the PC can
  be seen by non authorized people when one lefts the PC suspended and
  password protected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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 Mar 29 18:37:41 2014
  DistUpgraded: 2014-03-28 16:07:01,468 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.6, 3.13.0-19-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-20-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1436]
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobility Radeon HD 5650 [103c:1436]
  InstallationDate: Installed on 2013-09-23 (187 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130923.1)
  MachineType: Hewlett-Packard HP ENVY 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=ca667e96-4f50-4077-8344-88c49b0769a2 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-28 (1 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1436
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 59.24
  dmi.chassis.asset.tag: CNU03538DZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.26:bd12/01/2011:svnHewlett-Packard:pnHPENVY14NotebookPC:pvr0492102419162:rvnHewlett-Packard:rn1436:rvr59.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 14 Notebook PC
  dmi.product.version: 0492102419162
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140328-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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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-1ubuntu3
  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 Mar 29 14:23:06 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id3593 
   vendor LCD
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1299596/+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 1302081] [NEW] Menu in title bar is missing after a modal window child

2014-04-03 Thread Huck-bernhard
Public bug reported:

steps to get this behavior

1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
2. Open qtcreator in Normal Window Size (not maximized) .
3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
4. Close Window About Qt Creator.
5. Move Mouse to the Title Bar, no menu bar is showing.

this behavior is also in different QT4 and QT5 Applicaion showing.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: appmenu-qt (0.2.7+14.04.20140305-0ubuntu1)
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic i686
ApportVersion: 2.14-0ubuntu1
Architecture: i386
CurrentDesktop: Unity
Date: Thu Apr  3 19:31:17 2014
InstallationDate: Installed on 2014-02-14 (47 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
SourcePackage: appmenu-qt
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: appmenu-qt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 trusty

** Description changed:

  steps to get this behavior
  
  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.
  
  this behavior is also in different QT4 and QT5 Applicaion showing.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
- Package: appmenu-qt (not installed)
+ Package: appmenu-qt (0.2.7+14.04.20140305-0ubuntu1)
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Apr  3 19:31:17 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- Menu in title bar is missing after a modal window child Edit
+ Menu in title bar is missing after a modal window child

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

Title:
  Menu in title bar is missing after a modal window child

Status in “appmenu-qt” package in Ubuntu:
  New

Bug description:
  steps to get this behavior

  1. Settings | Appearance | Behavior set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu Open Help | 
About QtCreator...
  4. Close Window About Qt Creator.
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt (0.2.7+14.04.20140305-0ubuntu1)
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Apr  3 19:31:17 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140214)
  SourcePackage: appmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1302081/+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 1302086] Re: compiz crashed with SIGSEGV in g_mount_spec_match_with_path()

2014-04-03 Thread Apport retracing service
*** This bug is a duplicate of bug 1054223 ***
https://bugs.launchpad.net/bugs/1054223

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1302086/+attachment/4063618/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1302086/+attachment/4063620/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1302086/+attachment/4063621/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1302086/+attachment/4063622/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1302086/+attachment/4063623/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1302086/+attachment/4063624/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1302086/+attachment/4063625/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1054223
   compiz crashed with SIGSEGV in g_mount_spec_match_with_path() from ... from 
g_file_load_contents() from 
unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in g_mount_spec_match_with_path()

Status in “unity” package in Ubuntu:
  New

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  3 19:27:47 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-12-22 (102 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f7dea32c3f8 g_mount_spec_match_with_path+24:  
mov0x8(%r8),%ecx
   PC (0x7f7dea32c3f8) ok
   source 0x8(%r8) (0x7f7d0043) not located in a known VMA region (needed 
readable region)!
   destination %ecx ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   g_mount_spec_match_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
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
  Title: compiz crashed with SIGSEGV in g_mount_spec_match_with_path()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302086/+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 1169054] Re: Disabling then Re-Enabling login without password does remove user from nopasswdlogin group

2014-04-03 Thread Eric Chaskes
This bug is still present in 14.04

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

Title:
  Disabling then Re-Enabling login without password does remove user
  from nopasswdlogin group

Status in “accountsservice” package in Ubuntu:
  Confirmed

Bug description:
  I am using 12.04.

  Under System Settings, User Accounts, Passwords, Action, changing to
  Login without a password works as expected. On the next login,
  LightDM will not prompt you for a password, You can just login by
  hitting Enter.

  But, re-enabling password, or changing a password for the same user
  does not change LightDM behavior. LightDM does not re-enable asking
  for password at login.

  I think the problem is re-enabling password under Systems Settings
  does not delete user from nopasswdlogin group. You have to delete it
  from the command line:

  sudo gpasswd -d username nopasswdlogin

  This problem is the same ones described here:

  http://ubuntuforums.org/showthread.php?p=11566335

  http://askubuntu.com/questions/211084/how-do-i-get-ubuntu-to-ask-me-
  for-at-password-at-login-again/281615#281615

  http://askubuntu.com/questions/100010/no-password-asked-at-login-
  screen-just-start-session-button-with-lightdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1169054/+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 1169054] Re: Disabling then Re-Enabling login without password does remove user from nopasswdlogin group

2014-04-03 Thread Eric Chaskes
This bug title is worded incorrectly. More accurate would be:

Changing user setting in User Accounts from Login without password to
Disable this account does not remove the user from the nopasswdlogin
group.

The user remains in the nopasswdlogin group only when going from Login
without password to Disable this account. In this case, lightdm will
remain set to allow login without a password.

After setting a password, the user is properly removed from
nopasswdlogin and lightdm behaves correctly, so setting a password in
User Settings and then disabling the account in User Settings avoids the
bug.

I confirmed this in 12.04.4, 13.10, and 14.04 Beta 2.

See: http://askubuntu.com/questions/442641/how-to-disable-a
-passwordless-account/442995#442995

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

Title:
  Disabling then Re-Enabling login without password does remove user
  from nopasswdlogin group

Status in “accountsservice” package in Ubuntu:
  Confirmed

Bug description:
  I am using 12.04.

  Under System Settings, User Accounts, Passwords, Action, changing to
  Login without a password works as expected. On the next login,
  LightDM will not prompt you for a password, You can just login by
  hitting Enter.

  But, re-enabling password, or changing a password for the same user
  does not change LightDM behavior. LightDM does not re-enable asking
  for password at login.

  I think the problem is re-enabling password under Systems Settings
  does not delete user from nopasswdlogin group. You have to delete it
  from the command line:

  sudo gpasswd -d username nopasswdlogin

  This problem is the same ones described here:

  http://ubuntuforums.org/showthread.php?p=11566335

  http://askubuntu.com/questions/211084/how-do-i-get-ubuntu-to-ask-me-
  for-at-password-at-login-again/281615#281615

  http://askubuntu.com/questions/100010/no-password-asked-at-login-
  screen-just-start-session-button-with-lightdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1169054/+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 1201180] Re: powerbtn.sh conflicts with logind

2014-04-03 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/trusty-proposed/acpid

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

Title:
  powerbtn.sh conflicts with logind

Status in “acpid” package in Ubuntu:
  Fix Committed
Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd-shim” package in Ubuntu:
  Invalid

Bug description:
  In saucy the PC powers down as soon as I press the power button, it
  seems that systemd is calling poweroff, but I'm not sure if it's
  doing that in response of some other event (i.e. as callback of a dbus
  call):

  root  4998  0.0  0.0 177932  2104 ?Sl   20:41   0:00 
/usr/lib/x86_64-linux-gnu/systemd-shim
  root  5012  0.0  0.0   4440   624 ?S20:41   0:00  \_ sh -c 
/sbin/poweroff
  root  5013  0.0  0.0   4440   628 ?S20:41   0:00  \_ 
/bin/sh /sbin/shutdown -h -P now

  In any case the caller or systemd itself should be aware that there's
  a session-manager running and that it shouldn't actually directly
  power off the system then.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+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 1281297] Re: Scale/Spread Search does not use applications name

2014-04-03 Thread Doctor Rover
First of all, thank you for fixing that )))
But still, an issue remains with this. I use Russian localisation in Ubuntu and 
if I type terminal, I still can't see the terminals as matches. This is 
simply  because in Russian, the terminal app is called Терминал. Obviously, 
the search is done now only by localised app names.
I believe that search should also be done by original app names.

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

Title:
  Scale/Spread Search does not use applications name

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

Bug description:
  To reproduce:

  1) Open 2 gnome-terminal
  2) Super+W (to go into scale mode)
  3) type terminal

  Expected:
    The 2 gnome-terminals to be left as valid matches.

  Result:
    Empty search results on the gnome-terminals.

  Also, based on a duplicate:
  I propose that not only are the windows in spread filtered by title, but also 
by
  - application name, e.g. gnome terminal
  - generic name, e.g. web browser
  - application category, e.g. multimedia

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1281297/+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 1302123] [NEW] Won't respawn when restarting unity-panel-service

2014-04-03 Thread Edwin Pujols
Public bug reported:

If I run `restart unity-panel-service` or `killall unity-panel-service`,
indicator-application is not respawned and I need to start it manually
with `start indicator-application`. The other indicators are restarted
normally.

As a consequence, Network Manager's applet is not drawn (nor other
custom appindicators).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-application 12.10.1+14.04.20140402-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr  3 14:54:16 2014
InstallationDate: Installed on 2014-03-16 (18 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316)
SourcePackage: indicator-application
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Summary changed:

- The service won't respawn when restarting unity-panel-service
+ Won't respawn when restarting unity-panel-service

** Description changed:

  If I run `restart unity-panel-service` or `killall unity-panel-service`,
  indicator-application is not respawned and I need to start it manually.
  All the other indicators are restarted normally.
+ 
+ As a consequence, Network Manager's applet is not drawn (nor other
+ custom appindicators).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-application 12.10.1+14.04.20140402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  3 14:54:16 2014
  InstallationDate: Installed on 2014-03-16 (18 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316)
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  If I run `restart unity-panel-service` or `killall unity-panel-service`,
- indicator-application is not respawned and I need to start it manually.
- All the other indicators are restarted normally.
+ indicator-application is not respawned and I need to start it manually
+ with `start indicator-application`. The other indicators are restarted
+ normally.
  
  As a consequence, Network Manager's applet is not drawn (nor other
  custom appindicators).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-application 12.10.1+14.04.20140402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  3 14:54:16 2014
  InstallationDate: Installed on 2014-03-16 (18 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316)
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Won't respawn when restarting unity-panel-service

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

Bug description:
  If I run `restart unity-panel-service` or `killall unity-panel-
  service`, indicator-application is not respawned and I need to start
  it manually with `start indicator-application`. The other indicators
  are restarted normally.

  As a consequence, Network Manager's applet is not drawn (nor other
  custom appindicators).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-application 12.10.1+14.04.20140402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  3 14:54:16 2014
  InstallationDate: Installed on 2014-03-16 (18 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316)
  SourcePackage: indicator-application
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1302123/+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 1201180] Re: powerbtn.sh conflicts with logind

2014-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package acpid - 1:2.0.21-1ubuntu2

---
acpid (1:2.0.21-1ubuntu2) trusty; urgency=medium

  * ./debian/powerbtn.sh: Don't do anything if logind is running, as that
already handles power button presses. This fixes unconditional shutdowns
if a desktop environment wants to handle the power key by itself (and
inhibits logind). (LP: #1201180)
 -- Martin Pitt martin.p...@ubuntu.com   Thu, 03 Apr 2014 14:53:35 +0100

** Changed in: acpid (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  powerbtn.sh conflicts with logind

Status in “acpid” package in Ubuntu:
  Fix Released
Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd-shim” package in Ubuntu:
  Invalid

Bug description:
  In saucy the PC powers down as soon as I press the power button, it
  seems that systemd is calling poweroff, but I'm not sure if it's
  doing that in response of some other event (i.e. as callback of a dbus
  call):

  root  4998  0.0  0.0 177932  2104 ?Sl   20:41   0:00 
/usr/lib/x86_64-linux-gnu/systemd-shim
  root  5012  0.0  0.0   4440   624 ?S20:41   0:00  \_ sh -c 
/sbin/poweroff
  root  5013  0.0  0.0   4440   628 ?S20:41   0:00  \_ 
/bin/sh /sbin/shutdown -h -P now

  In any case the caller or systemd itself should be aware that there's
  a session-manager running and that it shouldn't actually directly
  power off the system then.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+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 1290997] Re: click crashed with gi._glib.GError in run(): Child process exited with code 139

2014-04-03 Thread Launchpad Bug Tracker
** Branch linked: lp:~ted/url-dispatcher/cache-permissions

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

Title:
  click crashed with gi._glib.GError in run(): Child process exited with
  code 139

Status in “url-dispatcher” package in Ubuntu:
  Triaged

Bug description:
  after update and logout  login again

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: click 0.4.17.2
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 11 19:47:29 2014
  ExecutablePath: /usr/bin/click
  InstallationDate: Installed on 2013-12-11 (89 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131211)
  InterpreterPath: /usr/bin/python3.4
  ProcCmdline: /usr/bin/python3 /usr/bin/click hook run-user
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/click', 'hook', 'run-user']
  SourcePackage: click
  Title: click crashed with gi._glib.GError in run(): Child process exited with 
code 139
  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/url-dispatcher/+bug/1290997/+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 1104236] Re: [regression] Unity show desktop fade out hides windows on all workspaces and makes them invisible in spread.

2014-04-03 Thread Christopher Townsend
The hides in all workspaces part of this bug is not present in Trusty.
However, the window missing in the Spread is still present.  Adjusting
the bug title accordingly...

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

** Changed in: unity
 Assignee: (unassigned) = Christopher Townsend (townsend)

** Changed in: unity
   Status: Triaged = In Progress

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) = Christopher Townsend (townsend)

** Summary changed:

- [regression] Unity show desktop fade out hides windows on all workspaces and 
makes them invisible in spread.
+ [regression] Unity show desktop fade out makes them invisible in spread.

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

Title:
  [regression] Unity show desktop fade out makes them invisible in
  spread.

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

Bug description:
  This looks like a regression.  Bug 88 describes what we now have
  in current trunk again.

  STR:

  1. Open 2 application windows, e.g. gnome-terminal
  2. Alt-tab to show desktop
  3. Click  on gnome-terminal icon with 2 pips on the launcher

  Expected results:
  Two windows are displayed in spread.

  Actual results:
  One window is displayed in spread with another one still being there, the 
outline appears on hover but the window itself is not displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.01.21bzr3064pkg0raring147 [origin: 
LP-PPA-unity-team-staging]
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  Date: Thu Jan 24 19:08:09 2013
  InstallationDate: Installed on 2013-01-04 (20 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130104)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

  
  ADDITION: 

  Furthermore Show desktop shows desktop on all workspaces which is not 
desired behavior. This makes the issue even worse, because you can only use the 
launcher and alt-tab to navigate between the windows which results in a big 
usability bug. 
  The following video demonstrates this:
  http://ubuntuone.com/4zt3CfDbgOZmanRGBCrbeE

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

2014-04-03 Thread boon
*** This bug is a duplicate of bug 1244285 ***
https://bugs.launchpad.net/bugs/1244285

Was working fine yesterday running Ubuntu 13.10. Then a bunch of updates
came through, including a kernel update from 3.11.0-18 to 3.11.0-19
which resulted in a reboot. After the reboot the time had disappeared
from the menu bar.

I hadn't realised how reliant I am on the time's being visible!

This should be a HIGH priority to fix.

If someone can tell me the necessary commands, I should be able to look
up exactly what upgrades occurred yesterday and what other upgrades had
been applied since the _previous_ reboot.

killall unity-panel-service restored the clock. However I am yet to
see whether this is a permanent workaround or is only good for one login
or is only good for one boot. I suspect that it is not a permanent
workaround.

-- 
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 1302108] [NEW] Login is required twice after screensaver-activation

2014-04-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

hey,

i installed the daily build from yesterday on my probook 4720s and each
time the login screen appears when i'm afk for a while, i need to login
twice (with password). After the first time, I see the Desktop or
application that is in front but only for less then a second befor the
login-screen appears for a second time.

I hope this information is useful for you.

Cheers!

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


** Tags: bot-comment
-- 
Login is required twice after screensaver-activation
https://bugs.launchpad.net/bugs/1302108
You received this bug notification because you are a member of DX Packages, 
which is subscribed to unity in Ubuntu.

-- 
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 1302169] Re: compiz crashed with SIGSEGV in FT_Load_Glyph()

2014-04-03 Thread Apport retracing service
*** This bug is a duplicate of bug 1199571 ***
https://bugs.launchpad.net/bugs/1199571

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1302169/+attachment/4063916/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1302169/+attachment/4063918/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1302169/+attachment/4063919/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1302169/+attachment/4063920/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1302169/+attachment/4063921/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1302169/+attachment/4063922/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1302169/+attachment/4063923/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1199571
   compiz crashed with SIGSEGV in af_latin_hints_compute_edges()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in FT_Load_Glyph()

Status in “unity” package in Ubuntu:
  New

Bug description:
  I was simply searching the dash, and then this crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  3 14:37:57 2014
  ExecutablePath: /usr/bin/compiz
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd78cf9d92f:orb$0x2,0x18(%rdx)
   PC (0x7fd78cf9d92f) ok
   source $0x2 ok
   destination 0x18(%rdx) (0x0009) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing 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: 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/1302169/+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 1302108] Re: Login is required twice after screensaver-activation

2014-04-03 Thread Brian Murray
This happens to me after I manually lock the screen and leave long
enough for the screensaver timeout to activate.  Maddeningly, I can log
in and work for a minute before the second lock occurs.

** Package changed: ubuntu = unity (Ubuntu)

** Tags added: 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/1302108

Title:
  Login is required twice after screensaver-activation

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  hey,

  i installed the daily build from yesterday on my probook 4720s and
  each time the login screen appears when i'm afk for a while, i need to
  login twice (with password). After the first time, I see the Desktop
  or application that is in front but only for less then a second befor
  the login-screen appears for a second time.

  I hope this information is useful for you.

  Cheers!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302108/+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 1302108] Re: Login is required twice after screensaver-activation

2014-04-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  Login is required twice after screensaver-activation

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  hey,

  i installed the daily build from yesterday on my probook 4720s and
  each time the login screen appears when i'm afk for a while, i need to
  login twice (with password). After the first time, I see the Desktop
  or application that is in front but only for less then a second befor
  the login-screen appears for a second time.

  I hope this information is useful for you.

  Cheers!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302108/+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 1289099] Re: [SRU] Window Matching fixes

2014-04-03 Thread Brian Murray
Hello Robert, or anyone else affected,

Accepted libunity-webapps into saucy-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/libunity-
webapps/2.4.8+13.10.20140327-0ubuntu1 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: libunity-webapps (Ubuntu Saucy)
   Status: In Progress = Fix Committed

** Tags added: verification-needed

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

Title:
  [SRU] Window Matching fixes

Status in WebApps: libunity:
  Fix Released
Status in “libunity-webapps” package in Ubuntu:
  Fix Released
Status in “libunity-webapps” source package in Saucy:
  Fix Committed

Bug description:
  [Impact]

   * Window matching behaviors are deficient. This means that the Dash
  does not always correctly indicate which app is active, and sometimes
  two icons can be displayed for the same app (one that stays
  permanently for launching, and one that appears only when the app is
  running).

  [Test Case]

   * Browse to the affected website, notice the behavior of the webapps in the 
Dash is inconsistent. Behavior can include -
* Browser Launcher item is not associated with the appropriate WebApp 
Launcher item
* Two items may appear associated with the WebApp (instead of one)
* Icon may appear as Launcher default, not the appropriate WebApp icon

  [Regression Potential]

  * Quite small, this change is confined to libunity-webapps and can't
  impact anything outisde of the webapps interaction in Unity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity-webapps/+bug/1289099/+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 1302221] [NEW] shutdown and restart options display logout dialog instead

2014-04-03 Thread fossfreedom
Public bug reported:

using virtualbox 4.3.10 - with the latest updates, either the shutdown
or restart options displays the logout dialog instead.  Clicking logout
indeeds log the user out - not shutdown as chosen.

There doesnt appear to be anyway to shutdown other than via a terminal
sudo shutdown  now

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-session 12.10.5+14.04.20140324-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr  3 23:02:05 2014
InstallationDate: Installed on 2014-02-22 (40 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140220.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: indicator-session
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-session (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 indicator-session in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1302221

Title:
  shutdown and restart options display logout dialog instead

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

Bug description:
  using virtualbox 4.3.10 - with the latest updates, either the shutdown
  or restart options displays the logout dialog instead.  Clicking
  logout indeeds log the user out - not shutdown as chosen.

  There doesnt appear to be anyway to shutdown other than via a terminal
  sudo shutdown  now

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-session 12.10.5+14.04.20140324-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  3 23:02:05 2014
  InstallationDate: Installed on 2014-02-22 (40 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140220.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1302221/+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 1302004] Re: Indicator-datetime still doesn't list all events for today's date (Trusty)

2014-04-03 Thread Khurshid Alam
** Description changed:

  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)
  
  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
- lists all events for all past selected dates properly (which is fixed in
- bug Bug #1293646) except today's date. When I click on any past date in
- calendar it shows:
+ lists all events for all past selected dates properly (which was fixed
+ in bug Bug #1293646) except today's date. When I click on any past date
+ in calendar it shows:
  
  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time
  
  But when I click on today's date it only shows:
  
  1. future all day events
  2. future events with time
  
- 
- I still have to click on previous day's date to find out all all-day events 
for today.
+ I still have to click on previous day's date to find out all all-day
+ events for today.
  
  The behavior(showing all events for a day) should be same for any date,
  including today's date.

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

Title:
  Indicator-datetime still doesn't list all events for today's date
  (Trusty)

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

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior(showing all events for a day) should be same for any
  date, including today's date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1302004/+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 1302249] [NEW] Rhythmbox play button not working in indicator-sound applet

2014-04-03 Thread Rael
Public bug reported:

In the Rhythmbox music controls at the indicator-sound, after click in
the play button, button displays the loading image, but then nothing
happens.

In its own window, Rhythmbox buttons are working properly.

Steps to reproduce:
1 - Click on indicator sound to expand it;
2 - In indicator sound menu, click in the Play button for Rhythmbox.

Expected result(s):
Last selected music/radio will start to play.

Current result(s):
Button displays the loading image, but nothing happens (see attached image).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'mic-volume': (true, '', [0.2818603515625]), 'scroll': (true, 
'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '', 
[{'running': false, 'state': 'Launching'}]), 
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i', 
[0.46783116740198283]), 'root': (true, '', [{'title': 'Sound', 
'accessible-desc': 'Volume (71%)', 'icon': ('themed', 
['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']), 
'visible': true}]), 'play.rhythmbox.desktop': (true, '', ['Launching']), 
'play-playlist.rhythmbox.desktop': (true, 's', []), 'next.rhythmbox.desktop': 
(true, '', [])},)
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr  3 20:28:22 2014
InstallationDate: Installed on 2014-03-28 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Attachment added: Play button in indicator-sound after click
   
https://bugs.launchpad.net/bugs/1302249/+attachment/4064205/+files/Rhythmbox_play_not_working_at_indicator-sound.png

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

Title:
  Rhythmbox play button not working in indicator-sound applet

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

Bug description:
  In the Rhythmbox music controls at the indicator-sound, after click in
  the play button, button displays the loading image, but then
  nothing happens.

  In its own window, Rhythmbox buttons are working properly.

  Steps to reproduce:
  1 - Click on indicator sound to expand it;
  2 - In indicator sound menu, click in the Play button for Rhythmbox.

  Expected result(s):
  Last selected music/radio will start to play.

  Current result(s):
  Button displays the loading image, but nothing happens (see attached image).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'mic-volume': (true, '', [0.2818603515625]), 'scroll': (true, 
'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '', 
[{'running': false, 'state': 'Launching'}]), 
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i', 
[0.46783116740198283]), 'root': (true, '', [{'title': 'Sound', 
'accessible-desc': 'Volume (71%)', 'icon': ('themed', 
['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']), 
'visible': true}]), 'play.rhythmbox.desktop': (true, '', ['Launching']), 
'play-playlist.rhythmbox.desktop': (true, 's', []), 'next.rhythmbox.desktop': 
(true, '', [])},)
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  3 20:28:22 2014
  InstallationDate: Installed on 2014-03-28 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1302249/+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 1302249] Re: Rhythmbox play button not working in indicator-sound applet

2014-04-03 Thread Rael
Hm, I just realized now that all 3 buttons are not working (previous,
play, next).

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

Title:
  Rhythmbox play button not working in indicator-sound applet

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

Bug description:
  In the Rhythmbox music controls at the indicator-sound, after click in
  the play button, button displays the loading image, but then
  nothing happens.

  In its own window, Rhythmbox buttons are working properly.

  Steps to reproduce:
  1 - Click on indicator sound to expand it;
  2 - In indicator sound menu, click in the Play button for Rhythmbox.

  Expected result(s):
  Last selected music/radio will start to play.

  Current result(s):
  Button displays the loading image, but nothing happens (see attached image).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'mic-volume': (true, '', [0.2818603515625]), 'scroll': (true, 
'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '', 
[{'running': false, 'state': 'Launching'}]), 
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i', 
[0.46783116740198283]), 'root': (true, '', [{'title': 'Sound', 
'accessible-desc': 'Volume (71%)', 'icon': ('themed', 
['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']), 
'visible': true}]), 'play.rhythmbox.desktop': (true, '', ['Launching']), 
'play-playlist.rhythmbox.desktop': (true, 's', []), 'next.rhythmbox.desktop': 
(true, '', [])},)
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  3 20:28:22 2014
  InstallationDate: Installed on 2014-03-28 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1302249/+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 1295593] Re: indicator-appmenu depends on hud

2014-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package indicator-appmenu -
13.01.0+14.04.20140403-0ubuntu1

---
indicator-appmenu (13.01.0+14.04.20140403-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * Clean leftover hud files, it has its own source now. Drop depends as
well (LP: #1295593)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 03 Apr 2014 
14:03:27 +

** Changed in: indicator-appmenu (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  indicator-appmenu depends on hud

Status in “indicator-appmenu” package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Trusty

  indicator-appmenu depends on hud. Probably it shouldn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1295593/+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 1302266] [NEW] unity relies on super (windows) key

2014-04-03 Thread Chris Bainbridge
Public bug reported:

14.04 beta 2. On booting an older Thinkpad (sans Windows key) - Unity
shows and use shortcuts that rely heavily on a Super (Windows) key. This
laptop does not have such a key. Would be good to fallback to a
reasonable alternative.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140321-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CasperVersion: 1.339
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Apr  4 01:57:17 2014
LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 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/1302266

Title:
  unity relies on super (windows) key

Status in “unity” package in Ubuntu:
  New

Bug description:
  14.04 beta 2. On booting an older Thinkpad (sans Windows key) - Unity
  shows and use shortcuts that rely heavily on a Super (Windows) key.
  This laptop does not have such a key. Would be good to fallback to a
  reasonable alternative.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140321-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Apr  4 01:57:17 2014
  LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302266/+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 1298706] Re: Shutdown menu does not include shutdown option

2014-04-03 Thread Charles Profitt
I can confirm this same behavior after my last upgrade. I end up using a
terminal command to shutdown or restart my computer. This is a
regression.

** Changed in: unity (Ubuntu)
   Importance: Undecided = Critical

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

Title:
  Shutdown menu does not include shutdown option

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When going to shutdown, it displays logout and lock options. When
  using the power button it displays the standard shutdown menu but is
  missing the shutdown option. I have attatched screenshots below to
  better explain.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140321-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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: Thu Mar 27 20:20:18 2014
  DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed
   vboxhost, 4.3.8, 3.13.0-19-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fa20]
  InstallationDate: Installed on 2014-01-03 (83 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: TOSHIBA Satellite C55-A
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic 
root=UUID=6b37c83b-b64c-42fc-89d3-3db46a397734 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-20 (7 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.10
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.10:bd04/12/2013:svnTOSHIBA:pnSatelliteC55-A:pvrPSCF6U-01Y00C:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55-A
  dmi.product.version: PSCF6U-01Y00C
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11+14.04.20140320.1-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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
10.0.0-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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-1ubuntu3
  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: Thu Mar 27 19:39:00 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17223 
   vendor SDC
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298706/+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 1298706] Re: Shutdown menu does not include shutdown option

2014-04-03 Thread Charles Profitt
** Package changed: unity (Ubuntu) = indicator-session (Ubuntu)

-- 
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, dx-packages
https://bugs.launchpad.net/bugs/1298706

Title:
  Shutdown menu does not include shutdown option

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

Bug description:
  When going to shutdown, it displays logout and lock options. When
  using the power button it displays the standard shutdown menu but is
  missing the shutdown option. I have attatched screenshots below to
  better explain.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140321-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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: Thu Mar 27 20:20:18 2014
  DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed
   vboxhost, 4.3.8, 3.13.0-19-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fa20]
  InstallationDate: Installed on 2014-01-03 (83 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: TOSHIBA Satellite C55-A
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic 
root=UUID=6b37c83b-b64c-42fc-89d3-3db46a397734 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-20 (7 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.10
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.10:bd04/12/2013:svnTOSHIBA:pnSatelliteC55-A:pvrPSCF6U-01Y00C:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55-A
  dmi.product.version: PSCF6U-01Y00C
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11+14.04.20140320.1-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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
10.0.0-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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-1ubuntu3
  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: Thu Mar 27 19:39:00 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17223 
   vendor SDC
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1298706/+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 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-04-03 Thread Jamie Strandboge
** Tags added: rls-t-incoming

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

Title:
  lightdm screen lock has triggered but keyboard is still connected to
  the main session

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have a laptop which has screensaved naturally due to timeout (most
  likely) and it is sitting there showing the lock screen but keyboard
  is still connected to the session, I can alt-tab to applications and
  via IRC i was able to send myself messages (blind) so clearly the
  keyboard is really operational.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.11-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 13 20:56:10 2014
  EcryptfsInUse: Yes
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (55 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292217/+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 1302302] [NEW] [regression] Unity now only starts in software rendering mode (i965 Mesa driver can't load)

2014-04-03 Thread Daniel van Vugt
Public bug reported:

After updating today Unity only starts in software rendering mode. I can tell 
because:
  1. There's no dash blur.
  2. Graphics performance is slow.
  3. .xsession-errors says:
   libGL error: failed to open drm device: Permission denied
   libGL error: failed to load driver: i965
  4. compiz is linked to the software driver:

$ pmap `pidof compiz` | grep dri
7f9a1e386000   3256K r-x-- swrast_dri.so
7f9a1e6b4000   2048K - swrast_dri.so
7f9a1e8b4000 60K r swrast_dri.so
7f9a1e8c3000 32K rw--- swrast_dri.so

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140403-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.14-0ubuntu1
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: Fri Apr  4 10:46:53 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:220c]
InstallationDate: Installed on 2014-04-03 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140331)
MachineType: LENOVO 20AQCTO1WW
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed 
root=UUID=a759a4aa-6f67-434e-8f5a-eae13c810c59 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET67WW (2.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQCTO1WW
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.04.20140328-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-4ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
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-1ubuntu3
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: Fri Apr  4 10:46:12 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1034 
 vendor LGD
xserver.version: 2:1.15.0-1ubuntu7

** Affects: compiz
 Importance: High
 Status: New

** Affects: unity
 Importance: High
 Status: New

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


** Tags: amd64 apport-bug compiz-0.9 regression-update trusty ubuntu

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

** Changed in: unity
   Importance: Undecided = High

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

** Changed in: compiz
   Importance: Undecided = High

** Summary changed:

- 4/4/2014: Unity now only starts in software rendering mode (i965 Mesa driver 
can't load)
+ [regression] Unity now only starts in software rendering mode (i965 Mesa 
driver can't load)

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

Title:
  [regression] Unity now only starts in software rendering mode (i965
  Mesa driver can't load)

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

Bug description:
  After updating today Unity only starts in software rendering mode. I can tell 
because:
1. There's no dash blur.
2. Graphics performance is slow.
3. .xsession-errors says:
 libGL error: failed to open drm device: Permission denied
 libGL error: failed to load driver: i965
4. compiz is linked to the software driver:

  $ pmap `pidof compiz` | grep dri
  7f9a1e386000   3256K r-x-- swrast_dri.so
  7f9a1e6b4000   2048K 

[Dx-packages] [Bug 1302302] Re: [regression] Unity now only starts in software rendering mode (i965 Mesa driver can't load)

2014-04-03 Thread Stéphane Graber
*** This bug is a duplicate of bug 1302264 ***
https://bugs.launchpad.net/bugs/1302264

** This bug is no longer a duplicate of bug 1302270
   [regression] Poor performance with recent update with i965: libGL error: 
failed to open drm device: Permission denied
** This bug has been marked a duplicate of bug 1302264
   systemd-logind assert failure: error.c:319: Assertion failed in 
nih_error_get: context_stack != NULL

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

Title:
  [regression] Unity now only starts in software rendering mode (i965
  Mesa driver can't load)

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

Bug description:
  After updating today Unity only starts in software rendering mode. I can tell 
because:
1. There's no dash blur.
2. Graphics performance is slow.
3. .xsession-errors says:
 libGL error: failed to open drm device: Permission denied
 libGL error: failed to load driver: i965
4. compiz is linked to the software driver:

  $ pmap `pidof compiz` | grep dri
  7f9a1e386000   3256K r-x-- swrast_dri.so
  7f9a1e6b4000   2048K - swrast_dri.so
  7f9a1e8b4000 60K r swrast_dri.so
  7f9a1e8c3000 32K rw--- swrast_dri.so

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14-0ubuntu1
  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: Fri Apr  4 10:46:53 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:220c]
  InstallationDate: Installed on 2014-04-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140331)
  MachineType: LENOVO 20AQCTO1WW
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed 
root=UUID=a759a4aa-6f67-434e-8f5a-eae13c810c59 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET67WW (2.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140328-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-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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-1ubuntu3
  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: Fri Apr  4 10:46:12 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1034 
   vendor LGD
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1302302/+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 1302344] [NEW] compiz crashed with signal 5 in g_type_create_instance()

2014-04-03 Thread Brad Heap
Public bug reported:

Unity isn't starting from command DISPLAY=:0 unity under 14.04

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140403-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Apr  4 16:40:23 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2013-12-09 (115 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
ProcCmdline: compiz --replace
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=linux
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2
 g_type_create_instance () 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_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: compiz crashed with signal 5 in g_type_create_instance()
UpgradeStatus: Upgraded to trusty on 2014-04-01 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (process:4626): dconf-CRITICAL **: unable to create file 
'/home/brad/.cache/dconf/user': Permission denied.  dconf will not work 
properly.
 (process:4626): dconf-CRITICAL **: unable to create file 
'/home/brad/.cache/dconf/user': Permission denied.  dconf will not work 
properly.

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

Title:
  compiz crashed with signal 5 in g_type_create_instance()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Unity isn't starting from command DISPLAY=:0 unity under 14.04

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr  4 16:40:23 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-12-09 (115 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcCmdline: compiz --replace
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2
   g_type_create_instance () 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_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with signal 5 in g_type_create_instance()
  UpgradeStatus: Upgraded to trusty on 2014-04-01 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (process:4626): dconf-CRITICAL **: unable to create file 
'/home/brad/.cache/dconf/user': Permission denied.  dconf will not work 
properly.
   (process:4626): dconf-CRITICAL **: unable to create file 
'/home/brad/.cache/dconf/user': Permission denied.  dconf will not work 
properly.

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