[Dx-packages] [Bug 1322865] Re: Calendar keeps highlighting the day when the system was booted rather than the current date

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 793450
   When the datetime-indicator's menu becomes visible, the Calendar isn't 
always focused on 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/1322865

Title:
  Calendar keeps highlighting the day when the system was booted rather
  than the current date

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

Bug description:
  Steps to reproduce:
  - boot
  - wait at least one day
  - click on the clock to display the datetime widget

  Expected: the date shown in text and the day highlighted in the
  calendar widget should be consistent and both should correspond to the
  current date

  Observed: the date shown as text on the top is correct (current date),
  but the one highlighted on the calendar remains the one when the
  system was booted!!

  See screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat May 24 17:00:41 2014
  InstallationDate: Installed on 2013-10-11 (224 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (90 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1322865/+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 1317649] Re: When clearing messages from greeter, it should sync to session

[Charles Kerr]

** Changed in: indicator-messages (Ubuntu)
   Status: New = Triaged

** Changed in: indicator-messages (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  When clearing messages from greeter, it should sync to session

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

Bug description:
  Testing split greeter on the phone, when I clear messages from the
  greeter's copy of indicator-messages, it should clear it from the
  user's session too.

  Here's how to test split greeter:
  $ ubuntu-device-flash --channel=devel-proposed
  $ adb shell
  # add-apt-repository -y ppa:ci-train-ppa-service/landing-002
  # apt-get update
  # apt-get dist-upgrade
  # exit
  $ adb reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1317649/+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 1319955] Re: indicator-sound disappeared

[Charles Kerr]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

Title:
  indicator-sound disappeared

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

Bug description:
  When I log in, indicator-sound isn't shown. It is present on the login
  screen, however. there appear to be reports in /var/crash, so I guess
  it crashed at some point. I would have expected it to get restarted
  though. Neither logging out and back in again, nor rebooting, have had
  any effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute': 
(true, '', [false]), 'phone-settings': (true, '', []), 'mic-volume': (true, 
'', [0.196075439453125]), 'scroll': (true, 'i', []), 'vlc.desktop': (true, 
'', [{'running': false, 'state': 'Paused'}]), 'previous.vlc.desktop': 
(true, '', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, 
'', [{'running': false, 'state': 'Paused'}]), 
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i', 
[0.2928619384765625]), 'play-playlist.vlc.desktop': (true, 's', []), 'root': 
(true, '', [{'title': 'Sound', 'accessible-desc': 'Volume (29%)', 'icon': 
('themed', ['audio-volume-low-panel', 'audio-volume-low', 'audio-volume', 
'audio']), 'visible': false}]), 'play.rhythmbox.desktop': (true, '', 
['Paused']), 'play-playlist.rhythmbox.desktop': (true, 's', []), 
'next.rhythmbox.desktop': (true, '', []), 'play.vlc.desktop': (true, '', 
['Paused'])},)
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 15 15:00:51 2014
  InstallationDate: Installed on 2013-01-12 (487 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  SourcePackage: indicator-sound
  UpgradeStatus: Upgraded to trusty on 2014-05-08 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1319955/+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 1321777] Re: Split greeter shows three batteries entries on manta

[Charles Kerr]

mterry, I don't have the scrollback handy, but the upower dump that you
provided in irc showed that upower actually /was/ reporting three
batteries, so indicator-power is passing that along.

Maybe we could put some heuristics into indicator-power for guessing
when multiple upower devices are actually the same device, but that runs
the risk of new bugs folding genuine devices together too.

IMO this would be better handled at the upower level.

** Package changed: indicator-power (Ubuntu) = upower (Ubuntu)

** Changed in: upower (Ubuntu)
 Assignee: Ted Gould (ted) = (unassigned)

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

Title:
  Split greeter shows three batteries entries on manta

Status in “upower” package in Ubuntu:
  New

Bug description:
  Pull down the power indicator on manta in split greeter mode and you
  see three battery entries.  Doesn't seem right.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1321777/+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 1323050] Re: Natural scrolling reverts without unchecking box

[Andrea Azzarone]

** Also affects: unity-settings-daemon
   Importance: Undecided
   Status: New

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

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

Title:
  Natural scrolling reverts without unchecking box

Status in Unity Settings Daemon:
  New
Status in “unity” package in Ubuntu:
  Invalid
Status in “unity-settings-daemon” package in Ubuntu:
  New

Bug description:
  I have installed Ubuntu 14.04 on my Thinkpad W510.

  The first thing I do, post-install, is enable natural scrolling.

  It works for a while, but eventually (possibly after a reboot), my
  machine reverts to classic scrolling direction, even though I still
  have the natural scrolling button checked in mouse preferences.

  If I *uncheck* the natural scrolling box, it then goes back to natural
  scrolling.

  I've re-installed Ubuntu 14.04 and fully updated before checking the
  natural scrolling box again, and gotten the same behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-settings-daemon/+bug/1323050/+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 1218810] Re: video switch hot key will return super key and p and no response to switch video mode

[Taihsiang Ho]

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

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

** Tags removed: verification-needed-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/1218810

Title:
  video switch hot key will return super key and p and no response to
  switch video mode

Status in “linux” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  New
Status in “linux” source package in Precise:
  New
Status in “unity” source package in Precise:
  New
Status in “linux” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  CID 201209-11735

  For some machines, for example, HP laptop HP 1000 has a hot key on F4 to 
perform the shorcut super + p to switch video modes.
  Use command sudo showkey -k to capture the key code of the hot key you will 
see the key code of super key and p
  This key combination is expected to change the video mode.

  
  platfrom: HP laptop HP 1000
  image: 12.04.3

  Steps to reproduce:
  1. open an terminal, 
  2. plugin an external monitor
  3. press the video switch hotkey, for HP 1000 it is the F4 key

  Expected result:
  1. Video mode is changed by the hotkey
  2. no character is printed on terminal

  Actual result
  1. Video mode is not changed.
  2. a p will be printed on the terminal screen

  The other information:
  1. A similar bug was reported on LP:#539477 before.
  2. The hotkey in 13.04 works

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified: 
boot/vmlinuz-3.8.0-29-generic]
  ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  Date: Fri Aug 30 17:34:56 2013
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-raring
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-29-generic.
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1675 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x6360 irq 47'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,103c1855,00100202 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  CurrentDmesg:
   [   45.884915] ISO 9660 Extensions: RRIP_1991A
   [   60.442781] audit_printk_skb: 3 callbacks suppressed
   [   60.442785] type=1400 audit(1378093422.964:31): apparmor=DENIED 
operation=open parent=1 profile=/usr/lib/telepathy/mission-control-5 
name=/usr/share/gvfs/remote-volume-monitors/ pid=1849 comm=mission-control 
requested_mask=r denied_mask=r fsuid=1000 ouid=0
   [   65.385488] r8169 :0e:00.0 eth0: link up
   [   65.385510] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=932733cb-db60-4153-8565-3e3ccb1a6f6d
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  Lsusb:
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 05c8:0223 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
  MachineType: Hewlett-Packard HP 1000 Notebook PC
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=770667e1-92a4-4f2e-a434-b9998d55cb30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware1.79.6
  Tags:  precise running-unity
  Uname: Linux 3.8.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/25/2012
  

[Dx-packages] [Bug 1319339] Re: Unity lock screen - please fix password input delay.

[Andrea Azzarone]

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

** This bug has been marked a duplicate of bug 1308265
   First password letter not registered in lockscreen if screen off

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

Title:
  Unity lock screen - please fix password input delay.

Status in “unity” package in Ubuntu:
  New

Bug description:
  Before 14.04:
  I could type password and press enter to log on even when displays were still 
sleeping.

  in 14.04:
  The first keypresses are never registered, tping PW directly+enter gives 
wrong password (and too few dots appear in the PW field)
  now I furst need to wake the computer, by pressing other kays like arrows, 
then enter PW.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1319339/+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 1319283] Re: unity screensaver lockup/crash

[Andrea Azzarone]

Can you provide a backtrack of the crash? Thanks.

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

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

** Tags added: lockscreen

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

Title:
  unity screensaver lockup/crash

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

Bug description:
  I have seen several instances where resuming from suspend results in a 
slightly corrupted unity screensaver/lockscreen. Login is impossible. 
  Sometimes it crashes after a few minutes and restarts and all is ok. Other 
times it crashes after a few minutes and simply unlocks the screen, though this 
is often accompanies by no unity windowmanager running in the desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 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-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Tue May 13 21:01:18 2014
  DistUpgraded: 2014-04-17 13:16:06,322 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107GLM [Quadro K1000M] [10de:0ffc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:21f6]
  InstallationDate: Installed on 2013-07-05 (311 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: LENOVO 24491D1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (26 days ago)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24491D1
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET96WW(2.56):bd11/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 24491D1
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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
  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  8 19:16:07 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1319283/+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 1316005] Re: Panel shadow appears over full screen applications

[Christopher Townsend]

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

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

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

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

** Summary changed:

