[Dx-packages] [Bug 1072206] Re: [nvidia] Window content is black or transparent

2015-02-18 Thread Kieran Grant
I have not noticed this in Ubuntu 14.04.1 until now because I had
previous been using Openbox (LXDE Desktop Environment), but after
switching back to Unity I noticed this.

I haven't seen any issues prior with any OpenGL programs under the LXDE
Desktop Environment nor so far any artifacts/glitches in OpenGL software
on Unity.

In my case it has nothing to do with Video memory (only about 23% used,
hovering at about 9% GPU Utilization), as far as I can tell, this is not
an NVIDIA bug, but a compiz bug.

For Reference:
Ubuntu 14.04.1
Linux Kernel 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015 
x86_64
NVIDIA Driver 331.113
Compiz: 0.9.11.3

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

Title:
  [nvidia] Window content is black or transparent

Status in Compiz:
  Confirmed
Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in Unity:
  Confirmed
Status in compiz package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.10 64bit (updated from 12.04) / NVIDIA GeForce 8 proprietary
  driver.

  This bug happens to me from 12.04 from some update I think.
  It appears mostly when I open a new application and only ocassionally.
  As temporary solution creating some other event like opening Unity dash or 
opening some next window, etc. fix it. Then window content is refreshed and I 
can see all correctly.
  Same with stable and experimental nvidia drivers.

  Screenshot of this bug is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.48  Sun Sep  9 20:22:27 
