date:20150117

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1399983

Title:
  gdebi-gtk crashed with AttributeError in
  _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute
  '_cand'

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  updating teamviewer

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gdebi 0.9.5.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Sat Dec  6 21:13:20 2014
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2014-02-17 (292 days ago)
  InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive 
/home/master/Downloads/teamviewer_10.0.36281_i386.deb
  PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', 
'/home/master/Downloads/teamviewer_10.0.36281_i386.deb']
  SourcePackage: gdebi
  Title: gdebi-gtk crashed with AttributeError in 
_maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand'
  UpgradeStatus: Upgraded to trusty on 2014-05-23 (197 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1359740] Re: the livecd based on initrd.img-3.13.0-34-generic.img does not start :unable to find a medium containing a live file system

2015-01-17 Thread BigK

I finally got something to work.

to summarize : 
I first applied patches from  bug #1325142 to avoid package installation errors 
while issuing dist-upgrade.
THEN 
I applied patch from bug #1325142.

I succesfully remastered a xubuntu 14.04.1 64 bits iso with  dist-
upgrade in chroot and guess what :

It boots !

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1359740

Title:
  the livecd based on  initrd.img-3.13.0-34-generic.img does not start
  :unable to find a medium containing a live file system

Status in Ubuntu Customization Kit:
  New

Bug description:
  I used  uck and manual live cd customization with chroot. I remastered a 
14.04 xubuntu livecd.
  Done a successfull  apt-get dist-upgrade in chroot using workarounds  from 
Bug #1325142 and Bug #1211933.
  But the cd won't boot due to initramfs initrd.img-3.13.0-34-generic updated 
during upgrade.

  I got a 'unable to find a medium containing a live file system'
  message error and a busybox shell.

  last boot messages were : 'mount: mounting /dev/sr0 on /cdrom failed:
  No such device'

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

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

[Touch-packages] [Bug 1359740] Re: the livecd based on initrd.img-3.13.0-34-generic.img does not start :unable to find a medium containing a live file system

2015-01-17 Thread BigK

there is a typo in my last message
it's patches from bug #1325142 and bug  #1201911 

** No longer affects: initramfs-tools (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1359740

Title:
  the livecd based on  initrd.img-3.13.0-34-generic.img does not start
  :unable to find a medium containing a live file system

Status in Ubuntu Customization Kit:
  New

Bug description:
  I used  uck and manual live cd customization with chroot. I remastered a 
14.04 xubuntu livecd.
  Done a successfull  apt-get dist-upgrade in chroot using workarounds  from 
Bug #1325142 and Bug #1211933.
  But the cd won't boot due to initramfs initrd.img-3.13.0-34-generic updated 
during upgrade.

  I got a 'unable to find a medium containing a live file system'
  message error and a busybox shell.

  last boot messages were : 'mount: mounting /dev/sr0 on /cdrom failed:
  No such device'

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

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

[Touch-packages] [Bug 1411075] Re: bluez-simple-agent crashes

2015-01-17 Thread gregrwm

it seems under utopic it works fine, while under vivid it works for my
Bose SLIII but crashes for my 8XXPlantronics.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1411075

Title:
  bluez-simple-agent crashes

Status in bluez package in Ubuntu:
  New

Bug description:
  bluez-simple-agent crashes, in utopic, on a fresh install and fresh
  boot.  same crash after updating packages and reboot:

  $ bluez-simple-agent hci0 00:0C:8A:AA:FE:70 x
  Traceback (most recent call last):
File /usr/bin/bluez-simple-agent, line 127, in module
  device = adapter.FindDevice(args[1])
File /usr/lib/python3/dist-packages/dbus/proxies.py, line 70, in __call__
  return self._proxy_method(*args, **keywords)
File /usr/lib/python3/dist-packages/dbus/proxies.py, line 145, in __call__
  **keywords)