- Panel shadow appears over full screen applications
+ Panel shadow appears over full screen applications w/ locally integrated 
menus enabled

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

Title:
  Panel shadow appears over full screen applications w/ locally
  integrated menus enabled

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

Bug description:
  The shadow of the top Unity panel draws over full screen applications
  that have controls visible when the mouse is moved.

  Steps to reproduce:

  1) Open an image in Image Viewer
  2) Double click the image to full-screen it
  3) Move the mouse to the top of the screen to access the controls

  Expected behavior:

  Only the image and the Image Viewer controls should be visible

  Acutal behavior:

  The Unity panel shadow is drawn on top of the controls at the top of
  the screen

  Notes:

  This also appears in the Videos application, but does not in VLC or
  gimp. I believe it is GTK applications with UI elements that only
  appear on mouse movement (gimp's UI is static, and I believe VLC is Qt
  based).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-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-19ubuntu1)
  .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.14.1-0ubuntu3
  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: Sun May  4 22:37:44 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:2117]
  InstallationDate: Installed on 2014-04-19 (15 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. G55VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=927ff2bd-c81d-4a5d-9acb-3bd3dd820e35 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G55VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G55VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G55VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11+14.04.20140409-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-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  

[Dx-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account

[Jan Groenewald]

Same behavior on ldap without kerberos.

root@muizenberg:~# lsb_release -d; apt-cache policy unity lightdm 
libpam-modules|grep Installed; grep unix_chkpwd /var/log/auth.log|tail -3
Description:Ubuntu 14.04 LTS
  Installed: 7.2.0+14.04.20140423-0ubuntu1.2
  Installed: 1.10.1-0ubuntu1
  Installed: 1.1.8-1ubuntu2
May 27 09:07:11 muizenberg unix_chkpwd[4186]: check pass; user unknown
May 27 09:07:11 muizenberg unix_chkpwd[4186]: password check failed for user 
(jan)
May 27 09:07:11 muizenberg unix_chkpwd[4187]: could not obtain user info (jan)

Workaround in #2 also works for me.

-- 
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 “unity” package in Ubuntu:
  Confirmed

Bug 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 06:49:37 localhost unix_chkpwd[15825]: password check failed for user 
(user)
  Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication 
failure; logname= uid=1001 euid=1001 tty= ruser= rhost=  user=user
  Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement 
user ingroup nopasswdlogin not met by user user

  cat /etc/pam.d/common-auth 
  account requiredpam_unix.so
  authrequiredpam_group.so
  auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure
  auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200
  authrequisite   pam_deny.so
  authrequiredpam_permit.so

  authoptionalpam_afs_session.so minimum_uid=200
  authoptionalpam_ecryptfs.so unwrap
  authoptionalpam_cap.so

  cat /etc/pam.d/common-account 
  account requiredpam_unix.so

  cat /etc/pam.d/lightdm
  authrequisite   pam_nologin.so
  authsufficient  pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  authoptionalpam_gnome_keyring.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  authoptionalpam_group.so
  session requiredpam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optionalpam_gnome_keyring.so auto_start
  session requiredpam_env.so readenv=1
  session requiredpam_env.so 

[Dx-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen

[Andrea Azzarone]

** Changed in: unity
 Assignee: (unassigned) = Andrea Azzarone (andyrock)

** Changed in: unity-greeter (Ubuntu)
 Assignee: (unassigned) = Andrea Azzarone (andyrock)

** Changed in: unity-greeter (Ubuntu)
   Status: New = Invalid

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

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

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

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

Title:
  Allow a distinct pam config file for greeter and for lock-screen

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress
Status in “unity-greeter” package in Ubuntu:
  Invalid

Bug description:
  It might be desirable to have a distinct pam config file when logging
  in and when unlocking the screen. Specifically, using a fingerprint
  reader is fine for sudo or for unlocking, but you want to use your
  password when logging in, to provide a secret and be able to unlock
  the gnome-keyring for example.

  See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific-
  pam-config-in-the-lockscreen

  So this feature request is about allowing for a (optional) pam config
  file for the lock-screen, distinct from the /etc/pam.d/lightdm
  currently used and shared with the greeter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1305440/+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 1319283] Re: unity screensaver lockup/crash

[Anton Piatek]

Sure, How?

On 27 May 2014 08:21, Andrea Azzarone 1319...@bugs.launchpad.net wrote:
 Can you provide a backtrack of the crash? Thanks.

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

 ** Changed in: unity
Status: New = Invalid

 ** Changed in: unity (Ubuntu)
Status: New = Invalid

 ** Tags added: lockscreen

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1319283

 Title:
   unity screensaver lockup/crash

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


-- 
Anton Piatek
email: an...@piatek.co.uk
blog/photos:http://www.strangeparty.com
pgp: [74B1FA37](http://www.strangeparty.com/anton.asc)

No trees were destroyed in the sending of this message, however, a
significant number of electrons were terribly inconvenienced.

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

Title:
  unity screensaver lockup/crash

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

Bug description:
  I have seen several instances where resuming from suspend results in a 
slightly corrupted unity screensaver/lockscreen. Login is impossible. 
  Sometimes it crashes after a few minutes and restarts and all is ok. Other 
times it crashes after a few minutes and simply unlocks the screen, though this 
is often accompanies by no unity windowmanager running in the desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 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-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Tue May 13 21:01:18 2014
  DistUpgraded: 2014-04-17 13:16:06,322 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107GLM [Quadro K1000M] [10de:0ffc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:21f6]
  InstallationDate: Installed on 2013-07-05 (311 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: LENOVO 24491D1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (26 days ago)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24491D1
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET96WW(2.56):bd11/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 24491D1
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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
  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  8 19:16:07 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1319283/+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 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen

[Andrea Azzarone]

** Tags added: lockscreen

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

Title:
  Allow a distinct pam config file for greeter and for lock-screen

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress
Status in “unity-greeter” package in Ubuntu:
  Invalid

Bug description:
  It might be desirable to have a distinct pam config file when logging
  in and when unlocking the screen. Specifically, using a fingerprint
  reader is fine for sudo or for unlocking, but you want to use your
  password when logging in, to provide a secret and be able to unlock
  the gnome-keyring for example.

  See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific-
  pam-config-in-the-lockscreen

  So this feature request is about allowing for a (optional) pam config
  file for the lock-screen, distinct from the /etc/pam.d/lightdm
  currently used and shared with the greeter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1305440/+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 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen

[Launchpad Bug Tracker]

** Branch linked: lp:~andyrock/unity/fix-lp-1305440

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

Title:
  Allow a distinct pam config file for greeter and for lock-screen

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress
Status in “unity-greeter” package in Ubuntu:
  Invalid

Bug description:
  It might be desirable to have a distinct pam config file when logging
  in and when unlocking the screen. Specifically, using a fingerprint
  reader is fine for sudo or for unlocking, but you want to use your
  password when logging in, to provide a secret and be able to unlock
  the gnome-keyring for example.

  See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific-
  pam-config-in-the-lockscreen

  So this feature request is about allowing for a (optional) pam config
  file for the lock-screen, distinct from the /etc/pam.d/lightdm
  currently used and shared with the greeter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1305440/+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 1319283] Re: unity screensaver lockup/crash

[Anton Piatek]

** Changed in: unity (Ubuntu)
   Status: Invalid = New

** Changed in: unity
   Status: Invalid = New

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

Title:
  unity screensaver lockup/crash

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

Bug description:
  I have seen several instances where resuming from suspend results in a 
slightly corrupted unity screensaver/lockscreen. Login is impossible. 
  Sometimes it crashes after a few minutes and restarts and all is ok. Other 
times it crashes after a few minutes and simply unlocks the screen, though this 
is often accompanies by no unity windowmanager running in the desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 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-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Tue May 13 21:01:18 2014
  DistUpgraded: 2014-04-17 13:16:06,322 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107GLM [Quadro K1000M] [10de:0ffc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:21f6]
  InstallationDate: Installed on 2013-07-05 (311 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: LENOVO 24491D1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (26 days ago)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24491D1
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET96WW(2.56):bd11/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 24491D1
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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
  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  8 19:16:07 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1319283/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app

[Antti Kaijanmäki]

** Also affects: indicator-network
   Importance: Undecided
   Status: New

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

Title:
  snap decision timeout needs to be determined by the requesting app

Status in Network Menu:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in Unity:
  Triaged
Status in Server and client library for desktop notifications in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity-notifications” package in Ubuntu:
  Confirmed

Bug description:
  Problem:
  If user receives an SMS/call, snap decision for incoming SMS/call stays on 
screen for always only 60sec. and then disappears from screen (by default). 
There was no interaction from user. 

  Possible solution:
  The snap decision should stay on screen for the amount of time the app asks 
it to, being always app dependant. 
  A 60sec. time-out is too short due to use cases where an action from user is 
mandatory. 

  Use case example: A class 1/2 SMS arrives after user triggered a USSD
  command from dialer. These type of SMS always requires a response from
  user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is
  too short because it can be missed and these type of SMS is NOT saved
  into the usual messages thread.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1295762/+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 1295762] Re: snap decision timeout needs to be determined by the requesting app

[Antti Kaijanmäki]

** Branch linked: lp:~unity-api-team/indicator-network/devel

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

Title:
  snap decision timeout needs to be determined by the requesting app

Status in Network Menu:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in Unity:
  Triaged
Status in Server and client library for desktop notifications in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity-notifications” package in Ubuntu:
  Confirmed

Bug description:
  Problem:
  If user receives an SMS/call, snap decision for incoming SMS/call stays on 
screen for always only 60sec. and then disappears from screen (by default). 
There was no interaction from user. 

  Possible solution:
  The snap decision should stay on screen for the amount of time the app asks 
it to, being always app dependant. 
  A 60sec. time-out is too short due to use cases where an action from user is 
mandatory. 

  Use case example: A class 1/2 SMS arrives after user triggered a USSD
  command from dialer. These type of SMS always requires a response from
  user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is
  too short because it can be missed and these type of SMS is NOT saved
  into the usual messages thread.

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

[Jan Groenewald]

Some reference (marked as WONTFIX)
https://bugzilla.redhat.com/show_bug.cgi?id=638279

Above might suggest a configuration that fixes this: check ldap first in
common-auth, which currently does:

# here are the per-package modules (the Primary block)
auth[success=2 default=ignore]  pam_unix.so nullok_secure
auth[success=1 default=ignore]  pam_ldap.so minimum_uid=1000 
use_first_pass

That should not be a default (having ldap first) but could be a better
workaround than setuid unix_chkpwd ?

** Bug watch added: Red Hat Bugzilla #638279
   https://bugzilla.redhat.com/show_bug.cgi?id=638279

-- 
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 “unity” package in Ubuntu:
  Confirmed

Bug 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 06:49:37 localhost unix_chkpwd[15825]: password check failed for user 
(user)
  Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication 
failure; logname= uid=1001 euid=1001 tty= ruser= rhost=  user=user
  Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement 
user ingroup nopasswdlogin not met by user user

  cat /etc/pam.d/common-auth 
  account requiredpam_unix.so
  authrequiredpam_group.so
  auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure
  auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200
  authrequisite   pam_deny.so
  authrequiredpam_permit.so

  authoptionalpam_afs_session.so minimum_uid=200
  authoptionalpam_ecryptfs.so unwrap
  authoptionalpam_cap.so

  cat /etc/pam.d/common-account 
  account requiredpam_unix.so

  cat /etc/pam.d/lightdm
  authrequisite   pam_nologin.so
  authsufficient  pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  authoptionalpam_gnome_keyring.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  authoptionalpam_group.so
  session requiredpam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optionalpam_gnome_keyring.so auto_start
  session requiredpam_env.so readenv=1
  session 

[Dx-packages] [Bug 1295267] Re: Windows change Monitor/Desktop after screen lock

[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/1295267

Title:
  Windows change Monitor/Desktop after screen lock

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I run a dual monitor configuration, with one portrait and one
  landscape.

  I nearly always have multiple applications open in multiple windows
  across both monitors and all virtual desktops.

  When I lock the screen and then unlock, my application windows will
  move from their original position.

  Sometimes they are in completely random positions;

  Other times they seem to get the monitors confused, and rather than
  being in the top half of the portrait monitor they are on the top half
  of the landscape monitor;

  Sometimes it is only a new desktop, but the monitor position is the
  same;

  Sometimes it is the same desktop, but on the other monitor.

  Description:  Ubuntu 13.10
  Release:  13.10

  What I expect to happen: When I unlock my computer, all the windows
  are in the same position on the same monitor and desktop as I left
  them.

  What actually happens: When I unlock my computer, some or all of the
  windows have been changed to a random position on a random monitor
  and/or desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295267/+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 1295267] Re: Windows change Monitor/Desktop after screen lock

[José Casero Cantos]

Same in 14.04.

My laptop is a Samsung NP900X4C.

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

Title:
  Windows change Monitor/Desktop after screen lock

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I run a dual monitor configuration, with one portrait and one
  landscape.

  I nearly always have multiple applications open in multiple windows
  across both monitors and all virtual desktops.

  When I lock the screen and then unlock, my application windows will
  move from their original position.

  Sometimes they are in completely random positions;

  Other times they seem to get the monitors confused, and rather than
  being in the top half of the portrait monitor they are on the top half
  of the landscape monitor;

  Sometimes it is only a new desktop, but the monitor position is the
  same;

  Sometimes it is the same desktop, but on the other monitor.

  Description:  Ubuntu 13.10
  Release:  13.10

  What I expect to happen: When I unlock my computer, all the windows
  are in the same position on the same monitor and desktop as I left
  them.

  What actually happens: When I unlock my computer, some or all of the
  windows have been changed to a random position on a random monitor
  and/or desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295267/+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 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen

[Andrea Azzarone]

** Changed in: unity
Milestone: None = 7.2.1

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

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

** No longer affects: unity/7.3

** Changed in: unity
Milestone: 7.2.1 = 7.3.0

** Changed in: unity/7.2
Milestone: None = 7.2.1

** Changed in: unity/7.2
   Status: New = In Progress

** Changed in: unity/7.2
 Assignee: (unassigned) = Andrea Azzarone (andyrock)

** Changed in: unity-greeter (Ubuntu)
 Assignee: Andrea Azzarone (andyrock) = (unassigned)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) = Andrea Azzarone (andyrock)

** Changed in: unity/7.2
   Importance: Undecided = Medium

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

Title:
  Allow a distinct pam config file for greeter and for lock-screen

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress
Status in “unity-greeter” package in Ubuntu:
  Invalid

Bug description:
  It might be desirable to have a distinct pam config file when logging
  in and when unlocking the screen. Specifically, using a fingerprint
  reader is fine for sudo or for unlocking, but you want to use your
  password when logging in, to provide a secret and be able to unlock
  the gnome-keyring for example.

  See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific-
  pam-config-in-the-lockscreen

  So this feature request is about allowing for a (optional) pam config
  file for the lock-screen, distinct from the /etc/pam.d/lightdm
  currently used and shared with the greeter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1305440/+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 1304434] Re: indicator-printers not working on Ubuntu 14.04

[Sebastien Bacher]

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

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

** Changed in: indicator-printers (Ubuntu Trusty)
   Status: Confirmed = Triaged

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

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

Title:
  indicator-printers not working on Ubuntu 14.04

Status in Print Indicator:
  In Progress
Status in “indicator-printers” package in Ubuntu:
  In Progress
Status in “indicator-printers” source package in Trusty:
  Triaged

Bug description:
  [Impact]
  The panel should have a print indicator as long as there are any print jobs 
queued or processed. Currently, this indicator never appears, even though 
printing works fine.

  This is because the service that listens to CUPS fails to register its
  D-Bus name (as of revision 68), which results in the panel component
  not finding the service. The attached branch fixes this by making the
  service register the name the panel expects.

  [Test Case]
  Print a document from any application and check whether the print indicator 
appears while it is printing.

  [Regression Potential]
  Almost none. The print indicator is not working at all right now, and the fix 
only touches that indicator.

  [Original Description]
  even after lates updates still no printer notifications in the panel . I 
checked and the package indicator-printers is correctly installed and the 
printer prints without problems. But, there is no notification icons on unity 
panel. I had no problems at all with 13.10 instead

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-printers/+bug/1304434/+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 1315517] Re: Resizing windows is difficult