PDT 2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Oct 27 23:00:14 2012
  DistUpgraded: 2012-10-23 19:34:29,842 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-experimental-304, 304.48, 3.5.0-17-generic, x86_64: installed
   virtualbox, 4.1.18, 3.2.0-32-generic, x86_64: installed
   virtualbox, 4.1.18, 3.5.0-17-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Giga-byte Technology Device [1458:3468]
  InstallationDate: Installed on 2012-08-29 (59 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
  JockeyStatus:
   kmod:nvidia_experimental_304 - nvidia_experimental_304 (Proprietary, 
Enabled, Not in use)
   kmod:nvidia_173 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_current - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_173_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and 
VDPAU library (Proprietary, Disabled, Not in use)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=3ae94b68-4a0c-4633-aec7-b4ed25a23003 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2012-10-23 (4 days ago)
  XorgConf:
   Section Device
Identifier  Default Device
Option  NoLogoTrue
   EndSection
  dmi.bios.date: 05/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0208
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  

[Dx-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

2015-02-18 Thread Kieran Grant
The workaround I am using to this bug is simple:
Copy /var/lib/AccountsService/users/root to /var/lib/AccountsService/users/user
It's is probably a bad thing to do...

What actually happens if one uses SystemAccount=true in that file, as
far as I understand (correct me if I am wrong) that won't grant any
special powers to that user, still relies on group membership and
PolicyKit rules.

Essentially as a temporary workaround the following lines hide the user:
[User]
SystemAccount=true

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

Title:
  Unable to hide users from login screen / user switcher

Status in D-Bus interfaces for querying and manipulating user account 
information:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/857651/+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 1419391] Re: LANG=C environment breaks clock

2015-02-18 Thread Dmitry Shachnev
In your first screenshot the clock is not gnome-panel's clock, but
indicator-datetime clock. Reassigning to correct package.

** Package changed: gnome-panel (Ubuntu) = indicator-datetime (Ubuntu)

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

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

Title:
  LANG=C environment breaks clock

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  When the environment contains LANG=C (in .pam_environment, for
  example), the clock in gnome-panel disapears if it is either in
  12-hour format, or it displays seconds.

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-panel 1:3.8.0-1ubuntu12.2
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  8 14:06:58 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-panel
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-09-26 (134 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1419391/+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 1419391] [NEW] LANG=C environment breaks clock

2015-02-18 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When the environment contains LANG=C (in .pam_environment, for example),
the clock in gnome-panel disapears if it is either in 12-hour format, or
it displays seconds.


Thanks

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-panel 1:3.8.0-1ubuntu12.2
ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Feb  8 14:06:58 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-panel
GsettingsChanges:
 
InstallationDate: Installed on 2014-09-26 (134 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages trusty
-- 
LANG=C environment breaks clock
https://bugs.launchpad.net/bugs/1419391
You received this bug notification because you are a member of DX Packages, 
which is subscribed to indicator-datetime 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 1419391] Re: LANG=C environment breaks clock

2015-02-18 Thread Joshua Rogers
Is this one gnome panel clock? Or is this also the indicator?


Thanks

** Attachment added: Screenshot from 2015-02-19 04:52:43.png
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1419391/+attachment/4322008/+files/Screenshot%20from%202015-02-19%2004%3A52%3A43.png

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

Title:
  LANG=C environment breaks clock

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  When the environment contains LANG=C (in .pam_environment, for
  example), the clock in gnome-panel disapears if it is either in
  12-hour format, or it displays seconds.

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-panel 1:3.8.0-1ubuntu12.2
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  8 14:06:58 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-panel
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-09-26 (134 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1419391/+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 1322246] Re: Invisible mouse cursor when mouse integration is disabled and 3d acceleration is enabled in virtualbox

2015-02-18 Thread Nicole
This happened to me too when I disabled mouse capture. The mouse cursor
outside of virtualbox became stuck in one place (because I disabled it)
and the new mouse pointer in virtual box becomes invisible. The best
thing to fix this problem is to actually use an external device, such as
a pc contoller with analog sticks. So, plug in your pc controller of
whatever external device you want first, then download a free program
called JoyToKey or something similar ( I would suggest JoyToKey, it
works perfectly). Now, open JoyToKey and map your keyboard keys, like
w,a,s,d or up, down, left, right and left and right mouse clicks,
including middle mouse roll onto your pc controller. Next, open
virtualbox (disable capture). This way, at least now you can move the
pointer that was stuck initially in one place with your pc controller.

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

Title:
  Invisible mouse cursor when mouse integration is disabled and 3d
  acceleration is enabled in virtualbox

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

Bug description:
  When running Ubuntu as a guest OS using Virtualbox the mouse cursor is
  invisible when mouse integration is disabled AND 3d acceleration is
  enabled. This issue is also described amongst the comments here:
  https://bugs.launchpad.net/unity/+bug/971018 with people reporting the
  same issue in Parallells and in VMWare.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.1
  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
  CurrentDesktop: Unity
  Date: Thu May 22 23:21:59 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2014-04-19 (33 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=fa72170c-60a1-4799-a997-a2530d060583 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  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.1
  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 May 22 22:46:15 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputSleep Button KEYBOARD, id 7
   inputVirtualBox mouse integration TOUCHSCREEN, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImExPS/2 Generic Explorer Mouse MOUSE, id 10
  xserver.errors:
   AIGLX error: vboxvideo does not export required DRI extension
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: vboxvideo

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1322246/+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 997440] Re: Mouse cursor disappears when mouse integration is disabled in Virtualbox

2015-02-18 Thread Nicole
This happened to me too when I disabled mouse capture. The mouse cursor
outside of virtualbox became stuck in one place (because I disabled it)
and the new mouse pointer in virtual box becomes invisible. The best
thing to fix this problem is to actually use an external device, such as
a pc contoller with analog sticks. So, plug in your pc controller of
whatever external device you want first, then download a free program
called JoyToKey or something similar ( I would suggest JoyToKey, it
works perfectly). Now, open JoyToKey and map your keyboard keys, like
w,a,s,d or up, down, left, right and left and right mouse clicks,
including middle mouse roll onto your pc controller. Next, open
virtualbox (disable capture). This way, at least now you can move the
pointer that was stuck initially in one place with your pc controller.
So, if you want to use in Unity3d, open Unity3d now. Move your pointer
using your external device, try to preview a game you made, and now you
can look around using the mouse!

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

Title:
  Mouse cursor disappears when mouse integration is disabled in
  Virtualbox

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Currently in 12.04 Precise Pangolin, left-edge reveal for an auto-
  hidden launcher does not work within Virtualbox, possibly due to how
  Virtualbox captures the mouse pointer (bug 971018). A work-around for
  this issue to Machine - Disable Mouse Integration. This makes the
  edge reveal behaviour for the launcher work correctly, but
  unfortunately, the mouse cursor disappears.

  Kernel version is: Ubuntu 3.2.0-24.37-generic 3.2.14
  lspci output is attached.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 
82801AA-ICH]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yubink 1650 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 21'
 Mixer name : 'SigmaTel STAC9700,83,84'
 Components : 'AC97a:83847600'
 Controls  : 34
 Simple ctrls  : 24
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=7ec668cf-c6c7-4936-9b27-6c71bec02f26
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=e89567a6-457e-434d-8f2a-df9760452d50 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  Tags:  precise precise
  Uname: Linux 3.2.0-24-generic i686
  UpgradeStatus: Upgraded to precise on 2012-05-03 (6 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/997440/+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 997440] Re: Mouse cursor disappears when mouse integration is disabled in Virtualbox