File /usr/lib/python3/dist-packages/dbus/connection.py, line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.bluez.Error.DoesNotExist: Does Not Exist

  this appears similar to Bug #1227584, but the dbus exception is not
  the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic i686
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Jan 14 20:30:08 2015
  InstallationDate: Installed on 2015-01-11 (3 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=9212f425-c8f3-4c80-8d62-41faf2b27d30 panic=30
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: K8M800-8237
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2008:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:15:83:6A:58:96  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:1170 acl:0 sco:0 events:65 errors:0
TX bytes:1056 acl:0 sco:0 commands:65 errors:0
  mtime.conffile..etc.bluetooth.audio.conf: 2015-01-11T15:59:05.078489
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

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

[Touch-packages] [Bug 1412075] [NEW] dvd play back

2015-01-17 Thread tom randolph

Public bug reported:

was trying to play advd

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.65  Tue Dec  2 09:50:34 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Sat Jan 17 17:28:59 2015
DistUpgraded: 2014-10-10 11:24:25,254 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation Device [10de:0f02] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Device [196e:1117]
InstallationDate: Installed on 2014-09-25 (114 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MachineType: Hewlett-Packard HP Z600 Workstation
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=44d13d87-248f-409f-9487-7d647bf1000b ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-10-10 (99 days ago)
dmi.bios.date: 08/19/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G4 v01.17
dmi.board.name: 0AE8h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA9420NLB
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G4v01.17:bd08/19/2009:svnHewlett-Packard:pnHPZ600Workstation:pvr:rvnHewlett-Packard:rn0AE8h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z600 Workstation
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20150114.efef6c82-0ubuntu0ricotz3~trusty
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20150114.efef6c82-0ubuntu0ricotz3~trusty
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git20141215.99537089-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2
xserver.bootTime: Sat Jan 17 13:53:56 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB OPTICAL MOUSEMOUSE, id 8
 inputCHICONY HP Basic USB Keyboard KEYBOARD, id 9
 inputHP WMI hotkeys   KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.6

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


** Tags: amd64 apport-bug third-party-packages trusty ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1412075

Title:
  dvd play back

Status in xorg package in Ubuntu:
  New

Bug description:
  was trying to play advd

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.65  Tue Dec  2 09:50:34 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Sat Jan 17 17:28:59 2015
  DistUpgraded: 2014-10-10 11:24:25,254 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation Device [10de:0f02] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Device [196e:1117]
  InstallationDate: Installed on 2014-09-25 (114 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: Hewlett-Packard HP Z600 Workstation
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=44d13d87-248f-409f-9487-7d647bf1000b ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-10-10 (99 days ago)
  dmi.bios.date: 08/19/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G4 v01.17
  dmi.board.name:

[Touch-packages] [Bug 1411100] Re: guest user not removed after guest session ends

** Branch linked: lp:~sschapiro/lightdm/guest-account-scripts-bash-
support

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1411100

Title:
  guest user not removed after guest session ends

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  The /usr/sbin/giest-account script contains a bug which prevents the
  removal of guest accounts:

  $ sudo /usr/sbin/guest-account remove guest-Hhiook
  /usr/sbin/guest-account: line 129: UID: readonly variable

  Maybe this is related to /bin/sh actually beeing a Bash:

  $ ll -d /bin/sh
  lrwxrwxrwx 1 root root 4 Jan  1 01:44 /bin/sh - bash*

  But since using Bash as default sh is still a feature of Ubuntu, all
  scripts should work with both.

  Running the script with dash actually works:

  $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva
  umount: /tmp/guest-ZWCtva: mountpoint not found
  umount: /tmp/guest-ZWCtva: mountpoint not found
  Removing user `guest-ZWCtva' ...
  Warning: group `guest-ZWCtva' has no more members.
  Done.

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

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

[Touch-packages] [Bug 1411100] Re: guest user not removed after guest session ends

** Branch linked: lp:~sschapiro/lightdm/guest-account-scripts-bash-
support-1_12

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1411100

Title:
  guest user not removed after guest session ends

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  The /usr/sbin/giest-account script contains a bug which prevents the
  removal of guest accounts:

  $ sudo /usr/sbin/guest-account remove guest-Hhiook
  /usr/sbin/guest-account: line 129: UID: readonly variable

  Maybe this is related to /bin/sh actually beeing a Bash:

  $ ll -d /bin/sh
  lrwxrwxrwx 1 root root 4 Jan  1 01:44 /bin/sh - bash*

  But since using Bash as default sh is still a feature of Ubuntu, all
  scripts should work with both.

  Running the script with dash actually works:

  $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva
  umount: /tmp/guest-ZWCtva: mountpoint not found
  umount: /tmp/guest-ZWCtva: mountpoint not found
  Removing user `guest-ZWCtva' ...
  Warning: group `guest-ZWCtva' has no more members.
  Done.

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

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

[Touch-packages] [Bug 1412030] [NEW] Support for select multiple is missing

2015-01-17 Thread jezra

Public bug reported:

There is currently no mechanism for allow the user to select more than
one element in a select multiple

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1412030

Title:
  Support for select multiple is missing

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  There is currently no mechanism for allow the user to select more than
  one element in a select multiple

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1412030/+subscriptions

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

[Touch-packages] [Bug 1411100] Re: guest user not removed after guest session ends

2015-01-17 Thread Schlomo Schapiro

I tried my best - first time doing this on Launchpad so please forgive
if I am doing it the wrong way.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1411100

Title:
  guest user not removed after guest session ends

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  The /usr/sbin/giest-account script contains a bug which prevents the
  removal of guest accounts:

  $ sudo /usr/sbin/guest-account remove guest-Hhiook
  /usr/sbin/guest-account: line 129: UID: readonly variable

  Maybe this is related to /bin/sh actually beeing a Bash:

  $ ll -d /bin/sh
  lrwxrwxrwx 1 root root 4 Jan  1 01:44 /bin/sh - bash*

  But since using Bash as default sh is still a feature of Ubuntu, all
  scripts should work with both.

  Running the script with dash actually works:

  $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva
  umount: /tmp/guest-ZWCtva: mountpoint not found
  umount: /tmp/guest-ZWCtva: mountpoint not found
  Removing user `guest-ZWCtva' ...
  Warning: group `guest-ZWCtva' has no more members.
  Done.

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

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

[Touch-packages] [Bug 1412060] [NEW] Indicator sound fails to start with Asus Xonar

2015-01-17 Thread Elfy

Public bug reported:

Replaced Audigy with Xonar.

Clean installed to new drive and partition.

sound indicator fails to start

upstart --user --startup-event indicator-services-start

tries to start indicator - space in indicators shows where it is,
clicking and menu doesn't appear

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: indicator-sound 12.10.2+15.04.20141105-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Jan 17 21:37:27 2015
InstallationDate: Installed on 2015-01-09 (8 days ago)
InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1412060

Title:
  Indicator sound fails to start with Asus Xonar

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Replaced Audigy with Xonar.

  Clean installed to new drive and partition.

  sound indicator fails to start

  upstart --user --startup-event indicator-services-start

  tries to start indicator - space in indicators shows where it is,
  clicking and menu doesn't appear

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20141105-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jan 17 21:37:27 2015
  InstallationDate: Installed on 2015-01-09 (8 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  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/1412060/+subscriptions

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

[Touch-packages] [Bug 1067547] Re: Unity in 12.10 becomes unusably slow after using Alt-Tab to switch between programs (nvidia)

2015-01-17 Thread Andrea Azzarone

Ubuntu 12.10 is no longer supported? Can you reproduce it on 12.04 or
14.04 or 14.10?

** Changed in: unity
   Status: Confirmed = Incomplete

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1067547

Title:
  Unity in 12.10 becomes unusably slow after using Alt-Tab to switch
  between programs (nvidia)

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

Bug description:
  Not sure what else to say. On my laptop with a clean 12.10
  installation everything works great. On my desktop with an Nvidia
  gts250 card (all available drivers in the repo) unity works fine, but
  after I use alt-tab to switch between applications, compiz memory
  usage rises (20, 50, 100mb, depends on... well, something?) and dash,
  all effects and even window dragging becomes unbearably slow.

  After I do a unity --replace, everything is fine until I use alt-tab
  again. I can reproduce this as many times as I want.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  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 Kernel Module  304.51  Tue Sep 18 17:36:24 PDT 
2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Wed Oct 17 01:12:10 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-current-updates, 304.51, 3.5.0-17-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Giga-byte Technology Device [1458:34c7]
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta i386 (20120926)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=cad55f8d-5c9a-45ee-9ed1-a26e67b985ae ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A79XTD EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0X
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd09/15/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.8.4-0ubuntu2
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

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

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

[Touch-packages] [Bug 1326816] Re: Replace QNetwork with net-cpp

2015-01-17 Thread Marcus Tomlinson

** Changed in: unity-scopes-api (Ubuntu)
   Status: New = In Progress

** Branch unlinked: lp:~thomas-voss/unity-scopes-api/switch-to-net-cpp

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1326816

Title:
  Replace QNetwork with net-cpp

Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  There really is no need for us to over complicate unity-scopes-api by
  dragging Qt into the mix, when we have a cleaner pure C++ solution
  available: net-cpp.

  We should replace the use of QNetwork with net-cpp, hence removing our
  dependency on Qt all together.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1326816/+subscriptions

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

[Touch-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep

2015-01-17 Thread Marius B. Kotsbak

Issue still present.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1400235

Title:
  10de:11fc [Dell Precision M4800] Screen does not wake up after sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  When the laptop is either set to sleep by entering Fn-F1 or by
  timeout, the screen is black after waking it up again (using the power
  button, it does not wake by mousepad movement or key presses).

  In earlier Ubuntu versions (14.04), a workaround was to enter a
  terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does
  not seem to work anymore.

  The problem is is present in todays (2014-12-8) Vivid daily image
  (booted with nomodeset, but not done any configuration of the
  screen).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.346
  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: Mon Dec  8 08:28:24 2014
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell Device [1028:05cc]
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207)
  MachineType: Dell Inc. Precision M4800
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset --
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 077KCT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Dec  8 08:27:01 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.16.1.901-1ubuntu1

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

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

[Touch-packages] [Bug 1412036] Re: Fails to add additional language support

2015-01-17 Thread Nikita Yerenkov-Scott

** Package changed: xorg (Ubuntu) = ibus-hangul (Ubuntu)

** Tags removed: apport-bug compiz-0.9

** Description changed:

  At the moment I have got Russian and English (UK) installed on my
  computer. I installed them through System Settings  Language Support.
  But now I want to add Korean and that is where the problem has come up.
  
  So I go into the Language Support settings and click Install / Remove
  Languages..., I then select Korean from the list and click Apply
  Changes. After the installation has finished I go into the Text Entry
  settings: Text_Entry_GUI.bmp
  
  And click the little + sign. Then I find and add Korean from the
  list: Choose_an_input_source_GUI.bmp
  
  But then when I select Korean as the language I want to type as, it
  still stays at English. And not matter what I do, I cannot seem to get
  any other languages working.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 14.10
- Package: xorg 1:7.7+7ubuntu2
- ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
- Uname: Linux 3.16.0-29-generic x86_64
- .tmp.unity.support.test.0:
-  
- ApportVersion: 2.14.7-0ubuntu8
- Architecture: amd64
- CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
- CompositorRunning: compiz
- CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
- CompositorUnredirectFSW: true
- CurrentDesktop: Unity
- Date: Sat Jan 17 18:57:40 2015
- DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job
- DistroCodename: utopic
- DistroVariant: ubuntu
- ExtraDebuggingInterest: Yes
- GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:5002]
- InstallationDate: Installed on 2014-12-06 (42 days ago)
- InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
- MachineType: LENOVO 62742SG
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic 
root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7
- SourcePackage: xorg
- Symptom: display
- UpgradeStatus: Upgraded to utopic on 2014-12-13 (35 days ago)
- dmi.bios.date: 11/15/2012
- dmi.bios.vendor: LENOVO
- dmi.bios.version: H5ET69WW (1.12 )
- dmi.board.asset.tag: Not Available
- dmi.board.name: 62742SG
- dmi.board.vendor: LENOVO
- dmi.board.version: Win8 Pro DPK IPG
- dmi.chassis.asset.tag: No Asset Information
- dmi.chassis.type: 10
- dmi.chassis.vendor: LENOVO
- dmi.chassis.version: Not Available
- dmi.modalias: 
dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable:
- dmi.product.name: 62742SG
- dmi.product.version: Lenovo B590
- dmi.sys.vendor: LENOVO
- version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
- version.ia32-libs: ia32-libs N/A
- version.libdrm2: libdrm2 2.4.56-1
- version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
- version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
- version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
- version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
- version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
- version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
- version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
- version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
- xserver.bootTime: Sat Jan 17 18:50:54 2015
- xserver.configfile: default
- xserver.errors:
-  
- xserver.logfile: /var/log/Xorg.0.log
- xserver.outputs:
-  product id 827 
-  vendor LGD
- xserver.version: 2:1.16.0-1ubuntu1.2
+ I am running Ubuntu 14.10.
+ 
+ Package information:
+ 
+ ibus-hangul:
+   Installed: 1.4.2+git20140818-1
+   Candidate: 1.4.2+git20140818-1
+   Version table:
+  *** 1.4.2+git20140818-1 0
+ 500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
+ 100 /var/lib/dpkg/status

** Attachment removed: BootDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/ibus-hangul/+bug/1412036/+attachment/4300678/+files/BootDmesg.txt

** Attachment removed: BootLog.gz
   
https://bugs.launchpad.net/ubuntu/+source/ibus-hangul/+bug/1412036/+attachment/4300679/+files/BootLog.gz

** Attachment removed: xserver.devices.txt
   
https://bugs.launchpad.net/ubuntu/+source/ibus-hangul/+bug/1412036/+attachment/4300701/+files/xserver.devices.txt

** Attachment removed: CurrentDmesg.txt
   
https://bugs.launchpad.net/ubuntu/+source/ibus-hangul/+bug/1412036/+attachment/4300680/+files/CurrentDmesg.txt

** Attachment removed: Dependencies.txt
   
https://bugs.launchpad.net/ubuntu/+source/ibus-hangul/+bug/1412036/+attachment/4300681/+files/Dependencies.txt

** Attachment removed: DpkgLog.txt

[Touch-packages] [Bug 1388647] Re: DRI_PRIME=1 has no effect in Ubuntu 14.10

2015-01-17 Thread Christoph Buchner

Alain's workaround also works for me (on Intel+AMD)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1388647

Title:
  DRI_PRIME=1 has no effect in Ubuntu 14.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On an Optimus laptop with both GPUs enabled, having run this command
  so that the Nvidia GPU can be used to offload 3D work from the Intel
  GPU:

  ```
  xrandr --setprovideroffloadsink nouveau Intel
  ```

  Then running this command:

  ```
  DRI_PRIME=1 glxinfo | grep OpenGL vendor string
  ```

  provides the incorrect output:

  ```
  OpenGL vendor string: Intel Open Source Technology Center
  ```

  when it should actually show that the Nouveau driver is in use for the
  program.

  This worked previously in Ubuntu 14.04. Apart from only having a 3.16
  kernel (instead of 3.17) Ubuntu 14.10 actually supports recent enough
  versions of the requisite packages necesarry to get DRI 3 offloading
  support, so perhaps this is part of the problem.

  Or, more likely, I notice a Nouveau failure after startup, and then
  again after running xrandr commands, for example:

  ```
  [  170.912483] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  217.550205] thinkpad_acpi: EC reports that Thermal Table has changed
  [  223.857442] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  223.858395] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  223.860200] nouveau E[PBUS][:01:00.0] MMIO read of 0x 
FAULT at 0x002140 [ !ENGINE ]
  [  224.654622] thinkpad_acpi: EC reports that Thermal Table has changed
  [  825.172094] thinkpad_acpi: EC reports that Thermal Table has changed
  [  831.132156] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  831.133030] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  831.134832] nouveau E[PBUS][:01:00.0] MMIO read of 0x 
FAULT at 0x002140 [ !ENGINE ]
  ```

  Perhaps this is just a regression in either the Nouveau or Intel
  drivers for my hardware. I'm using a Lenovo T430. I can confirm that
  I'm able to start the laptop without errors when I only enable the
  Intel GPU or NVidia GPU separately, and only see this error when both
  GPUs are enabled simultaneously.

  Extra Info:

  1: Description:   Ubuntu 14.10
  Release:  14.10

  2: N/A

  3: The text 'nouveau' should have appeared in the output of the
  command.

  4: The text 'Intel' appeared in the output of the command.

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

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

[Touch-packages] [Bug 1412036] Re: Fails to add additional language support

2015-01-17 Thread Henry Fleminger Thomson

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1412036

Title:
  Fails to add additional language support

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  At the moment I have got Russian and English (UK) installed on my
  computer. I installed them through System Settings  Language
  Support. But now I want to add Korean and that is where the problem
  has come up.

  So I go into the Language Support settings and click Install /
  Remove Languages..., I then select Korean from the list and click
  Apply Changes. After the installation has finished I go into the
  Text Entry settings: Text_Entry_GUI.bmp

  And click the little + sign. Then I find and add Korean from the
  list: Choose_an_input_source_GUI.bmp

  But then when I select Korean as the language I want to type as, it
  still stays at English. And not matter what I do, I cannot seem to get
  any other languages working.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jan 17 18:57:40 2015
  DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:5002]
  InstallationDate: Installed on 2014-12-06 (42 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: LENOVO 62742SG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic 
root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-12-13 (35 days ago)
  dmi.bios.date: 11/15/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H5ET69WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 62742SG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK IPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 62742SG
  dmi.product.version: Lenovo B590
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sat Jan 17 18:50:54 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 827 
   vendor LGD
  xserver.version: 2:1.16.0-1ubuntu1.2

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

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

[Touch-packages] [Bug 1334329] Re: Sound input settings not saved

2015-01-17 Thread Nikos Paraschou

I am also affected by this bug. Is there any progress or a quick
workaround? It's quite annoying to have to chose the input device every
time you want to have a call.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1334329

Title:
  Sound input settings not saved

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When attempting to set my preferred sound input device, simply leaving
  sound preferences and going back to sound preferences, and selecting
  input, causes the default SPDIF to be selected again, and not the
  internal microphone I preferred.  I made a video to demonstrate what I
  mean by this here:  http://youtu.be/9Q9EQvLl_rA

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - 
About Ubuntu
  14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  I really don't know.  It's just the sound preferences.

  3) What you expected to happen
  For my selected sound input to be saved.

  4) What happened instead
  Keeps defaulting to the top sound input

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brandon   23953 F pulseaudio
   /dev/snd/controlC0:  brandon   23953 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 25 11:20:14 2014
  InstallationDate: Installed on 2014-04-26 (60 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B27.1201241646
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245A3940C91C80
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245A3940C91C80
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80:
  dmi.product.name: MacBookPro8,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1334329/+subscriptions

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

[Touch-packages] [Bug 1411992] Re: Network interface NamePolicy= disabled on kernel command line, ignoring

2015-01-17 Thread Bruce Pieterse

** Summary changed:

- Network interfce NamePolicy= disabled on kernel command line, ignoring
+ Network interface NamePolicy= disabled on kernel command line, ignoring

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1411992

Title:
  Network interface NamePolicy= disabled on kernel command line,
  ignoring

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

Bug description:
  As the title says. This is currently showing on installed and daily
  images of Vivid (seen in Ubuntu GNOME daily images).

  I apologise if this was reported against the wrong package, it was
  best guess.

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

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

[Touch-packages] [Bug 1412059] [NEW] Sync libva 1.5.0-1 (universe) from Debian experimental (main)

2015-01-17 Thread Rico Tzschichholz

Public bug reported:

Please sync libva 1.5.0-1 (universe) from Debian experimental (main)

Changelog entries since current vivid version 1.4.1-1:

libva (1.5.0-1) experimental; urgency=medium

  * New upstream release.

 -- Sebastian Ramacher sramac...@debian.org  Mon, 29 Dec 2014 22:04:11
+0100

libva (1.5.0~pre1-1) experimental; urgency=medium

  [ Matteo F. Vescovi ]
  * debian/control: Uploader e-mail address updated

  [ Sebastian Ramacher ]
  * New upstream release.
  * debian/patches: Refresh patches.
  * Add support for driver ABI tracking. (LP: #1384100)
- debian/control: Add Provides: libva-driver-abi-* to libva1 to track the
  supported driver ABI.
- debian/dh/*: Add dh_libva and a dh sequence so driver packages can
  generate dependencies automatically.
  * debian/rules: Build with -Wl,--as-needed.

 -- Sebastian Ramacher sramac...@debian.org  Mon, 15 Dec 2014 19:56:10
+0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1412059

Title:
  Sync libva 1.5.0-1 (universe) from Debian experimental (main)

Status in libva package in Ubuntu:
  New

Bug description:
  Please sync libva 1.5.0-1 (universe) from Debian experimental (main)

  Changelog entries since current vivid version 1.4.1-1:

  libva (1.5.0-1) experimental; urgency=medium

* New upstream release.

   -- Sebastian Ramacher sramac...@debian.org  Mon, 29 Dec 2014
  22:04:11 +0100

  libva (1.5.0~pre1-1) experimental; urgency=medium

[ Matteo F. Vescovi ]
* debian/control: Uploader e-mail address updated

[ Sebastian Ramacher ]
* New upstream release.
* debian/patches: Refresh patches.
* Add support for driver ABI tracking. (LP: #1384100)
  - debian/control: Add Provides: libva-driver-abi-* to libva1 to track the
supported driver ABI.
  - debian/dh/*: Add dh_libva and a dh sequence so driver packages can
generate dependencies automatically.
* debian/rules: Build with -Wl,--as-needed.

   -- Sebastian Ramacher sramac...@debian.org  Mon, 15 Dec 2014
  19:56:10 +0100

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

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

[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.

2015-01-17 Thread Andrea Azzarone

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1410582

Title:
  [Trusty / Unity] Desktop got unlocked on its own.

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I have a user reporting an incidence that trusty unity desktop got
  unlocked on its own:

  In the morning, after coming to my desk, I just pressed the space bar
  on my desktop to get the monitors woken up. The monitors came up with
  the locked screen and then after a while it got unlocked to my
  surprise!

     There was compiz crash file on his system at that time. However, I
  don't have the right debug symbols to which file (or function) it
  crashed into. Here is the top part of the stack trace when I ran
  apport-retrace -s  on his crash file:

  
---
  --- stack trace ---
  #0  0x7ff17ed06608 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #1  0x7ff17ed06cf3 in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #2  0x7ff17ed04e2d in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  No symbol table info available.
  #3  0x7ff17f3fdd02 in g_settings_backend_read (backend=optimized out, 
key=key@entry=0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen, 
expected_type=0x7ff1877135a0 g_variant_type_info_basic_chars, 
default_value=default_value@entry=0) at 
/build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
  value = optimized out
  #4  0x7ff17f401c7b in g_settings_read_from_backend 
(settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920, 
user_value_only=user_value_only@entry=0, default_value=default_value@entry=0) 
at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
  value = optimized out
  fixup = optimized out
  path = 0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen
  #5  0x7ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570, 
key=0x2087618 disable-lock-screen) at 
/build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
  skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c 
disable-lock-screen, is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length 
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0 
g_variant_type_info_basic_chars, minimum = 0x0, maximum = 0x0, default_value 
= 0xb9c5b30, ref_count = 0}
  value = optimized out
  __FUNCTION__ = g_settings_get_value
  
-

     The top part of the trash file when viewed in TextEdit has the information 
:
  -
  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Dec 12 10:16:52 2014
  DistroRelease: Ubuntu 14.04
  ExecutablePath: /usr/bin/compiz
  ExecutableTimestamp: 1405349348
  ProcCmdline: compiz
  --

     His system is Ubuntu trusty 14.04.1 LTS. Unity installed
  7.2.3+14.04.20140826-0ubuntu1.0.1 .

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

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

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

** Tags removed: 14.04 lock lts unity
** Tags added: amd64 lockscreen trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
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:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  In Progress

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/unity/+bug/1322769/+subscriptions

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

[Touch-packages] [Bug 1393624] Re: Lock screen rejects password on Ubuntu 14.04

** Tags removed: lock-screen password
** Tags added: amd64 lockscreen trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1393624

Title:
  Lock screen rejects password on Ubuntu 14.04

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

Bug description:
  Password is systematically rejected on the lock screen. However, if I
  click Switch account, the *greeter* does accept the same password.

  This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or 
by runnibg
  `gnome-screensaver-command -l`

  This happens after I upgraded from Ubuntu 12.04 to 14.04.
  I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 
Ti with NVIDIA proprietary drivers. Same thing.

  Ubuntu 14.04.1 LTS
  Linux 3.13.0-39-generic x86_64

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

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

[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10

2015-01-17 Thread Krzysztof Drewniak

I've experienced a significant (subjective) performance boost by
blacklisting intel_powerclamp and intel_ralp .

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386721

Title:
  Graphics Slow After Upgrade 14.04 - 14.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics

  After upgrading from 14.04 to 14.10 there are a lot of places where
  the graphics are working much slower than they were before:

  - Gnome Shell Interface is very sluggish, visible chops (redrawing)
  when pressing the [Super] key.

  - Selecting text in Gedit takes a full second pr. line

  Experiences some subjective improvement when I booted kernel 3.13.0-37
  instead of 3.16.0-23, but that may be my imagination as the problem
  persists.

  I've searched google, forums, found a couple of relevant links that
  point to the issue being the Intel drivers.

  http://askubuntu.com/questions/53962...E2%86%92-14-10
  http://www.webupd8.org/2014/10/ubunt...ent-1652086424

  But the drivers currently in 14.10 should be newer than those supplied
  by Intel to 14.04 so that doesn't make sense to me. As one Intel
  developer wrote:

  I would like to point out that since what we do is bring more ecent
  versions of the software to the target distributions than they ship
  with, a 14.04 targeted installer is unlikely to bring much to a 14.10
  installation, which most likely has the same or more recent versions
  already anyway.

  Source: https://01.org/linuxgraphics/node/375

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 28 15:24:30 2014
  DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-06-14 (135 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Oct 28 13:44:57 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1412101] Re: package rsyslog 7.4.4-1ubuntu11.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-01-17 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1412101

Title:
  package rsyslog 7.4.4-1ubuntu11.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in rsyslog package in Ubuntu:
  New

Bug description:
  This bug happened while updating programs from terminal

  Refer the below terminal output for details:

  sundaravenkataraman@sundararaman-desktop:~$ sudo apt-get update  sudo 
apt-get upgrade
  [sudo] password for sundaravenkataraman: 
  Ign http://extras.ubuntu.com utopic InRelease
  Hit http://extras.ubuntu.com utopic Release.gpg   

  
  Hit http://extras.ubuntu.com utopic Release   

  
  Hit http://extras.ubuntu.com utopic/main Sources  

  
  Hit http://extras.ubuntu.com utopic/main i386 Packages

  
  Ign http://extras.ubuntu.com utopic/main Translation-en_GB

  
  Ign http://extras.ubuntu.com utopic/main Translation-en   

  
  Ign http://ppa.launchpad.net utopic InRelease 

  
  Get:1 http://www.bchemnet.com debian InRelease [11.1 kB]  


  Ign http://security.ubuntu.com utopic-security InRelease  
   
  Ign http://ppa.launchpad.net utopic InRelease 
  
  Get:2 http://www.bchemnet.com debian/extra i386 Packages [14.8 kB]
  
  Hit http://security.ubuntu.com utopic-security Release.gpg

  
  Ign http://ppa.launchpad.net utopic InRelease 

  
  Hit http://security.ubuntu.com utopic-security Release

  
  Hit http://www.bchemnet.com debian/extra Translation-en_GB

  
  Hit http://ppa.launchpad.net utopic Release.gpg   

  
  Hit http://security.ubuntu.com utopic-security/main Sources   

  
  Hit http://www.bchemnet.com debian/extra Translation-en   

  
  Hit http://ppa.launchpad.net utopic Release.gpg   

  
  Hit http://security.ubuntu.com utopic-security/restricted Sources 

  
  Hit http://ppa.launchpad.net utopic Release.gpg   

  
  Hit http://security.ubuntu.com utopic-security/universe Sources   

  
  Hit http://ppa.launchpad.net utopic Release   

  
  Hit http://security.ubuntu.com utopic-security/multiverse Sources 

  
  Hit http://ppa.launchpad.net utopic Release

[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10

2015-01-17 Thread Gabriel Velo

Can confirm, poor performance on all video players ,  browsers. and
Unity Dash.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386721

Title:
  Graphics Slow After Upgrade 14.04 - 14.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics

  After upgrading from 14.04 to 14.10 there are a lot of places where
  the graphics are working much slower than they were before:

  - Gnome Shell Interface is very sluggish, visible chops (redrawing)
  when pressing the [Super] key.

  - Selecting text in Gedit takes a full second pr. line

  Experiences some subjective improvement when I booted kernel 3.13.0-37
  instead of 3.16.0-23, but that may be my imagination as the problem
  persists.

  I've searched google, forums, found a couple of relevant links that
  point to the issue being the Intel drivers.

  http://askubuntu.com/questions/53962...E2%86%92-14-10
  http://www.webupd8.org/2014/10/ubunt...ent-1652086424

  But the drivers currently in 14.10 should be newer than those supplied
  by Intel to 14.04 so that doesn't make sense to me. As one Intel
  developer wrote:

  I would like to point out that since what we do is bring more ecent
  versions of the software to the target distributions than they ship
  with, a 14.04 targeted installer is unlikely to bring much to a 14.10
  installation, which most likely has the same or more recent versions
  already anyway.

  Source: https://01.org/linuxgraphics/node/375

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 28 15:24:30 2014
  DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-06-14 (135 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Oct 28 13:44:57 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1203066] Re: [sdk] MainView background doesn't have the correct color when set to a light color

** Tags removed: background color
** Tags added: running-unity

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1203066

Title:
  [sdk] MainView background doesn't have the correct color when set to a
  light color

Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  If on a Page, you set a background to a yellow based color like
  yellow and you set also a button and a rectangle to the same color,
  you can see that the color of the background isn't the good one.
  Compare the color here: http://www.colorhexa.com/00 to the color
  of the background of the attached picture. When you do the same for
  other colors like black, green, blue everything is perfect.

  See attached code and screenshot.

  [edit] the button and the rectangle are only here to show you the
  color difference. But the problem is still true only with the
  background: the color isn't the required one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1203066/+subscriptions

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

[Touch-packages] [Bug 1412101] [NEW] package rsyslog 7.4.4-1ubuntu11.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-01-17 Thread Sundaravenkataraman

Public bug reported:

This bug happened while updating programs from terminal

Refer the below terminal output for details:

sundaravenkataraman@sundararaman-desktop:~$ sudo apt-get update  sudo apt-get 
upgrade
[sudo] password for sundaravenkataraman: 
Ign http://extras.ubuntu.com utopic InRelease
Hit http://extras.ubuntu.com utopic Release.gpg 


Hit http://extras.ubuntu.com utopic Release 


Hit http://extras.ubuntu.com utopic/main Sources


Hit http://extras.ubuntu.com utopic/main i386 Packages  


Ign http://extras.ubuntu.com utopic/main Translation-en_GB  


Ign http://extras.ubuntu.com utopic/main Translation-en 


Ign http://ppa.launchpad.net utopic InRelease   


Get:1 http://www.bchemnet.com debian InRelease [11.1 kB]

  
Ign http://security.ubuntu.com utopic-security InRelease
 
Ign http://ppa.launchpad.net utopic InRelease   

Get:2 http://www.bchemnet.com debian/extra i386 Packages [14.8 kB]  

Hit http://security.ubuntu.com utopic-security Release.gpg  


Ign http://ppa.launchpad.net utopic InRelease   


Hit http://security.ubuntu.com utopic-security Release  


Hit http://www.bchemnet.com debian/extra Translation-en_GB  


Hit http://ppa.launchpad.net utopic Release.gpg 


Hit http://security.ubuntu.com utopic-security/main Sources 


Hit http://www.bchemnet.com debian/extra Translation-en 


Hit http://ppa.launchpad.net utopic Release.gpg 


Hit http://security.ubuntu.com utopic-security/restricted Sources   


Hit http://ppa.launchpad.net utopic Release.gpg 


Hit http://security.ubuntu.com utopic-security/universe Sources 


Hit http://ppa.launchpad.net utopic Release 


Hit http://security.ubuntu.com utopic-security/multiverse Sources   


Hit http://ppa.launchpad.net utopic Release 


Hit http://security.ubuntu.com utopic-security/main i386 Packages   


Hit http://ppa.launchpad.net utopic Release 


Hit http://security.ubuntu.com utopic-security/restricted i386 Packages

[Touch-packages] [Bug 701876] Re: Caps lock led does not light on TTY console.

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

** Bug watch removed: Linux Kernel Bug Tracker #7063
   http://bugzilla.kernel.org/show_bug.cgi?id=7063

** Bug watch removed: Linux Kernel Bug Tracker #7746
   http://bugzilla.kernel.org/show_bug.cgi?id=7746

** Bug watch removed: Debian Bug tracker #452103
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452103

** Also affects: console-setup (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514464
   Importance: Unknown
   Status: Unknown

** Package changed: kbd (Ubuntu) = console-setup (Ubuntu)

** Tags removed: caps leds lock setleds

** No longer affects: console-setup (Debian)

** Bug watch removed: Debian Bug tracker #514464
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514464

** This bug has been marked a duplicate of bug 425704
   [Ubuntu server] Capslock don't turn on LED

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
https://bugs.launchpad.net/bugs/701876

Title:
  Caps lock led does not light on TTY console.

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: kbd

  Ubuntu version:
  Description:  Ubuntu 10.04.1 LTS
  Release:  10.04

  Description:

  Although the caps lock function properly on both the console pure as
  the X.org, its LED lights only in the latter. At console, Num Lock and
  Scroll Lock leds works properly.

  After some research, I found utyility. By running it, with all LEDs
  off, it return this information (where 'desligado'='turned off'):

  Sinalizações-padrão atuais:  NumLock desligado   CapsLock desligado   
ScrollLock desligado
  Sinalizações atuais:  NumLock desligado   CapsLock desligado   
ScrollLock desligado
  Leds atuais:   NumLock desligado   CapsLock desligado   ScrollLock 
desligado

  By press caps lock key, setleds returns this same information. By type
  setleds +caps , Caps lock leds is turned on, but doesn't go off
  anymore, only with setleds -caps.

  I guess that can be a kbd bug because setleds is in this package. My
  Keyboard layout is BR-ABNT2. If you use 10.10 or a different keyboard
  layout, please confirm if this bug affects you too.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: kbd 1.15-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.37-12.26~lucid1-generic 2.6.37
  Uname: Linux 2.6.37-12-generic i686
  Architecture: i386
  Date: Wed Jan 12 09:57:28 2011
  ProcEnviron:
   SHELL=/bin/bash
   LANG=pt_BR.utf8
   LANGUAGE=pt_BR:pt:en
  SourcePackage: kbd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/701876/+subscriptions

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

[Touch-packages] [Bug 425704] Re: [Ubuntu server] Capslock don't turn on LED

** Tags added: i386 karmic

** Bug watch removed: Debian Bug tracker #514212
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514212

** Bug watch removed: Linux Kernel Bug Tracker #7746
   http://bugzilla.kernel.org/show_bug.cgi?id=7746

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/425704

Title:
  [Ubuntu server] Capslock don't turn on LED

Status in console-setup package in Ubuntu:
  Triaged
Status in console-setup package in Debian:
  Confirmed

Bug description:
  Karmic server i386 alpha 5 
  When I press Capslock then LED don't turn on.
  But Shift switch register normally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/425704/+subscriptions

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

[Touch-packages] [Bug 1374785] Re: Screen-saver fade-to-black does not cover entire screen on HiDPI

** Tags removed: ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1374785

Title:
  Screen-saver fade-to-black does not cover entire screen on HiDPI

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

Bug description:
  [ Impact ]

  When display scaling is set to 2x or greater the fade-to-black
  animation when the screen saver is invoked covers only a fraction of
  the screen.

  [ Test Case ]

  Requires a display with 2x UI scaling (works best with a high-DPI
  display).

  The fade-to-black which occurs prior to the screen shutting off only
  covers the top left quarter of the screen.

  When scaling is set to 1x, the entire screen fades to black.

  [ Regression Potential ]

  An invalid scaling calculation (or rounding error) could result in writing 
outside the screen buffer bounds with resulting unknown impact.  Inpspection 
and code review shows this not to be the case wit this patch.
  [ Other Info ]

  The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where
  it has been in production use in Ubuntu 'Vivid Vervet' for some time
  and has not shown ergressions.

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

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

[Touch-packages] [Bug 1375271] Re: desktop or other past screen contents visible before lockscreen on resume

** Tags added: suspend

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1375271

Title:
  desktop or other past screen contents visible before lockscreen on
  resume

Status in GNOME Screensaver:
  New
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  On resume from suspend, screen contents are displayed for a brief time
  (perhaps 0.5 to 1 sec)  before the lock dialog appears.

  These screen contents are not always the desktop or open application
  beneath the lock screen. On at least one occasion, the screen showed
  content from a full-screen video that had been playing in Firefox some
  time before the computer had been suspended: neither the video nor its
  underlying tab were open anymore, so the image(s) was likely part of a
  buffer somewhere. (Needless to say, if the wrong full-screen video had
  been watched, depending on the setting, this could be a quite serious
  issue for some users).

  [Test Case]

  Suspend and resume the computer (closing the lid or using the session
  indicator).  Since this problem involves a race condition, it is not
  reliably reproducable at will.

  [Regression Potential]

  This fix unmaps windows when a suspend or shutdown event occurs:  it
  is possible that the window(s) do not get remapped when a wake event
  occurs, or the wake even does not get propagated.  This does not
  appear to occur in practice.

  [Other Info]

  The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where
  it has been released in the Ubuntu Vivid Vervet development release
  for a couple of months with no apparent regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1375271/+subscriptions

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

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

The package in trusty-proposed doesn't solve the problem as described by
Daniel Serpell in comment #4. After assigning the audio raise volume
button as a shortcut in unity-control-center, the dconf key is set to
'AudioRaiseVolume' rather than 'XF86AudioRaiseVolume'.

$ apt list unity
Listing... Done
unity/trusty-proposed,now 7.2.4+14.04.20141217-0ubuntu1 amd64 
[installed,automatic]
$ gsettings get org.gnome.settings-daemon.plugins.media-keys volume-up
'AudioRaiseVolume'
$ gsettings reset org.gnome.settings-daemon.plugins.media-keys volume-up
$ gsettings get org.gnome.settings-daemon.plugins.media-keys volume-up
'XF86AudioRaiseVolume'

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1302885

Title:
  Media keyboard shortcuts not working

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

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

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

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

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

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

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

[Touch-packages] [Bug 1326188] Re: Wrong PDF standard fonts are replaced when fonts package fonts-texgyre is installed - PDFs are rendered with missing characters

2015-01-17 Thread madbiologist

This is fixed on Utopic in fontconfig 2.11.1-0ubuntu3 and on Trusty in
fontconfig 2.11.0-0ubuntu4.1

the Trusty changelog says:

  * 0001-Bug-73291-poppler-does-not-show-fl-ligature.patch: Don't alias TeX
Gyre Termes to Times as it has a broken 'fi' ligature. (LP: #1325230)
 -- Iain Lane iain.l...@canonical.com

Apparently people who upgrade from Trusty to Utopic are still affected
by this bug.

An even better fix is in poppler 0.28.1-1ubuntu1, which is currently
available in Ubuntu 15.04 Vivid Vervet development version.  As a
result of this fix, there are comments in an upstream bug for the
fontconfig changes to be reverted so as to restore normal behaviour to
LaTex and other packages that use the texgyre fonts.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1326188

Title:
  Wrong PDF standard fonts are replaced when fonts package fonts-
  texgyre is installed - PDFs are rendered with missing characters

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Hi,

  
  please see following bug report on freedesktop with screenshots:
  https://bugs.freedesktop.org/show_bug.cgi?id=79527

  When fonts package fonts-texgyre from the texgyre package is installed,
  all PDFs containing e.g. a reference to a Helvetica font, which is usually 
not installed on Ubuntu systems, fontconfig mages a very bad choice with one of 
the fonts supplied in fonts-texgyre (like TeX Gyre Heros).

  The problem is, apparantly the texgyre fonts us a different naming
  style for some important glyphs (like greek characters contained in
  many mathematical documents), so that fontconfig cannot find them.

  See screenshots in abovementioned bugreport: 
  == PDF readers only display a blank space in this case, which has 
potentially disastrous results (there are six orders of magnitude difference 
between an Ampere current and a Microampere current e.g..).

  There is a likely explanation also unter this bugreport:
  https://bugs.launchpad.net/ubuntu/+source/tex-gyre/+bug/1317599

  == Please change the Ubuntu font configuration so that all those PDFs
  are displayed correctly.

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

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

[Touch-packages] [Bug 1379375] Re: evince does not display ligatures

2015-01-17 Thread madbiologist

The patch mentioned in comment #5 is included in poppler
0.28.1-1ubuntu1, which is currently available in Ubuntu 15.04 Vivid
Vervet development version.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1379375

Title:
  evince does not display ligatures

Status in fontconfig package in Ubuntu:
  New

Bug description:
  While there's Bug #1325230 with the same title and the linked PDFs there are 
working fine here (displaying fi correctly) there seems to be still some bug 
regarding ligatures. 
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325230

  I have some PDFs substituting Helvetica (and others) with TeX Gyre
  Heros and showing no fi ligature.  I attached a patch I derived from
  the patch in Bug #1325230 which is working fine. Now it uses Nimbus
  Sans L and the ligatures are fine.

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

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

[Touch-packages] [Bug 1412077] [NEW] Logitech USB keyboard not working in initramfs

2015-01-17 Thread legolas558

Public bug reported:

This bug might either be in kernel or initramfs-tools.

With kernel linux-image-extra-3.13.0-36-generic (and previous) I cannot
verify the issue, but all other subsequent versions, and also latest
linux-image-extra-3.13.0-44-generic are affected by this issue.

Basically the hid-logitech-dj (and hid and hid-generic) are missing and
this makes the keyboard impossible to use in any initramfs program.

I have tried to force the usage of this module, but even with modprobe
it fails for unknown reasons.

Possibly related bugs:

#1238194
#1066376
#229732

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-bug

** Description changed:

  This bug might either be in kernel or initramfs-tools.
  
  With kernel linux-image-extra-3.13.0-36-generic (and previous) I cannot
  verify the issue, but all other subsequent versions, and also latest
  linux-image-extra-3.13.0-44-generic are affected by this issue.
  
- See also bugs #1238194  #1066376 #229732 which could constitute proof
- that this is a regression.
- 
  Basically the hid-logitech-dj (and hid and hid-generic) are missing and
  this makes the keyboard impossible to use in any initramfs program.
  
  I have tried to force the usage of this module, but even with modprobe
  it fails for unknown reasons.
+ 
+ Possibly related bugs:
+ 
+ #1238194
+ #1066376
+ #229732

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1412077

Title:
  Logitech USB keyboard not working in initramfs

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This bug might either be in kernel or initramfs-tools.

  With kernel linux-image-extra-3.13.0-36-generic (and previous) I
  cannot verify the issue, but all other subsequent versions, and also
  latest linux-image-extra-3.13.0-44-generic are affected by this issue.

  Basically the hid-logitech-dj (and hid and hid-generic) are missing
  and this makes the keyboard impossible to use in any initramfs
  program.

  I have tried to force the usage of this module, but even with modprobe
  it fails for unknown reasons.

  Possibly related bugs:

  #1238194
  #1066376
  #229732

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1412077/+subscriptions

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

[Touch-packages] [Bug 1412077] Re: USB keyboard not working in initramfs (hid issue)

2015-01-17 Thread legolas558

I tried adding these modules:

ehci_pci
usbcore
usb_common
xhci_hcd
uhci_hcd
ehci_hcd
ohci_hcd
usbhid

Same result.

Would it be possible to have verbose errors output when initramfs-tools
fails at loading some module? Silent failure is evil.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1412077

Title:
  USB keyboard not working in initramfs (hid issue)

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This bug might either be in kernel or initramfs-tools.

  Known good kernels:
  - linux-image-extra-3.13.0-35-generic
  - linux-image-extra-3.13.0-36-generic

  All other subsequent versions (including latest linux-image-
  extra-3.13.0-44-generic) are affected by this issue.

  Basically the hid modules (hid, hid-generic and usbhid) are not loaded
  and this makes the keyboard impossible to use in any initramfs CLI
  program that requires user input.

  I have tried to force the usage of this module, but even with modprobe
  it fails for reasons unknown to me.

  Possibly related bugs:

  #1238194
  #1066376
  #229732

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1412077/+subscriptions

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

[Touch-packages] [Bug 1285783] Re: Right panel has a transparent background

** Tags removed: background panel right transparent
** Tags added: running-unity

** Tags added: trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1285783

Title:
  Right panel has a transparent background

Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Fix Committed

Bug description:
  Launching gnome-tweak-tool and choosing a category on the left panel
  makes the right panel transparent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1285783/+subscriptions

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

[Touch-packages] [Bug 1245136] Re: Super+Space and Shift+Super+Space hotkeys for keyboard layout switching do not work in Saucy and Unity session

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

** This bug has been marked a duplicate of bug 1218322
   Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1245136

Title:
  Super+Space and Shift+Super+Space hotkeys for keyboard layout
  switching do not work in Saucy and Unity session

Status in unity package in Ubuntu:
  Expired

Bug description:
  On clean Ubuntu 13.10 install with enabled proposed updates Super+Space and 
Shift+Super+Space are default options for keyboard layout change.
  But they do not work in Unity session.
  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Oct 27 12:39:30 2013
  InstallationDate: Installed on 2013-10-20 (6 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MarkForUpload: True
  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/1245136/+subscriptions

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

[Touch-packages] [Bug 1325285] Re: Ubuntu Desktop locks session when screen shutdown

** Tags removed: desktop lock power session
** Tags added: lockscreen

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1325285

Title:
  Ubuntu Desktop locks session when screen shutdown

Status in lightdm package in Ubuntu:
  New

Bug description:
  When you let the power shutdown the screen, the session is locked even
  when you uncheck the lock and ask my password after resume

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

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

[Touch-packages] [Bug 1412077] Re: Logitech USB keyboard not working in initramfs

2015-01-17 Thread legolas558

** Description changed:

  This bug might either be in kernel or initramfs-tools.
  
- With kernel linux-image-extra-3.13.0-36-generic (and previous) I cannot
- verify the issue, but all other subsequent versions, and also latest
- linux-image-extra-3.13.0-44-generic are affected by this issue.
+ Known good kernels:
+ - linux-image-extra-3.13.0-35-generic
+ - linux-image-extra-3.13.0-36-generic
  
- Basically the hid-logitech-dj (and hid and hid-generic) are missing and
- this makes the keyboard impossible to use in any initramfs program.
+ All other subsequent versions (including latest linux-image-
+ extra-3.13.0-44-generic) are affected by this issue.
+ 
+ Basically the hid modules (hid, hid-generic and usbhid) are not loaded
+ and this makes the keyboard impossible to use in any initramfs CLI
+ program that requires user input.
  
  I have tried to force the usage of this module, but even with modprobe
- it fails for unknown reasons.
+ it fails for reasons unknown to me.
  
  Possibly related bugs:
  
  #1238194
  #1066376
  #229732

** Summary changed:

- Logitech USB keyboard not working in initramfs
+ USB keyboard not working in initramfs (hid issue)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1412077

Title:
  USB keyboard not working in initramfs (hid issue)

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This bug might either be in kernel or initramfs-tools.

  Known good kernels:
  - linux-image-extra-3.13.0-35-generic
  - linux-image-extra-3.13.0-36-generic

  All other subsequent versions (including latest linux-image-
  extra-3.13.0-44-generic) are affected by this issue.

  Basically the hid modules (hid, hid-generic and usbhid) are not loaded
  and this makes the keyboard impossible to use in any initramfs CLI
  program that requires user input.

  I have tried to force the usage of this module, but even with modprobe
  it fails for reasons unknown to me.

  Possibly related bugs:

  #1238194
  #1066376
  #229732

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1412077/+subscriptions

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

[Touch-packages] [Bug 876092] [NEW] Screen Lock wallpaper doesn't change after wallpaper is changed

You have been subscribed to a public bug:

On my newly upgraded Ubuntu Oneiric 11.10, I recently changed my
wallpaper and I locked my computer. When I shook my mouse and the
password prompt opened, my old wallpaper was still in the background.
When I logged back in, my new wallpaper was there, like it should be. I
would think that the wallpaper should automatically change on the lock
screen after I changed it on my desktop, opposed to what is happening
now.

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


** Tags: lockscreen oneiric
-- 
Screen Lock wallpaper doesn't change after wallpaper is changed
https://bugs.launchpad.net/bugs/876092
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unity in Ubuntu.

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

[Touch-packages] [Bug 1394614] Re: Cached results stay in scopes even with no internet

Caching branch is here: https://code.launchpad.net/~michihenning/unity-
scopes-api/cache-results/+merge/246257

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1394614

Title:
  Cached results stay in scopes even with no internet

Status in unity-scopes-api package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I am testing the latest image and as per the test plan, if internet is
  disabled there are cached results in a scope they should vanish as we
  refresh the scope but right now that's not the case.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.01.1+15.04.2014~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 20 15:06:59 2014
  InstallationDate: Installed on 2014-11-19 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141119-181707)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394614/+subscriptions

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

[Touch-packages] [Bug 1411075] Re: bluez-simple-agent crashes

2015-01-17 Thread gregrwm

ok apparently if blueman has already paired the device, then simple-
agent will succeed without crashing.  kind of defeats the purpose tho.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1411075

Title:
  bluez-simple-agent crashes

Status in bluez package in Ubuntu:
  New

Bug description:
  bluez-simple-agent crashes, in utopic, on a fresh install and fresh
  boot.  same crash after updating packages and reboot:

  $ bluez-simple-agent hci0 00:0C:8A:AA:FE:70 x
  Traceback (most recent call last):
File /usr/bin/bluez-simple-agent, line 127, in module
  device = adapter.FindDevice(args[1])
File /usr/lib/python3/dist-packages/dbus/proxies.py, line 70, in __call__
  return self._proxy_method(*args, **keywords)
File /usr/lib/python3/dist-packages/dbus/proxies.py, line 145, in __call__
  **keywords)
File /usr/lib/python3/dist-packages/dbus/connection.py, line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.bluez.Error.DoesNotExist: Does Not Exist

  this appears similar to Bug #1227584, but the dbus exception is not
  the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic i686
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Jan 14 20:30:08 2015
  InstallationDate: Installed on 2015-01-11 (3 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=9212f425-c8f3-4c80-8d62-41faf2b27d30 panic=30
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: K8M800-8237
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2008:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:15:83:6A:58:96  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:1170 acl:0 sco:0 events:65 errors:0
TX bytes:1056 acl:0 sco:0 commands:65 errors:0
  mtime.conffile..etc.bluetooth.audio.conf: 2015-01-11T15:59:05.078489
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

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

[Touch-packages] [Bug 1375271] Re: desktop or other past screen contents visible before lockscreen on resume

** Tags removed: lock
** Tags added: lockscreen

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1375271

Title:
  desktop or other past screen contents visible before lockscreen on
  resume

Status in GNOME Screensaver:
  New
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  On resume from suspend, screen contents are displayed for a brief time
  (perhaps 0.5 to 1 sec)  before the lock dialog appears.

  These screen contents are not always the desktop or open application
  beneath the lock screen. On at least one occasion, the screen showed
  content from a full-screen video that had been playing in Firefox some
  time before the computer had been suspended: neither the video nor its
  underlying tab were open anymore, so the image(s) was likely part of a
  buffer somewhere. (Needless to say, if the wrong full-screen video had
  been watched, depending on the setting, this could be a quite serious
  issue for some users).

  [Test Case]

  Suspend and resume the computer (closing the lid or using the session
  indicator).  Since this problem involves a race condition, it is not
  reliably reproducable at will.

  [Regression Potential]

  This fix unmaps windows when a suspend or shutdown event occurs:  it
  is possible that the window(s) do not get remapped when a wake event
  occurs, or the wake even does not get propagated.  This does not
  appear to occur in practice.

  [Other Info]

  The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where
  it has been released in the Ubuntu Vivid Vervet development release
  for a couple of months with no apparent regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1375271/+subscriptions

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

[Touch-packages] [Bug 876092] Re: Screen Lock wallpaper doesn't change after wallpaper is changed

** Tags removed: change lock screen wallpaper
** Tags added: lockscreen oneiric

** Package changed: ubuntu = unity (Ubuntu)

** Tags added: wallpaper

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/876092

Title:
  Screen Lock wallpaper doesn't change after wallpaper is changed

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  On my newly upgraded Ubuntu Oneiric 11.10, I recently changed my
  wallpaper and I locked my computer. When I shook my mouse and the
  password prompt opened, my old wallpaper was still in the background.
  When I logged back in, my new wallpaper was there, like it should be.
  I would think that the wallpaper should automatically change on the
  lock screen after I changed it on my desktop, opposed to what is
  happening now.

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

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

[Touch-packages] [Bug 1014356] Re: Custom desktop wallpaper isn't displayed in the greeter (12.4)

** Package changed: lightdm (Ubuntu) = unity-greeter (Ubuntu)

** Tags removed: ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1014356

Title:
  Custom desktop wallpaper isn't displayed in the greeter (12.4)

Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  Simple as that. If I choose one of the wallpapers bundled with
  Precise, it displays in the login screen. If I choose a custom image,
  it doesn't.

  I'm choosing images from my Images directory (my OS is set to
  French), and their permissions are set to 775, or -rw-rw-r--.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1014356/+subscriptions

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

[Touch-packages] [Bug 958431] Re: GtkSwitch background isn't logical

** Tags removed: background light-themes

** Tags removed: switchbuttons

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/958431

Title:
  GtkSwitch background isn't logical

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Step to reproduce the bug:
   - Open a GTK3 program with Ambiance or Radiance theme (e.g: Gnome Tweak 
Tool)
   - Find a Switchbutton (see Switchbuttons.png)
   - Click on it and see the background canging from Orange (ON) to Light 
Brown (OFF)
   - Drag slowly the switchbutton and see both ON and OFF position with 
Orange or Light Brown (see Switchbuttons_real.png)

  Expected behaviour:
   - Dragging a switchbutton should reveal Orange background color under ON 
position and Light Brown under OFF position (see Switchbuttons_expected.png)

  For further information see images related

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/958431/+subscriptions

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

[Touch-packages] [Bug 1412090] [NEW] when headphones are plugged in to socket, no sound[EQUIUM P200, Realtek ALC268, Black Headphone Out, Front] Playback problem

2015-01-17 Thread Nigel

Public bug reported:

upgraded about 2 months ago, head phone socket has not worked since
then.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic i686
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  snarge 1528 F pulseaudio
 /dev/snd/pcmC0D0c:   snarge 1528 F...m pulseaudio
 /dev/snd/pcmC0D0p:   snarge 1528 F...m pulseaudio
CurrentDesktop: Unity
Date: Sun Jan 18 01:40:14 2015
InstallationDate: Installed on 2012-08-01 (899 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: Only some of outputs are working
Title: [EQUIUM P200, Realtek ALC268, Black Headphone Out, Front] Playback 
problem
UpgradeStatus: Upgraded to trusty on 2014-08-13 (158 days ago)
dmi.bios.date: 10/23/2007
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.90
dmi.board.name: ISRAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.90:bd10/23/2007:svnTOSHIBA:pnEQUIUMP200:pvrPSPB5E-003004KS:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: EQUIUM P200
dmi.product.version: PSPB5E-003004KS
dmi.sys.vendor: TOSHIBA

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1412090

Title:
  when headphones are plugged in to socket, no sound[EQUIUM P200,
  Realtek ALC268, Black Headphone Out, Front] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  upgraded about 2 months ago, head phone socket has not worked since
  then.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  snarge 1528 F pulseaudio
   /dev/snd/pcmC0D0c:   snarge 1528 F...m pulseaudio
   /dev/snd/pcmC0D0p:   snarge 1528 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jan 18 01:40:14 2015
  InstallationDate: Installed on 2012-08-01 (899 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [EQUIUM P200, Realtek ALC268, Black Headphone Out, Front] Playback 
problem
  UpgradeStatus: Upgraded to trusty on 2014-08-13 (158 days ago)
  dmi.bios.date: 10/23/2007
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.90
  dmi.board.name: ISRAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.90:bd10/23/2007:svnTOSHIBA:pnEQUIUMP200:pvrPSPB5E-003004KS:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: EQUIUM P200
  dmi.product.version: PSPB5E-003004KS
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1412090/+subscriptions

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

[Touch-packages] [Bug 978936] Re: Logout fails to return to login window

** Tags removed: gnome3 ui xfce xubuntu-desktop

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/978936

Title:
  Logout fails to return to login window

Status in lightdm package in Ubuntu:
  New

Bug description:
  I have recently installed Ubuntu 11.10, followed by my installing 
xubuntu-desktop through Synaptic. I can log in normally, and use XFCE 
normally(By selecting it with the gear icon at the login screen to select XFCE 
session), but upon logout, I get a blank screen for about 15 sec., followed by 
screen corruption which looks like scrambled pixels from the logon screen. I 
will attach a photo later.
  I expect to see the logon screen.
  Distro and flavor: Ubuntu 11.10
  xubuntu-desktop:
    Installed: 2.138.1
    Candidate: 2.138.1
  Steps to reproduce:
  1)Install Ubuntu 11.10 amd64 through wubi
  2)Install xubuntu-desktop through Synaptic.
  3)Attempt a logon selecting XFCE session instead of Ubuntu or Ubuntu 2D.
  4)Use XFCE normally.
  5)Attempt logout.
  5a) Note screen corruption.
  A hard reboot is necessary to fix situation.
  ALT+SYSRQ+K does not work to force logoff in this situation.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xubuntu-desktop 2.138.1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Wed Apr 11 09:40:39 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 876092] Re: Screen Lock wallpaper doesn't change after wallpaper is changed

2015-01-17 Thread Andrea Azzarone

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

** Also affects: gnome-screensaver (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/876092

Title:
  Screen Lock wallpaper doesn't change after wallpaper is changed

Status in gnome-screensaver package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Invalid

Bug description:
  On my newly upgraded Ubuntu Oneiric 11.10, I recently changed my
  wallpaper and I locked my computer. When I shook my mouse and the
  password prompt opened, my old wallpaper was still in the background.
  When I logged back in, my new wallpaper was there, like it should be.
  I would think that the wallpaper should automatically change on the
  lock screen after I changed it on my desktop, opposed to what is
  happening now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/876092/+subscriptions

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

[Touch-packages] [Bug 1378416] Re: [krillin] disable WiFi, Mobile Data not available

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1378416

Title:
  [krillin] disable WiFi, Mobile Data not available

Status in network-manager package in Ubuntu:
  Expired
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Install RTM88 on krillin
  2. Use the system a litlle on wifi
  3. Pull down the indicator network
  4. Disable Wifi

  EXPECTED:
  I expect the system to seemless flip over to using 3g

  ACTUAL:
  I got no page (see screen shot) I tried pinging google and got ping: unknown 
host google.com

  ip route gave no feedback
  phablet@ubuntu-phablet:~$ nmcli dev
  DEVICE TYPE  STATE
  /ril_1 gsm   disconnected
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  Devices is correct.

  The debug.txt in comment #3 clearly shows that mobile data is
  connected via the list-modems output and list-contexts output.  This
  output also agrees with the nmcli output which shows /ril_0 as
  connected.  The smoking gun here looks to be the routing table, which
  is empty.

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

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

[Touch-packages] [Bug 1025971] Re: bluetooth is ON after standby although I've switched it off in the settings

** Tags removed: 12.04 arm bluetooth power power-management power-saving 
powermanagement powersaving standby wakeup
** Tags added: resume suspend

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1025971

Title:
  bluetooth is ON after standby although I've switched it off in the
  settings

Status in Enablement project for the Toshiba AC100 NetBook:
  New
Status in GNOME Bluetooth:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  To save battery on my Toshiba AC100 with Ubuntu 12.04 installed on it,
  I've switched off bluetooth in the settings GUI. But I notice that
  sometimes bluetooth is again ON. It seems that it becomes ON after I
  go back from a standby mode.

  I'll make an experiment and I will attach an hci.log (as asked) if the
  bug reoccurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluetooth (not installed)
  Uname: Linux 3.0.27-1-ac100 armv7l
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: armhf
  Date: Wed Jul 18 14:04:53 2012
  InterestingModules: bnep rfcomm btusb bluetooth
  ProcKernelCmdLine: mem=448M@0M 
tegrapart=recovery:300:a00:800,boot:d00:1000:800,mbr:1d00:200:800 
root=UUID=d42b885d-2e92-4236-b17e-d1efc2edb7ca quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 6C:62:6D:17:96:FD  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:1106 acl:0 sco:0 events:37 errors:0
TX bytes:645 acl:0 sco:0 commands:36 errors:0

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

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

[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

2015-01-17 Thread Jeff Johnson

I found a way to duplicate this issue.

Run the following script in a terminal:
#!/bin/sh
sleep 10
update-manager --no-focus-on-map

Before the update-manager pops up, log into a Guest Session.  Wait
about 10 seconds, then switch back.  Enter your password at the greeting
screen.  Then you'll see a 'Enter the root password' type of box since
update-manager needs root permissions.  I hit cancel on that window.
Finally, there will be an update-manager icon (the green A with a
progress bar through it)  in the list of program at the left, but it
can't be clicked on to bring it up.  It can be right-clicked to close
it.  Also, alt-tab shows it, but won't switch to it.

Potential pre-requisites:  I'm running on a laptop with an external
monitor.  They are different resolutions.  Also there is an update
available to install.  I'm running Ubuntu 14.04, but I've seen it on
12.04.

Interestingly enough, my Guest Session runs on tty F8, meaning that I
can press Ctrl-Alt-F8 and see the guest session.  When I press Ctrl-
Alt-F7 I get my normal session.

I have no clue how to continue looking at this problem.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1003950

Title:
  launcher does not show minimized update manager while clicked

Status in Compiz:
  New
Status in Accelerated Xorg driver for nVidia cards:
  New
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in binary-driver-fglrx package in Ubuntu:
  New
Status in intel-linux-graphics-installer package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in binary-driver-fglrx source package in Precise:
  New
Status in intel-linux-graphics-installer source package in Precise:
  New
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Precise:
  New
Status in binary-driver-fglrx source package in Quantal:
  New
Status in intel-linux-graphics-installer source package in Quantal:
  New
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix
Status in xserver-xorg-video-nouveau source package in Quantal:
  New

Bug description:
  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

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

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

[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions

2015-01-17 Thread yohan

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/972077

Title:
  apt repository disk format has race conditions

Status in apt package in Ubuntu:
  New

Bug description:
  Apt archives are accessed over HTTP; this has resulted in a cluster of
  bugs (reported here, and upstream) about problems behind intercepting
  caches, problems with squid etc.

  There are 3 interlocking issues:
  A - mirror networks may be out of sync with each other (e.g. a file named on 
one mirror may no longer exist, or may not yet exist, on another mirror)
  B - updating files on a single mirror is not atomic - and even small windows 
of inconsistency will, given enough clients, cause headaches.
  C - caches exacerbate race conditions - when one happens, until the cached 
data expires, all clients of the cache will suffer from the race

  Solving this requires one of several things:
   - file system transactions
   - an archive format that requires only weakly ordered updates to the files 
at particular urls with the assumption that only one file may be observed to 
change at a time (because a lookup of file A, then B, may get a cache miss on A 
and a cache hit on B, so even if all clients strictly go A, then B, updates may 
still see old files when paths are reused).
   - super robust clients that repeatedly retry with progressively less cache 
friendly headers until they have a consistent view. (This is very tricky to do).

  It may be possible to do a tweak to the apt repository format though,
  which would allow publishing a race-free format in parallel with the
  existing layout, while clients migrate. To be safe against issue (A)
  the mirror network would need some care around handling of dns round-
  robin mirrors [to minimise the situation where referenced data is not
  available], but this should be doable - or alternatively clients doing
  'apt-get update' may need to be willing to retry to accommodate round-
  robin skew.

  What would such an archive format look like?
  It would have only one well known file name (e.g. Releases-2), which would be 
internally signed. Rather than signing e.g. Packages.gz, it would sign a 
uniquely named packages and sources file - e.g. Packages-$HASH.gz or 
Packages-$serialno.gz.

  Backwards compatibility is achieved by using the same filenames for
  deb's and the like. We need to keep writing Packages.gz though, and
  Releases, until we no longer worry about old apt clients. We can
  optimise disk space a little by making Packages.gz a symlink to a
  Packages-$HASH.gz (and so on for Sources..), but it may be simpler and
  less prone to unexpected behaviour to keep using regular files.

  tl;dr
   * Unique file names for all unique file content with one exception
   * Releases-2, a self-signed file that provides hashes and names the index 
files (Packages, Sources, Translations etc)
   * Coexists with existing archive layout

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

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

[Touch-packages] [Bug 1357143] Re: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:6:__gnu_cxx::__verbose_terminate_handler:cxxabiv1::terminate:std::terminate:cxxabiv1::cxa_throw:unity::

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1357143

Title:
  /usr/lib/arm-linux-gnueabihf/unity-
  
scopes/scoperunner:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:unity::scopes::Variant::get_string

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu RTM:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scopes-api.  This problem was most recently seen with
  version 0.6.1+14.10.20140809-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/c88b5501559a748cac3331be6593ccad021d1580
  contains more details.

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

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

[Touch-packages] [Bug 1326816] Re: Replace QNetwork with net-cpp

** Branch linked: lp:~marcustomlinson/unity-scopes-api/switch-to-net-cpp

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1326816

Title:
  Replace QNetwork with net-cpp

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  There really is no need for us to over complicate unity-scopes-api by
  dragging Qt into the mix, when we have a cleaner pure C++ solution
  available: net-cpp.

  We should replace the use of QNetwork with net-cpp, hence removing our
  dependency on Qt all together.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1326816/+subscriptions

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

[Touch-packages] [Bug 1394614] Re: Cached results stay in scopes even with no internet

I agree. Caching is nice. At least there is *something* on screen.

We have branch pending that adds push_surfacing_results_from_cache() to
the Reply proxy. The run time caches all surfacing queries
transparently. If scope gets a surfacing query and detects that it can't
answer it (network down, or data source off-line), it can call this
method to replay the results of the most recent successful surfacing
query.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1394614

Title:
  Cached results stay in scopes even with no internet

Status in unity-scopes-api package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I am testing the latest image and as per the test plan, if internet is
  disabled there are cached results in a scope they should vanish as we
  refresh the scope but right now that's not the case.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.01.1+15.04.2014~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 20 15:06:59 2014
  InstallationDate: Installed on 2014-11-19 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141119-181707)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394614/+subscriptions

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

[Touch-packages] [Bug 1394614] Re: Cached results stay in scopes even with no internet

Caching branch is here: https://code.launchpad.net/~michihenning/unity-
scopes-api/cache-results/+merge/246257

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1394614

Title:
  Cached results stay in scopes even with no internet

Status in unity-scopes-api package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I am testing the latest image and as per the test plan, if internet is
  disabled there are cached results in a scope they should vanish as we
  refresh the scope but right now that's not the case.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.01.1+15.04.2014~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 20 15:06:59 2014
  InstallationDate: Installed on 2014-11-19 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141119-181707)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394614/+subscriptions

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

[Touch-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

2015-01-17 Thread Norbert

** Tags removed: amd64

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1245473

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  Unknown
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

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

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1245473/+subscriptions

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

[Touch-packages] [Bug 1270579] Re: Ubuntu should have an upstart job for saving/restoring backlight level on laptops

2015-01-17 Thread Norbert

** Tags removed: i386
** Tags added: precise quantal raring saucy utopic

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1270579

Title:
Ubuntu should have an upstart job for saving/restoring backlight level
on laptops

Status in elementary OS:
Confirmed
Status in One Hundred Papercuts:
Confirmed
Status in The Linux Mint Distribution:
New
Status in Ubuntu MATE:
Opinion
Status in systemd package in Ubuntu:
Triaged
Status in sysvinit package in Ubuntu:
Confirmed
Status in upstart package in Ubuntu:
New
Status in sysvinit package in Debian:
New

Bug description:
Dear all!

I have tested many distros - Arch, OpenSuSe 13.1, Fedora 20, ALT Linux p7,
Sabayon, Mageia 4.
Many of them are based on systemd.
It does not matter what init system they use, but all of them have very
usefull script (or binary program, I don't know) for saving and restoring
backlight level on laptop.

In these distros there is a script for save and restore backlight levels for
two video-cards (acpi_video0 and acpi_video1). During system boot it is
indicated as follows:

[ OK ] Started Load/Save Screen Backlight Brightness of acpi_video1.
[ OK ] Started Load/Save Screen Backlight Brightness of acpi_video0.
.

Steps to reproduce:
1. User boots laptop (cold boot, not wake from suspend)
2. User sets comfortable backlight level
3. User ends his/her work by shutting down the laptop (not suspend, so
backlight level is not saved)
4. Go to 1 (another cold boot with reseted backlight level).

According to the list of duplicates and bug heat this bug/feature
request is very important.

As you know laptop market share is gigantic (see for example
http://www.statista.com/statistics/276772/ultrabook-share-of-global-notebook-market-since-2011/
for stats).
Also Ubuntu and Debian market share are increasing.

So I can't believe why this usability fault exists in Ubuntu (and Debian) for
years.
It seems that guys from `systemd` understand the problem correctly (sooner or
later - on 14 Aug 2013, see
https://github.com/systemd/systemd/commits/56f64d95763a799ba4475daf44d8e9f72a1bd474/src/backlight/backlight.c
), but `upstart` and `sysvinit` developers not.

As you can remember I tried to fix the problem by myself (see my comment on
askubuntu
http://askubuntu.com/questions/151651/brightness-is-reset-to-maximum-on-every-restart/227553#227553)
- I created first version of an init script for saving and restoring backlight
level (on 10 Dec 2012 - two years ago).
It had one disadvantage - it operates only when laptop has one graphical
adaptor and its name was hardcoded to the script (*acpi_video0* in my case).

So on 2014-12-28 I presented new version of a script - it can save and
restore backlight levels of all graphical, adaptors, which are found in
`/sys/class/backlight/*`.
The init script with symlink aPlease note: ire packed to archive (see
attachment to comment #18 -
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1270579/+attachment/4288756/+files/upstart_brightness.tar.gz
).
The script is tested on Ubuntu Precise 12.04.5 and Ubuntu Trusty 14.04.1.

If you have installed its previous version (from comment #15) - you can
remove its files with commands:
sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness
then extract new version with commands:
sudo tar -zxvf upstart_brightness.tar.gz -C /

I hope my script will help somebody.
Thanks for testing!

To Ubuntu developers: please contact me if you are ready to include
and distribute my script to 12.04 and 14.04 deb-pakages.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: initscripts 2.88dsf-41ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic i686
ApportVersion: 2.13.1-0ubuntu1
Architecture: i386
CurrentDesktop: GNOME
Date: Sun Jan 19 17:20:26 2014
InstallationDate: Installed on 2013-10-20 (91 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
SourcePackage: sysvinit
UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago)

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

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

[Touch-packages] [Bug 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)

2015-01-17 Thread Norbert

** Tags removed: i386
** Tags added: saucy utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1263228

Title:
  icons in indicators are small (difficult to view on FullHD display and
  smaller than was on 12.04)

Status in Application Indicators:
  New
Status in The Date and Time Indicator:
  New
Status in Indicator keyboard:
  New
Status in The Messaging Menu:
  New
Status in The Power Indicator:
  New
Status in The Session Menu:
  New
Status in Sound Menu:
  New
Status in Libindicator:
  New
Status in gnome-panel package in Ubuntu:
  Triaged
Status in indicator-application package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in indicator-keyboard package in Ubuntu:
  Triaged
Status in indicator-messages package in Ubuntu:
  Triaged
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-session package in Ubuntu:
  Triaged
Status in indicator-sound package in Ubuntu:
  Triaged
Status in libindicator package in Ubuntu:
  Triaged

Bug description:
  I have Ubuntu 14.04 with all updates installed.

  My screen resolution is 1920x1080 (FullHD) at 16.4 inches.
  Icons from the menu of newest indicator-keyboard and other gnome-panel icons 
are very small (difficult to read).

  Please adapt icon sizes to large screen resolutions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Dec 21 00:41:25 2013
  InstallationDate: Installed on 2013-10-20 (61 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago)

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

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

[Touch-packages] [Bug 1411954] [NEW] Screensaver not starting before login

2015-01-17 Thread M.C. Botha

Public bug reported:

Screen stays on

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity 7.3.1+14.10.20141016-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Jan 17 12:49:04 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c0d5]
 NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c0d5]
InstallationDate: Installed on 2014-12-12 (36 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3C/700Z5C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic 
root=UUID=aee4438f-42fe-4658-a44c-853832cd50a6 ro quiet splash 
intel_pstate=disable elevator=deadline vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P07ABJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP700Z5C-S02ZA
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP07ABJ:bd11/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3C/700Z5C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP700Z5C-S02ZA:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 700Z3C/700Z5C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Sat Jan 17 08:19:44 2015
xserver.configfile: default
xserver.errors:
 Failed to load module nvidia (module does not exist, 0)
 Failed to load module nvidia (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12619 
 vendor SEC
xserver.version: 2:1.16.0-1ubuntu1.2

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1411954

Title:
  Screensaver not starting before login

Status in unity package in Ubuntu:
  New

Bug description:
  Screen stays on

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jan 17 12:49:04 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c0d5]
   NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c0d5]
  InstallationDate: Installed on 2014-12-12 (36 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3C/700Z5C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic

[Touch-packages] [Bug 1411959] [NEW] Hide autostart launcher in Xfce

2015-01-17 Thread Thaddaeus Tintenfisch

Public bug reported:

Please remove Xfce from the OnlyShowIn= parameter in
/etc/xdg/autostart/indicator-{application,sound}.desktop. These
launchers should not be visible in the Xfce autostart settings window,
because indicators are already launched and managed by xfce4-indicator-
plugin (- upstart).

http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/xfce4
-indicator-plugin/vivid/view/head:/debian/patches/01_upstart-init.patch

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1411959

Title:
  Hide autostart launcher in Xfce

Status in indicator-application package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Please remove Xfce from the OnlyShowIn= parameter in
  /etc/xdg/autostart/indicator-{application,sound}.desktop. These
  launchers should not be visible in the Xfce autostart settings window,
  because indicators are already launched and managed by xfce4
  -indicator-plugin (- upstart).

  http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/xfce4
  -indicator-plugin/vivid/view/head:/debian/patches/01_upstart-
  init.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1411959/+subscriptions

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

[Touch-packages] [Bug 1312137] Re: Local menus broken for Qt apps after opening dialog

2015-01-17 Thread Alex Solanos

That was one nasty bug.

Glad it was fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1312137

Title:
  Local menus broken for Qt apps after opening dialog

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I have selected to have window menus in the window's title bar. This
  works great, except for Qt apps. After selecting a menu item in a Qt
  app that produces a dialog, the menu is no longer accessible. e.g.

  1. Start qtcreator
  2. Resize window so that it is not maximised
  3. Select 'Help' - 'About Qt Creator'
  4. Dismiss 'About Qt Creator' dialog
  5. Move mouse over window titlebar - menu is no longer shown.

  The only way to get the menu back, is to switch to another window, and
  then back to the affected app.

  Note: This does not seem to affect the 'File' dialog from QtCreator -
  I'm assuming this is because it loads the Gtk file dialog.

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

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

[Touch-packages] [Bug 1359740] Re: the livecd based on initrd.img-3.13.0-34-generic.img does not start :unable to find a medium containing a live file system

2015-01-17 Thread BigK

Results of some commands issued in this busybox shell

(initramfs) mountroot
mount: mounting /dev/sr0 on /cdrom failed: No such device

(initramfs) blkid
/dev/sr0: LABEL=Customized Ubuntu Live CD TYPE=iso9660

(initramfs) mount -t iso9660 -o ro,noatime /dev/sr0 /cdrom
mount: mounting /dev/sr0 on /cdrom failed: No such device

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1359740

Title:
  the livecd based on  initrd.img-3.13.0-34-generic.img does not start
  :unable to find a medium containing a live file system

Status in Ubuntu Customization Kit:
  New
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I used  uck and manual live cd customization with chroot. I remastered a 
14.04 xubuntu livecd.
  Done a successfull  apt-get dist-upgrade in chroot using workarounds  from 
Bug #1325142 and Bug #1211933.
  But the cd won't boot due to initramfs initrd.img-3.13.0-34-generic updated 
during upgrade.

  I got a 'unable to find a medium containing a live file system'
  message error and a busybox shell.

  last boot messages were : 'mount: mounting /dev/sr0 on /cdrom failed:
  No such device'

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

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

[Touch-packages] [Bug 1321045] Re: Can't unmount NFS mount point as user (not found error)

2015-01-17 Thread Erik

This problem has been actually solved upstream: upgrading to util-
linux-2.25 has solved the issue. I have used the ppa:flexiondotorg/util-
linux repo to do so.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1321045

Title:
  Can't unmount NFS mount point as user (not found error)

Status in util-linux package in Ubuntu:
  Confirmed
Status in util-linux package in Debian:
  New

Bug description:
  Dear fellows,

  I had a strange behavior since I upgraded to 14.04 LTS about my user-
  mountable NFS shares. My /etc/fstab follows:

  # NFS shares from Synology Diskstation
  192.168.25.107:/volume1/Documentos/mnt/Documentos nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Downloads /mnt/Downloads  nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Imagens   /mnt/Imagensnfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Músicas   /mnt/Músicasnfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Vídeos/mnt/Vídeos nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr

  Notice I'm using noauto (don't try to mount at boot) and users (any user can 
mount or umount).
  I can mount normally as user. However, when I try to umount, the following 
message appears:

  $ umount /mnt/Documentos
  umount.nfs4: /mnt/Documentos: not found
  umount.nfs4: /mnt/Documentos: not found
  (message appears 2 times, exactly)

  So, if I try to issue a umount as a superuser (sudo umount
  /mnt/Documentos), it works flawlessly.

  Believe this is a bug that happened in the past on Debian (see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661527), and it was
  solved back then. I'm afraid it would be reintroduced at some point.

  Status of directory permissions at /mnt:

  $ ls -l /mnt
  total 20
  drwxr-xr-x 2 tulio tulio 4096 Abr 12 19:57 Documentos
  drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Downloads
  drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Imagens
  drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Músicas
  drwxr-xr-x 2 tulio tulio 4096 Mar 12 20:59 Vídeos

  Thanks in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libmount1 2.20.1-5.1ubuntu20
  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.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 19 20:30:47 2014
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1321045/+subscriptions

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

[Touch-packages] [Bug 1411972] [NEW] systemd service blocks upgrade on desktop

2015-01-17 Thread Edwin Pujols

Public bug reported:

When powerd is installed on the desktop, upgrading it fails given that
`lxc-android-config.service` doesn't exist: dpkg aborts the upgrade on
the final steps since it cannot restart `lxc-android-config`.

I had powerd installed because I recognized that some Unity 7 packages
suggested it (I installed from a mini iso).

Description:Ubuntu Vivid Vervet (development branch)
Release:15.04

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: powerd (not installed)
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic x86_64
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
Date: Sat Jan 17 08:41:24 2015
SourcePackage: powerd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1411972

Title:
  systemd service blocks upgrade on desktop

Status in powerd package in Ubuntu:
  New

Bug description:
  When powerd is installed on the desktop, upgrading it fails given that
  `lxc-android-config.service` doesn't exist: dpkg aborts the upgrade on
  the final steps since it cannot restart `lxc-android-config`.

  I had powerd installed because I recognized that some Unity 7 packages
  suggested it (I installed from a mini iso).

  Description:Ubuntu Vivid Vervet (development branch)
  Release:15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: powerd (not installed)
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jan 17 08:41:24 2015
  SourcePackage: powerd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/972077

Title:
  apt repository disk format has race conditions

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Apt archives are accessed over HTTP; this has resulted in a cluster of
  bugs (reported here, and upstream) about problems behind intercepting
  caches, problems with squid etc.

  There are 3 interlocking issues:
  A - mirror networks may be out of sync with each other (e.g. a file named on 
one mirror may no longer exist, or may not yet exist, on another mirror)
  B - updating files on a single mirror is not atomic - and even small windows 
of inconsistency will, given enough clients, cause headaches.
  C - caches exacerbate race conditions - when one happens, until the cached 
data expires, all clients of the cache will suffer from the race

  Solving this requires one of several things:
   - file system transactions
   - an archive format that requires only weakly ordered updates to the files 
at particular urls with the assumption that only one file may be observed to 
change at a time (because a lookup of file A, then B, may get a cache miss on A 
and a cache hit on B, so even if all clients strictly go A, then B, updates may 
still see old files when paths are reused).
   - super robust clients that repeatedly retry with progressively less cache 
friendly headers until they have a consistent view. (This is very tricky to do).

  It may be possible to do a tweak to the apt repository format though,
  which would allow publishing a race-free format in parallel with the
  existing layout, while clients migrate. To be safe against issue (A)
  the mirror network would need some care around handling of dns round-
  robin mirrors [to minimise the situation where referenced data is not
  available], but this should be doable - or alternatively clients doing
  'apt-get update' may need to be willing to retry to accommodate round-
  robin skew.

  What would such an archive format look like?
  It would have only one well known file name (e.g. Releases-2), which would be 
internally signed. Rather than signing e.g. Packages.gz, it would sign a 
uniquely named packages and sources file - e.g. Packages-$HASH.gz or 
Packages-$serialno.gz.

  Backwards compatibility is achieved by using the same filenames for
  deb's and the like. We need to keep writing Packages.gz though, and
  Releases, until we no longer worry about old apt clients. We can
  optimise disk space a little by making Packages.gz a symlink to a
  Packages-$HASH.gz (and so on for Sources..), but it may be simpler and
  less prone to unexpected behaviour to keep using regular files.

  tl;dr
   * Unique file names for all unique file content with one exception
   * Releases-2, a self-signed file that provides hashes and names the index 
files (Packages, Sources, Translations etc)
   * Coexists with existing archive layout

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

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

[Touch-packages] [Bug 1411978] [NEW] package udev 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-01-17 Thread Kevin Cole

Public bug reported:

I don't have further details, other than this possibly being an artifact
of attempting to switch to systemd about a month ago, and an attempt to
switch back to upstart about a week ago.  While I'm sure that's the
problem with a few other packages, today was the first time I saw udev
complain during a dist-upgrade.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: udev 208-8ubuntu8.2
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CustomUdevRuleFiles: 55-primesense-usb.rules 60-raw1394.rules 51-android.rules
Date: Sat Jan 17 08:11:05 2015
DuplicateSignature: package:udev:208-8ubuntu8.2:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2011-10-25 (1179 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
MachineType: System76, Inc. Bonobo Professional
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic 
root=UUID=94f7fc1e-fa27-4b24-99f3-4b461665a4a4 ro quiet splash
SourcePackage: systemd
Title: package udev 208-8ubuntu8.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to utopic on 2014-11-03 (75 days ago)
dmi.bios.date: 08/09/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: Not Applicable
dmi.board.name: Bonobo Professional
dmi.board.vendor: System76, Inc.
dmi.board.version: bonp5
dmi.chassis.asset.tag: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: bonp5
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnBonoboProfessional:pvrbonp5:rvnSystem76,Inc.:rnBonoboProfessional:rvrbonp5:cvnSystem76,Inc.:ct10:cvrbonp5:
dmi.product.name: Bonobo Professional
dmi.product.version: bonp5
dmi.sys.vendor: System76, Inc.

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


** Tags: amd64 apport-package utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1411978

Title:
  package udev 208-8ubuntu8.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't have further details, other than this possibly being an
  artifact of attempting to switch to systemd about a month ago, and an
  attempt to switch back to upstart about a week ago.  While I'm sure
  that's the problem with a few other packages, today was the first time
  I saw udev complain during a dist-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: udev 208-8ubuntu8.2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CustomUdevRuleFiles: 55-primesense-usb.rules 60-raw1394.rules 51-android.rules
  Date: Sat Jan 17 08:11:05 2015
  DuplicateSignature: package:udev:208-8ubuntu8.2:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-10-25 (1179 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MachineType: System76, Inc. Bonobo Professional
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic 
root=UUID=94f7fc1e-fa27-4b24-99f3-4b461665a4a4 ro quiet splash
  SourcePackage: systemd
  Title: package udev 208-8ubuntu8.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2014-11-03 (75 days ago)
  dmi.bios.date: 08/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Bonobo Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: bonp5
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: bonp5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnBonoboProfessional:pvrbonp5:rvnSystem76,Inc.:rnBonoboProfessional:rvrbonp5:cvnSystem76,Inc.:ct10:cvrbonp5:
  dmi.product.name: Bonobo Professional
  dmi.product.version: bonp5
  dmi.sys.vendor: System76, Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe :

[Touch-packages] [Bug 1401677] Re: hwdb.bin does not exist during live system boot

2015-01-17 Thread Bruce Pieterse

** Tags removed: iso-testing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1401677

Title:
  hwdb.bin does not exist during live system boot

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Using the current daily build of vivid for Ubuntu Gnome in Virtualbox,
  after the welcome screen is displayed and switching to tty1 on the
  live CD I see:

  starting version 217
  hwdb.bin does not exist, please run udevadm hwdb --update
  Network interface NamePolicy= disabled on kernel commandline, ignoring.
  invalid key/value pair in file /lib/udev/rules.d/97-dmraid.rules on line 8, 
starting at character 95 ('a')
  [45.279072] systemd-logind[3430]: Failed to start user service: Unknown unit: 
user@999.service

  Welcome to Ubuntu Vivid Vervet (development branch)
  ...snip...

  Last week the above output was present post-installation. Currently
  this is not present post-installation with the current daily build.

  However the system-logind error (Unknown init) persists and is
  currently present post-installation with slight difference of user@999
  becoming user@1000.

  I found this bug report which has been marked as Fix released but
  not sure if these are related or not:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1190947.

  I have a screenshot from last week which I installed a daily build
  image on physical hardware. Some of the errors in that screenshot are
  no longer present (whoopsie  basename). If you need it please let me
  know.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 217-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 11 23:32:03 2014
  InstallationDate: Installed on 2014-12-11 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141211)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=c0cdf4f1-f502-41e5-8d1f-26b30d67242d ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1411978] Re: package udev 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-01-17 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1411978

Title:
  package udev 208-8ubuntu8.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't have further details, other than this possibly being an
  artifact of attempting to switch to systemd about a month ago, and an
  attempt to switch back to upstart about a week ago.  While I'm sure
  that's the problem with a few other packages, today was the first time
  I saw udev complain during a dist-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: udev 208-8ubuntu8.2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CustomUdevRuleFiles: 55-primesense-usb.rules 60-raw1394.rules 51-android.rules
  Date: Sat Jan 17 08:11:05 2015
  DuplicateSignature: package:udev:208-8ubuntu8.2:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-10-25 (1179 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MachineType: System76, Inc. Bonobo Professional
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic 
root=UUID=94f7fc1e-fa27-4b24-99f3-4b461665a4a4 ro quiet splash
  SourcePackage: systemd
  Title: package udev 208-8ubuntu8.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2014-11-03 (75 days ago)
  dmi.bios.date: 08/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Bonobo Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: bonp5
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: bonp5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnBonoboProfessional:pvrbonp5:rvnSystem76,Inc.:rnBonoboProfessional:rvrbonp5:cvnSystem76,Inc.:ct10:cvrbonp5:
  dmi.product.name: Bonobo Professional
  dmi.product.version: bonp5
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 796527] Re: Launcher - Count indicator should change size depending on the number of digits

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/796527

Title:
  Launcher - Count indicator should change size depending on the number
  of digits

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

Bug description:
  [ Impact ]

  The count indicator currently stays the same size irrespective of
  whether it is displaying one or two digits.

  Desired solution:
  If the count indicator only displays one digit it should be a circle e.g (7)
  If the count indicator displays two digits it should be a lozenge shape e.g. 
two half circles joined by two straight lines e.g. (27)
  If the count indicator displays three digits it should be a lozenge shape 
e.g. two half circles joined by two straight lines e.g (527)

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  unleash a new crash or lockup in the desktop.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some months now without
  apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/796527/+subscriptions

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

[Touch-packages] [Bug 1405954] Re: Touchpag detected but not working

2015-01-17 Thread Silmar

Bump

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1405954

Title:
  Touchpag detected but not working

Status in xorg package in Ubuntu:
  New

Bug description:
  Dec 27 10:49:30 skynote kernel: [0.838154] input: FocalTechPS/2 FocalTech 
FocalTech Touchpad as /devices/platform/i8042/serio1/input/input5
  Dec 27 10:49:30 skynote kernel: [0.858259] psmouse serio1: Failed to 
enable mouse on isa0060/serio1

  Notebook Asus x450lc.

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  I don't know how to figure the version at 'apt-cache policy pkgname' but it 
gave a lot of 500s without the pkgname I guess it's 500 then.
  I expected the touchpad to work, I updated the kernel to detect it and it 
detected but no working. It works if I add psmouse=proto.bare into 
/etc/default/grub and updating the grub. However it will work as a mouse (no 
multifingers) and it will crash at suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Dec 27 11:23:05 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-41-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-43-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-44-generic, x86_64: installed
   bbswitch, 0.7, 3.16.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13fd]
  InstallationDate: Installed on 2014-11-05 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  MachineType: ASUSTeK COMPUTER INC. X450LCP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=28130cba-7b95-42de-ab61-7fa6fdc62a4a ro quiet splash i8042.noloop=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X450LCP.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X450LCP
  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.:bvrX450LCP.208:bd06/12/2014:svnASUSTeKCOMPUTERINC.:pnX450LCP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450LCP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X450LCP
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Dec 27 10:49:34 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12860 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.6

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

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

[Touch-packages] [Bug 1411620] Re: Unity requires restart after enabling always-show-menus or LIM

2015-01-17 Thread Treviño

Are those the only affected options?

As I can't see how things changed in this area.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1411620

Title:
  Unity requires restart after enabling always-show-menus or LIM

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity requires restart after enabling always-show-menus or LIM. When
  I first tested the always-show-menus (about 3-4 weeks ago, by using
  Marco's branch), I don't remember it requiring a restart.

  Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require
  restarting Unity but it does with the latest Unity in Ubuntu 15.04
  Vivid Vervet.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150115-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jan 16 13:23:00 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150116)
  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/1411620/+subscriptions

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

[Touch-packages] [Bug 1401677] Re: hwdb.bin does not exist during live system boot

2015-01-17 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1401677

** Tags added: iso-testing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1401677

Title:
  hwdb.bin does not exist during live system boot

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Using the current daily build of vivid for Ubuntu Gnome in Virtualbox,
  after the welcome screen is displayed and switching to tty1 on the
  live CD I see:

  starting version 217
  hwdb.bin does not exist, please run udevadm hwdb --update
  Network interface NamePolicy= disabled on kernel commandline, ignoring.
  invalid key/value pair in file /lib/udev/rules.d/97-dmraid.rules on line 8, 
starting at character 95 ('a')
  [45.279072] systemd-logind[3430]: Failed to start user service: Unknown unit: 
user@999.service

  Welcome to Ubuntu Vivid Vervet (development branch)
  ...snip...

  Last week the above output was present post-installation. Currently
  this is not present post-installation with the current daily build.

  However the system-logind error (Unknown init) persists and is
  currently present post-installation with slight difference of user@999
  becoming user@1000.

  I found this bug report which has been marked as Fix released but
  not sure if these are related or not:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1190947.

  I have a screenshot from last week which I installed a daily build
  image on physical hardware. Some of the errors in that screenshot are
  no longer present (whoopsie  basename). If you need it please let me
  know.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 217-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 11 23:32:03 2014
  InstallationDate: Installed on 2014-12-11 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141211)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=c0cdf4f1-f502-41e5-8d1f-26b30d67242d ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1366829] Re: 7.4.4-1ubuntu2.1 makes rsyslogd to take all the CPU in OpenVZ

2015-01-17 Thread Paul Donohue

I have also verified the fix on Trusty.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1366829

Title:
  7.4.4-1ubuntu2.1 makes rsyslogd to take all the CPU in OpenVZ

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Trusty:
  Fix Committed
Status in rsyslog source package in Utopic:
  Fix Committed

Bug description:
  Test Case
  -
  * Install rsyslog 7.4.4-1ubuntu2.1 on an Ubuntu system that runs inside an 
OpenVZ container (If necessary, use ProxMox to quickly establish an OpenVZ 
container environment)
  * Verify that '$KLogPermitNonKernelFacility on' is set in /etc/rsyslog.conf
  * Restart rsyslog to make sure any changes to the binaries/config are picked 
up
  * Run 'top' and observe that the rsyslogd process is running at 100% CPU. 
When working properly, the rsyslogd process should generally be idle.

  -

  After updating  rsyslog from 7.4.4-1ubuntu2 to 7.4.4-1ubuntu2.1 the rsyslogd 
process started to take all the CPU on my machine.
  The modification made by this release is described in #127, it is the 
activation of KLogPermitNonKernelFacility option.
  I don't know exactly the effect of this option but it seems to have a 
permanent effect : even after downgrading the package or manually removing the 
option from /etc/rsyslog.conf the issue remains.
  My syslog is full of :
  Sep  8 10:28:40 sentry rsyslogd: imklog: error reading kernel log - shutting 
down: Bad file descriptor
  Sep  8 10:28:40 sentry rsyslogd: message repeated 498 times: [imklog: error 
reading kernel log - shutting down: Bad file descriptor]
  Sep  8 10:28:46 sentry rsyslogd-2177: rsyslogd[internal_messages]: 519517 
messages lost due to rate-limiting
  I guess this is what causes the CPU load.

  I am running Ubuntu 14.04.1 LTS in an OpenVZ container on Proxmox 3.2. The 
kernel is 2.6.32-28-pve
  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.1
  PackageArchitecture: amd64
  Tags:  trusty
  Uname: Linux 2.6.32-28-pve x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

** Description changed:

- After a new install of 64 bit Ubuntu 13.10 on my second partition, I
- used dpkg to reinstall all the same packages I had on my 32 bit 13.04
- partition.  I copied all my home directory files over and updated all
- the packages.  I now find that I don't have permissions to change the
- network settings; I can't mount my other hard drive or any USB stick
- using nautilus, or (udisks without using sudo)' I can't run synaptic by
- clicking on the GUI (I have to go to a terminal and sudo synaptic); etc.
- I can't find any documentation on the configuration of policykit-
- desktop-privileges, so I'm filing this bug.  For me it appears to be
- totally broken.  Maybe someone can help me out.
+ HOW TO REPRODUCE:
+ - Upgrade Ubuntu to the next release.
  
- Thanks,
- 
- Rob
+ RESULT:
+ - The user looses permissions for several basic actions in the system.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
-  LANGUAGE=en_US
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- Not authorized to perform operation / Unable to determine the session we are 
in: No session for pid
+ The user looses permissions for several basic actions in the system after 
release upgrade

** Summary changed:

- The user looses permissions for several basic actions in the system after 
release upgrade
+ After release upgrade, the user looses permissions for several basic actions 
in the system

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1240336

Title:
  After release upgrade, the user looses permissions for several basic
  actions in the system

Status in gdm package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in lxdm package in Ubuntu:
  Triaged
Status in policykit-desktop-privileges package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  - Upgrade Ubuntu to the next release.

  RESULT:
  - The user looses permissions for several basic actions in the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1411982] [NEW] Firefox HTML5 Sound Doesn't work with ALSA Jack Plugin

2015-01-17 Thread josh

Public bug reported:

This is not an Ubuntu specific bug, but rather a bug in the version of
the alsa jack plugin that comes with Trusty (exists in any release
before 1.0.28 of the plugin). Here is a bug report from the Mozilla
database that describes the problem in more detail:

https://bugzilla.mozilla.org/show_bug.cgi?id=812900

The basic issue is that if you use a .asoundrc file to route alsa sound
through Jack Audio via the alsa-jack plugin, HTML5 sound doesn't work
properly in Firefox. There are probably other affected apps as well.

** Affects: alsa-plugins (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1411982

Title:
  Firefox HTML5 Sound Doesn't work with ALSA Jack Plugin

Status in alsa-plugins package in Ubuntu:
  New

Bug description:
  This is not an Ubuntu specific bug, but rather a bug in the version of
  the alsa jack plugin that comes with Trusty (exists in any release
  before 1.0.28 of the plugin). Here is a bug report from the Mozilla
  database that describes the problem in more detail:

  https://bugzilla.mozilla.org/show_bug.cgi?id=812900

  The basic issue is that if you use a .asoundrc file to route alsa
  sound through Jack Audio via the alsa-jack plugin, HTML5 sound doesn't
  work properly in Firefox. There are probably other affected apps as
  well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1411982/+subscriptions

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

[Touch-packages] [Bug 1240336] Re: After release upgrade, the user looses permissions for several basic actions in the system

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

** No longer affects: lightdm

** Changed in: gdm (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: lightdm (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: policykit-desktop-privileges (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: lxdm (Ubuntu)
   Status: Confirmed = Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1240336

Title:
  After release upgrade, the user looses permissions for several basic
  actions in the system

Status in gdm package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in lxdm package in Ubuntu:
  Triaged
Status in policykit-desktop-privileges package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  - Upgrade Ubuntu to the next release.

  RESULT:
  - The user looses permissions for several basic actions in the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1292218] Re: Lockscreen prompt missing hi dpi

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1292218

Title:
  Lockscreen prompt missing hi dpi

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

Bug description:
  [ Impact ]

  The lockscreen has correct Panel HiDPI support, but the prompt doesn't
  scale right now.

  [ Test Case ]

  (1) Using the System Settings, adjust the scaling for your monitor to, say, 
1.88
  (2) Invoke the screen lock by, say, pressing Super-L
  (3) hit the shift key to bring up the lockscreen, observe the scaling of the 
password prompt: it should be appropriately scaled.

  [ Regression Potential ]

  Any change to the Unity desktop shell could potentially introduce a
  new crash or lockup:  in this case, a crash could be a security
  violation.

  [ Additional Info ]

  The SRU for for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time without apparent
  regression.

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

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

[Touch-packages] [Bug 1321045] Re: Can't unmount NFS mount point as user (not found error)

2015-01-17 Thread Tulio Lazarini

Well, I tried to download and build util-linux 2.25 from kernel.org, and messed 
up the mount/ umount with error messages like:
mount: /lib/x86_64-linux-gnu/libmount.so.1: version `MOUNT_2.25' not found 
(required by mount)
mount: /lib/x86_64-linux-gnu/libmount.so.1: version `MOUNT_2.23' not found 
(required by mount)
mount: /lib/x86_64-linux-gnu/libmount.so.1: version `MOUNT_2.21' not found 
(required by mount)
mount: /lib/x86_64-linux-gnu/libmount.so.1: version `MOUNT_2.24' not found 
(required by mount)
mount: /lib/x86_64-linux-gnu/libmount.so.1: version `MOUNT_2.22' not found 
(required by mount)
Then I added ppa:flexiondotorg/util-linux to apt and run a update/ dist-upgrade.
Everything went fine now. But the question is: why not to bring a new 
util-linux to Trusty Tahr default stream?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1321045

Title:
  Can't unmount NFS mount point as user (not found error)

Status in util-linux package in Ubuntu:
  Confirmed
Status in util-linux package in Debian:
  New

Bug description:
  Dear fellows,

  I had a strange behavior since I upgraded to 14.04 LTS about my user-
  mountable NFS shares. My /etc/fstab follows:

  # NFS shares from Synology Diskstation
  192.168.25.107:/volume1/Documentos/mnt/Documentos nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Downloads /mnt/Downloads  nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Imagens   /mnt/Imagensnfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Músicas   /mnt/Músicasnfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Vídeos/mnt/Vídeos nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr

  Notice I'm using noauto (don't try to mount at boot) and users (any user can 
mount or umount).
  I can mount normally as user. However, when I try to umount, the following 
message appears:

  $ umount /mnt/Documentos
  umount.nfs4: /mnt/Documentos: not found
  umount.nfs4: /mnt/Documentos: not found
  (message appears 2 times, exactly)

  So, if I try to issue a umount as a superuser (sudo umount
  /mnt/Documentos), it works flawlessly.

  Believe this is a bug that happened in the past on Debian (see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661527), and it was
  solved back then. I'm afraid it would be reintroduced at some point.

  Status of directory permissions at /mnt:

  $ ls -l /mnt
  total 20
  drwxr-xr-x 2 tulio tulio 4096 Abr 12 19:57 Documentos
  drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Downloads
  drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Imagens
  drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Músicas
  drwxr-xr-x 2 tulio tulio 4096 Mar 12 20:59 Vídeos

  Thanks in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libmount1 2.20.1-5.1ubuntu20
  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.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 19 20:30:47 2014
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1321045/+subscriptions

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

[Touch-packages] [Bug 1299741] Re: Shadows shouldn't wrap around to other workspaces/monitors

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1299741

Title:
  Shadows shouldn't wrap around to other workspaces/monitors

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

Bug description:
  [ Impact ]

  Window shadows can be seen on adjacent workspaces.

  [ Test Case ]

  To reproduce, launch a whole bunch (10, 20, a lot) of windows on
  workspace 2, and position them on or near the right edge.  Then switch
  to workspace 1, and observe the massive black blob on the left of the
  screen.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  a new crash or lockup.

  [ Other Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time without apparent
  regression.

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

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

[Touch-packages] [Bug 598308] Re: Volume at login set to Maximum

2015-01-17 Thread Matt Hanyok

Anyone? Chance of a backport to the current LTS release? It'd be nice to
have this fix included before 16.04.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/598308

Title:
  Volume at login set to Maximum

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Release: Ubuntu 10.04 64-bit Desktop Edition

  What You Expected to Happen: System volume to remain as set before reboot and 
as shown in volume panel applet
  What Happened Instead: After reboot/shutdown at and after login system volume 
is set to maximum

  Extended Description:

  Intel HD Audio Chipset using S/PDIF coax out to speakers and system
  audio set to digital output

  After either rebooting or shutting down my system at the next login
  the system volume will be set to maximum. Once the panel loads I can
  click on the system volume applet and if I move the volume slider in
  any direction the volume will immediately be set to the correct level.

  Here is how the process goes:

  1. (logged in system running)slide volume to 75% using system volume applet 
on panel
  2. reboot
  3. Login,
  4. login soundbite plays at 100% volume
  5. open rhythmbox play audio track system volume at 100%
  6. click on system volume panel applet, do not click slider, slider shows 
volume set at 75% as before reboot  This is the odd part
  7. click on volume slider and adjust in either direction system volume 
abruptly adjusts to match the volume level indicated by the slider.

  If any more information is needed please let me know. Thank you

  **MORE INFO 6/25/10**

  This also affects the system alert volume in the same fashion as
  above. Adjusting the slider for the alert value via the panel applet
  reset the volume to the correct level.

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

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

[Touch-packages] [Bug 1321045] Re: Can't unmount NFS mount point as user (not found error)

2015-01-17 Thread Tulio Lazarini

Just tested mount and umount as normal user (not su) for my Synology 
Diskstation NFS shares, and IT WORKED FLAWLESSLY.
Thank tou for the tip, Erik! I'm actually using 2.25-8ubuntu1~trusty2 from PPA 
hosted on https://launchpad.net/~flexiondotorg/+archive/ubuntu/util-linux.
There's a philosophycal discussion about backporting a non-LTS package to a LTS 
version of Ubuntu, however I really don't care that much about it. Finally it 
worked, after almost 8 months. Thank you, guys.
But...
The util-linux 2.20 bug ISN'T SOLVED YET. If you decide to install a new 
util-linux from an external repo, do it at your own risk.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1321045

Title:
  Can't unmount NFS mount point as user (not found error)

Status in util-linux package in Ubuntu:
  Confirmed
Status in util-linux package in Debian:
  New

Bug description:
  Dear fellows,

  I had a strange behavior since I upgraded to 14.04 LTS about my user-
  mountable NFS shares. My /etc/fstab follows:

  # NFS shares from Synology Diskstation
  192.168.25.107:/volume1/Documentos/mnt/Documentos nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Downloads /mnt/Downloads  nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Imagens   /mnt/Imagensnfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Músicas   /mnt/Músicasnfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
  192.168.25.107:/volume1/Vídeos/mnt/Vídeos nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr

  Notice I'm using noauto (don't try to mount at boot) and users (any user can 
mount or umount).
  I can mount normally as user. However, when I try to umount, the following 
message appears:

  $ umount /mnt/Documentos
  umount.nfs4: /mnt/Documentos: not found
  umount.nfs4: /mnt/Documentos: not found
  (message appears 2 times, exactly)

  So, if I try to issue a umount as a superuser (sudo umount
  /mnt/Documentos), it works flawlessly.

  Believe this is a bug that happened in the past on Debian (see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661527), and it was
  solved back then. I'm afraid it would be reintroduced at some point.

  Status of directory permissions at /mnt:

  $ ls -l /mnt
  total 20
  drwxr-xr-x 2 tulio tulio 4096 Abr 12 19:57 Documentos
  drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Downloads
  drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Imagens
  drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Músicas
  drwxr-xr-x 2 tulio tulio 4096 Mar 12 20:59 Vídeos

  Thanks in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libmount1 2.20.1-5.1ubuntu20
  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.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 19 20:30:47 2014
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to trusty on 2014-04-27 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1321045/+subscriptions

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

[Touch-packages] [Bug 1301776] Re: Update manager is really small and not resizeable

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1301776

Title:
  Update manager is really small and not resizeable

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

Bug description:
  [ Impact ]
  update-manager 1:0.196.9, Ubuntu Trusty

  Update manager's window, and especially its fields inside the window, are way 
too small and also it's not resizeable, making it almost useless at least on my 
HiDPI screen (3200 x 1800).
  https://launchpadlibrarian.net/171657786/update-manager-is-small.png

  https://wiki.ubuntu.com/SoftwareUpdates#expanded: The Updates
  Available window should be manually resizable only when it is in this
  expanded state.

  [ Test Case ]

  Run the Ubuntu update manager and attempt to resize the window.  See
  above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell has the potential to
  introduce new crashes or lockups.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  apparent regressions.

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

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

[Touch-packages] [Bug 1324104] Re: Ctrl + Super + D hides windows but still resizable when cursor over border

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1324104

Title:
  Ctrl + Super + D hides windows but still resizable when cursor over
  border

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

Bug description:
  [ Impact ]

  If You Press Ctrl + Super + D Shortcut To minimize all windows
  it works but when you move the cursor you will see it change
  to an arrow for resizing the hidden windows when the cursor
  is in the location of the border of the hidden windows

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could potentially introduce
  a new crash of lockup.

  This particular change could possibly introduce a regression in which
  no windows are re-sizable.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use with no sign of regression.

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

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

[Touch-packages] [Bug 1353070] Re: Launcher icon emblems (count) do not scale to match DPI settings

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1353070

Title:
  Launcher icon emblems (count) do not scale to match DPI settings

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

Bug description:
  [ Impact ]
  The launcher icons count bubble is not properly scaled to match current 
monitor DPI

  [ Test Case ]

  (1) Adjust the monitor scaling factor to 1.88 using the System Settings.
  (2) observe the scaling of an emblem (eg. unread-email count in your email 
client)

  [ Regression Potential ]

  Any code change in Unity has the potential to cause a crash or other
  instability in the desktop shell.

  This specific change has the potential to render the emblems
  unreadable, or or to introduce visible artifacts such as blurry edges
  to the text.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU fix was cherry-picked from Ubuntu 14.10 where
  it has been in production use for some time without any regressions.

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

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

[Touch-packages] [Bug 1328677] Re: unity first-run stamp should not be in XDG_CACHE_HOME

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1328677

Title:
  unity first-run stamp should not be in XDG_CACHE_HOME

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

Bug description:
  [ Impact ]

  The unity first_run.stamp file should not be in XDG_CACHE_HOME.  As it
  is a _cache_, it can be ephemeral.  Rather, it should be in
  XDG_CONFIG_HOME.  Once the keyboard shortcut list, for example, has
  been presented, I don't need to be told about it again, even if I need
  to purge my ~/.cache directory.

  This is a problem at our site, where XDG_CACHE_HOME is stored on a
  temporary filesystem, to cut down on the tremendous amount of useless
  network traffic between workstations and the user's file server.  As a
  result, users now have to learn about Unity keyboard shortcuts on
  every single login.

  [ Test Case ]

  On a non-fresh install, log in to the Unity desktop.  The Shortcuts
  screen should ne be displayed.

  [ Regression Potential ]

  The regression potential in Ubuntu 14.04 LTS is nil since
  XDG_CONFIG_HOME is required to be writable in that distribution.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU was cherry-picked from Ubuntu 14.10 where the
  fix has been in production use for some time and has been stable.

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

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

[Touch-packages] [Bug 1379375] Re: evince does not display ligatures

2015-01-17 Thread Iain Lane

Could you try the poppler patch in
http://cgit.freedesktop.org/poppler/poppler/commit/?id=01723aa17e836e818158dbdc56df642a290be300
?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1379375

Title:
  evince does not display ligatures

Status in fontconfig package in Ubuntu:
  New

Bug description:
  While there's Bug #1325230 with the same title and the linked PDFs there are 
working fine here (displaying fi correctly) there seems to be still some bug 
regarding ligatures. 
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325230

  I have some PDFs substituting Helvetica (and others) with TeX Gyre
  Heros and showing no fi ligature.  I attached a patch I derived from
  the patch in Bug #1325230 which is working fine. Now it uses Nimbus
  Sans L and the ligatures are fine.

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

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

[Touch-packages] [Bug 1314871] Re: Ubuntu 14.04 random screen freeze while Normal OS activites

If your graphic processor is from AMD, please review if the following bug 
report describes better your problem:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/881526

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1314871

Title:
  Ubuntu 14.04 random screen freeze while Normal OS activites

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  same symptom described in https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/1184451

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  .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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May  1 09:21:51 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:044d]
   NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:044d]
  InstallationDate: Installed on 2014-04-27 (3 days ago)
  InstallationMedia: Ubuntu-Kylin 14.04 LTS Trusty Tahr - Release amd64 
(20140417.1)
  MachineType: Dell Inc. Vostro 3400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=96cf6b4d-5e19-4d7a-b765-b71e4b0b94da ro locale=zh_CN quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RXV7H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3400:pvrA10:rvnDellInc.:rn0RXV7H:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3400
  dmi.product.version: A10
  dmi.sys.vendor: Dell 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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2

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

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

[Touch-packages] [Bug 1361679] Re: Switcher Icons does not show progress emblem

Tested with Hello Unity.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1361679

Title:
  Switcher Icons does not show progress emblem

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

Bug description:
  [ Impact ]

  - Open an application that shows progress information on its icon (i.e. 
nautilus or Hello Unity)
  - Open Alt-Tab switcher

  Expected behavior:
  - The icon should show the progress bar overlay

  Actual behavior:
  - No progress bar is shown.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any change to Switcher rendering has the potential to mess up drawing
  icons in the Switcher or crashing Unity.

  [ Other Info ]

  The Ubuntu 14.04 LTS SRU was cherry-picked from the Ubuntu 14.10
  release where it has been in production use for some time without
  apparent regression.

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

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

[Touch-packages] [Bug 1066971] Re: Launcher count overflows when displaying 5+ digits

Tested with Hello Unity set to he max count which apparently is 1.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1066971

Title:
  Launcher count overflows when displaying 5+ digits

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

Bug description:
  [ Impact ]

  What happens:

  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3. The count becomes an unreadable mess.

  What should happen:

  1. The user (Me, in this case) installs the gmail plugin for the launcher.
  2. The user has more than  unread emails.
  3a. The count stretches, allowing for up to 8-9 digits to be displayed.
  3b. The count is truncated, still showing the most important parts of the 
number.

  [ Test Case ]

  See above.

  [ Regression Potential ]

  Any software change in the Unity desktop shell has the potential to
  introduce desktop shell crashes or lockups.

  [ Other Info ]

  The SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10
  where it has been in production use for some time with apparent
  regressions.

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

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

[Touch-packages] [Bug 1411998] [NEW] package apt 1.0.1ubuntu2.1 failed to install/upgrade

2015-01-17 Thread psionx

Public bug reported:

I just installed a fresh xubuntu 14.04. Everything went well. I got the 
notification for new updates. Downloaded updates but the installation alwas 
fails. 
It says system problem detected or failed to install updates.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Sat Jan 17 16:29:25 2015
DuplicateSignature: package:apt:1.0.1ubuntu2.1:
ErrorMessage:
 
InstallationDate: Installed on 2015-01-17 (0 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723)
SourcePackage: apt
Title: package apt 1.0.1ubuntu2.1 failed to install/upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1411998

Title:
  package apt 1.0.1ubuntu2.1 failed to install/upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  I just installed a fresh xubuntu 14.04. Everything went well. I got the 
notification for new updates. Downloaded updates but the installation alwas 
fails. 
  It says system problem detected or failed to install updates.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Sat Jan 17 16:29:25 2015
  DuplicateSignature: package:apt:1.0.1ubuntu2.1:
  ErrorMessage:
   
  InstallationDate: Installed on 2015-01-17 (0 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140723)
  SourcePackage: apt
  Title: package apt 1.0.1ubuntu2.1 failed to install/upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1364225] Re: Shadow applied inconsistently to windows that use XShape

Tested with attached C code.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1364225

Title:
  Shadow applied inconsistently to windows that use XShape

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

Bug description:
  [ Impact ]

  Non-standard windows of a non-rectangular shape end up with
  rectangular shadows drawn behind them by Unity.

  It is better to have no shadow at all for these windows rather than an
  incorrect rectangular shadow.

  [ Test Case ]

  C code for a test case is attached to this bug.  It needs to be
  compiled and run to demonstrate the problem and solution.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could introduce a new crash
  or hang.

  A possible regression in this particular fix is a lack of shadows when
  expected, or a non-standard non-rectangular window still having a
  shadow as before.

  [ Additional Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  regression.

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

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

[Touch-packages] [Bug 1398025] Re: Errors messages like error: /dev/sdb: No medium found on booting

2015-01-17 Thread Bruce Pieterse

I no longer see this with a daily image and udev 218

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1398025

Title:
  Errors messages like error: /dev/sdb: No medium found on booting

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 15.04 dev with udev 217-1ubuntu1 and for a few days
  I'm seeing on every boot errors like error: /dev/sdb: No medium
  found. Here is the content of /var/log/boot.log:

  Begin: Loading essential drivers ... done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
done.
  Begin: Running /scripts/local-premount ... error: /dev/sdb: No medium found
  error: /dev/sdc: No medium found
  error: /dev/sdd: No medium found
  error: /dev/sde: No medium found
  error: /dev/sdb: No medium found
  error: /dev/sdc: No medium found
  error: /dev/sdd: No medium found
  error: /dev/sde: No medium found
  done.
  Begin: Running /scripts/local-bottom ... done.
  done.
  Begin: Running /scripts/init-bottom ... done.
   * Setting up X socket directories...   [210G 
  [204G[ OK ]
   * cryptswap1 (running)...   [210G  * Starting early crypto disks... 
  [210G 
  [204G[ OK ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1398025/+subscriptions

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

[Touch-packages] [Bug 1391422] Re: GeForce 820M running very hot in Ubuntu

2015-01-17 Thread Christopher M. Penalver

Lars Hansson, could you please boot into a live environment via
http://cdimage.ubuntu.com/daily-live/current/ and then run the apport-
collect?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1391422

Title:
  GeForce 820M running very hot in Ubuntu

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu release: Ubuntu 14.10
  Wine: 1:1.6.2-0ubuntu6
  GPU: Intel HD 4000+Nvidia GeForce 820M
  Nvidia drivers: nvidia-331-updates

  Expected behaviour: GPU temperature should not be excessively high
  when running OpenGL games.

  What happens: The GPU temperature gets very high when running OpenGL games. 
For example, running The Talos Principle Public Beta from Steam in Ubuntu the 
GPU temperature will go up to 95-98C but running the same in Windows 8.1 (on 
the same laptop)  the temperature stays below 80.
  The same thing happens when running other games and games in wine.

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

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

[Touch-packages] [Bug 1314871] Re: NVIDIA graphics freeze without kernel hang

2015-01-17 Thread Alexander

This is not my case. I have just the screen freeze. Started after the
addition of a second monitor.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1314871

Title:
  Graphics freeze, with applications continuing working properly

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Happens at random during normal desktop usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  .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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May  1 09:21:51 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:044d]
   NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Dell Device [1028:044d]
  InstallationDate: Installed on 2014-04-27 (3 days ago)
  InstallationMedia: Ubuntu-Kylin 14.04 LTS Trusty Tahr - Release amd64 
(20140417.1)
  MachineType: Dell Inc. Vostro 3400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=96cf6b4d-5e19-4d7a-b765-b71e4b0b94da ro locale=zh_CN quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RXV7H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3400:pvrA10:rvnDellInc.:rn0RXV7H:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3400
  dmi.product.version: A10
  dmi.sys.vendor: Dell 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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1314871/+subscriptions

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

[Touch-packages] [Bug 1314871] Re: NVIDIA graphics freeze without kernel hang