[Andrea Azzarone]

** Also affects: ayatana-design
   Importance: Undecided
   Status: New

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

** Changed in: unity
   Status: New = Incomplete

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

Title:
  Resizing windows is difficult

Status in Ayatana Design:
  New
Status in Unity:
  Incomplete
Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  I understand that border-less windows are a new hype and most of the
  people find this better and prettier, but sometimes it is very hard to
  resize windows because there is are no borders around the windows.

  When two dark windows overlap, there is very little indication on
  where one window ends and the other begins. Grabbing corners to resize
  such windows is difficult because there is almos no contrast between
  active and inactive window.

  See attached image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1315517/+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 1296715] Re: Menu items are greyed out in Libreoffice menu.

[Björn Michaelsen]

** Description changed:

+ [Impact]
+ 
+  * Unity-only bug
+ 
+ [Test Case]
+ 
+  * Start LibreOffice Writer
+  * click menu Insert-Object-Formula
+  * press Escape to leave formula mode
+  * Open Insert menu
+  * expected behaviour: e.g. Insert Bookmark is enabled
+  * actual behavious: Insert Bookmark is disabled
+ 
+ [Regression Potential]
+ 
+  * limited:
+- patch has been released to the LibreOffice PPA for a while without
+  any negative feedback
+- changes limited to vcl (mostly gtk backend) and framework (trivial)
+ 
+ [Other Info]
+ 
+  * original report:
+ 
  After adding a formula, OLE-Object or diagram to the document and then
  exiting the editing mode, one cannot choose several items from the
  menubar, neither using a mouse or the HUD. The affected items are greyed
  out and mostly in the Add and Format dropdown menu. After first
  navigating to that item with the mouse pointer, the second time the
  items become available.
  
  After deinstalling the indicator-appmenu package, the Libreoffice menu works 