2015-02-18 Thread Nicole
I forgot to mention, also of course map the mouse movements to the
controller too.  (what you use to move a mouse around, the axis)  I
mapped mine to the analog sticks, so I can move the mouse pointer with
the analog sticks.

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

Title:
  Mouse cursor disappears when mouse integration is disabled in
  Virtualbox

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Currently in 12.04 Precise Pangolin, left-edge reveal for an auto-
  hidden launcher does not work within Virtualbox, possibly due to how
  Virtualbox captures the mouse pointer (bug 971018). A work-around for
  this issue to Machine - Disable Mouse Integration. This makes the
  edge reveal behaviour for the launcher work correctly, but
  unfortunately, the mouse cursor disappears.

  Kernel version is: Ubuntu 3.2.0-24.37-generic 3.2.14
  lspci output is attached.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 
82801AA-ICH]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yubink 1650 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 21'
 Mixer name : 'SigmaTel STAC9700,83,84'
 Components : 'AC97a:83847600'
 Controls  : 34
 Simple ctrls  : 24
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=7ec668cf-c6c7-4936-9b27-6c71bec02f26
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=e89567a6-457e-434d-8f2a-df9760452d50 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  Tags:  precise precise
  Uname: Linux 3.2.0-24-generic i686
  UpgradeStatus: Upgraded to precise on 2012-05-03 (6 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/997440/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service

2015-02-18 Thread Michael
** Changed in: systemd-shim (Ubuntu)
   Status: Triaged = New

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

Title:
  [7.287663] systemd-logind[1057]: Failed to start unit
  user@126.service: Unknown unit: user@126.service

Status in systemd-shim package in Ubuntu:
  New
Status in systemd-shim package in Debian:
  New

Bug description:
  ATTENTION: This bug is fully understood, there is *no need* to add
  even more comments about me too here.

  [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: 
Unknown unit: user@126.service
  [7.287677] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@126.service
  [7.293871] systemd-logind[1057]: New session c1 of user lightdm.
  [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/126/X11-display.
  [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team
  [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
  [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready
  [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec
  [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3)
  [9.920181] wlan0: authenticated
  [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3)
  [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 
status=0 aid=2)
  [9.927753] wlan0: associated
  [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [   12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope
  [   12.677122] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc1_2escope
  [   12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: 
Unknown unit: user@1000.service
  [   12.683912] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@1000.service
  [   12.685157] systemd-logind[1057]: New session c2 of user caravena.
  [   12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
  [  234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope
  [  234.494478] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc2_2escope
  [  235.514349] systemd-logind[1057]: New session c3 of user lightdm.
  [  244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope
  [  244.245923] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc3_2escope

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-7ubuntu4 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 20 18:26:06 2014
  InstallationDate: Installed on 2014-04-27 (115 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+subscriptions

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


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

2015-02-18 Thread Mathew Hodson
** Changed in: zeitgeist (Ubuntu)
   Status: In Progress = Confirmed

** Changed in: zeitgeist (Ubuntu Trusty)
   Status: In Progress = Confirmed

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

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

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

  [Regression Potential]

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

  ---

  [Impact]

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

  [Test Case]

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

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

  [Regression Potential]

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

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

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


[Dx-packages] [Bug 1302885] Re: Media keyboard shortcuts not working

2015-02-18 Thread quequotion
defaria

I think you may have encountered what I was getting at in #32

GNOME has tied hotkey support into gnome-shell, such that hotkeys no
longer work without gnome-shell in any gnome-derivative desktops (like
Unity).

The GNOME team has provided a utility to restore hotkey support without
gnome-shell: gnome-fallback-media-keys-helper

At the moment, the only Ubuntu package available is in the Zorion OS PPA:
https://launchpad.net/~zorin-os/+archive/ubuntu/packages

Rather than add the whole PPA, it's probably a better idea to download
the one package and install it with dpkg.

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

Title:
  Media keyboard shortcuts not working

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume
  up/down to Volume up/down, but when I press the Volume keys on the
  keyboard nothing happens.

  I have noticed the same problem with other keys on my Logitech Internet 350 
keyboard with Tools, Mail, and HomePage.
  They can all be mapped with Keyboard Shortcuts, but nothing happens 
afterwards when the keyboard key is pressed.

  All these keyboard settings worked fine in older versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 23:49:58 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-04-02 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 30.0-0ubuntu4

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

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


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

2015-02-18 Thread Ted Gould
Okay, to recreate. Start up the device. Send this from ADB shell:

gdbus call --session --dest com.ubuntu.Postal --object-path
/com/ubuntu/Postal/com_2eubuntu_2edeveloper_2ewebapps_2ewebapp_2dtwitter
--method com.ubuntu.Postal.Post com.ubuntu.developer.webapps.webapp-
twitter_webapp-twitter '{\message\: \foobar\,
\notification\:{\card\: {\summary\: \yes\, \body\: \hello\,
\popup\: true, \persist\: true}}}'

Then on the messaging menu select Clear All. Notice the tweet is
removed from the list but the envelope remains signaling new messages.

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

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

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

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

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

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


[Dx-packages] [Bug 425823] Re: Notifications not always visible

2015-02-18 Thread Alberts Muktupāvels
** Branch linked: lp:~albertsmuktupavels/metacity/lp1403583

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

Title:
  Notifications not always visible

Status in The Metacity Window Manager:
  New
Status in notify-osd package in Ubuntu:
  Invalid

Bug description:
  Sometimes, part of, or the whole notifiction does not show up, while
  hoovering over it, it becomes clearly visible.

  Howto reproduce: to be honest: I have no idea
  What seems to work (sometimes): 
  use notify-send to display a big image (in the screenshot a jpg of 40.5 kb 
with res 600x600px) and before it loads load a long loading page in firefox

  on terminal : sleep 4  notify-send Title Body text -i
  /path/to/big/image, go to firefox and load planet.ubuntu.com (for
  example)

  I'm using metacity with compositor, notify-osd 0.9.20-0ubuntu1, latest
  karmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/metacity/+bug/425823/+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 425823] Re: Notifications not always visible

2015-02-18 Thread Bug Watch Updater
** Changed in: metacity
   Status: New = Fix Released

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

Title:
  Notifications not always visible

Status in The Metacity Window Manager:
  Fix Released
Status in notify-osd package in Ubuntu:
  Invalid

Bug description:
  Sometimes, part of, or the whole notifiction does not show up, while
  hoovering over it, it becomes clearly visible.

  Howto reproduce: to be honest: I have no idea
  What seems to work (sometimes): 
  use notify-send to display a big image (in the screenshot a jpg of 40.5 kb 
with res 600x600px) and before it loads load a long loading page in firefox

  on terminal : sleep 4  notify-send Title Body text -i
  /path/to/big/image, go to firefox and load planet.ubuntu.com (for
  example)

  I'm using metacity with compositor, notify-osd 0.9.20-0ubuntu1, latest
  karmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/metacity/+bug/425823/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service

2015-02-18 Thread Martin Pitt
** Changed in: systemd-shim (Ubuntu)
   Status: New = Triaged

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

Title:
  [7.287663] systemd-logind[1057]: Failed to start unit
  user@126.service: Unknown unit: user@126.service

Status in systemd-shim package in Ubuntu:
  Triaged
Status in systemd-shim package in Debian:
  New

Bug description:
  ATTENTION: This bug is fully understood, there is *no need* to add
  even more comments about me too here.

  [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: 
Unknown unit: user@126.service
  [7.287677] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@126.service
  [7.293871] systemd-logind[1057]: New session c1 of user lightdm.
  [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/126/X11-display.
  [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team
  [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
  [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready
  [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec
  [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3)
  [9.920181] wlan0: authenticated
  [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3)
  [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 
status=0 aid=2)
  [9.927753] wlan0: associated
  [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [   12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope
  [   12.677122] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc1_2escope
  [   12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: 
Unknown unit: user@1000.service
  [   12.683912] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@1000.service
  [   12.685157] systemd-logind[1057]: New session c2 of user caravena.
  [   12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
  [  234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope
  [  234.494478] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc2_2escope
  [  235.514349] systemd-logind[1057]: New session c3 of user lightdm.
  [  244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope
  [  244.245923] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc3_2escope

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-7ubuntu4 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 20 18:26:06 2014
  InstallationDate: Installed on 2014-04-27 (115 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+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 1423463] [NEW] package unity 7.2.2+14.04.20140714-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/compiz/libunityshell.so' to '/usr/lib/compiz/libunity

2015-02-18 Thread Elemer
Public bug reported:

Brand new install of ubuntu 14.04.1 amd64 on a Dell Inspiron N5110 and
was just doing an update and the software updater gave me this error for
a package

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
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
Date: Thu Feb 19 07:11:54 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DuplicateSignature: package:unity:7.2.2+14.04.20140714-0ubuntu1:cannot copy 
extracted data for './usr/lib/compiz/libunityshell.so' to 
'/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/compiz/libunityshell.so' to 
'/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or stream
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:04b0]
InstallationDate: Installed on 2015-02-18 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: Dell Inc. Inspiron N5110
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=cd239b5b-1946-412e-b58d-290c1970af38 ro quiet splash vt.handoff=7
SourcePackage: unity
Title: package unity 7.2.2+14.04.20140714-0ubuntu1 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/compiz/libunityshell.so' to 
'/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 034W60
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
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.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Feb 19 04:23:36 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   21569 
 vendor SEC
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-package 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/1423463

Title:
  package unity 7.2.2+14.04.20140714-0ubuntu1 failed to install/upgrade:
  cannot copy extracted data for './usr/lib/compiz/libunityshell.so' to
  '/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or
  stream

Status in unity package in Ubuntu:
  New

Bug description:
  Brand new install of ubuntu 14.04.1 amd64 on a Dell Inspiron N5110 and
  was just doing an update and the software updater gave me this error
  for a package

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  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
  Date: Thu Feb 19 07:11:54 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:unity:7.2.2+14.04.20140714-0ubuntu1:cannot copy 
extracted data for './usr/lib/compiz/libunityshell.so' to 

[Dx-packages] [Bug 1218019] Re: Missing close button in spread when window is in fullscreen

2015-02-18 Thread Launchpad Bug Tracker
[Expired for unity (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Missing close button in spread when window is in fullscreen

Status in Unity:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  When a window is in fullscreen and you open the spread view it doesn't
  show a close button. See the image. This happens also when  suing
  alt+tab switcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1218019/+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 1218019] Re: Missing close button in spread when window is in fullscreen

2015-02-18 Thread Launchpad Bug Tracker
[Expired for Unity because there has been no activity for 60 days.]

** Changed in: unity
   Status: Incomplete = Expired

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

Title:
  Missing close button in spread when window is in fullscreen

Status in Unity:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  When a window is in fullscreen and you open the spread view it doesn't
  show a close button. See the image. This happens also when  suing
  alt+tab switcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1218019/+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 1423463] Re: package unity 7.2.2+14.04.20140714-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/compiz/libunityshell.so' to '/usr/lib/compiz/libunitysh

2015-02-18 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package unity 7.2.2+14.04.20140714-0ubuntu1 failed to install/upgrade:
  cannot copy extracted data for './usr/lib/compiz/libunityshell.so' to
  '/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or
  stream

Status in unity package in Ubuntu:
  New

Bug description:
  Brand new install of ubuntu 14.04.1 amd64 on a Dell Inspiron N5110 and
  was just doing an update and the software updater gave me this error
  for a package

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  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
  Date: Thu Feb 19 07:11:54 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:unity:7.2.2+14.04.20140714-0ubuntu1:cannot copy 
extracted data for './usr/lib/compiz/libunityshell.so' to 
'/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/compiz/libunityshell.so' to 
'/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or stream
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04b0]
  InstallationDate: Installed on 2015-02-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=cd239b5b-1946-412e-b58d-290c1970af38 ro quiet splash vt.handoff=7
  SourcePackage: unity
  Title: package unity 7.2.2+14.04.20140714-0ubuntu1 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/compiz/libunityshell.so' to 
'/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 034W60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Feb 19 04:23:36 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   21569 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1423463/+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 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account

2015-02-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nss-pam-ldapd (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/1314095

Title:
  Unity Lockscreen in 14.04 can't unlock when using LDAP account

Status in Unity:
  Confirmed
Status in nss-pam-ldapd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in nss-pam-ldapd package in Debian:
  Fix Released

Bug description:
  SRU justification:

  [Impact]

  * Summary: in Trusty, when libnss-ldapd is used, LDAP users are not
  able to unlock the Unity lockscreen. Utopic and later are not
  affected. Some workarounds are listed in comment #29.

  * nslcd in Trusty and earlier does not permit unprivileged users to
  read shadow entries. When invoked by the Unity lockscreen, running as
  the logged-in user, pam_unix returns PAM_AUTHINFO_UNAVAIL in
  pam_acct_mgmt when it tries to get password expiry information from
  shadow. This leads to an authorization failure, so Unity refuses to
  unlock the screen. pam_ldap is not consulted for pam_acct_mgmt after
  pam_unix fails because its rule is in the Additional section.

  * In Utopic and later, nslcd returns partial shadow entries to
  unprivileged users. This is enough for the expiry check in pam_unix to
  succeed, so the screen can be unlocked. See
  http://bugs.debian.org/706913 for a discussion of the upstream fix.

  * This proposed SRU backports the upstream solution to Trusty's nslcd.
  This is a change of behaviour for shadow queries from unprivileged
  users, compared to the current package. An alternative, more targeted
  fix would be to change Unity to ignore AUTHINFO_UNAVAIL results from
  pam_acct_mgmt, like gnome-screensaver already does (see comment #29).
  The nslcd change is a more general fix for not just Unity, but any
  PAM-using program run by an unprivileged user.

  [Test Case]

  * Install and configure libnss-ldapd. Ensure ldap is enabled for at
  least the passwd and shadow services in /etc/nsswitch.conf.

  * Log into Unity as an LDAP user, lock the screen, and then try to
  unlock it again.

  [Regression Potential]

  * The patch is minimal, was written by the upstream author, and was
  backported (adjusting for whitespace changes) to Trusty. The change
  has already been released in Utopic and will be included in Debian
  Jessie as well.

  * Regression testing should include checking that shadow queries, both
  by name and for listing all users, are unchanged when issued as root.

  [Other Info]

  * Packages for testing are available in ppa:rtandy/lp1314095

  Original description:

  My setup is:

  Ubuntu 14.04 LTS,
  ldap accounts,
  krb5 authentication,
  Lightdm,
  Unity session

  ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent 
passwd and getent shadow works fine.
  I am able to login in console without any problems.
  I was able to login in lightdm.
  Then I used the lock screen.
  I could not disable the lock screen using my password.
  I rebooted my computer.

  Now:
  After logging in through lightdm, the unity lockscreen locks the screen 
immediately and I can not disable it using my password.

  From my short inspection of auth.log and unix_chkpwd sources it seems,
  that unix_chkpwd works fine when called from lightdm and fails to get
  user info when called from unity lockscreen.

  lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  apt-cache policy unity lightdm libpam-modules
  unity:
    Installed: 7.2.0+14.04.20140416-0ubuntu1
    Candidate: 7.2.0+14.04.20140416-0ubuntu1
    Version table:
   *** 7.2.0+14.04.20140416-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  lightdm:
    Installed: 1.10.0-0ubuntu3
    Candidate: 1.10.0-0ubuntu3
    Version table:
   *** 1.10.0-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  libpam-modules:
    Installed: 1.1.8-1ubuntu2
    Candidate: 1.1.8-1ubuntu2
    Version table:
   *** 1.1.8-1ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Contents of /var/log/auth.log:

  Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement 
user ingroup nopasswdlogin not met by user user
  Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication 
failure; logname= uid=0 euid=0 tty=:2 ruser= rhost=  user=user
  Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown
  Apr 29 

[Dx-packages] [Bug 1417188] Re: Shell frozen/crashed when alarm triggered

2015-02-18 Thread Albert Astals Cid
I've moved the Canonical System Image bug to incomplete too so that
the bug expires in 59 days if no more information is given since with
the current information it can't really be fixed.

If i overstepped and we want it open even if we have no ways to
reproduce/information on how to fix please revert back and accept my
apologies.

** Changed in: canonical-devices-system-image
   Status: New = Incomplete

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

Title:
  Shell frozen/crashed when alarm triggered

Status in the base for Ubuntu mobile products:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  rtm build 224 on krillin

  - I set an alarm for 9am with the clock app and then went to bed
  - The alarm was ringing in the morning
  - The phone screen was black
  - I pressed the power button to turn on the screen and there was no 
notification on the screen, just the greeter
  - The shell was completely frozen. I couldn't unlock or do anything, yet the 
alarm played on

  I had to hold down the power key to hard boot the phone as there was
  no way to silence the alarm, the volume keys were not working either.

  Found the attached crash file in /var/crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417188/+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 1423394] Re: Unity Desktop Crashes when using Google Chrome Browser

2015-02-18 Thread Stephen M. Webb
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:

  apport-collect 1423394

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Unity Desktop Crashes when using Google Chrome Browser

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1.) Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2.) google-chrome-stable:
Installed: 40.0.2214.111-1
Candidate: 40.0.2214.111-1
Version table:
   *** 40.0.2214.111-1 0
  500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
  100 /var/lib/dpkg/status

  3.) Expect to see video play and no crashing.

  4.) When using Google Chrome (current version 40.0.2214.111 (64-bit))
  and attempting to watch any Youtube video, the Unity Desktop
  experiences a crash and the Unity Desktop (unity start/search and task
  bar) disappear. I am unable to launch a terminal window. All Window
  menus disappear (i.e. Minimize, Maximize, Close) including those that
  are related to the top right shutdown/restart/logoff menu. Desktop
  background remains viewable and Desktop icons are also viewable.
  Keyboard input starts to malfunction in window sections.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1423394/+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 1416520] Re: vivid: Sound indicator pops up on initial boot after a flash

2015-02-18 Thread Ted Gould
** Branch linked: lp:~ted/indicator-sound/volume-reason

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

Title:
  vivid: Sound indicator pops up on initial boot after a flash

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash vivid 84+ onto you mako/manta/flo
  2. When the welcome wizard start run though it
  3. At some point in the wizard or just after the volume osd with popup

  EXPECTED:
  I don't expect to the the indicator popup randomly

  ACTUAL:
  At some point in the boot process post flash the sound indicator osd pops up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1416520/+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 1367818] Re: Silent Mode causes no indication of a change in [icon] state.

2015-02-18 Thread Ted Gould
** Changed in: indicator-sound (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  Silent Mode causes no indication of a change in [icon] state.

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  New
Status in indicator-sound package in Ubuntu:
  Fix Released

Bug description:
  - When the sound is muted, the volume icon to the left of the volume slider 
should have a red / running through it.
  - Add an explicit Mute button to the sound indicator menu.
  - Pressing and holding the icon to the left of the volume slider should mute 
volume straight away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+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