without problems.
  ---
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-05-03 (324 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  NonfreeKernelModules: nvidia
  Package: indicator-appmenu 13.01.0+14.04.20140320-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-03-16 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

Title:
  Menu items are greyed  out in Libreoffice menu.

Status in “hud” package in Ubuntu:
  Invalid
Status in “indicator-appmenu” package in Ubuntu:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * Unity-only bug

  [Test Case]

   * Start LibreOffice Writer
   * click menu Insert-Object-Formula
   * press Escape to leave formula mode
   * Open Insert menu
   * expected behaviour: e.g. Insert Bookmark is enabled
   * actual behavious: Insert Bookmark is disabled

  [Regression Potential]

   * limited:
 - patch has been released to the LibreOffice PPA for a while without
   any negative feedback
 - changes limited to vcl (mostly gtk backend) and framework (trivial)

  [Other Info]

   * original report:

  After adding a formula, OLE-Object or diagram to the document and then
  exiting the editing mode, one cannot choose several items from the
  menubar, neither using a mouse or the HUD. The affected items are
  greyed out and mostly in the Add and Format dropdown menu. After
  first navigating to that item with the mouse pointer, the second time
  the items become available.

  After deinstalling the indicator-appmenu package, the Libreoffice menu works 
without problems.
  ---
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-05-03 (324 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  NonfreeKernelModules: nvidia
  Package: indicator-appmenu 13.01.0+14.04.20140320-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-03-16 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1296715/+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 1319283] Re: unity screensaver lockup/crash

[Andrea Azzarone]

https://wiki.ubuntu.com/DebuggingCompiz. Make sure to install also the
unity debug symbols.

** Changed in: unity
   Status: New = Incomplete

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

Title:
  unity screensaver lockup/crash

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

Bug description:
  I have seen several instances where resuming from suspend results in a 
slightly corrupted unity screensaver/lockscreen. Login is impossible. 
  Sometimes it crashes after a few minutes and restarts and all is ok. Other 
times it crashes after a few minutes and simply unlocks the screen, though this 
is often accompanies by no unity windowmanager running in the desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 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-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Tue May 13 21:01:18 2014
  DistUpgraded: 2014-04-17 13:16:06,322 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107GLM [Quadro K1000M] [10de:0ffc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:21f6]
  InstallationDate: Installed on 2013-07-05 (311 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: LENOVO 24491D1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (26 days ago)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24491D1
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET96WW(2.56):bd11/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 24491D1
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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
  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  8 19:16:07 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1319283/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.

[Brian Murray]

Hello Steve, or anyone else affected,

Accepted qtbase-opensource-src into trusty-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source
/qtbase-opensource-src/5.2.1+dfsg-1ubuntu14.2 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: qtbase-opensource-src (Ubuntu Trusty)
   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 unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701

Title:
  xserver mouse pointer emulation from touch breaks with QML app.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  Triaged
Status in X.Org X server:
  Confirmed
Status in “qtbase-opensource-src” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid
Status in “xorg-server” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” source package in Trusty:
  Fix Committed
Status in “unity” source package in Trusty:
  Invalid
Status in “xorg-server” source package in Trusty:
  Confirmed

Bug description:
  When running an SDK app on the desktop, it's not possible to use the
  touchscreen to move windows, use the launcher, etc. The SDK app seems
  to consume all touchscreen events.

  To reproduce:
  1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 
14.04 and check that the touchscreen works for moving windows
  2) Install the camera-app package from universe (I have 
2.9.1+14.04.20140331-0ubuntu1)
  3) Launch the camera app
  4) Touch once inside the camera-app window
  5) Use the touchscreen to drag the camera-app window

  Expected results:
  You can move the camera-app window using the touchscreen

  Actual results:
  You cannot move the camera-app window, or perform any other touch tasks in 
unity, with the touchscreen

  This only affects touchscreen input - mouse/touchpad input is not
  affected

  This affects all apps written with the SDK (I tried camera-app,
  gallery-app, reminders-app). It's 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Mon Apr 14 14:59:09 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-02 (132 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1323654] [NEW] error launching calendar/g+ from gmail webapp

[Bill Filler]

Public bug reported:

r48

- Launch gmail webapp and login
- on the main screen there are icons at the top for G+, Calendar, and Web
- Click on G+ or Calendar

Expected results:
- G+ or Calendar should be launched in webbrowser-app

Actual results:
- nothing happens

Getting this error in the log:
Opening: https://www.google.com/calendar/gpcal?source=moggl=us in the browser 
window.
[0527/093205:ERROR:browser_main_loop.cc(240)] unknown: Unable to dispatch url 
'https://www.google.com/calendar/gpcal?source=moggl=us':GDBus.Error:com.canonical.URLDispatcher.BadURL:
 URL 'https://www.google.com/calendar/gpcal?source=moggl=us' is not handleable 
by the URL Dispatcher

Works fine when clicking the Web icon as that is directed to a http
url not https

** Affects: oxide
 Importance: Undecided
 Status: New

** Affects: webapps-core
 Importance: High
 Status: New

** Affects: url-dispatcher (Ubuntu)
 Importance: High
 Status: New

** Also affects: url-dispatcher (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: webapps-core
   Importance: Undecided = High

** Changed in: url-dispatcher (Ubuntu)
   Importance: Undecided = High

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

Title:
  error launching calendar/g+ from gmail webapp

Status in Oxide Webview:
  New
Status in The Webapps-core project:
  New
Status in “url-dispatcher” package in Ubuntu:
  New

Bug description:
  r48

  - Launch gmail webapp and login
  - on the main screen there are icons at the top for G+, Calendar, and Web
  - Click on G+ or Calendar

  Expected results:
  - G+ or Calendar should be launched in webbrowser-app

  Actual results:
  - nothing happens

  Getting this error in the log:
  Opening: https://www.google.com/calendar/gpcal?source=moggl=us in the 
browser window.
  [0527/093205:ERROR:browser_main_loop.cc(240)] unknown: Unable to dispatch 
url 
'https://www.google.com/calendar/gpcal?source=moggl=us':GDBus.Error:com.canonical.URLDispatcher.BadURL:
 URL 'https://www.google.com/calendar/gpcal?source=moggl=us' is not handleable 
by the URL Dispatcher

  Works fine when clicking the Web icon as that is directed to a http
  url not https

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1323654/+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 1323050] Re: Natural scrolling reverts without unchecking box

[Zachary Alex Stern]

The issue was caused by an .Xmodmap carried over from a backup of my
dotfiles. No bug. :/

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

Title:
  Natural scrolling reverts without unchecking box

Status in Unity Settings Daemon:
  New
Status in “unity” package in Ubuntu:
  Invalid
Status in “unity-settings-daemon” package in Ubuntu:
  New

Bug description:
  I have installed Ubuntu 14.04 on my Thinkpad W510.

  The first thing I do, post-install, is enable natural scrolling.

  It works for a while, but eventually (possibly after a reboot), my
  machine reverts to classic scrolling direction, even though I still
  have the natural scrolling button checked in mouse preferences.

  If I *uncheck* the natural scrolling box, it then goes back to natural
  scrolling.

  I've re-installed Ubuntu 14.04 and fully updated before checking the
  natural scrolling box again, and gotten the same behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-settings-daemon/+bug/1323050/+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 1170647] Re: Clicking onNautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations

[martincasc]

While I had reported the bug, it was gone just like that. However 
after reinstalling Ubuntu 14.04 64 bits,nautilus froze recently and from 
there the bug reappeared.-
El 23/05/14 10:01, Sasa Batistic escribió:
 bug is still in 14.04_86x


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

Title:
  Clicking on Nautilus’ launcher icon opens new window instead of
  restoring the minimized one when browsing external drives/locations

Status in “bamf” package in Ubuntu:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Sometimes left clicking the nautilus launcher icon doesn't bring up a
  minimized nautilus window. Instead of restoring the window a new
  instance of nautilus is showing up.

  Steps to reproduce:

  1. Open a nautilus window by clicking on the launcher icon.
  2. Navigate to a symlinked directory whose target is located on a different 
harddrive (for example: a symlink to a folder on a sd-card).
  3. Minimize the nautilus window.
  4. Try to bring up that window again by clicking the launcher icon.

  What happens:

  1. A new instance (window) of nautilus is opened.
  2. There's no obvious way to access the first window again. The only way is 
ALT+TAB.

  What schould happen:

  If a nautilus window is already open and minimized clicking the
  launcher icon should bring up that window. This was the behavior of
  nautilus windows in Ubuntu 12.10 (quantal).

  Ubuntu 13.04 Raring Ringtail (development branch)
  nautilus 3.6.3-0ubuntu16
  unity 7.0.0daily13.04.18~13.04-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+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 1323654] Re: error launching calendar/g+ from gmail webapp

[Bill Filler]

** Tags added: rtm14

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

Title:
  error launching calendar/g+ from gmail webapp

Status in Oxide Webview:
  New
Status in The Webapps-core project:
  New
Status in “url-dispatcher” package in Ubuntu:
  New

Bug description:
  r48

  - Launch gmail webapp and login
  - on the main screen there are icons at the top for G+, Calendar, and Web
  - Click on G+ or Calendar

  Expected results:
  - G+ or Calendar should be launched in webbrowser-app

  Actual results:
  - nothing happens

  Getting this error in the log:
  Opening: https://www.google.com/calendar/gpcal?source=moggl=us in the 
browser window.
  [0527/093205:ERROR:browser_main_loop.cc(240)] unknown: Unable to dispatch 
url 
'https://www.google.com/calendar/gpcal?source=moggl=us':GDBus.Error:com.canonical.URLDispatcher.BadURL:
 URL 'https://www.google.com/calendar/gpcal?source=moggl=us' is not handleable 
by the URL Dispatcher

  Works fine when clicking the Web icon as that is directed to a http
  url not https

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1323654/+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 1323654] Re: error launching calendar/g+ from gmail webapp

[David Barth]

For reference:

I can't reproduce with 2 different accounts (personal and professional).

I am on r44 while you are on r48

I am using the gmail webapp version 1.0.10 has pre-integrated in the
image.


** Tags removed: rtm14
** Tags added: webapps-hotlist

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

Title:
  error launching calendar/g+ from gmail webapp

Status in Oxide Webview:
  New
Status in The Webapps-core project:
  New
Status in “url-dispatcher” package in Ubuntu:
  New

Bug description:
  r48

  - Launch gmail webapp and login
  - on the main screen there are icons at the top for G+, Calendar, and Web
  - Click on G+ or Calendar

  Expected results:
  - G+ or Calendar should be launched in webbrowser-app

  Actual results:
  - nothing happens

  Getting this error in the log:
  Opening: https://www.google.com/calendar/gpcal?source=moggl=us in the 
browser window.
  [0527/093205:ERROR:browser_main_loop.cc(240)] unknown: Unable to dispatch 
url 
'https://www.google.com/calendar/gpcal?source=moggl=us':GDBus.Error:com.canonical.URLDispatcher.BadURL:
 URL 'https://www.google.com/calendar/gpcal?source=moggl=us' is not handleable 
by the URL Dispatcher

  Works fine when clicking the Web icon as that is directed to a http
  url not https

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1323654/+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 1323654] Re: error launching calendar/g+ from gmail webapp

[Bill Filler]

Seems like a url-dispatcher bug 
url-dispatcher version 0.1+14.04.20140403-0ubuntu1

When in the failed state I'm running the following from the command line:
 url-dispatcher https://www.google.com/calendar/gpcal?source=mog and it fails

 url-dispatcher http://www.google.com/calendar/gpcal?source=mog this
works

looks like an issue of http vs. https

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

Title:
  error launching calendar/g+ from gmail webapp

Status in Oxide Webview:
  New
Status in The Webapps-core project:
  New
Status in “url-dispatcher” package in Ubuntu:
  New

Bug description:
  r48

  - Launch gmail webapp and login
  - on the main screen there are icons at the top for G+, Calendar, and Web
  - Click on G+ or Calendar

  Expected results:
  - G+ or Calendar should be launched in webbrowser-app

  Actual results:
  - nothing happens

  Getting this error in the log:
  Opening: https://www.google.com/calendar/gpcal?source=moggl=us in the 
browser window.
  [0527/093205:ERROR:browser_main_loop.cc(240)] unknown: Unable to dispatch 
url 
'https://www.google.com/calendar/gpcal?source=moggl=us':GDBus.Error:com.canonical.URLDispatcher.BadURL:
 URL 'https://www.google.com/calendar/gpcal?source=moggl=us' is not handleable 
by the URL Dispatcher

  Works fine when clicking the Web icon as that is directed to a http
  url not https

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1323654/+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 1236902] Re: [Ubuntu 12.04.3, Raring and perhaps Saucy] The indicator-applet-complete shortcut not working

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [Ubuntu 12.04.3, Raring and perhaps Saucy] The indicator-applet-
  complete shortcut not working

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

Bug description:
  Dear developers,

  In Ubuntu 12.04.3 if I using GNOME fallback session with no effects and 
installed the indicator-applet-complete package (indicator-applet is installed 
too), the SUPER+S keystroke has not effect.
  If I navigate my top panel and click the applet, everithing works fine.
  I not experiencing this problem my prewious Ubuntu 12.04.2 installation.
  I experienced this issue under Ubuntu Saucy too.

  Attila

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-applet-complete 0.5.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic i686
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: i386
  CasperVersion: 1.315.1
  Date: Tue Oct  8 16:45:56 2013
  LiveMediaBuild: BeLin 3.01 i386
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-applet
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1236902/+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 1323654] Re: error launching calendar/g+ from gmail webapp

[Ted Gould]

It seems that the URL database isn't getting updated properly, as there
are some insert failures in bfiller's update logs. After removing the
database and rerunning the update, there are no errors. I'm not able to
recreate those errors on a database. We're going to keep this open and
push through an MR to create recoverable errors on the insert failures
to see if we can get more data and see if the bug occurs in other
situations.

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

Title:
  error launching calendar/g+ from gmail webapp

Status in Oxide Webview:
  Invalid
Status in The Webapps-core project:
  Invalid
Status in “url-dispatcher” package in Ubuntu:
  New

Bug description:
  r48

  - Launch gmail webapp and login
  - on the main screen there are icons at the top for G+, Calendar, and Web
  - Click on G+ or Calendar

  Expected results:
  - G+ or Calendar should be launched in webbrowser-app

  Actual results:
  - nothing happens

  Getting this error in the log:
  Opening: https://www.google.com/calendar/gpcal?source=moggl=us in the 
browser window.
  [0527/093205:ERROR:browser_main_loop.cc(240)] unknown: Unable to dispatch 
url 
'https://www.google.com/calendar/gpcal?source=moggl=us':GDBus.Error:com.canonical.URLDispatcher.BadURL:
 URL 'https://www.google.com/calendar/gpcal?source=moggl=us' is not handleable 
by the URL Dispatcher

  Works fine when clicking the Web icon as that is directed to a http
  url not https

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1323654/+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 1303249] Re: Indicator-datetime doesn't show evolution/eds calendar color for all-day events (Trusty)

[Khurshid Alam]

Also after more testing I found out that, it doesn't show calendar color
or clock icon for online calendars added to evolution. In saucy, for
online calendars, it uses evolution calendar color for all events.

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

Title:
  Indicator-datetime doesn't show evolution/eds calendar color for all-
  day events (Trusty)

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

Bug description:
  It used to show respective calendar color from evolution for all-day
  events  clock/alarm icon for events with time. But with latest
  update, it seems it has stopped showing evolution calendar color for
  all-day events in indicator-datetime.

  However alarm/clock icon still appears as usual. I have attached a
  screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1303249/+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 1323654] Re: error launching calendar/g+ from gmail webapp

[Ted Gould]

MR for the recoverable errors: https://code.launchpad.net/~ted/url-
dispatcher/recoverable-inserts/+merge/221121

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

Title:
  error launching calendar/g+ from gmail webapp

Status in Oxide Webview:
  Invalid
Status in The Webapps-core project:
  Invalid
Status in “url-dispatcher” package in Ubuntu:
  New

Bug description:
  r48

  - Launch gmail webapp and login
  - on the main screen there are icons at the top for G+, Calendar, and Web
  - Click on G+ or Calendar

  Expected results:
  - G+ or Calendar should be launched in webbrowser-app

  Actual results:
  - nothing happens

  Getting this error in the log:
  Opening: https://www.google.com/calendar/gpcal?source=moggl=us in the 
browser window.
  [0527/093205:ERROR:browser_main_loop.cc(240)] unknown: Unable to dispatch 
url 
'https://www.google.com/calendar/gpcal?source=moggl=us':GDBus.Error:com.canonical.URLDispatcher.BadURL:
 URL 'https://www.google.com/calendar/gpcal?source=moggl=us' is not handleable 
by the URL Dispatcher

  Works fine when clicking the Web icon as that is directed to a http
  url not https

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1323654/+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 877444] Re: launcher does not show minimized update manager while clicked

[Joel Östblom]

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

I am experiencing this bug in 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/877444

Title:
  launcher does not show minimized update manager while clicked

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

Bug description:
  The update manager gets launched automatically because it founds some
  new update. I click on the laucher button, it does NOT show the update
  manager window. I tried everything I can but the window simply does
  not show up.

  It looks similar to bug #801593, but I am not sure, because this
  application should not be positioned across desktops.

  However, the differences are: 1) I am not

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/877444/+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 1322769] [NEW] 14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with VirtualBox VMs Running

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have replicated this bug on two different laptops, one at work running
mulitple monitors, one at home running a single monitor.

Symptom: When the Unity System Settings Lock Screen Settings activate,
and I notice the screen has gone blank and locked, I re-activate the
keyboard (usually left CRTL) and the 14.04 LTS Login Screen appears.

In all cases the keyboard is locked out and non-responsive, I can click
on the password box for my account and anything I type no longer
appears. I have to select Switch Account option with the mouse to get
a new login screen for my account and I can log in.

In some cases both the keyboard and the mouse input is locked out and
non-responsive. I can not select Switch Account and must power off the
laptop which of course is dangerous for the file systems of both Windows
VMs that are running and the host/14.04 LTS file system.  I have already
corrupted the Windows VM file systems and had to repair while testing
this bug for repeatability.

Both laptops run the AMD64 version of Ubuntu 14.04 LTS.
Both have built in Intel Integrated Graphics, one laptop with the older 
Ironlake, one with the newer ivy bridge.

Both are running Oracle VirtualBox but different version:

1. Home is running the Ubuntu 14.04 Repository version of Oracle VirtualBox 
(Currently 4.3.10_Ubuntu r93012)
2. Work is running the Oracle downloadable AMD64 version of Oracle VirtualBox 
Currently 4.3.12
3. Both have the respective Oracle Virtual Box Extensions installed for 4.3.10 
and 4.3.12
3. Both are running Windows 7 64 VMs

Both 14.04 LTS have the following System Settings for Lock Screen:
Brightness slider - All the way left
Dim screen to save power - Checked
Lock - Switch to ON position
Lock Screen after: 5 minutes
Require my password when weking form suspend - Checked


I have tested this with both a VM running (no other running applications were 
tested) and with no apps running (fresh boot and login into 14.04 LTS unity 
desktops).

1. On fresh boot with no apps running the lock screen activates (after 5
min of no activity) and when I re-activate the laptops (usually pressing
left CTRL on keyboard) I get the login screen and can enter my password
successfully and the Unity desktop is presented.

2. On fresh boot with a Windows 7 VM running the lock screen activates
(after 5 min of no activity) and when I re-activate the laptops (usually
pressing the left CTRL on the keyboard) I get the login screen and the
keyboard is locked and non-responsive and I can not log into my account.

Variations on 2. I can not enter password but I can use CTRL-ALT-F1, etc. to 
switch to TTY and gain access to system.
Variations on 2. I can not enter password and can not use CTRL-ALT-F1, etc. the 
entire keyboard appears locked out, but I can use mouse and select Switch 
Account to force a new login screen to appear and the keyboard now works to 
enter password.
Variations on 2. I can not enter password and can not use CTRL-ALT-F1, etc. and 
I can not use the mouse, the entire input interfaces appear locked out and I 
have to power off the laptops to restart and be able to log in to Unity again.

If I turn Lock: Off but leave Turn Screen off when inactive for 5
minutes set. If I have a VM running or no apps running, after 5 minutes
the screen dims. I re-activate the system by pressing a key on the
keyboard (usually the left CTRL key) and the Unity desktop re-appears.

This bug only seems to occur when the Lock/Require Password when waking
from suspend is active.

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


** Tags: 14.04 bot-comment keyboard lock lts unity virtualbox
-- 
14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with 
VirtualBox VMs Running
https://bugs.launchpad.net/bugs/1322769
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 1322769] Re: 14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with VirtualBox VMs Running

[Brian Murray]

** Package changed: ubuntu = unity (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/1322769

Title:
  14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with
  VirtualBox VMs Running

Status in “unity” package in Ubuntu:
  New

Bug description:
  I have replicated this bug on two different laptops, one at work
  running mulitple monitors, one at home running a single monitor.

  Symptom: When the Unity System Settings Lock Screen Settings activate,
  and I notice the screen has gone blank and locked, I re-activate the
  keyboard (usually left CRTL) and the 14.04 LTS Login Screen appears.

  In all cases the keyboard is locked out and non-responsive, I can
  click on the password box for my account and anything I type no longer
  appears. I have to select Switch Account option with the mouse to
  get a new login screen for my account and I can log in.

  In some cases both the keyboard and the mouse input is locked out and
  non-responsive. I can not select Switch Account and must power off
  the laptop which of course is dangerous for the file systems of both
  Windows VMs that are running and the host/14.04 LTS file system.  I
  have already corrupted the Windows VM file systems and had to repair
  while testing this bug for repeatability.

  Both laptops run the AMD64 version of Ubuntu 14.04 LTS.
  Both have built in Intel Integrated Graphics, one laptop with the older 
Ironlake, one with the newer ivy bridge.

  Both are running Oracle VirtualBox but different version:

  1. Home is running the Ubuntu 14.04 Repository version of Oracle VirtualBox 
(Currently 4.3.10_Ubuntu r93012)
  2. Work is running the Oracle downloadable AMD64 version of Oracle VirtualBox 
Currently 4.3.12
  3. Both have the respective Oracle Virtual Box Extensions installed for 
4.3.10 and 4.3.12
  3. Both are running Windows 7 64 VMs

  Both 14.04 LTS have the following System Settings for Lock Screen:
  Brightness slider - All the way left
  Dim screen to save power - Checked
  Lock - Switch to ON position
  Lock Screen after: 5 minutes
  Require my password when weking form suspend - Checked

  
  I have tested this with both a VM running (no other running applications were 
tested) and with no apps running (fresh boot and login into 14.04 LTS unity 
desktops).

  1. On fresh boot with no apps running the lock screen activates (after
  5 min of no activity) and when I re-activate the laptops (usually
  pressing left CTRL on keyboard) I get the login screen and can enter
  my password successfully and the Unity desktop is presented.

  2. On fresh boot with a Windows 7 VM running the lock screen activates
  (after 5 min of no activity) and when I re-activate the laptops
  (usually pressing the left CTRL on the keyboard) I get the login
  screen and the keyboard is locked and non-responsive and I can not log
  into my account.

  Variations on 2. I can not enter password but I can use CTRL-ALT-F1, etc. to 
switch to TTY and gain access to system.
  Variations on 2. I can not enter password and can not use CTRL-ALT-F1, etc. 
the entire keyboard appears locked out, but I can use mouse and select Switch 
Account to force a new login screen to appear and the keyboard now works to 
enter password.
  Variations on 2. I can not enter password and can not use CTRL-ALT-F1, etc. 
and I can not use the mouse, the entire input interfaces appear locked out and 
I have to power off the laptops to restart and be able to log in to Unity again.

  If I turn Lock: Off but leave Turn Screen off when inactive for 5
  minutes set. If I have a VM running or no apps running, after 5
  minutes the screen dims. I re-activate the system by pressing a key on
  the keyboard (usually the left CTRL key) and the Unity desktop re-
  appears.

  This bug only seems to occur when the Lock/Require Password when
  waking from suspend is active.

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

[Tural Gurbanov]

+1 
Hotkeys don't work PyCharm 3.1.3 in English (US) layout after PPA + the 
restart unity-settings-daemon.

Output of setxkbmap -query:

rules:  evdev
model:  pc105
layout: ru,us
variant:,
options:grp_led:scroll

However hotkeys now work in other apps (for ex: chromium) both in EN and
RU layouts.

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

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

Status in Aptana Studio Installer:
  New
Status in 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:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

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

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

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


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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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

[Dx-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

[Yotam Benshalom]

Can these patches to gnome-settings-daemon be submitted to the gnome3
team, so they can merge them in one of their ppa's? This way we will be
able to use newer Gnome desktops.

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

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

Status in Aptana Studio Installer:
  New
Status in 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:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

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

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

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


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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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

[Dx-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

[Artur Eshenbrener]

Yotam, is this bug also affects pure gnome?

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

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

Status in Aptana Studio Installer:
  New
Status in 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:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

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

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

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


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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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

[Dx-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

[Yotam Benshalom]

I'm not sure what is pure gnome. It happens to me on 14.04, with
http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu and
http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu enabled, but
WITHOUT Ricotz testing PPA. The unity-settings-daemon is not installed
on my system.

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

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

Status in Aptana Studio Installer:
  New
Status in 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:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

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

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

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


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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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

Re: [Dx-packages] [Bug 1322769] Re: 14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with VirtualBox VMs Running

[Peter Dilley]

Thank you Brian. For the life of me I couldn't sort out the interface as
its the first report I have done and its all a bit intimidating for first
time users of the report system.
On 28/05/2014 4:45 am, Brian Murray br...@ubuntu.com wrote:

 ** Package changed: ubuntu = unity (Ubuntu)

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1322769

 Title:
   14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with
   VirtualBox VMs Running

 Status in “unity” package in Ubuntu:
   New

 Bug description:
   I have replicated this bug on two different laptops, one at work
   running mulitple monitors, one at home running a single monitor.

   Symptom: When the Unity System Settings Lock Screen Settings activate,
   and I notice the screen has gone blank and locked, I re-activate the
   keyboard (usually left CRTL) and the 14.04 LTS Login Screen appears.

   In all cases the keyboard is locked out and non-responsive, I can
   click on the password box for my account and anything I type no longer
   appears. I have to select Switch Account option with the mouse to
   get a new login screen for my account and I can log in.

   In some cases both the keyboard and the mouse input is locked out and
   non-responsive. I can not select Switch Account and must power off
   the laptop which of course is dangerous for the file systems of both
   Windows VMs that are running and the host/14.04 LTS file system.  I
   have already corrupted the Windows VM file systems and had to repair
   while testing this bug for repeatability.

   Both laptops run the AMD64 version of Ubuntu 14.04 LTS.
   Both have built in Intel Integrated Graphics, one laptop with the older
 Ironlake, one with the newer ivy bridge.

   Both are running Oracle VirtualBox but different version:

   1. Home is running the Ubuntu 14.04 Repository version of Oracle
 VirtualBox (Currently 4.3.10_Ubuntu r93012)
   2. Work is running the Oracle downloadable AMD64 version of Oracle
 VirtualBox Currently 4.3.12
   3. Both have the respective Oracle Virtual Box Extensions installed for
 4.3.10 and 4.3.12
   3. Both are running Windows 7 64 VMs

   Both 14.04 LTS have the following System Settings for Lock Screen:
   Brightness slider - All the way left
   Dim screen to save power - Checked
   Lock - Switch to ON position
   Lock Screen after: 5 minutes
   Require my password when weking form suspend - Checked


   I have tested this with both a VM running (no other running applications
 were tested) and with no apps running (fresh boot and login into 14.04 LTS
 unity desktops).

   1. On fresh boot with no apps running the lock screen activates (after
   5 min of no activity) and when I re-activate the laptops (usually
   pressing left CTRL on keyboard) I get the login screen and can enter
   my password successfully and the Unity desktop is presented.

   2. On fresh boot with a Windows 7 VM running the lock screen activates
   (after 5 min of no activity) and when I re-activate the laptops
   (usually pressing the left CTRL on the keyboard) I get the login
   screen and the keyboard is locked and non-responsive and I can not log
   into my account.

   Variations on 2. I can not enter password but I can use CTRL-ALT-F1,
 etc. to switch to TTY and gain access to system.
   Variations on 2. I can not enter password and can not use CTRL-ALT-F1,
 etc. the entire keyboard appears locked out, but I can use mouse and select
 Switch Account to force a new login screen to appear and the keyboard now
 works to enter password.
   Variations on 2. I can not enter password and can not use CTRL-ALT-F1,
 etc. and I can not use the mouse, the entire input interfaces appear locked
 out and I have to power off the laptops to restart and be able to log in to
 Unity again.

   If I turn Lock: Off but leave Turn Screen off when inactive for 5
   minutes set. If I have a VM running or no apps running, after 5
   minutes the screen dims. I re-activate the system by pressing a key on
   the keyboard (usually the left CTRL key) and the Unity desktop re-
   appears.

   This bug only seems to occur when the Lock/Require Password when
   waking from suspend is active.

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

Title:
  14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with
  VirtualBox VMs Running

Status in “unity” package in Ubuntu:
  New

Bug description:
  I have replicated this bug on two different laptops, one at work
  running mulitple monitors, one at home running a single monitor.

  Symptom: When the Unity System Settings Lock Screen Settings activate,
  and I notice the screen has gone blank and locked, 

[Dx-packages] [Bug 1320999] Re: Drums sound when screen locks

[Scott Ritchie]

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

Title:
  Drums sound when screen locks

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Since Trusty, the drums now sound when the screen locks.  To
  reproduce, just leave your computer untouched for 10 minutes.

  I believe this is an unintentional side-effect of the use of unity-greeter 
instead of gnome-screensaver.  I can't see any usability benefit, and it can 
even be mildly annoying.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-03-05 (82 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1320999/+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 1302930] Re: Every message gets new list item on empathy indicator

[Michal Zubkowicz]

It was ok for some time, but now it's bad again.

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

Title:
  Every message gets new list item on empathy indicator

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

Bug description:
  In messaging indicator i see every message as a separate item, even
  with same person. So i have many notifications with same persons. Also
  opening empathy doesn't remove item from list. Only clicking on
  indicator element.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1302930/+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 1323050] Re: Natural scrolling reverts without unchecking box

[Andrea Azzarone]

** Changed in: unity-settings-daemon (Ubuntu)
   Status: New = Invalid

** Changed in: unity-settings-daemon
   Status: New = Invalid

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

Title:
  Natural scrolling reverts without unchecking box

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

Bug description:
  I have installed Ubuntu 14.04 on my Thinkpad W510.

  The first thing I do, post-install, is enable natural scrolling.

  It works for a while, but eventually (possibly after a reboot), my
  machine reverts to classic scrolling direction, even though I still
  have the natural scrolling button checked in mouse preferences.

  If I *uncheck* the natural scrolling box, it then goes back to natural
  scrolling.

  I've re-installed Ubuntu 14.04 and fully updated before checking the
  natural scrolling box again, and gotten the same behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-settings-daemon/+bug/1323050/+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 1047660] Re: With default setting of Only Mounted for Show Devices audio cd's have no icon in launcher

[Doug McMahon]

No longer an issue

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  With default setting of Only Mounted for Show Devices audio cd's
  have no icon in launcher

Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Test case: insert an audio cd
  However if you change that setting to Never   then back to Only Mounted with 
an audio cd already inserted then the icon appears

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.4.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  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]
  Date: Fri Sep  7 17:57:39 2012
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120813.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   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/1047660/+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 1055308] Re: Dash: when using static blur, opening the Dash over windows that change, those windows flash thru

[Doug McMahon]

fixed along the way to 14.04, marking invalid

** Changed in: unity (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: unity
   Status: Confirmed = Invalid

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

Title:
  Dash: when using static blur, opening the Dash over windows that
  change,  those windows flash thru

Status in Unity:
  Invalid
Status in Unity 6.0 series:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  There's quite a nimber that will cause this but most obvious is Totem
  Test case:
  enable static blur, open Dash to set
  Open any audio or video file in Totem so it will be under Dash area
  Open the Dash, totem will continually flash thru

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.324
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Sep 24 06:06:50 2012
  LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120923)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   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/unity/+bug/1055308/+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 954519] Re: Wishlist: Enable resizing with the thumb in nautilus 'Extra Pane' mode

[Doug McMahon]

no longer an extra pane

** Changed in: overlay-scrollbar (Ubuntu)
   Status: New = Invalid

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

Title:
  Wishlist: Enable resizing with the thumb in nautilus 'Extra Pane' mode

Status in “overlay-scrollbar” package in Ubuntu:
  Invalid

Bug description:
  Would be very convenient, especially with the current size of the 
pane-separator which makes resizing  difficult, more so if there is a 
scrollbar. (though the location bar is an option to affect resizing
  I actually like the 1px separator, currently a bug in light-themes though 
hoping it doesn't get fixed

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: overlay-scrollbar 0.2.15-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  Uname: Linux 3.2.0-18-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Tue Mar 13 18:09:48 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: overlay-scrollbar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/954519/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

[LA]

In Ubuntu 12.04-12.10 I had solved this problem by moving the bookmarks
from the toolbar and the menu, to Unsorted Bookmarks. Back then,
bookmarks which were not in the menu, did not get tracked by hud and
therefore did not create an issue any more.

After having upgraded to 13.10, the issue is back. I haven't confirmed
that unsorted bookmarks get tracked again, but I start assuming that
this is the case.

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in The Application Menu:
  Confirmed
Status in Unity:
  Won't Fix
Status in “hud” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/987060/+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 1311403] Re: Can't type password after resume.

[Hannu Haahti]

This has happened to me a couple of times after resuming from suspend
(opening the laptop's lid).

Sometimes there is a delay before the lock screen is displayed -- your
session is visible for a second or so.

Once I managed to focus on a terminal window before the lock screen
appeared, and I was unable to type my password in the password field. I
managed to work around this somehow (unfortunately I don't remember how)
and discovered that all characters I had typed were entered into the
terminal window.

Looks like a serious security risk.

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

Title:
  Can't type password after resume.

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

Bug description:
  I couldn't type password after resume - no characters displayed this
  time.

  I had to Ctrl+alt+f2 and service lightdm restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Tue Apr 22 17:37:49 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-23 (150 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311403/+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 1323871] [NEW] Lag when adjusting sound

[Ian Nicholson]

Public bug reported:

When I adjust the volume - either by hovering the cursor over the
indicator and scroling, or by clicking on the indicator and dragging the
widget - the volume will jump up and down rather than smoothly
increasing or decreasing.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'mic-volume': (true, '', [0.1600189208984375]), 'scroll': 
(true, 'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': 
(true, '', [{'running': false, 'state': 'Paused'}]), 
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i', 
[0.5999298095703125]), 'root': (true, '', [{'title': 'Sound', 
'accessible-desc': 'Volume (59%)', 'icon': ('themed', 
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume', 
'audio']), 'visible': true}]), 'play.rhythmbox.desktop': (true, '', 
['Paused']), 'play-playlist.rhythmbox.desktop': (true, 's', []), 
'next.rhythmbox.desktop': (true, '', [])},)
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 27 17:35:28 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-22 (94 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140221)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Lag when adjusting sound

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

Bug description:
  When I adjust the volume - either by hovering the cursor over the
  indicator and scroling, or by clicking on the indicator and dragging
  the widget - the volume will jump up and down rather than smoothly
  increasing or decreasing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ActionStates: ({'mute': (true, signature '', [false]), 'phone-settings': 
(true, '', []), 'mic-volume': (true, '', [0.1600189208984375]), 'scroll': 
(true, 'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': 
(true, '', [{'running': false, 'state': 'Paused'}]), 
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i', 
[0.5999298095703125]), 'root': (true, '', [{'title': 'Sound', 
'accessible-desc': 'Volume (59%)', 'icon': ('themed', 
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume', 
'audio']), 'visible': true}]), 'play.rhythmbox.desktop': (true, '', 
['Paused']), 'play-playlist.rhythmbox.desktop': (true, 's', []), 
'next.rhythmbox.desktop': (true, '', [])},)
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 27 17:35:28 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-22 (94 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140221)
  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/1323871/+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 1125442] Re: Always Visible and On Top Windows Steal Focus on Workspace Switch

[Edward]

This issue is present in trusty. Possibly a duplicate of #1073488
Google Hangout chats in Chrome (and Chromium?) are probably the most popular 
trigger for this issue.

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

Title:
  Always Visible and On Top Windows Steal Focus on Workspace Switch

Status in Ayatana Design:
  New
Status in Xubuntu:
  New
Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity” source package in Precise:
  Confirmed
Status in “unity” source package in Quantal:
  Confirmed
Status in “unity” source package in Raring:
  Confirmed

Bug description:
  1. Open any application (e.g. TextEditor)
  2. Right click the title bar
   2a. Select Always on Visible Workspace
  3. Right click the title bar
   3a. Select Always on Top
  4. Open a different application (e.g. Terminal)
  5. Ensure that window has focus
  6. Switch workspaces (Notice: the first application now has focus)
  7. Return to first workspace (Notice: the second application does not regain 
focus)

  Expected:

  The initial application should not have ever regained focus, and
  certainly the second application should have it when returning to that
  workspace.

  antarus@mach ~ $ lsb_release -rd
  Description:Ubuntu 12.04.1 LTS
  Release:12.04

  antarus@mach ~ $ apt-cache policy unity
  unity:
Installed: 5.18.0-0ubuntu2
Candidate: 5.18.0-0ubuntu2
Version table:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1125442/+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 1323879] [NEW] Unity dash does not include sufficient space for all label in spanish when filtering results

[hexafraction]

Public bug reported:

When the system language is set to Spanish (es) using unity-control-
center's language subsection, the Unity dash, as expected, uses Spanish
localizations.

However, when viewing the options to filter results under applications
(but not under the option for all results) the buttons for all are
displayed next to the category and source selections. While they should
say Todo or Todos, this is cut off to To This presents a
usability limitation, as even with experience using the Unity Dash in
English, it took a few seconds for me to realize the meaning and use of
those buttons.

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 x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Tue May 27 19:31:53 2014
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug i18n trusty

** Attachment added: Screenshot of the buttons in question.
   
https://bugs.launchpad.net/bugs/1323879/+attachment/4121006/+files/unitybug.png

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

Title:
  Unity dash does not include sufficient space for all label in
  spanish when filtering results

Status in “unity” package in Ubuntu:
  New

Bug description:
  When the system language is set to Spanish (es) using unity-control-
  center's language subsection, the Unity dash, as expected, uses
  Spanish localizations.

  However, when viewing the options to filter results under
  applications (but not under the option for all results) the buttons
  for all are displayed next to the category and source selections.
  While they should say Todo or Todos, this is cut off to To
  This presents a usability limitation, as even with experience using
  the Unity Dash in English, it took a few seconds for me to realize the
  meaning and use of those buttons.

  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 x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue May 27 19:31:53 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/1323879/+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 734908] Re: Unity is visible on top of fullscreen apps

[Mathew Hodson]

The proposed package unity - 5.16.0-0ubuntu1 was released, so removing
the verification-needed tag.

** Tags removed: verification-needed

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

Title:
  Unity is visible on top of fullscreen apps

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Triaged
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity Distro Priority:
  Confirmed
Status in “compiz” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Precise:
  Confirmed
Status in “unity” source package in Precise:
  Fix Released

Bug description:
  [Test Case]
  1. Start a fullscreen application (e.g. Firefox in Fullscreen mode)
 - Verify that the panel is not visible

  [Regression Potential]
  Visual regressions, shell drawing problems. Part of a big change, many 
regression potentials.

  Original description:

  NOTE: This bug is only about the single monitor case. If you still
  have problems with multiple monitors, see bug 748539 instead.

  ORIGINAL DESCRIPTION:
  In natty alpha 3 up to date, I cannot get fullscreen in any application. 
Panels are still visible.

  Tested with:
  - totem
  - vlc
  - firefox
  - chrome
  - geany

  Unity panel and top bar are always on top.

  -
  Desired Solution:

  - When a window is fullscreen (note: this should not be confused with
  the *maximised* state) the menu bar should not be displayed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/734908/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.

[Steve Magoun]

I can no longer reproduce this with qtbase 5.2.1+dfsg-1ubuntu14.2 - nice
work!

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

Title:
  xserver mouse pointer emulation from touch breaks with QML app.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  Triaged
Status in X.Org X server:
  Confirmed
Status in “qtbase-opensource-src” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid
Status in “xorg-server” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” source package in Trusty:
  Fix Committed
Status in “unity” source package in Trusty:
  Invalid
Status in “xorg-server” source package in Trusty:
  Confirmed

Bug description:
  When running an SDK app on the desktop, it's not possible to use the
  touchscreen to move windows, use the launcher, etc. The SDK app seems
  to consume all touchscreen events.

  To reproduce:
  1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 
14.04 and check that the touchscreen works for moving windows
  2) Install the camera-app package from universe (I have 
2.9.1+14.04.20140331-0ubuntu1)
  3) Launch the camera app
  4) Touch once inside the camera-app window
  5) Use the touchscreen to drag the camera-app window

  Expected results:
  You can move the camera-app window using the touchscreen

  Actual results:
  You cannot move the camera-app window, or perform any other touch tasks in 
unity, with the touchscreen

  This only affects touchscreen input - mouse/touchpad input is not
  affected

  This affects all apps written with the SDK (I tried camera-app,
  gallery-app, reminders-app). It's 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Mon Apr 14 14:59:09 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-02 (132 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.

[Timo Jyrinki]

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  xserver mouse pointer emulation from touch breaks with QML app.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  Triaged
Status in X.Org X server:
  Confirmed
Status in “qtbase-opensource-src” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid
Status in “xorg-server” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” source package in Trusty:
  Fix Committed
Status in “unity” source package in Trusty:
  Invalid
Status in “xorg-server” source package in Trusty:
  Confirmed

Bug description:
  When running an SDK app on the desktop, it's not possible to use the
  touchscreen to move windows, use the launcher, etc. The SDK app seems
  to consume all touchscreen events.

  To reproduce:
  1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 
14.04 and check that the touchscreen works for moving windows
  2) Install the camera-app package from universe (I have 
2.9.1+14.04.20140331-0ubuntu1)
  3) Launch the camera app
  4) Touch once inside the camera-app window
  5) Use the touchscreen to drag the camera-app window

  Expected results:
  You can move the camera-app window using the touchscreen

  Actual results:
  You cannot move the camera-app window, or perform any other touch tasks in 
unity, with the touchscreen

  This only affects touchscreen input - mouse/touchpad input is not
  affected

  This affects all apps written with the SDK (I tried camera-app,
  gallery-app, reminders-app). It's 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Mon Apr 14 14:59:09 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-02 (132 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1297447] Re: Notify-osd fails to send messages to accessibility when using Gnome-orca

[Launchpad Bug Tracker]

[Expired for notify-osd (Ubuntu) because there has been no activity for
60 days.]

** Changed in: notify-osd (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Notify-osd fails to send messages to accessibility when using Gnome-
  orca

Status in “notify-osd” package in Ubuntu:
  Expired

Bug description:
  When using Gnome-Orca notify-send This is a test. results in Orca
  saying nothing, further more I have not had a single notification
  message using Trusty. Expected behaviour is to hear notification
  messages such as network status, Dropbox or Ubuntu 1 messages etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 26 05:25:57 2014
  DesktopSession: 'ubuntu'
  GtkTheme: 'Ambiance'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2014-03-01 (24 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140228)
  MachineType: Gigabyte Technology Co., Ltd. Z87M-D3H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic 
root=UUID=aaa62c2b-53c2-4702-9fa4-ed243a3c922b ro quiet splash
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libgl1-mesa-glx  10.1.0-1ubuntu1
   libdrm2  2.4.52-1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1
   xserver-xorg-video-ati   1:7.3.0-1ubuntu3
  SourcePackage: notify-osd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87M-D3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  glxinfo: Error: [Errno 2] No such file or directory: 'glxinfo'

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