date:20140721

You have been subscribed to a public bug:

Ubuntu 14.04 guest runs pretty much standard standard configuration: KVM
hypervisor, ACPI and APIC enabled, virtio disk bus, raw storage
format...

While running this project, I am also involved in testing SSD drives
across different Linux distributions and their support for discard
option (TRIM).

To cut the story short, Ubuntu-based KVM guest did not set any scheduler
on the boot disk vda):

# lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX
KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX
sr0 rom deadline 1 0B 0B
vda disk 1 0B 0B
vda1 part 1 0B 0B
vda2 part 1 0B 0B
vda5 part 1 0B 0B
dm-0 lvm 1 0B 0B
dm-1 lvm 1 0B 0B

That is in stark contrast with other distributions running almost
identical KVM guest configuration (with the exception of the root file
system using BTRFS instead of EXT4 on SUSE).

Oracle Linux 6.5:

# lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX
KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX
sr0 rom deadline 1 0B 0B
vda disk deadline 1 0B 0B
vda1 part deadline 1 0B 0B
vda2 part deadline 1 0B 0B
dm-0 lvm 1 0B 0B
dm-1 lvm 1 0B 0B

OpenSUSE 13.1:

# lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX
KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX
sr0 rom cfq 1 0B 0B
vda disk cfq 1 0B 0B
vda1 part cfq 1 0B 0B
vda2 part cfq 1 0B 0B
dm-0 lvm 1 0B 0B
dm-1 lvm 1 0B 0B

Indeed, checking elevator capabilities for boot disk on Ubuntu KVM guest
showed:

# cat /sys/block/vda/queue/scheduler
none

Other Linux distributions show more options:

# cat /sys/block/vda/queue/scheduler
noop deadline [cfq]

As well, attempts to change the elevator on Ubuntu guest fail. For
example:

# echo noop > /sys/block/vda/queue/scheduler

# echo $?
0

# cat /sys/block/vda/queue/scheduler
none

Setting it globally in /etc/default/grub and updating it via update-
grub2 fails too.

In the meantime, to automate check of elevators (schedulers) and discard
support for SSD drives and thin-provisioned volumes on Linux, I wrote
simple Perl script:

http://www.circlingcycle.com.au/Unix-sources/Linux-check-IO-scheduler-
and-discard-support.pl.txt

Part of the results on RHEL 6.5 server would look like:

INFO: I/O elevator (scheduler) and discard support summary
INFO: Hard Disk sdb configured with I/O scheduler "cfq"
INFO: SSD sda configured with I/O scheduler "deadline" supports discard 
operation
INFO: Hard Disk sdc configured with I/O scheduler "cfq"
INFO: Hard Disk sdi configured with I/O scheduler "cfq"
INFO: Hard Disk sdh configured with I/O scheduler "cfq"

The Ubuntu KVM guest runs latest paches:

Linux ubuntu14-vm2.circlingcycle.com.au 3.13.0-24-generic
#47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Regards,

Dusan Baljevic VK2COT

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
Ubuntu 14 KVM Guest I/O Elevator Non-configurable
https://bugs.launchpad.net/bugs/1346687
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to util-linux 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 1257120] Re: Screen not refreshing when second display has full-screen application running

2014-07-21 Thread Christopher M. Penalver

Antonio Roberts, if the issue is reproducible in a live environment then
yes.

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

Title:
  Screen not refreshing when second display has full-screen application
  running

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  I have several external displays that I connect to my laptop (800x600,
  1660x1050). When I put an application, such as Totem, Pure Data or Eye
  of Gnome, full screen (via F11) in the external display, the display
  on the primary screen (my laptop) starts to act weird and not refresh
  properly. Examples:

  http://i.stack.imgur.com/hJVwQ.png - Running Pure Data full screen.
  There is only one window open but the ghost of one is displayed

  http://i.stack.imgur.com/mls7M.png - Attempting to resize a window.
  The orange resize animati is left behind

  Is there a way to fix this?

  I have a Dell XPS 13 developer edition running Ubuntu 13.10 with Intel® 
Ivybridge Mobile graphics and Intel® Core™ i7-3537U CPU @ 2.00GHz × 4 
processors.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2014-05-22 17:58:24,058 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058b]
  InstallationDate: Installed on 2013-10-30 (264 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  MachineType: Dell Inc. XPS L322X
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=54eb282c-f856-4c82-8f6a-a6b664234e56 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-22 (59 days ago)
  UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  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.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Jul 19 18:06:54 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1257120/+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 1257120] Re: Screen not refreshing when second display has full-screen application running

2014-07-21 Thread Antonio Roberts

Is it ok to test it out from a live usb/live cd?

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

Title:
  Screen not refreshing when second display has full-screen application
  running

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  I have several external displays that I connect to my laptop (800x600,
  1660x1050). When I put an application, such as Totem, Pure Data or Eye
  of Gnome, full screen (via F11) in the external display, the display
  on the primary screen (my laptop) starts to act weird and not refresh
  properly. Examples:

  http://i.stack.imgur.com/hJVwQ.png - Running Pure Data full screen.
  There is only one window open but the ghost of one is displayed

  http://i.stack.imgur.com/mls7M.png - Attempting to resize a window.
  The orange resize animati is left behind

  Is there a way to fix this?

  I have a Dell XPS 13 developer edition running Ubuntu 13.10 with Intel® 
Ivybridge Mobile graphics and Intel® Core™ i7-3537U CPU @ 2.00GHz × 4 
processors.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2014-05-22 17:58:24,058 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058b]
  InstallationDate: Installed on 2013-10-30 (264 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  MachineType: Dell Inc. XPS L322X
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=54eb282c-f856-4c82-8f6a-a6b664234e56 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-22 (59 days ago)
  UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  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.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Jul 19 18:06:54 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1257120/+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 1346723] Re: Cannot delete my chroot.

2014-07-21 Thread Zoltan Balogh

** Project changed: qtcreator-plugin-ubuntu => click (Ubuntu)

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

Title:
  Cannot delete my chroot.

Status in Click packages:
  New
Status in “click” package in Ubuntu:
  New

Bug description:
  I found that my install chroot did not appear when I tried to manage
  my kits to add the build for it. The started to delete it. However, I
  found that I could not delete it, and it gave me the error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click/+bug/1346723/+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 1346723] [NEW] Cannot delete my chroot.

You have been subscribed to a public bug:

I found that my install chroot did not appear when I tried to manage my
kits to add the build for it. The started to delete it. However, I found
that I could not delete it, and it gave me the error.

** Affects: click
 Importance: Undecided
 Status: New

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

-- 
Cannot delete my chroot.
https://bugs.launchpad.net/bugs/1346723
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to click 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 1332418] Re: Fail to report a crash

At that time reports just went to errors.ubuntu.com. Utopic now re-
enabled sending reports to Launchpad.

** Changed in: apport (Ubuntu)
   Status: New => Invalid

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

Title:
  Fail to report a crash

Status in “apport” package in Ubuntu:
  Invalid

Bug description:
  Utopic i386 logged with gnome-shell and booted with systemd

  That latest apport-gtk does not report a crash: when the crash file is
  selected to be reported with apport, the process start as usual and
  the crash details can be viewed. Then when 'continue' is clicked,
  nothing happen: usually the browser is loaded if not already done
  (chromium-browser default here on that pc), then the launchpad login
  is called. But that time the process seems silently died.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: apport-gtk 2.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportLog:
   ERROR: apport (pid 3532) Fri Jun 20 06:15:40 2014: called for pid 1839, 
signal 6, core limit 0
   ERROR: apport (pid 3532) Fri Jun 20 06:15:40 2014: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
   ERROR: apport (pid 3532) Fri Jun 20 06:15:40 2014: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3532) Fri Jun 20 06:16:34 2014: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: i386
  CrashReports: 640:1000:114:66062779:2014-06-20 06:17:18.385129451 
+0200:2014-06-20 07:42:21.784167341 
+0200:/var/crash/_usr_bin_gnome-shell.1000.crash
  CurrentDesktop: GNOME
  Date: Fri Jun 20 07:43:36 2014
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1332418/+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 1341083] Re: ufw needs systemd unit or init.d script

** Summary changed:

- [systemd-boot] [utopic] ufw status 'inactive' at cold boot
+ ufw needs systemd unit or init.d script

** Changed in: ufw (Ubuntu)
   Status: New => Triaged

** Changed in: ufw (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  ufw needs systemd unit or init.d script

Status in “ufw” package in Ubuntu:
  Triaged

Bug description:
  Always get an 'inactive' status when the system is booted, even if the
  setting is set to be 'active' into the 'system settings'

  oem@dev32:~$ sudo ufw status
  [sudo] password for oem: 
  Status: inactive

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ufw 0.34~rc-0ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.16.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Jul 12 11:07:30 2014
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1341083/+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 1345533] Re: [regression][hammerhead] Mir fails to start on Nexus 5 & 10 as it fails to turn vsync signal on

This bug was fixed in the package mir - 0.5.0+14.10.20140722-0ubuntu1

---
mir (0.5.0+14.10.20140722-0ubuntu1) utopic; urgency=medium

  [ Kevin Gunn ]
  * Fixed: [regression] Mir fails to start on Nexus 5 / Nexus 10 (LP: #1345533)
 -- Ubuntu daily releaseTue, 22 Jul 2014 
02:17:22 +

** Changed in: mir (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [regression][hammerhead] Mir fails to start on Nexus 5 & 10 as it
  fails to turn vsync signal on

Status in Mir:
  Fix Committed
Status in Mir 0.5 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Fix Released

Bug description:
  Starting from image 137, with mir 0.5, Mir fails to start on Nexus 5
  (hammerhead), as it fails to turn the vsync signal on.

  This is what I get from logcat:

  D/libEGL  ( 3038): loaded /vendor/lib/egl/libEGL_adreno.so
  D/libEGL  ( 3038): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
  D/libEGL  ( 3038): loaded /vendor/lib/egl/libGLESv2_adreno.so
  I/qdutils ( 3038): Right Split=0
  D/qdhwcomposer( 3038): int qhwc::adRead(): /sys/class/graphics/fb2/ad could 
not be opened : No such file or directory
  I/qdhwcomposer( 3038): Initializing Qualcomm Hardware Composer
  I/qdhwcomposer( 3038): MDP version: 500
  I/Adreno-EGL( 3038): : EGL 1.4 QUALCOMM Build: 
I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
  D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, width = 1080
  D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, height = 1920
  I/Adreno-EGL( 3038): : EGL 1.4 QUALCOMM Build: 
I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
  I/qdhwcomposer( 3038): hwc_registerProcs
  I/qdhwcomposer( 3038): Initializing UEVENT Thread
  I/qdhwcomposer( 3038): Initializing VSYNC Thread
  I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=0 from 
/sys/class/graphics/fb0/vsync_event
  I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=1 from 
/sys/class/graphics/fb1/vsync_event
  D/qdhwcomposer( 3038): hwc_blank: Unblanking display: 0
  D/qdhwcomposer( 3038): hwc_blank: Done unblanking display: 0
  E/qdhwcomposer( 3038): hwc_vsync_control: vsync control failed. Dpy=0, 
enable=1 : Operation not supported
  W/libEGL  ( 3038): eglTerminate() called w/ 1 objects remaining
  E/libEGL  ( 3038): validate_display:263 error 3001 (EGL_NOT_INITIALIZED)
  I/ServiceManager(  913): service 'display.qservice' died

  The vsync control failed message was always there, and Mir 0.4 worked
  fine with it still.

  System compositor log:
  root@ubuntu-phablet:/var/log/lightdm# cat unity-system-compositor.log
  ERROR: 
/build/buildd/mir-0.5.0+14.10.20140717/src/platform/graphics/android/real_hwc_wrapper.cpp(75):
 Throw in function virtual void 
mir::graphics::android::RealHwcWrapper::vsync_signal_on() const
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
  std::exception::what: error turning vsync signal on. rc = ffa1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1345533/+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 1271839] Re: ibus-ui-gtk3 big memory leak

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

** Changed in: ibus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  ibus-ui-gtk3 big memory leak

Status in “ibus” package in Ubuntu:
  Expired

Bug description:
  ubuntu 13.10 64bit
  2gb of memory leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+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 1322394] Re: Can't install linux-restricted-modules

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

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Can't install linux-restricted-modules

Status in “pulseaudio” package in Ubuntu:
  Expired

Bug description:
  I have a dual booted chromebook (chromeos and ubuntu 13.10).

  I updated my chromebook and my audio stopped working when I boot into
  the linux os. I don't know if that is the cause.

  I have run through all the commands for troubleshooting the audio
  failure and I have gotten the expected readouts.

  I don't know what to do next.

  Thanks in advance for the help,

  Chukleberryfinn

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1322394/+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 1318244] Re: cups hang whilst trying to print

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

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  cups hang whilst trying to print

Status in “cups” package in Ubuntu:
  Expired

Bug description:
  Printing to networked cups printer via smb is not working.  Printer is
  an Epson Stylus Color 660.

  Printer was originally configured as ipp but that was not working due
  to an older version of cups at the far end, so switched to smb as a
  workaround.

  Printing the openoffice document in normal quality worked ok.

  Then tried printing with print quality set to best and have seen some
  segvs in libgutenprint.  Same problem occurs if print to PDF then
  print from evince.

  May 10 17:56:08 netbook kernel: [ 8215.038642] rastertogutenpr[3482]: 
segfault at 4 ip b76715ca sp bf952d70 error 4 in 
libgutenprint.so.2.3.0[b7667000+5b000]
  May 10 17:58:29 netbook kernel: [ 8356.299635] rastertogutenpr[3515]: 
segfault at 4 ip b767e5ca sp bfcd39e0 error 4 in 
libgutenprint.so.2.3.0[b7674000+5b000]

  
  Restarted cups with loglevel=debug and tried printing again, this time it all 
hangs.

  pstree shows this:

  |-cupsd(4538)-+-dbus(4543)
  | |-gstoraster(4567)---gs(4570)
  | |-rastertogutenpr(4568)
  | `-smb(4569)

  It's been stuck like this for 45 minutes or so now.  It has created a
  0 bytes file in the smb spool area on the server and the local print
  queue shows a size of 411k.

  This printing setup has been working fine for several years; including
  with 8.04 and 12.04 and Windows clients.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  Date: Sat May 10 20:49:56 2014
  Lpstat: device for home: smb://AJ/ROOT/epson_raw
  MachineType: Dell Inc. Inspiron 910
  Papersize: a4
  PpdFiles: home: Epson Stylus Color 660 - CUPS+Gutenprint v5.2.10-pre2
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=46a2656e-ba44-410c-ae8e-89865249301a ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: CN0J14
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd03/05/2009:svnDellInc.:pnInspiron910:pvrA05:rvnDellInc.:rnCN0J14:rvrA05:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 910
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1318244/+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 1334596] Re: update-rc.d does not use LSB header information for "default"

Ah, this is because our update-rc.d still interprets "defaults" as
"2345"/"016" instead of reading the LSB header. This needs a merged
sysvinit.

** Summary changed:

- [udev] update-rc.d: init-script not matching default LSB
+ update-rc.d does not use LSB header information for "default"

** Summary changed:

- update-rc.d does not use LSB header information for "default"
+ update-rc.d does not use LSB header information for "defaults"

** Package changed: systemd (Ubuntu) => sysvinit (Ubuntu)

** Summary changed:

- update-rc.d does not use LSB header information for "defaults"
+ update-rc.d warns about mismatching LSB header information for "defaults"

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

Title:
  update-rc.d warns about mismatching LSB header information for
  "defaults"

Status in “sysvinit” package in Ubuntu:
  Triaged

Bug description:
  Utopic i386 booted with 'systemd-boot' and logged with gnome-shell

  From time to time i'm seeing such update-rc.d init-script not matching
  the standard default LSB.

  Setting up udev (204-12ubuntu1) ...
  update-initramfs: deferring update (trigger activated)
  update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match 
udev Default-Start values (S)
  update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match 
udev Default-Stop values (none)
  update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match 
udev-finish Default-Start values (S)
  update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match 
udev-finish Default-Stop values (none)
  update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match 
lvm2 Default-Start values (S)
  update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match 
lvm2 Default-Stop values (none)

  As i've found an old report with the same subject, i'm reporting against 
sysvinit, but feel free to select an other package if more appropriate.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614895

  note: such kind of warnings are seen since a long time now. If that
  does not matter, then close that report.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: sysvinit-utils 2.88dsf-41ubuntu16
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Jun 26 12:14:10 2014
  SourcePackage: sysvinit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1334596/+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 1334596] Re: update-rc.d warns about mismatching LSB header information for "defaults"

Sorry, it it does use the LSB header information, it should just stop
warning about the legacy defaults.

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

Title:
  update-rc.d warns about mismatching LSB header information for
  "defaults"

Status in “sysvinit” package in Ubuntu:
  Triaged

Bug description:
  Utopic i386 booted with 'systemd-boot' and logged with gnome-shell

  From time to time i'm seeing such update-rc.d init-script not matching
  the standard default LSB.

  Setting up udev (204-12ubuntu1) ...
  update-initramfs: deferring update (trigger activated)
  update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match 
udev Default-Start values (S)
  update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match 
udev Default-Stop values (none)
  update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match 
udev-finish Default-Start values (S)
  update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match 
udev-finish Default-Stop values (none)
  update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match 
lvm2 Default-Start values (S)
  update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match 
lvm2 Default-Stop values (none)

  As i've found an old report with the same subject, i'm reporting against 
sysvinit, but feel free to select an other package if more appropriate.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614895

  note: such kind of warnings are seen since a long time now. If that
  does not matter, then close that report.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: sysvinit-utils 2.88dsf-41ubuntu16
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Jun 26 12:14:10 2014
  SourcePackage: sysvinit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1334596/+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 1345533] Re: [regression][hammerhead] Mir fails to start on Nexus 5 & 10 as it fails to turn vsync signal on

** Branch linked: lp:ubuntu/utopic-proposed/mir

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

Title:
  [regression][hammerhead] Mir fails to start on Nexus 5 & 10 as it
  fails to turn vsync signal on

Status in Mir:
  Fix Committed
Status in Mir 0.5 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  In Progress

Bug description:
  Starting from image 137, with mir 0.5, Mir fails to start on Nexus 5
  (hammerhead), as it fails to turn the vsync signal on.

  This is what I get from logcat:

  D/libEGL  ( 3038): loaded /vendor/lib/egl/libEGL_adreno.so
  D/libEGL  ( 3038): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
  D/libEGL  ( 3038): loaded /vendor/lib/egl/libGLESv2_adreno.so
  I/qdutils ( 3038): Right Split=0
  D/qdhwcomposer( 3038): int qhwc::adRead(): /sys/class/graphics/fb2/ad could 
not be opened : No such file or directory
  I/qdhwcomposer( 3038): Initializing Qualcomm Hardware Composer
  I/qdhwcomposer( 3038): MDP version: 500
  I/Adreno-EGL( 3038): : EGL 1.4 QUALCOMM Build: 
I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
  D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, width = 1080
  D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, height = 1920
  I/Adreno-EGL( 3038): : EGL 1.4 QUALCOMM Build: 
I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
  I/qdhwcomposer( 3038): hwc_registerProcs
  I/qdhwcomposer( 3038): Initializing UEVENT Thread
  I/qdhwcomposer( 3038): Initializing VSYNC Thread
  I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=0 from 
/sys/class/graphics/fb0/vsync_event
  I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=1 from 
/sys/class/graphics/fb1/vsync_event
  D/qdhwcomposer( 3038): hwc_blank: Unblanking display: 0
  D/qdhwcomposer( 3038): hwc_blank: Done unblanking display: 0
  E/qdhwcomposer( 3038): hwc_vsync_control: vsync control failed. Dpy=0, 
enable=1 : Operation not supported
  W/libEGL  ( 3038): eglTerminate() called w/ 1 objects remaining
  E/libEGL  ( 3038): validate_display:263 error 3001 (EGL_NOT_INITIALIZED)
  I/ServiceManager(  913): service 'display.qservice' died

  The vsync control failed message was always there, and Mir 0.4 worked
  fine with it still.

  System compositor log:
  root@ubuntu-phablet:/var/log/lightdm# cat unity-system-compositor.log
  ERROR: 
/build/buildd/mir-0.5.0+14.10.20140717/src/platform/graphics/android/real_hwc_wrapper.cpp(75):
 Throw in function virtual void 
mir::graphics::android::RealHwcWrapper::vsync_signal_on() const
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
  std::exception::what: error turning vsync signal on. rc = ffa1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1345533/+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 1334596] Re: [systemd] update-rc.d: init-script not matching default LSB

** Package changed: sysvinit (Ubuntu) => systemd (Ubuntu)

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu)
   Status: New => Triaged

** Tags removed: systemd-boot

** Summary changed:

- [systemd] update-rc.d: init-script not matching default LSB
+ [udev] update-rc.d: init-script not matching default LSB

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

Title:
  [udev] update-rc.d: init-script not matching default LSB

Status in “systemd” package in Ubuntu:
  Triaged

Bug description:
  Utopic i386 booted with 'systemd-boot' and logged with gnome-shell

  From time to time i'm seeing such update-rc.d init-script not matching
  the standard default LSB.

  Setting up udev (204-12ubuntu1) ...
  update-initramfs: deferring update (trigger activated)
  update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match 
udev Default-Start values (S)
  update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match 
udev Default-Stop values (none)
  update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match 
udev-finish Default-Start values (S)
  update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match 
udev-finish Default-Stop values (none)
  update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match 
lvm2 Default-Start values (S)
  update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match 
lvm2 Default-Stop values (none)

  As i've found an old report with the same subject, i'm reporting against 
sysvinit, but feel free to select an other package if more appropriate.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614895

  note: such kind of warnings are seen since a long time now. If that
  does not matter, then close that report.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: sysvinit-utils 2.88dsf-41ubuntu16
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Jun 26 12:14:10 2014
  SourcePackage: sysvinit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1334596/+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 1346734] [NEW] Unprivileged LXC containers don't work under systemd

Public bug reported:

With systemd 208, unprivileged containers stop working when running
under systemd (working fine under upstart with cgmanager). Quoting
Stephane Graber:

In this setup, things don't work nearly as well. On login I'm only
placed into the name=systemd cgroup and not in any of the others, which
means that unprivileged LXC isn't usable.

Martin suggested setting JoinControllers in /etc/systemd/system.conf but
upon closer inspection, this isn't at all what we want. This setting is
used to tell systemd what controllers to co-mount, by default this is
set to cpu,cpuset (which caused the earlier cgmanager breakage).

Even though this option isn't helpful for what we want (i.e. setting the
list of cgroup controllers the first PID of a user session should be
added to), we should nonetheless set it to an empty string which should
instruct systemd not to co-mount any controller, therefore giving us a
more reliable behavior (identical to what we have in the upstart world
and unlikely to confuse lxc and other stuff doing direct cgroup access).

Additionally, we need to find an equivalent to our good old
"Controllers" logind.conf option, or re-introduce it or just patch
logind so that it will always join all the controllers (similar to what
the shim does).


== Actions ==
 * Update systemd.conf to set JoinControllers to an empty value.
 * Make it so new user sessions are joined to all the available
   controllers by doing one of the following:
   - Find the magic undocumented config variable
   - Re-introduce the "Controllers" option in logind.conf
   - Patch logind to have it always join all available controllers

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


** Tags: systemd-boot

** Tags added: systemd-boot

** Changed in: systemd (Ubuntu)
   Status: New => Triaged

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

Title:
  Unprivileged LXC containers don't work under systemd

Status in “systemd” package in Ubuntu:
  Triaged

Bug description:
  With systemd 208, unprivileged containers stop working when running
  under systemd (working fine under upstart with cgmanager). Quoting
  Stephane Graber:

  In this setup, things don't work nearly as well. On login I'm only
  placed into the name=systemd cgroup and not in any of the others, which
  means that unprivileged LXC isn't usable.

  Martin suggested setting JoinControllers in /etc/systemd/system.conf but
  upon closer inspection, this isn't at all what we want. This setting is
  used to tell systemd what controllers to co-mount, by default this is
  set to cpu,cpuset (which caused the earlier cgmanager breakage).

  Even though this option isn't helpful for what we want (i.e. setting the
  list of cgroup controllers the first PID of a user session should be
  added to), we should nonetheless set it to an empty string which should
  instruct systemd not to co-mount any controller, therefore giving us a
  more reliable behavior (identical to what we have in the upstart world
  and unlikely to confuse lxc and other stuff doing direct cgroup access).

  Additionally, we need to find an equivalent to our good old
  "Controllers" logind.conf option, or re-introduce it or just patch
  logind so that it will always join all the controllers (similar to what
  the shim does).

  
  == Actions ==
   * Update systemd.conf to set JoinControllers to an empty value.
   * Make it so new user sessions are joined to all the available
 controllers by doing one of the following:
 - Find the magic undocumented config variable
 - Re-introduce the "Controllers" option in logind.conf
 - Patch logind to have it always join all available controllers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1346734/+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 1346199] Re: Needs testing in -proposed: systemd 208

** Description changed:

  I just uploaded systemd 208-6ubuntu1 to utopic-proposed, which makes use
  of the new cgmanager-enabled systemd-shim. This bug prevents this new
  version to migrate to utopic until we get more confirmation that this
  doesn't regress udev/logind.
  
  I already tested this in a clean utopic VM, upgrade and fresh install on
  my Utopic amd64 workstation, and manually built armhf binaries (from an
  intermediate 208 version) on the current Ubuntu Touch image.
  
  TODO:
  
-  * pitti: re-test Ubuntu Touch with the actual binaries from -proposed
-  * stgraber: confirm that this works well with system/user containers
+  * pitti: re-test Ubuntu Touch with the actual binaries from -proposed  -- 
DONE
+  * stgraber: confirm that this works well with system/user containers -- 
DONE; works under upstart, fails under systemd, filed as bug 1346734

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

Title:
  Needs testing in -proposed: systemd 208

Status in “systemd” package in Ubuntu:
  In Progress

Bug description:
  I just uploaded systemd 208-6ubuntu1 to utopic-proposed, which makes
  use of the new cgmanager-enabled systemd-shim. This bug prevents this
  new version to migrate to utopic until we get more confirmation that
  this doesn't regress udev/logind.

  I already tested this in a clean utopic VM, upgrade and fresh install
  on my Utopic amd64 workstation, and manually built armhf binaries
  (from an intermediate 208 version) on the current Ubuntu Touch image.

  TODO:

   * pitti: re-test Ubuntu Touch with the actual binaries from -proposed  -- 
DONE
   * stgraber: confirm that this works well with system/user containers -- 
DONE; works under upstart, fails under systemd, filed as bug 1346734

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1346199/+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 1346650] Re: ubuntu-ui-toolkit-examples has unsatisfiable qtdeclarative5-ubuntu-ui-toolkit-plugin dependency (conflicts with -gles)

ubuntu-ui-toolkit-examples is uninstallable in that environment indeed:
It depends on qtdeclarative5-ubuntu-ui-toolkit-plugin (=
0.1.49+14.10.20140715-0ubuntu1), i. e. a versioned dependency. This
won't be satisfied by the "Provides: qtdeclarative5-ubuntu-ui-toolkit-
plugin" of qtdeclarative5-ubuntu-ui-toolkit-plugin-gles, but this is
installed by default.

So ubuntu-ui-toolkit-examples either needs to drop the strict versioned
dependency (so that the Provides: gets effective), or grow an
alternative dependency to qtdeclarative5-ubuntu-ui-toolkit-plugin-gles.

** Summary changed:

- adt-run fails under x86 emulator
+ ubuntu-ui-toolkit-examples has unsatisfiable 
qtdeclarative5-ubuntu-ui-toolkit-plugin dependency (conflicts with -gles)

** Package changed: autopkgtest (Ubuntu) => ubuntu-ui-toolkit (Ubuntu)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  ubuntu-ui-toolkit-examples has unsatisfiable qtdeclarative5-ubuntu-ui-
  toolkit-plugin dependency (conflicts with -gles)

Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Triaged

Bug description:
  Running adt for click testing fails when using the x86 emulator. Both
  r/o and r/w mode fail in the same way. During the installation of
  depends, dpkg configure fails and the test is aborted.

  adt-run: DBG: testbed command ['dpkg', '--unpack', 
'/tmp/adt-run.0ixHLB/adt-satdep.deb'], kind short, sout raw, serr pipe, env 
['LANG=C.UTF-8']
  (Reading database ... 39433 files and directories currently installed.)
  Preparing to unpack .../adt-run.0ixHLB/adt-satdep.deb ...
  Unpacking adt-satdep (0) over (0) ...
  adt-run: DBG: testbed command exited with code 0
  adt-run: DBG: testbed command ['apt-get', 'install', '-q', '-y', '-f', '-o', 
'APT::Install-Recommends=False', '-o', 'Debug::pkgProblemResolver=true'], kind 
install, sout raw, serr raw, env ['DEBIAN_FRONTEND=noninteractive', 
'APT_LISTBUGS_FRONTEND=none', 'LANG=C.UTF-8']
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies...Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) qtdeclarative5-ubuntu-ui-toolkit-plugin-gles [ i386 ] < 
0.1.49+14.10.20140707-0ubuntu1 -> 0.1.49+14.10.20140715-0ubuntu1 > ( 
universe/libs )
  Broken qtdeclarative5-ubuntu-ui-toolkit-plugin-gles:i386 Conflicts on 
qtdeclarative5-ubuntu-ui-toolkit-plugin [ i386 ] < none -> 
0.1.49+14.10.20140715-0ubuntu1 > ( libs )
Considering qtdeclarative5-ubuntu-ui-toolkit-plugin:i386 30 as a solution 
to qtdeclarative5-ubuntu-ui-toolkit-plugin-gles:i386 38
Added qtdeclarative5-ubuntu-ui-toolkit-plugin:i386 to the remove list
Fixing qtdeclarative5-ubuntu-ui-toolkit-plugin-gles:i386 via keep of 
qtdeclarative5-ubuntu-ui-toolkit-plugin:i386
  Investigating (0) ubuntu-ui-toolkit-examples [ i386 ] < none -> 
0.1.49+14.10.20140715-0ubuntu1 > ( universe/devel )
  Broken ubuntu-ui-toolkit-examples:i386 Depends on 
qtdeclarative5-ubuntu-ui-toolkit-plugin [ i386 ] < none -> 
0.1.49+14.10.20140715-0ubuntu1 > ( libs ) (= 0.1.49+14.10.20140715-0ubuntu1)
Considering qtdeclarative5-ubuntu-ui-toolkit-plugin:i386 30 as a solution 
to ubuntu-ui-toolkit-examples:i386 -1
Holding Back ubuntu-ui-toolkit-examples:i386 rather than change 
qtdeclarative5-ubuntu-ui-toolkit-plugin:i386
  Investigating (1) ubuntu-ui-toolkit-autopilot [ i386 ] < none -> 
0.1.49+14.10.20140715-0ubuntu1 > ( universe/libs )
  Broken ubuntu-ui-toolkit-autopilot:i386 Depends on ubuntu-ui-toolkit-examples 
[ i386 ] < none -> 0.1.49+14.10.20140715-0ubuntu1 > ( universe/devel ) (>= 
0.1.49+14.10.20140715-0ubuntu1)
Considering ubuntu-ui-toolkit-examples:i386 -1 as a solution to 
ubuntu-ui-toolkit-autopilot:i386 0
Holding Back ubuntu-ui-toolkit-autopilot:i386 rather than change 
ubuntu-ui-toolkit-examples:i386
  Investigating (1) adt-satdep [ i386 ] < 0 > ( oldlibs )
  Broken adt-satdep:i386 Depends on ubuntu-ui-toolkit-autopilot [ i386 ] < none 
-> 0.1.49+14.10.20140715-0ubuntu1 > ( universe/libs )
Considering ubuntu-ui-toolkit-autopilot:i386 0 as a solution to 
adt-satdep:i386 -2
Removing adt-satdep:i386 rather than change ubuntu-ui-toolkit-autopilot:i386
  
  adt-run [18:34:43]: ERROR: unexpected error: test dependencies are 
unsatisfiable


  The full output from an example run is attached.

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

[Touch-packages] [Bug 808962] Re: unity launcher keeps on top when running java programs (do not autohide)

2014-07-21 Thread Christopher Murphy

This is also an issue in 14.04, happens to me daily, just happened then
while I was using chrome and sublime.

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

Title:
  unity launcher keeps on top when running java programs (do not
  autohide)

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

Bug description:
  unity launcher keeps on top when running java programs (do not
  autohide)

  i think this happens only with java programs. and as i am java
  developer, use netbeans all day and that s##$% keeps happening.

  if i can help anyother way please say. that is disturbing

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/808962/+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 1346650] [NEW] ubuntu-ui-toolkit-examples has unsatisfiable qtdeclarative5-ubuntu-ui-toolkit-plugin dependency (conflicts with -gles)

You have been subscribed to a public bug:

Running adt for click testing fails when using the x86 emulator. Both
r/o and r/w mode fail in the same way. During the installation of
depends, dpkg configure fails and the test is aborted.

adt-run: DBG: testbed command ['dpkg', '--unpack', 
'/tmp/adt-run.0ixHLB/adt-satdep.deb'], kind short, sout raw, serr pipe, env 
['LANG=C.UTF-8']
(Reading database ... 39433 files and directories currently installed.)
Preparing to unpack .../adt-run.0ixHLB/adt-satdep.deb ...
Unpacking adt-satdep (0) over (0) ...
adt-run: DBG: testbed command exited with code 0
adt-run: DBG: testbed command ['apt-get', 'install', '-q', '-y', '-f', '-o', 
'APT::Install-Recommends=False', '-o', 'Debug::pkgProblemResolver=true'], kind 
install, sout raw, serr raw, env ['DEBIAN_FRONTEND=noninteractive', 
'APT_LISTBUGS_FRONTEND=none', 'LANG=C.UTF-8']
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) qtdeclarative5-ubuntu-ui-toolkit-plugin-gles [ i386 ] < 
0.1.49+14.10.20140707-0ubuntu1 -> 0.1.49+14.10.20140715-0ubuntu1 > ( 
universe/libs )
Broken qtdeclarative5-ubuntu-ui-toolkit-plugin-gles:i386 Conflicts on 
qtdeclarative5-ubuntu-ui-toolkit-plugin [ i386 ] < none -> 
0.1.49+14.10.20140715-0ubuntu1 > ( libs )
  Considering qtdeclarative5-ubuntu-ui-toolkit-plugin:i386 30 as a solution to 
qtdeclarative5-ubuntu-ui-toolkit-plugin-gles:i386 38
  Added qtdeclarative5-ubuntu-ui-toolkit-plugin:i386 to the remove list
  Fixing qtdeclarative5-ubuntu-ui-toolkit-plugin-gles:i386 via keep of 
qtdeclarative5-ubuntu-ui-toolkit-plugin:i386
Investigating (0) ubuntu-ui-toolkit-examples [ i386 ] < none -> 
0.1.49+14.10.20140715-0ubuntu1 > ( universe/devel )
Broken ubuntu-ui-toolkit-examples:i386 Depends on 
qtdeclarative5-ubuntu-ui-toolkit-plugin [ i386 ] < none -> 
0.1.49+14.10.20140715-0ubuntu1 > ( libs ) (= 0.1.49+14.10.20140715-0ubuntu1)
  Considering qtdeclarative5-ubuntu-ui-toolkit-plugin:i386 30 as a solution to 
ubuntu-ui-toolkit-examples:i386 -1
  Holding Back ubuntu-ui-toolkit-examples:i386 rather than change 
qtdeclarative5-ubuntu-ui-toolkit-plugin:i386
Investigating (1) ubuntu-ui-toolkit-autopilot [ i386 ] < none -> 
0.1.49+14.10.20140715-0ubuntu1 > ( universe/libs )
Broken ubuntu-ui-toolkit-autopilot:i386 Depends on ubuntu-ui-toolkit-examples [ 
i386 ] < none -> 0.1.49+14.10.20140715-0ubuntu1 > ( universe/devel ) (>= 
0.1.49+14.10.20140715-0ubuntu1)
  Considering ubuntu-ui-toolkit-examples:i386 -1 as a solution to 
ubuntu-ui-toolkit-autopilot:i386 0
  Holding Back ubuntu-ui-toolkit-autopilot:i386 rather than change 
ubuntu-ui-toolkit-examples:i386
Investigating (1) adt-satdep [ i386 ] < 0 > ( oldlibs )
Broken adt-satdep:i386 Depends on ubuntu-ui-toolkit-autopilot [ i386 ] < none 
-> 0.1.49+14.10.20140715-0ubuntu1 > ( universe/libs )
  Considering ubuntu-ui-toolkit-autopilot:i386 0 as a solution to 
adt-satdep:i386 -2
  Removing adt-satdep:i386 rather than change ubuntu-ui-toolkit-autopilot:i386

adt-run [18:34:43]: ERROR: unexpected error: test dependencies are unsatisfiable


The full output from an example run is attached.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Status: Triaged

-- 
ubuntu-ui-toolkit-examples has unsatisfiable 
qtdeclarative5-ubuntu-ui-toolkit-plugin dependency (conflicts with -gles)
https://bugs.launchpad.net/bugs/1346650
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-ui-toolkit 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 1346199] Re: Needs testing in -proposed: systemd 208

Anders: When you boot with upstart, can you please attach
/var/log/auth.log after booting? I'm not sure why restarting gdm would
work, but maybe there's a libpam_systemd error message in there?

If you try and log into VT1 right after boot, does that work? I. e. do
you see a session for that in "loginctl"? (You can inspect a particular
session with e. g. loginctl show-session c2)

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

Title:
  Needs testing in -proposed: systemd 208

Status in “systemd” package in Ubuntu:
  In Progress

Bug description:
  I just uploaded systemd 208-6ubuntu1 to utopic-proposed, which makes
  use of the new cgmanager-enabled systemd-shim. This bug prevents this
  new version to migrate to utopic until we get more confirmation that
  this doesn't regress udev/logind.

  I already tested this in a clean utopic VM, upgrade and fresh install
  on my Utopic amd64 workstation, and manually built armhf binaries
  (from an intermediate 208 version) on the current Ubuntu Touch image.

  TODO:

   * pitti: re-test Ubuntu Touch with the actual binaries from -proposed
   * stgraber: confirm that this works well with system/user containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1346199/+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 1346428] Re: [HDA-Intel - HDA Intel, playback] No sound at all

2014-07-21 Thread Daniel Letzeisen

You're still booted into the kernel from 12.04
Kernel release:3.2.0-61-generic-pae

Boot into the Trusty kernel and see if sound returns.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

Title:
  [HDA-Intel - HDA Intel, playback] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  I recently installed ubuntu 14.04 LTS since then there is no sound at
  all. On the same computer windows XP runs then I have sound!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-61.93-generic-pae 3.2.55
  Uname: Linux 3.2.0-61-generic-pae i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  klaus  1965 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 21 19:40:58 2014
  InstallationDate: Installed on 2012-05-16 (796 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internes Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  klaus  1965 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel, playback] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-07-17 (4 days ago)
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0310
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5GC-MX/1333
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0310:bd12/24/2007:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GC-MX/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.name: System Product Name
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1346428/+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 1346490] Re: Only audio over HDMI in certain modes

xrandr --verbose


does output show audio is enabled at different graphic modes ?

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

Title:
  Only audio over HDMI in certain modes

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  I've hooked up my computer (Ubuntu server 14.04 LTS) to my receiver
  which in turn is hooked up to my TV.

  The problem is that audio only works on certain modes. For instance,
  if I set the mode to 1080i60 using xrandr, audio works fine. The same
  goes for 1080p25. However, when I increase the framerate on the
  progressive scans on the 1920x1080 resolution the audio switches off.
  E.g. 1080p60 (the preferred mode) shows the video just fine,  but
  there's no audio.

  When the computer is directly connected to the TV I'm able to play
  audio despite using the preferred 1080p60 mode on the built-in TV
  speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 2606 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 21 21:10:27 2014
  InstallationDate: Installed on 2013-01-10 (556 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [To be filled by O.E.M., Intel PantherPoint HDMI, Digital Out, HDMI] 
Playback problem
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (0 days ago)
  dmi.bios.date: 03/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1346490/+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 1346490] Re: Only audio over HDMI in certain modes

you have to ask the graphic driver developer since the graphic driver
have the abillity todisable hdmi audio when bandwidth is not enough

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

Title:
  Only audio over HDMI in certain modes

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  I've hooked up my computer (Ubuntu server 14.04 LTS) to my receiver
  which in turn is hooked up to my TV.

  The problem is that audio only works on certain modes. For instance,
  if I set the mode to 1080i60 using xrandr, audio works fine. The same
  goes for 1080p25. However, when I increase the framerate on the
  progressive scans on the 1920x1080 resolution the audio switches off.
  E.g. 1080p60 (the preferred mode) shows the video just fine,  but
  there's no audio.

  When the computer is directly connected to the TV I'm able to play
  audio despite using the preferred 1080p60 mode on the built-in TV
  speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 2606 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 21 21:10:27 2014
  InstallationDate: Installed on 2013-01-10 (556 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [To be filled by O.E.M., Intel PantherPoint HDMI, Digital Out, HDMI] 
Playback problem
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (0 days ago)
  dmi.bios.date: 03/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1346490/+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 1346490] Re: Only audio over HDMI in certain modes

xrandr -x verborse


does output show audio is enabled at different graphic modes ?

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

Title:
  Only audio over HDMI in certain modes

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  I've hooked up my computer (Ubuntu server 14.04 LTS) to my receiver
  which in turn is hooked up to my TV.

  The problem is that audio only works on certain modes. For instance,
  if I set the mode to 1080i60 using xrandr, audio works fine. The same
  goes for 1080p25. However, when I increase the framerate on the
  progressive scans on the 1920x1080 resolution the audio switches off.
  E.g. 1080p60 (the preferred mode) shows the video just fine,  but
  there's no audio.

  When the computer is directly connected to the TV I'm able to play
  audio despite using the preferred 1080p60 mode on the built-in TV
  speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 2606 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 21 21:10:27 2014
  InstallationDate: Installed on 2013-01-10 (556 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [To be filled by O.E.M., Intel PantherPoint HDMI, Digital Out, HDMI] 
Playback problem
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (0 days ago)
  dmi.bios.date: 03/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1346490/+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 631241] Re: The command usage "fc-match Serif:lang=xx" where xx is any language not revealing correct results

2014-07-21 Thread Rex Tsai

Thank you for reporting this bug to Ubuntu. 10.10 reached EOL on April 10, 2012.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with 14.04 trusty and was unable to,
given the information you've provided. Please upgrade to the latest
version and re-test. If the bug is still reproducible, increase the
verbosity of the steps to recreate it so we can try again.

Please note the language code of en-us. Do feel free to report any other
bugs you may find.

** Changed in: fontconfig (Ubuntu)
   Status: New => Incomplete

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

Title:
  The command usage "fc-match Serif:lang=xx" where xx is any language
  not revealing correct results

Status in “fontconfig” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: fontconfig

  To find out what font the fontconfig matches to a generic, say Sans,
  for a language, say English-US, I can use fc-match command in
  following two ways:

  LANG=en_US.UTF-8 && fc-match Sans

  fc-match Sans:lang=en_US.UTF-8

  Of the above two it is usually the second I use for finding what fonts
  are set to Sans, Mono and Serif for different languages.

  Now in freshly installed Ubuntu 10.10 - Beta platform / Gnome Desktop/
  I find that the second form fails to reveal correct matching only in
  case of Serif generic for any language.

  I have shown comparison of the above two forms of command usage -
  Sans, Mono and Serif respectively for languages en-US, ta_IN (Tamil),
  si_LK (Sinhala) and hi_IN (Hindi).

  As shown by the boxed in (with red) parts  , the above 2nd form of
  usage on left terminal yields match to Serif for each language wrongly
  as "Lohit Tamil" font whereas on the right side the first form if
  usage reveals correct matches.

  By checking out effects of changing fonts in GEDIT, I have found that
  actual matching is correct as revealed by the first of the above two
  forms. So it is the second syntax that is affected only for Serif.

  Since I noticed another issue with newly introduced 90-ttf-tamil-
  fonts.conf (ref: https://bugs.launchpad.net/ubuntu/+source/ttf-indic-
  fonts/+bug/630269 ) I got to wonder whether the newly introduced
  90-ttf--fonts.conf (wherein  to mean Tamil, Hindi
  etc ) files in /etc/fonts/conf.avail cause these problems. I removed
  the "/etc/fonts/conf.d/90-ttf-tamil-fonts.conf ->
  /etc/fonts/conf.avail/90-ttf-tamil-fonts.conf" link first. Sure enough
  "Lohit Tamil" changed to "Lohit Punjabi" in the above mentioned wrong
  results. Then removing the link for Punjabi, the wrong result changes
  to another indic language font and so on. Removing such "90-ttf-"
  links for all indic languages restores normalcy for the fc-match
  command usage with ":lang=" element !

  So it appears the bug arises from the conf files whose file name start
  with "90-ttf-"

  K. Sethu

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: fontconfig 2.8.0-2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
  Uname: Linux 2.6.35-19-generic i686
  Architecture: i386
  Date: Mon Sep  6 07:11:35 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: fontconfig

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/631241/+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 1329014] Re: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

THE LOCKING CTL BUG can be easily reproduced by open two terminals

aplay -D front:AUDIGY2 -f DAT Foo1.wav

arecord -D front:AUDIGY2 -f DAT Foo2.wav


you need to change /usr/share/alsa/conf/cards/AUDIGY2.conf

so that the slave capture device has no locks or just define playback
slave only

Plugin: asym

This plugin is a combination of playback and capture PCM streams. Slave PCMs 
can be defined asymmetrically for both directions.
pcm.name {
type asym   # Asym PCM
playback STR# Playback slave name
# or
playback {  # Playback slave definition
pcm STR # Slave PCM name
# or
pcm { } # Slave PCM definition
}
capture STR # Capture slave name
# or
capture {   # Capture slave definition
pcm STR # Slave PCM name
# or
pcm { } # Slave PCM definition
}
}

For example, you can combine a dmix plugin and a dsnoop plugin as as a single 
PCM for playback and capture directions, respectively. 
pcm.duplex {
type asym
playback.pcm "dmix"
capture.pcm "dsnoop"
}

By defining only a single direction, the resultant PCM becomes half-
duplex.

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

Title:
  [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  newage@newage-desktop:~$ aplay -l
   Lista PLAYBACK de dispozitive 
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 0: emu10k1 [ADC 
Capture/Standard PCM Playback]
subdispozitive: 32/32
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
Subdispozitiv #8: subdevice #8
Subdispozitiv #9: subdevice #9
Subdispozitiv #10: subdevice #10
Subdispozitiv #11: subdevice #11
Subdispozitiv #12: subdevice #12
Subdispozitiv #13: subdevice #13
Subdispozitiv #14: subdevice #14
Subdispozitiv #15: subdevice #15
Subdispozitiv #16: subdevice #16
Subdispozitiv #17: subdevice #17
Subdispozitiv #18: subdevice #18
Subdispozitiv #19: subdevice #19
Subdispozitiv #20: subdevice #20
Subdispozitiv #21: subdevice #21
Subdispozitiv #22: subdevice #22
Subdispozitiv #23: subdevice #23
Subdispozitiv #24: subdevice #24
Subdispozitiv #25: subdevice #25
Subdispozitiv #26: subdevice #26
Subdispozitiv #27: subdevice #27
Subdispozitiv #28: subdevice #28
Subdispozitiv #29: subdevice #29
Subdispozitiv #30: subdevice #30
Subdispozitiv #31: subdevice #31
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 2: emu10k1 efx 
[Multichannel Capture/PT Playback]
subdispozitive: 8/8
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 3: emu10k1 [Multichannel 
Playback]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 4: p16v [p16v]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0

  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 i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newage 2071 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 11 20:38:53 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-11 (0 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audigy2 failed
  Symptom_Card: SB0240 Audigy 2 Platinum 6.1 - SB Audigy 2 [SB0240]
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newage 2071 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BZ87510A.86A.0125.P34.0503312215
  dmi.board.name: D875PBZ
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC26680-205
  dmi.chassis.type: 2
  dmi.modalias: 
dm

[Touch-packages] [Bug 1346199] Re: Needs testing in -proposed: systemd 208

2014-07-21 Thread Anders Kaseorg

Works fine for me when booted via systemd.

When booted via Upstart, gdm shows no users to log in as, and no “Not
listed?” link, so I can’t log in graphically.
/var/log/gdm/:0-greeter.log has these errors:

"""
gnome-session[1854]: WARNING: Could not get session id for session. Check that 
logind is properly installed and pam_systemd is getting used at login.
gnome-session[1854]: WARNING: Could not parse desktop file 
orca-autostart.desktop or it references a not found TryExec binary

(gnome-settings-daemon:1954): media-keys-plugin-WARNING **: Unable to
inhibit keypresses: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied:
Operation not permitted

(gnome-settings-daemon:1954): color-plugin-WARNING **: failed to create
device: failed to obtain org.freedesktop.color-manager.create-device
auth

(gnome-settings-daemon:1954): color-plugin-WARNING **: failed to obtain
org.freedesktop.color-manager.create-profile auth

(gnome-settings-daemon:1954): AccountsService-WARNING **:
SetInputSources call failed:
GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: Not
authorized

(gnome-settings-daemon:1954): AccountsService-WARNING **: SetInputSources call 
failed: GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: Not 
authorized
Gjs-Message: JS LOG: Failed to register AuthenticationAgent
Gjs-Message: JS LOG: No permission to trigger offline updates: Polkit.Error: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action 
org.freedesktop.packagekit.trigger-offline-update is not registered
Gjs-Message: JS LOG: GNOME Shell started at Mon Jul 21 2014 23:00:29 GMT-0400 
(EDT)

(gnome-shell:2211): Gjs-WARNING **: JS ERROR: Exception in callback for
signal: startup-prepared: GLib.Error gdm_display_error:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gdm_5fdisplay_5ferror.Code2:
Error getting session id from systemd: No such file or directory

(gnome-shell:2211): Gjs-WARNING **: JS ERROR: could not get remote objects for 
service org.gnome.SettingsDaemon.Smartcard path 
/org/gnome/SettingsDaemon/Smartcard: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SettingsDaemon.Smartcard was not provided by any .service files
_proxyInvoker/asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:83

Window manager warning: Log level 16: 
/build/buildd/glib2.0-2.41.1/./gobject/gsignal.c:3102: signal id '504' is 
invalid for instance '0x3473630'
"""

Restarting gdm makes it work again.

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

Title:
  Needs testing in -proposed: systemd 208

Status in “systemd” package in Ubuntu:
  In Progress

Bug description:
  I just uploaded systemd 208-6ubuntu1 to utopic-proposed, which makes
  use of the new cgmanager-enabled systemd-shim. This bug prevents this
  new version to migrate to utopic until we get more confirmation that
  this doesn't regress udev/logind.

  I already tested this in a clean utopic VM, upgrade and fresh install
  on my Utopic amd64 workstation, and manually built armhf binaries
  (from an intermediate 208 version) on the current Ubuntu Touch image.

  TODO:

   * pitti: re-test Ubuntu Touch with the actual binaries from -proposed
   * stgraber: confirm that this works well with system/user containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1346199/+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 1046335] Re: USB Printer: some times the jobs are printed and some times not

2014-07-21 Thread Miguel Gastelum

I have three thermal receipt printers connected to Xubuntu 14.04 with
Model Generic / Text only driver when print command three jobs, one for
each printer, sometimes one or two printers stops are left with the job
without printing, and the queue print says that the printer is turned
off or disconnected.

If I send a new print job to the printer that has been standing prints
the job that had been printed and the new, but the new print was
incomplete.

CUPS Version:  cups 1.7.2-0ubuntu1  amd64

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

Title:
  USB Printer: some times the jobs are printed and some times not

Status in “cups” package in Ubuntu:
  Fix Released

Bug description:
  This is a Samsung ML-1860 laser monochromatic printer, attached at
  usb.

  The problem is: only some pages are printed. Example: I send 6 copies
  of some page to print but only 4 are actually printed. Or some times
  none of them. Rarely all of them are printed. If I disconnect from
  usb, then send the job and reconnect, the chance of get the print done
  is increased.

  More technical information:

  ~$ lsmod | grep usb
  usblp  18307  0

  ~$ tail -f /var/log/syslog
  Sep  5 10:42:54 desguai3 udev-configure-printer: device devpath is 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Sep  5 10:42:54 desguai3 udev-configure-printer: Device already handled
  Sep  5 10:45:12 desguai3 wpa_supplicant[1135]: WPA: Group rekeying completed 
with 1c:7e:e5:46:5b:9d [GTK=TKIP]
  Sep  5 10:46:43 desguai3 kernel: [ 6539.488475] usb 2-1.1: USB disconnect, 
device number 9
  Sep  5 10:46:43 desguai3 kernel: [ 6539.488755] usblp0: removed
  Sep  5 10:46:43 desguai3 udev-configure-printer: remove 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Sep  5 10:46:43 desguai3 udev-configure-printer: URI of print queue: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X., normalized: samsung ml 
1860 series serial z5m7bdab501185x
  Sep  5 10:46:43 desguai3 udev-configure-printer: URI of detected printer: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X., normalized: samsung ml 
1860 series serial z5m7bdab501185x
  Sep  5 10:46:43 desguai3 udev-configure-printer: Queue 
ipp://localhost:631/printers/ML-1860-Series has matching device URI
  Sep  5 10:46:43 desguai3 udev-configure-printer: Disabled printer 
ipp://localhost:631/printers/ML-1860-Series as the corresponding device was 
unplugged or turned off
  Sep  5 10:47:05 desguai3 kernel: [ 6560.789503] usb 2-1.1: new high-speed USB 
device number 10 using ehci_hcd
  Sep  5 10:47:05 desguai3 kernel: [ 6560.885528] usblp0: USB Bidirectional 
printer dev 10 if 0 alt 0 proto 2 vid 0x04E8 pid 0x330C
  Sep  5 10:47:05 desguai3 mtp-probe: checking bus 2, device 10: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1"
  Sep  5 10:47:05 desguai3 mtp-probe: bus: 2, device: 10 was not an MTP device
  Sep  5 10:47:05 desguai3 udev-configure-printer: add 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0
  Sep  5 10:47:05 desguai3 udev-configure-printer: device devpath is 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Sep  5 10:47:05 desguai3 udev-configure-printer: Device vendor/product is 
04E8:330C
  Sep  5 10:47:05 desguai3 udev-configure-printer: add 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/usb/lp0
  Sep  5 10:47:05 desguai3 udev-configure-printer: failed to claim interface
  Sep  5 10:47:05 desguai3 udev-configure-printer: device devpath is 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Sep  5 10:47:05 desguai3 udev-configure-printer: MFG:Samsung MDL:ML-1860 
Series SERN:- serial:Z5M7BDAB501185X.
  Sep  5 10:47:06 desguai3 kernel: [ 6562.056195] usblp0: removed
  Sep  5 10:47:06 desguai3 udev-configure-printer: URI contains USB serial 
number
  Sep  5 10:47:06 desguai3 udev-configure-printer: URI match: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  Sep  5 10:47:06 desguai3 kernel: [ 6562.061236] usblp0: USB Bidirectional 
printer dev 10 if 0 alt 0 proto 2 vid 0x04E8 pid 0x330C
  Sep  5 10:47:06 desguai3 udev-configure-printer: Consider also queues with 
"/usb/lp0" or "/usblp0" in their URIs as matching
  Sep  5 10:47:06 desguai3 udev-configure-printer: URI of print queue: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X., normalized: samsung ml 
1860 series serial z5m7bdab501185x
  Sep  5 10:47:06 desguai3 udev-configure-printer: URI of detected printer: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X., normalized: samsung ml 
1860 series serial z5m7bdab501185x
  Sep  5 10:47:06 desguai3 udev-configure-printer: Queue 
ipp://localhost:631/printers/ML-1860-Series has matching device URI
  Sep  5 10:47:06 desguai3 udev-configure-printer: Re-enabled printer 
ipp://localhost:631/printers/ML-1860-Series
  Sep  5 10:47:06 desguai3 udev-configure-printer: add 
/devices/pci:00/:00:1d.0/usb2/

[Touch-packages] [Bug 1346641] Re: Mobility X700 graphic corruption

2014-07-21 Thread Daniel Letzeisen

Modern versions of Catalyst do not support the X700 (and the last
version of Catalyst to support it will not work on any currently
supported version of Ubuntu). Please make sure you completely purge
Catalyst:
http://wiki.cchtml.com/index.php/Ubuntu_Trusty_Installation_Guide#Removing_Catalyst.2Ffglrx

After you've done that, please gather logs with the command:
apport-collect 1346641

** Summary changed:

- yes
+ Mobility X700 graphic corruption

** Changed in: xorg (Ubuntu)
Status: New => Incomplete

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

Title:
Mobility X700 graphic corruption

Status in “xorg” package in Ubuntu:
Incomplete

Bug description:
thank you for helping me. I love ubuntu and i resently got this pc.
its old but it works well with the proper drivers unfortunaly I need a
sertain driver in order for my cpu and my graphics card to work
properly. im using a transport x3100 mpc. my driver is the Mobility
Radeon X700. im using the amd catalyst and it seems pretty glitched
out. also with out the proper driver it won't work. ive used the
regular driver in witch came with xubuntu but on start up sometimes
gets really screwy. done countless reserch and no cigar. thank you.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CurrentDesktop: XFCE
Date: Mon Jul 21 18:09:08 2014
InstallationDate: Installed on 2014-07-21 (0 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1346641/+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 1345533] Re: [regression][hammerhead] Mir fails to start on Nexus 5 as it fails to turn vsync signal on

2014-07-21 Thread Daniel van Vugt

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Mir development team (mir-team)

** Summary changed:

- [regression][hammerhead] Mir fails to start on Nexus 5 as it fails to turn 
vsync signal on
+ [regression][hammerhead] Mir fails to start on Nexus 5 & 10 as it fails to 
turn vsync signal on

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

Title:
  [regression][hammerhead] Mir fails to start on Nexus 5 & 10 as it
  fails to turn vsync signal on

Status in Mir:
  Fix Committed
Status in Mir 0.5 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  In Progress

Bug description:
  Starting from image 137, with mir 0.5, Mir fails to start on Nexus 5
  (hammerhead), as it fails to turn the vsync signal on.

  This is what I get from logcat:

  D/libEGL  ( 3038): loaded /vendor/lib/egl/libEGL_adreno.so
  D/libEGL  ( 3038): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
  D/libEGL  ( 3038): loaded /vendor/lib/egl/libGLESv2_adreno.so
  I/qdutils ( 3038): Right Split=0
  D/qdhwcomposer( 3038): int qhwc::adRead(): /sys/class/graphics/fb2/ad could 
not be opened : No such file or directory
  I/qdhwcomposer( 3038): Initializing Qualcomm Hardware Composer
  I/qdhwcomposer( 3038): MDP version: 500
  I/Adreno-EGL( 3038): : EGL 1.4 QUALCOMM Build: 
I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
  D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, width = 1080
  D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, height = 1920
  I/Adreno-EGL( 3038): : EGL 1.4 QUALCOMM Build: 
I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
  I/qdhwcomposer( 3038): hwc_registerProcs
  I/qdhwcomposer( 3038): Initializing UEVENT Thread
  I/qdhwcomposer( 3038): Initializing VSYNC Thread
  I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=0 from 
/sys/class/graphics/fb0/vsync_event
  I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=1 from 
/sys/class/graphics/fb1/vsync_event
  D/qdhwcomposer( 3038): hwc_blank: Unblanking display: 0
  D/qdhwcomposer( 3038): hwc_blank: Done unblanking display: 0
  E/qdhwcomposer( 3038): hwc_vsync_control: vsync control failed. Dpy=0, 
enable=1 : Operation not supported
  W/libEGL  ( 3038): eglTerminate() called w/ 1 objects remaining
  E/libEGL  ( 3038): validate_display:263 error 3001 (EGL_NOT_INITIALIZED)
  I/ServiceManager(  913): service 'display.qservice' died

  The vsync control failed message was always there, and Mir 0.4 worked
  fine with it still.

  System compositor log:
  root@ubuntu-phablet:/var/log/lightdm# cat unity-system-compositor.log
  ERROR: 
/build/buildd/mir-0.5.0+14.10.20140717/src/platform/graphics/android/real_hwc_wrapper.cpp(75):
 Throw in function virtual void 
mir::graphics::android::RealHwcWrapper::vsync_signal_on() const
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
  std::exception::what: error turning vsync signal on. rc = ffa1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1345533/+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 1345533] Re: [regression][hammerhead] Mir fails to start on Nexus 5 as it fails to turn vsync signal on

2014-07-21 Thread Daniel van Vugt

** Changed in: mir
   Status: In Progress => Fix Committed

** Changed in: mir/0.5
   Status: In Progress => Fix Committed

** Changed in: mir (Ubuntu)
   Status: New => In Progress

** Branch linked: lp:~kdub/mir/fix-1345533

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

Title:
  [regression][hammerhead] Mir fails to start on Nexus 5 as it fails to
  turn vsync signal on

Status in Mir:
  Fix Committed
Status in Mir 0.5 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  In Progress

Bug description:
  Starting from image 137, with mir 0.5, Mir fails to start on Nexus 5
  (hammerhead), as it fails to turn the vsync signal on.

  This is what I get from logcat:

  D/libEGL  ( 3038): loaded /vendor/lib/egl/libEGL_adreno.so
  D/libEGL  ( 3038): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
  D/libEGL  ( 3038): loaded /vendor/lib/egl/libGLESv2_adreno.so
  I/qdutils ( 3038): Right Split=0
  D/qdhwcomposer( 3038): int qhwc::adRead(): /sys/class/graphics/fb2/ad could 
not be opened : No such file or directory
  I/qdhwcomposer( 3038): Initializing Qualcomm Hardware Composer
  I/qdhwcomposer( 3038): MDP version: 500
  I/Adreno-EGL( 3038): : EGL 1.4 QUALCOMM Build: 
I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
  D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, width = 1080
  D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, height = 1920
  I/Adreno-EGL( 3038): : EGL 1.4 QUALCOMM Build: 
I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
  I/qdhwcomposer( 3038): hwc_registerProcs
  I/qdhwcomposer( 3038): Initializing UEVENT Thread
  I/qdhwcomposer( 3038): Initializing VSYNC Thread
  I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=0 from 
/sys/class/graphics/fb0/vsync_event
  I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=1 from 
/sys/class/graphics/fb1/vsync_event
  D/qdhwcomposer( 3038): hwc_blank: Unblanking display: 0
  D/qdhwcomposer( 3038): hwc_blank: Done unblanking display: 0
  E/qdhwcomposer( 3038): hwc_vsync_control: vsync control failed. Dpy=0, 
enable=1 : Operation not supported
  W/libEGL  ( 3038): eglTerminate() called w/ 1 objects remaining
  E/libEGL  ( 3038): validate_display:263 error 3001 (EGL_NOT_INITIALIZED)
  I/ServiceManager(  913): service 'display.qservice' died

  The vsync control failed message was always there, and Mir 0.4 worked
  fine with it still.

  System compositor log:
  root@ubuntu-phablet:/var/log/lightdm# cat unity-system-compositor.log
  ERROR: 
/build/buildd/mir-0.5.0+14.10.20140717/src/platform/graphics/android/real_hwc_wrapper.cpp(75):
 Throw in function virtual void 
mir::graphics::android::RealHwcWrapper::vsync_signal_on() const
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
  std::exception::what: error turning vsync signal on. rc = ffa1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1345533/+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 1346646] Re: init-functions: status_of_proc has incorrect call to pidofproc

Nevermind this is in error, I just noticed the:

if [ -n "$pidfile" ]; then
pidfile="-p $pidfile"
fi

bit in there.

So there is no bug.  You can close this, if I can't.

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

Title:
  init-functions: status_of_proc has incorrect call to pidofproc

Status in “lsb” package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 12.04.4 LTS
  Release:12.04

  lsb-base:
Installed: 4.0-0ubuntu20.3
Candidate: 4.0-0ubuntu20.3
Version table:
   *** 4.0-0ubuntu20.3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.0-0ubuntu20 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  
  Appears that the status_of_proc() function in /lib/lsb/init-functions 
incorrectly calls pidofproc.  pidofproc requires a -p switch to specify a 
pidfile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+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 1329014] Re: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

2014-07-21 Thread Joel Chav

Hello Raymond,

How to do it? (how use the asym plugin, can you explain?)

Joe

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

Title:
  [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  newage@newage-desktop:~$ aplay -l
   Lista PLAYBACK de dispozitive 
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 0: emu10k1 [ADC 
Capture/Standard PCM Playback]
subdispozitive: 32/32
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
Subdispozitiv #8: subdevice #8
Subdispozitiv #9: subdevice #9
Subdispozitiv #10: subdevice #10
Subdispozitiv #11: subdevice #11
Subdispozitiv #12: subdevice #12
Subdispozitiv #13: subdevice #13
Subdispozitiv #14: subdevice #14
Subdispozitiv #15: subdevice #15
Subdispozitiv #16: subdevice #16
Subdispozitiv #17: subdevice #17
Subdispozitiv #18: subdevice #18
Subdispozitiv #19: subdevice #19
Subdispozitiv #20: subdevice #20
Subdispozitiv #21: subdevice #21
Subdispozitiv #22: subdevice #22
Subdispozitiv #23: subdevice #23
Subdispozitiv #24: subdevice #24
Subdispozitiv #25: subdevice #25
Subdispozitiv #26: subdevice #26
Subdispozitiv #27: subdevice #27
Subdispozitiv #28: subdevice #28
Subdispozitiv #29: subdevice #29
Subdispozitiv #30: subdevice #30
Subdispozitiv #31: subdevice #31
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 2: emu10k1 efx 
[Multichannel Capture/PT Playback]
subdispozitive: 8/8
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 3: emu10k1 [Multichannel 
Playback]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 4: p16v [p16v]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0

  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 i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newage 2071 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 11 20:38:53 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-11 (0 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audigy2 failed
  Symptom_Card: SB0240 Audigy 2 Platinum 6.1 - SB Audigy 2 [SB0240]
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newage 2071 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BZ87510A.86A.0125.P34.0503312215
  dmi.board.name: D875PBZ
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC26680-205
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBZ87510A.86A.0125.P34.0503312215:bd03/31/2005:svn:pn:pvr:rvnIntelCorporation:rnD875PBZ:rvrAAC26680-205:cvn:ct2:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1329014/+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 1343039] Re: Cannot install chroot

2014-07-21 Thread XiaoGuo, Liu

HI Michael,

Thanks for your investigation. I think this problem has been resolved. I
talked to xnox, and an engineer said that that could be caused by some
of the rouge mirror on the server side.

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

Title:
  Cannot install chroot

Status in “click” package in Ubuntu:
  Incomplete

Bug description:
  I have the following error when trying to install chroot in the VM.

  ---Click exited with errors, please check the output---Traceback (most recent 
call last):
File "/usr/bin/click", line 86, in 
  sys.exit(main())
File "/usr/bin/click", line 82, in main
  return mod.run(args)
File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 244, 
in run
  return args.func(parser, args)
File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 67, in 
create
  return chroot.create(args.keep_broken_chroot)
File "/usr/lib/python3/dist-packages/click/chroot.py", line 422, in create
  self._debootstrap(components, mount)
File "/usr/lib/python3/dist-packages/click/chroot.py", line 360, in 
_debootstrap
  self.archive
File "/usr/lib/python3.4/subprocess.py", line 561, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['debootstrap', '--arch', 'amd64', 
'--variant=buildd', '--components=main,restricted,universe,multiverse', 
'utopic', '/var/lib/schroot/chroots/click-ubuntu-sdk-14.10-armhf', 
'http://archive.ubuntu.com/ubuntu']' returned non-zero exit status 1
  I: Retrieving Release 
  I: Retrieving Release.gpg 
  I: Checking Release signature
  E: Invalid Release signature (key id 40976EAF437D05B5)
  There was an error creating the click target, cleaning up
  A chroot for that name and architecture does not exist.
  Please use 'create' to create it.
  Deleting /etc/schroot/chroot.d/click-ubuntu-sdk-14.10-armhf
  Deleting /var/lib/schroot/chroots/click-ubuntu-sdk-14.10-armhf
  click target was removed successfullyuo

  Is there any way to uninstall my current SDK. I want to reinstall
  everything again.

  Best regards,
  XiaoG

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1343039/+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 1335635] Re: avconv is a poor substitute for ffmpeg

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

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

** Changed in: libav (Ubuntu)
   Status: New => Confirmed

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

Title:
  avconv is a poor substitute for ffmpeg

Status in “libav” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I currently have the problem that I have around 2 dozens of video
  (still counting) that can't be converted with avconv because of a bug
  in avconv, causing it to abort.  I have been informed by ffmpeg people
  that avconv currently contains several hundred of open bugs that don't
  get fixed.

  After all, it seems somewhat questionable that ffmpeg has been
  replaced by avconv in ubuntu.

  I'd like to propose to offer both (ffmpeg and avconv) for some time,
  to compare and to see what's more stable and reliable.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libav-tools 6:9.13-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jun 29 17:15:00 2014
  SourcePackage: libav
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (71 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1335635/+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 1346646] Re: init-functions: status_of_proc has incorrect call to pidofproc

I removed "A proposed patch", it was bad.

** Patch removed: "A proposed patch"
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+attachment/4159596/+files/init-functions.patch

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

Title:
  init-functions: status_of_proc has incorrect call to pidofproc

Status in “lsb” package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 12.04.4 LTS
  Release:12.04

  lsb-base:
Installed: 4.0-0ubuntu20.3
Candidate: 4.0-0ubuntu20.3
Version table:
   *** 4.0-0ubuntu20.3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.0-0ubuntu20 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  
  Appears that the status_of_proc() function in /lib/lsb/init-functions 
incorrectly calls pidofproc.  pidofproc requires a -p switch to specify a 
pidfile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+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 1333330] Re: Uploads use /com/canonical/applications/download as object paths

This bug was fixed in the package ubuntu-download-manager -
0.7+14.10.20140721-0ubuntu1

---
ubuntu-download-manager (0.7+14.10.20140721-0ubuntu1) utopic; urgency=medium

  [ Manuel de la Pena ]
  * Modify the upload process by storing the reply data in a local path
and change the signal emitted to have a string. This changes the
public dbus API for uploads but no clients use it yet.
  * Fix segfault that we get when performing and upload.
  * Ensure that the timeout is stopped when uploads are added to the
queue.

  [ Manuel de la Peña ]
  * Fix lp:130 to ensure that the correct object path is used. (LP:
#130)
  * Fix segfault that we get when performing and upload.
 -- Ubuntu daily releaseMon, 21 Jul 2014 
09:40:02 +

** Changed in: ubuntu-download-manager (Ubuntu)
   Status: New => Fix Released

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

Title:
  Uploads use /com/canonical/applications/download as object paths

Status in Ubuntu Download Manager:
  In Progress
Status in “ubuntu-download-manager” package in Ubuntu:
  Fix Released

Bug description:
  The path should indicate it is an upload.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-download-manager/+bug/130/+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 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*

2014-07-21 Thread Martin Spacek

I still get this error in Xubuntu 14.04 when I run "sudo gnome-disks",
and possibly other commands that I can't recall at the moment:

$ sudo gnome-disks 
[sudo] password for mspacek: 

** (gnome-disks:474): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-xW1zTsGFKW: Connection refused

Bug #1314782 suggests there's a dbus race condition affecting lots of
packages in Ubuntu.

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

Title:
   Couldn't connect to accessibility bus: Failed to connect to socket
  /tmp/dbus-*

Status in pixbuf library for gtk+:
  Fix Released
Status in “gdk-pixbuf” package in Ubuntu:
  Fix Released

Bug description:
  Since a few days, xsession-errors is fullfilled by that kind of
  errors:

  ** (nautilus:22621): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection
  refused

  ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused

  Similar errors are reported all over the net, but Debian have tried to fix it 
already:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517

  But some other devs seems to blame an atk-bridge:
  https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA

  And some others suggest a dbus/gdbus race; the good thing is that
  seems not disturbing that much the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: i386
  Date: Fri Jun 21 08:35:40 2013
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1193236/+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 1346646] Re: init-functions: status_of_proc has incorrect call to pidofproc

2014-07-21 Thread Ubuntu Foundations Team Bug Bot

The attachment "A proposed patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  init-functions: status_of_proc has incorrect call to pidofproc

Status in “lsb” package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 12.04.4 LTS
  Release:12.04

  lsb-base:
Installed: 4.0-0ubuntu20.3
Candidate: 4.0-0ubuntu20.3
Version table:
   *** 4.0-0ubuntu20.3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.0-0ubuntu20 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  
  Appears that the status_of_proc() function in /lib/lsb/init-functions 
incorrectly calls pidofproc.  pidofproc requires a -p switch to specify a 
pidfile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+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 1257120] Re: Screen not refreshing when second display has full-screen application running

2014-07-21 Thread Christopher M. Penalver

Antonio Roberts, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
please just make a comment to this.

** Changed in: xorg (Ubuntu)
   Importance: Low => Medium

** Changed in: xorg (Ubuntu)
   Status: Expired => Incomplete

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

Title:
  Screen not refreshing when second display has full-screen application
  running

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  I have several external displays that I connect to my laptop (800x600,
  1660x1050). When I put an application, such as Totem, Pure Data or Eye
  of Gnome, full screen (via F11) in the external display, the display
  on the primary screen (my laptop) starts to act weird and not refresh
  properly. Examples:

  http://i.stack.imgur.com/hJVwQ.png - Running Pure Data full screen.
  There is only one window open but the ghost of one is displayed

  http://i.stack.imgur.com/mls7M.png - Attempting to resize a window.
  The orange resize animati is left behind

  Is there a way to fix this?

  I have a Dell XPS 13 developer edition running Ubuntu 13.10 with Intel® 
Ivybridge Mobile graphics and Intel® Core™ i7-3537U CPU @ 2.00GHz × 4 
processors.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2014-05-22 17:58:24,058 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058b]
  InstallationDate: Installed on 2013-10-30 (264 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  MachineType: Dell Inc. XPS L322X
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=54eb282c-f856-4c82-8f6a-a6b664234e56 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-22 (59 days ago)
  UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  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.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Jul 19 18:06:54 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 976638] Re: pkexec does not find any authentication agent

2014-07-21 Thread Martin Spacek

I have an unsubstantiated hunch that Bug #1314782 (multimedia keys don't
work when xfce4-volumed is run in daemon mode) is related. Something to
do with a dbus race condition.

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

Title:
  pkexec does not find any authentication agent

Status in “policykit-1” package in Ubuntu:
  Confirmed

Bug description:
  I am using xubuntu, but I am pretty sure that other variants are
  affected too.

  My problem started with being unable to start synaptic from the menu.
  So far, I have found out that synaptic is started with pkexec.

  When I test starting
  pkexec /usr/sbin/synaptic
  in a terminal, it asks for the password in text mode.

  With another test
  pkexec --disable-internal-agent /usr/sbin/synaptic
  in the terminal, it says it has not found any authentication agent.

  I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the 
PC's and the laptop.
  Comparing the /etc directory trees of the PC's showed many differences, but I 
could not find anything suspicious about the polycikit configuration.

  For the moment, using gksu instead of pkexec is a workaround.

  Thanks and Regards,
  Markus

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: policykit-1 0.104-1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sun Apr  8 17:05:34 2012
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120330)
  ProcEnviron:
   LANGUAGE=de_DE:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/976638/+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 1342270] Re: mms Content-Id and Content-Location mismatch with smil contents

This bug was fixed in the package nuntium - 0.1+14.10.20140721-0ubuntu1

---
nuntium (0.1+14.10.20140721-0ubuntu1) utopic; urgency=low

  [ Sergio Schvezov ]
  * Calling sync and close after encoding and before uploading.
  * Header parameter encoding corrections for content type and from
token insert address length.
  * Attachment encoding fixes. (LP: #1342270)
  * Tracking response file for uploads (remaining parts to be done when
telepathy-ofono integration work starts)
 -- Ubuntu daily releaseMon, 21 Jul 2014 
09:44:10 +

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

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

Title:
  mms Content-Id and Content-Location mismatch with smil contents

Status in “nuntium” package in Ubuntu:
  Fix Released
Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  There's a content id and content location mismatch in the smil so the
  generated artifacts won't be seen.

  Here's an example:
  Content-Location: attachmentSa1737
  Content-Id: \"image20140712_0001.jpg\"

  Content-Location: attachmentsc1737
  Content-Id: "text"

  Content-Location: attachmentFV1737
  Content-Id: "smil"
 

  I use the basename of the file for the Content-Location

  On attachment encoding, I am going to make
  ContentLocation = ContentId

  So just make sure ContentId matches the "src" entry in the smil
  And to avoid any possible problems with other implementations, let's set the 
ContentId for the smil to be smil.xml

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: telepathy-ofono 0.2+14.10.20140701-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Tue Jul 15 15:15:38 2014
  InstallationDate: Installed on 2014-07-15 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140715-020204)
  SourcePackage: telepathy-ofono
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nuntium/+bug/1342270/+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 1257120] Re: Screen not refreshing when second display has full-screen application running

2014-07-21 Thread Christopher M. Penalver

** Tags added: latest-bios-a10

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

Title:
  Screen not refreshing when second display has full-screen application
  running

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  I have several external displays that I connect to my laptop (800x600,
  1660x1050). When I put an application, such as Totem, Pure Data or Eye
  of Gnome, full screen (via F11) in the external display, the display
  on the primary screen (my laptop) starts to act weird and not refresh
  properly. Examples:

  http://i.stack.imgur.com/hJVwQ.png - Running Pure Data full screen.
  There is only one window open but the ghost of one is displayed

  http://i.stack.imgur.com/mls7M.png - Attempting to resize a window.
  The orange resize animati is left behind

  Is there a way to fix this?

  I have a Dell XPS 13 developer edition running Ubuntu 13.10 with Intel® 
Ivybridge Mobile graphics and Intel® Core™ i7-3537U CPU @ 2.00GHz × 4 
processors.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2014-05-22 17:58:24,058 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058b]
  InstallationDate: Installed on 2013-10-30 (264 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  MachineType: Dell Inc. XPS L322X
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=54eb282c-f856-4c82-8f6a-a6b664234e56 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-22 (59 days ago)
  UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  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.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Jul 19 18:06:54 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1257120/+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 976638] Re: pkexec does not find any authentication agent

2014-07-21 Thread Martin Spacek

I'm seeing the same thing in Xubuntu 14.04: pkexec works in text mode,
but not GUI mode. If I run it with the --disable-internal-agent flag, it
raises "Error executing command as another user: No authentication agent
found." polkitd is running, as is polkit-gnome-authentication-agent-1.

This is a fresh install. This wasn't a problem in Xubuntu 12.10. I have
installed some gnome-related packages in order to compile various
programs. "Policykit Authentication Agent" in Session & Startup in the
settings is enabled.

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

Title:
  pkexec does not find any authentication agent

Status in “policykit-1” package in Ubuntu:
  Confirmed

Bug description:
  I am using xubuntu, but I am pretty sure that other variants are
  affected too.

  My problem started with being unable to start synaptic from the menu.
  So far, I have found out that synaptic is started with pkexec.

  When I test starting
  pkexec /usr/sbin/synaptic
  in a terminal, it asks for the password in text mode.

  With another test
  pkexec --disable-internal-agent /usr/sbin/synaptic
  in the terminal, it says it has not found any authentication agent.

  I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the 
PC's and the laptop.
  Comparing the /etc directory trees of the PC's showed many differences, but I 
could not find anything suspicious about the polycikit configuration.

  For the moment, using gksu instead of pkexec is a workaround.

  Thanks and Regards,
  Markus

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: policykit-1 0.104-1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sun Apr  8 17:05:34 2012
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120330)
  ProcEnviron:
   LANGUAGE=de_DE:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/976638/+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 1160638] Re: usb printer works intermittently after upgrade to Precise

2014-07-21 Thread Miguel Gastelum

I have three thermal receipt printers connected to Xubuntu 14.04 with
Model Generic / Text only driver when print command three jobs, one for
each printer, sometimes one or two printers stops are left with the job
without printing, and the queue print says that the printer is turned
off or disconnected.

If I send a new print job to the printer that has been standing prints
the job that had been printed and the new, but the new print was
incomplete.

This is used in a restaurant so that these errors can not happen.

And I hope you can help me with this problem.

CUPS Version: cups 1.7.2-0ubuntu1 amd64

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

Title:
usb printer works intermittently after upgrade to Precise

Status in “cups” package in Ubuntu:
Fix Released

Bug description:
I have a Canon MF4150 mono laser printer...was in use on Oneric with
no problems. Testing Precise (12.04) on another machine before
cutting over & found printing problems with this printer. Tried to
research the issue but have not found a fix.

When first powered up, the printer works fine initially. After a few
jobs, it stops working. It appears that after the last successful
job, the printer is left in a hung state...visible evidence is the
"Processing Data" indicator on the printer remains on...forever. In
normal operation, this indicator goes off immediately after the last
page of the job is completed. Once in thsi state, the printer never
prints again until power is cycled.

However, while in this state, Cups still appears to send print jobs,
but nothing actually prints. The cups log indicates that cups is
sending data to the printer in a sequence of transfers (8192 bytes
each). So cups apparently thinks the printer is accepting the job.
I've compared the log sequence for jobs that print and jobs that don't
and I can find no difference in the information reported in the cups
log (at full debug level logging).

The problem is unlikely to be related to drivers since the printer is
operating in raw mode (the machine is a samba server for Windows
printing clients).

Have tried uni-directional constraint suggested in various places.
This printer does not work at all if this option is applied.

I have tried blacklisting the usblp module. This does not solver the
problem.

Since it does not happen every time, it seems related to the sequence
or timing of usb transactions. Were there significant changes in usb
behavior that would have affected raw printer handling between Oneric
and Precise?

Need to move forward from Oneric...printer testing is my last issue.
Help would be greatly appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: cups 1.5.3-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-39.62-generic-pae 3.2.39
Uname: Linux 3.2.0-39-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
Date: Tue Mar 26 19:05:11 2013
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386
(20120423)
Lpstat:
device for Canon_iP6000D: usb://Canon/iP6000D?serial=1020CF
device for Canon_MF4100_Series:
usb://Canon/MF4100%20Series?serial=SDF690291911B&interface=1
device for Canon_MF4150_Linux: cnusb:/dev/usb/lp1
MarkForUpload: True
Papersize: letter
PpdFiles: Canon_MF4150_Linux: Canon MF4100 Series UFRII LT ver.2.5
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-39-generic-pae
root=UUID=350ae1ab-5bf6-44d2-b966-a72404d9a30c ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0572.2009.0715.2346
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG33FB
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD81072-306
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0572.2009.0715.2346:bd07/15/2009:svn:pn:pvr:rvnIntelCorporation:rnDG33FB:rvrAAD81072-306:cvn:ct3:cvr:
mtime.conffile..etc.cups.cupsd.conf: 2013-03-24T23:56:10.278670

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1160638/+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 1346646] Re: init-functions: status_of_proc has incorrect call to pidofproc

I had a copy paste error with that patch. Adding another.

** Patch added: "init-functions.patch"
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+attachment/4159603/+files/init-functions.patch

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

Title:
  init-functions: status_of_proc has incorrect call to pidofproc

Status in “lsb” package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 12.04.4 LTS
  Release:12.04

  lsb-base:
Installed: 4.0-0ubuntu20.3
Candidate: 4.0-0ubuntu20.3
Version table:
   *** 4.0-0ubuntu20.3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.0-0ubuntu20 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  
  Appears that the status_of_proc() function in /lib/lsb/init-functions 
incorrectly calls pidofproc.  pidofproc requires a -p switch to specify a 
pidfile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+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 1346646] [NEW] init-functions: status_of_proc has incorrect call to pidofproc

Public bug reported:

Description:Ubuntu 12.04.4 LTS
Release:12.04

lsb-base:
  Installed: 4.0-0ubuntu20.3
  Candidate: 4.0-0ubuntu20.3
  Version table:
 *** 4.0-0ubuntu20.3 0
500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 4.0-0ubuntu20 0
500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages


Appears that the status_of_proc() function in /lib/lsb/init-functions 
incorrectly calls pidofproc.  pidofproc requires a -p switch to specify a 
pidfile.

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

** Patch added: "A proposed patch"
   
https://bugs.launchpad.net/bugs/1346646/+attachment/4159596/+files/init-functions.patch

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

Title:
  init-functions: status_of_proc has incorrect call to pidofproc

Status in “lsb” package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 12.04.4 LTS
  Release:12.04

  lsb-base:
Installed: 4.0-0ubuntu20.3
Candidate: 4.0-0ubuntu20.3
Version table:
   *** 4.0-0ubuntu20.3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.0-0ubuntu20 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  
  Appears that the status_of_proc() function in /lib/lsb/init-functions 
incorrectly calls pidofproc.  pidofproc requires a -p switch to specify a 
pidfile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+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 1346632] Re: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal()

2014-07-21 Thread Apport retracing service

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1346632/+attachment/4159578/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1346632/+attachment/4159580/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1346632/+attachment/4159582/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1346632/+attachment/4159583/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1346632/+attachment/4159584/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1346632/+attachment/4159585/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1346632/+attachment/4159586/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1344473

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-store crashed with SIGSEGV in _IO_vfprintf_internal()

Status in “tracker” package in Ubuntu:
  New

Bug description:
  Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: tracker 1.0.2-1ubuntu1
  Uname: Linux 3.16.0-031600rc6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jul 21 19:07:18 2014
  ExecutablePath: /usr/lib/tracker/tracker-store
  InstallationDate: Installed on 2014-04-27 (85 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: /usr/lib/tracker/tracker-store
  SegvAnalysis:
   Segfault happened at: 0x7f450300ce13 <_IO_vfprintf_internal+7443>:   repnz 
scas %es:(%rdi),%al
   PC (0x7f450300ce13) ok
   source "%es:(%rdi)" (0xf02b0e50) not located in a known VMA region 
(needed readable region)!
   destination "%al" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   _IO_vfprintf_internal (s=s@entry=0x7f44fabe3600, format=, 
format@entry=0x7f450433ad00 "Unable to insert multiple values for subject `%s' 
and single valued property `%s' (old_value: '%s', new value: '%s')", 
ap=ap@entry=0x7f44fabe37a8) at vfprintf.c:1642
   __GI___vasprintf_chk (result_ptr=0x7f44fabe3758, flags=1, 
format=0x7f450433ad00 "Unable to insert multiple values for subject `%s' and 
single valued property `%s' (old_value: '%s', new value: '%s')", 
args=0x7f44fabe37a8) at vasprintf_chk.c:66
   g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_error_new_valist () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1346632/+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 1346641] [NEW] yes

2014-07-21 Thread Brandon

Public bug reported:

thank you for helping me. I love ubuntu and i resently got this pc. its
old but it works well with the proper drivers unfortunaly I need a
sertain driver in order for my cpu and my graphics card to work
properly. im using a transport x3100 mpc. my driver is the Mobility
Radeon X700. im using the amd catalyst and it seems pretty glitched out.
also with out the proper driver it won't work. ive used the regular
driver in witch came with xubuntu but on start up sometimes gets really
screwy. done countless reserch and no cigar. thank you.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CurrentDesktop: XFCE
Date: Mon Jul 21 18:09:08 2014
InstallationDate: Installed on 2014-07-21 (0 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xorg (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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1346641

Title:
  yes

Status in “xorg” package in Ubuntu:
  New

Bug description:
  thank you for helping me. I love ubuntu and i resently got this pc.
  its old but it works well with the proper drivers unfortunaly I need a
  sertain driver in order for my cpu and my graphics card to work
  properly. im using a transport x3100 mpc. my driver is the Mobility
  Radeon X700. im using the amd catalyst and it seems pretty glitched
  out. also with out the proper driver it won't work. ive used the
  regular driver in witch came with xubuntu but on start up sometimes
  gets really screwy. done countless reserch and no cigar. thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Mon Jul 21 18:09:08 2014
  InstallationDate: Installed on 2014-07-21 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1346641/+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 1342270] Re: mms Content-Id and Content-Location mismatch with smil contents

** Branch linked: lp:ubuntu/utopic-proposed/nuntium

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

Title:
  mms Content-Id and Content-Location mismatch with smil contents

Status in “nuntium” package in Ubuntu:
  New
Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  There's a content id and content location mismatch in the smil so the
  generated artifacts won't be seen.

  Here's an example:
  Content-Location: attachmentSa1737
  Content-Id: \"image20140712_0001.jpg\"

  Content-Location: attachmentsc1737
  Content-Id: "text"

  Content-Location: attachmentFV1737
  Content-Id: "smil"
 

  I use the basename of the file for the Content-Location

  On attachment encoding, I am going to make
  ContentLocation = ContentId

  So just make sure ContentId matches the "src" entry in the smil
  And to avoid any possible problems with other implementations, let's set the 
ContentId for the smil to be smil.xml

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: telepathy-ofono 0.2+14.10.20140701-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Tue Jul 15 15:15:38 2014
  InstallationDate: Installed on 2014-07-15 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140715-020204)
  SourcePackage: telepathy-ofono
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nuntium/+bug/1342270/+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 1303516] Re: ubiquity crashed with SIGSEGV in _int_malloc()

This bug was fixed in the package harfbuzz - 0.9.29-1ubuntu2

---
harfbuzz (0.9.29-1ubuntu2) utopic; urgency=medium

  * No-change rebuild to drop version of glib2.0-udeb dep
 -- Iain LaneMon, 21 Jul 2014 22:30:44 +0100

** Changed in: harfbuzz (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  ubiquity crashed with SIGSEGV in _int_malloc()

Status in HarfBuzz:
  Invalid
Status in “graphite2” package in Ubuntu:
  Invalid
Status in “harfbuzz” package in Ubuntu:
  Fix Released
Status in “graphite2” source package in Trusty:
  Invalid
Status in “harfbuzz” source package in Trusty:
  In Progress

Bug description:
  [ Description ]

  Memory corruption when rendering Myanmar text leeds to a crash

  [ Test case ]

  IMPORTANT NOTE: below will modify currently running locale/keyboard be
  prepared to restore it, e.g. by enabling keyboard indicator to change
  keyboard back to normal.

  1. Install ubiquity on a desktop or boot from an ISO
    $ sudo apt-get install ubiquity-frontend-gtk
  2. If you run on a desktop start ubiquity with:
    $ ubiquity --greeter
  3. Scroll to the bottom of the language list, click on 5th or 4th from the 
bottom

  ACTUAL RESULT
  python3 segmentation fault:
  *** Error in `/usr/bin/python3': malloc(): memory corruption: 
0x03b33d80 ***
  Segmentation fault (core dumped)

  EXPECTED RESULT
  No crash

  [ QA ]

  Check that the test case doesn't crash after applying the SRU

  [ Original Report ]

  I was testing a daily imagine of Ubuntu Gnome 14.04 (Live Image test),
  and was just checking out the languages on the initial boot up. When i
  was trying to click on the 4th language from the bottom ubiquitity
  crashed to give me this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.17.10
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.339
  Date: Mon Apr  7 00:06:38 2014
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  InterpreterPath: /usr/bin/python3.4
  LiveMediaBuild: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f3d8a71dd71 <_int_malloc+689>:  mov
%r14,0x10(%r9)
   PC (0x7f3d8a71dd71) ok
   source "%r14" ok
   destination "0x10(%r9)" (0x18001210) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ubiquity
  StacktraceTop:
   _int_malloc (av=0x7f3d8aa5c760 , bytes=1824) at malloc.c:3489
   __GI___libc_malloc (bytes=1824) at malloc.c:2891
   ?? () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3
   gr_make_font_with_ops () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3
   gr_make_font_with_advance_fn () from 
/usr/lib/x86_64-linux-gnu/libgraphite2.so.3
  Title: ubiquity crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartUbiquity: debconf: DbDriver "templatedb": 
/var/cache/debconf/templates.dat is locked by another process: Resource 
temporarily unavailable
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/harfbuzz/+bug/1303516/+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 1299975] Re: wireless script checks wrong sys file

2014-07-21 Thread katsu

The bug was corrected.

** 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 pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1299975

Title:
  wireless script checks wrong sys file

Status in “pm-utils” package in Ubuntu:
  Fix Released
Status in “pm-utils” source package in Trusty:
  Fix Committed

Bug description:
  TEST CASE: 
  - on a machine with a wireless interface, run:  
PM_FUNCTIONS=/usr/lib/pm-utils/functions sh -ex  
/usr/lib/pm-utils/power.d/wireless true
and verify that it fails with /sys/class/net/wlan0/device/enable: No such 
file or directory
  - install the update and run the command again and verify that the script 
continue beyond the point it stopped earlier, i.e. that it stops at a later 
point when running e.g. iwconfig 
  - now powersaving for wireless via pm-utils should work as intended from the 
script

  REGRESSION POTENTIAL:
  - the functionality in the script was completely broken before, by fixing 
this bug any bug in the power management that were previously hidden may now be 
uncovered. 

  On Trusty (beta), while trying to diagnose an issue with the wireless
  not connecting upon resume from standby, I discovered an invalid check
  in '/usr/lib/pm-utils/power.d/wireless'.  The script checks
  '/sys/class/net/$1/device/enable' to see if the wireless device is
  enabled, failing to perform any configuration if this sys file does
  not exist.  That happens to be the case for me (intel wireless), which
  the actual location is '/sys/class/net/$1/device/enabled' (enable ->
  enabled).

  Changing the script to use the correct location has not fixed my
  wireless resume issue, but perhaps it is contributing to wireless
  issues for others.  My wireless power-saving is correctly turned off
  upon resume now, though (it would get stuck in power-saving mode
  sometimes).

  $> lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  $> apt-cache policy pm-utils
  pm-utils:
    Installed: 1.4.1-13
    Candidate: 1.4.1-13
    Version table:
   *** 1.4.1-13 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1299975/+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 1346604] [NEW] [530U3BI/530U4BI/530U4BH, Realtek ALC269VC, Pink Mic, Rear] No autoswitch

2014-07-21 Thread mszczuj

Public bug reported:

sound works for a while and then breaks up! It's random and
inconsitient. In Pavucontrol I'm able to see sound indicator that
actually works but neither the speakers or headphones do not produce any
sound. I was trying upgrading alsa, pulseaudio, upstream kernel but none
of them seems to work,

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mich   2281 F pulseaudio
  mich   2449 F pulseaudio
 /dev/snd/pcmC0D0p:   mich   2281 F...m pulseaudio
CurrentDesktop: KDE
Date: Tue Jul 22 00:24:28 2014
InstallationDate: Installed on 2014-05-15 (67 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
Symptom_Jack: Pink Mic, Rear
Symptom_Type: No auto-switch between inputs
Title: [530U3BI/530U4BI/530U4BH, Realtek ALC269VC, Pink Mic, Rear] No autoswitch
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/28/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 13XK
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 530U3BI/530U4BI/530U4BH
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr13XK:bd03/28/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3BI/530U4BI/530U4BH
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-07-22T00:12:50.233861

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


** Tags: amd64 apport-bug 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/1346604

Title:
  [530U3BI/530U4BI/530U4BH, Realtek ALC269VC, Pink Mic, Rear] No
  autoswitch

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  sound works for a while and then breaks up! It's random and
  inconsitient. In Pavucontrol I'm able to see sound indicator that
  actually works but neither the speakers or headphones do not produce
  any sound. I was trying upgrading alsa, pulseaudio, upstream kernel
  but none of them seems to work,

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2281 F pulseaudio
mich   2449 F pulseaudio
   /dev/snd/pcmC0D0p:   mich   2281 F...m pulseaudio
  CurrentDesktop: KDE
  Date: Tue Jul 22 00:24:28 2014
  InstallationDate: Installed on 2014-05-15 (67 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: No auto-switch between inputs
  Title: [530U3BI/530U4BI/530U4BH, Realtek ALC269VC, Pink Mic, Rear] No 
autoswitch
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/28/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 13XK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 530U3BI/530U4BI/530U4BH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr13XK:bd03/28/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3BI/530U4BI/530U4BH
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-07-22T00:12:50.233861

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

-- 
Mailing list: https://launchpad.net/~touch-pac

[Touch-packages] [Bug 1346585] Re: rhythmbox crashed with SIGFPE in g_hash_table_lookup_node()

2014-07-21 Thread Apport retracing service

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1346585/+attachment/4159492/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1346585/+attachment/4159494/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1346585/+attachment/4159496/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1346585/+attachment/4159497/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1346585/+attachment/4159498/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1346585/+attachment/4159499/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1346585/+attachment/4159500/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1203530

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  rhythmbox crashed with SIGFPE in g_hash_table_lookup_node()

Status in “gstreamer1.0” package in Ubuntu:
  New

Bug description:
  It just crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libgstreamer1.0-0 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul 21 23:44:20 2014
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2011-11-13 (981 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: rhythmbox /home/username/WilX/stop.mid.ogg
  Signal: 8
  SourcePackage: gstreamer1.0
  StacktraceTop:
   g_hash_table_lookup_node (hash_return=, 
key=0x7f8a745b1a58, hash_table=0x70f2a0) at 
/build/buildd/glib2.0-2.40.0/./glib/ghash.c:374
   g_hash_table_lookup (hash_table=0x70f2a0, key=0x7f8a745b1a58) at 
/build/buildd/glib2.0-2.40.0/./glib/ghash.c:1092
   rb_refstring_new () from /usr/lib/librhythmbox-core.so.8
   ?? () from /usr/lib/librhythmbox-core.so.8
   g_thread_proxy (data=0x18aa6d0) at 
/build/buildd/glib2.0-2.40.0/./glib/gthread.c:764
  Title: rhythmbox crashed with SIGFPE in g_hash_table_lookup_node()
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (93 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin 
netdev plugdev sambashare scanner tape vboxusers video wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1346585/+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 198759] Re: Right CTRL don't work

2014-07-21 Thread Yann

I just installed Ubuntu 14.04, instead of 13.10 (new install, not an upgrade): 
I confirm this bug reappeared.
When you are used to the CTRL key to copy, paste, CTRL+C, etc, it is quite 
annoying.
How can one apply this 2008 patch to fix it on his system?

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

Title:
  Right CTRL don't work

Status in “xkeyboard-config” package in Ubuntu:
  Fix Released
Status in “xkeyboard-config” source package in Hardy:
  Fix Released

Bug description:
  Binary package hint: xkeyboard-config

  1/ Do a fresh and french Hardy desktop-live (pre Alpha6) installation.
  2/ Open shortcuts management
  3/ assign ejection of cd to Right CTRL + Alt + P
  -> shotcut don't work

  OR

  Install and use virtualbox (that use Right CTRL), and once virtualbox
  have keyboard and mouse focus try to exit VM with the Right CTRL ;)

  OR

  boot in recovery mode -> root shell -> Right CTRL+C don't work

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

Re: [Touch-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application

2014-07-21 Thread Michele Giacomoli

Hi Marco,

After I posted the comment I thought that your implementation was similar
to the mouse-clicking policy, so I thought maybe it was the expected
behavior. Now you confirmed me it was :)

Thank you for your answer, is not too common for Ubuntu developers to reply
in such short time.
Keep up the good work


2014-07-21 21:30 GMT+02:00 Marco Trevisan (Treviño) :

> Michele,
>
> Well, I thought about that when implementing it, and I was a little
> undecided, but I think this is actually the correct behavior considering
> the way that workspaces are handled in unity, where they're always a
> "different world" (so this is for alt-tab, and launcher).
> So, in the same way you won't be able to switch - using the mouse - to a
> secondary instance of an application that is open in a different workspace,
> using the DnD should not behave differently.
>
> So, in terms of consistency I think we're right. Although I understand
> there's a loose of functionality (and no, pressing ctrl+alt+arrow to
> switch workspace when dragging something is not convenient). so I think
> we maybe could allow this when pressing Ctrl when clicking/DnD'ing over
> an icon, or something like that.
>
> Feel free to open a new bug, including ayatana-design.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/607796
>
> Title:
>   Launcher, Window management - Dragging and holding a selection over an
>   entry in the Launcher should spread out windows belonging to that
>   application
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ayatana-design/+bug/607796/+subscriptions
>

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

Title:
  Launcher, Window management - Dragging and holding a selection over an
  entry in the Launcher should spread out windows belonging to that
  application

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in One Hundred Papercuts:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]
  If the user drags and hold a file over a running application in the Launcher, 
all the windows of that application should be shown with the spread. The user 
should then be able to drag and drop the file in a windows in the spread to 
load the file into that specific window.

  [Test Case]
  1) Open two windows instances of the same application (say firefox)
  2) Drag a file from the file-manager or the desktop and hover the firefox icon
  3) After one second the firefox icon is hovered, the spread will occur
  4) You should be able to hover one of the firefox windows and it should
     show a spinner, after 750ms (by default) the hovered windows should be 
focused
     and raised
  5) You should now be able to drop the content you're dragging (if the selected
     application supports that content).

  [Regression Potential]
  This codepath was mostly disabled in the current compiz and unity code 
because it was buggy, so the regression potential is very low, although it 
might happen that, if some race-condition happens, when closing the scale the 
launcher might be still painted as if it would be in scale mode (desaturated) 
even if it's not the case anymore.

  *** SRU debdiff links ***
  The Unity SRU debdiff for this can be found at 
https://launchpadlibrarian.net/180013321/unity-7.2.2-trusty-sru.debdiff.

  The Compiz SRU debdiff for this can be found at
  https://launchpadlibrarian.net/180013356/compiz-0.9.11.2-trusty-
  sru.debdiff

  ###

  Bug #727903 needs to be fixed at the same time.

  ---

  History:

  This bug had been previously fixed as "buggybutclosed" for Unity on 
2011-04-18, leaving this function with other bugs:
  https://bugs.launchpad.net/ayatana-design/+bug/727903
  https://bugs.launchpad.net/ayatana-design/+bug/727904
  https://bugs.launchpad.net/ayatana-design/+bug/727902
  https://bugs.launchpad.net/ayatana-design/+bug/764424
  https://bugs.launchpad.net/ayatana-design/+bug/832988

  On 2011-10-18, it was reopened for regression in Oneiric.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/607796/+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 1227034] Re: Default Chinese font changed to fonts-arphic-ukai after completing language support installation for zh-* locales

2014-07-21 Thread Gunnar Hjalmarsson

Well, if you run fc-match with the zh_TW.UTF-8 locale (which in fact
simulates the use of Traditional Chinese as the display language), it
indeed should make a difference if you install version 0.129.2 of
language-selector-*.

OTOH, if you actually are using English as the display language, a more
adequate test is:

fc-match -a 'sans-serif'

That should result in a long list, and you ought to see a bunch of Droid
Sans fonts (including DroidSansFallbackFull.ttf) before AR PL UMing TW.

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

Title:
  Default Chinese font changed to fonts-arphic-ukai after completing
  language support installation for zh-* locales

Status in Ubuntu Kylin:
  Fix Released
Status in “fonts-android” package in Ubuntu:
  Fix Released
Status in “fonts-takao” package in Ubuntu:
  Fix Released
Status in “language-selector” package in Ubuntu:
  Fix Released
Status in “fonts-android” package in Debian:
  Fix Committed

Bug description:
  After completing language support installation, fonts-arphic-ukai and
  fonts-arphic-uming are pulled into user's system and then fontconfig
  chooses Ukai over Droid Sans Fallback for the default sans-serif font.
  This is not the desired behavior as Ukai doesn't fit well into the
  category of screen fonts comparing to Droid Sans.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1227034/+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 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

This bug was fixed in the package ofono -
1.12.bzr6870+14.10.20140721-0ubuntu1

---
ofono (1.12.bzr6870+14.10.20140721-0ubuntu1) utopic; urgency=medium

  [ Martti Piirainen ]
  * drivers/rilmodem/sim.c: notify on SIM removal (LP: #1332306)
  * unit/rilmodem/test-sim-online: fix serial number check (LP: #1334867)

  [ Alfonso Sanchez-Beato ]
  * plugins/mtk.c: fix race condition when onlining modem
  * build, drivers/infeonmodem, drivers/rilmodem, gril,
plugins/infeon.c, plugins/ril.*, unit: add Infeon OEM hooks

  [ Tony Espy ]
  * build, plugins/ubuntu-provision.c, ubuntu-apndb.*: re-named
provisioning plugin code from android-* to ubuntu-*.  Also removed
code that queries mobile-broadband-provider-info's db, and finally
implemented a /custom hook for custom apn dbs (LP: #1315509).
 -- Ubuntu daily releaseMon, 21 Jul 2014 
18:59:17 +

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

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in “ofono” package in Ubuntu:
  Fix Released
Status in “telepathy-ofono” package in Ubuntu:
  Confirmed
Status in “telephony-service” package in Ubuntu:
  Confirmed

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1332306/+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 1227034] Re: Default Chinese font changed to fonts-arphic-ukai after completing language support installation for zh-* locales

2014-07-21 Thread Alex Yu

The display language is still English (unchanged.)The weird part is
that fc-match returns "AR PL UMing TW".  Let me know if I should still
try language-selector-common 0.129.2 and language-selector-gnome 0.129.2
and update in the other bug https://bugs.launchpad.net/bugs/1335482.

$ sudo locale-gen zh_TW.UTF-8
Generating locales...
  zh_TW.UTF-8... done
Generation complete.

$ LANG=zh_TW.UTF-8 fc-match 'sans-serif'
uming.ttc: "AR PL UMing TW" "Light"

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

Title:
  Default Chinese font changed to fonts-arphic-ukai after completing
  language support installation for zh-* locales

Status in Ubuntu Kylin:
  Fix Released
Status in “fonts-android” package in Ubuntu:
  Fix Released
Status in “fonts-takao” package in Ubuntu:
  Fix Released
Status in “language-selector” package in Ubuntu:
  Fix Released
Status in “fonts-android” package in Debian:
  Fix Committed

Bug description:
  After completing language support installation, fonts-arphic-ukai and
  fonts-arphic-uming are pulled into user's system and then fontconfig
  chooses Ukai over Droid Sans Fallback for the default sans-serif font.
  This is not the desired behavior as Ukai doesn't fit well into the
  category of screen fonts comparing to Droid Sans.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1227034/+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 1346548] [NEW] DepartmentsDbConcurrencyTest.ConcurrentReadWrite is incredibly slow and disk-usage heavy

2014-07-21 Thread Rodney Dawes

Public bug reported:

[   OK ] DepartmentsDbConcurrencyTest.ConcurrentReadWrite (111900
ms)

It is taking almost two whole minutes for this one test to run, and it
is eating up several hundred KB/s of disk I/O while doing so. Our test
suite should not be this slow.

** Affects: unity-scope-click (Ubuntu)
 Importance: High
 Status: Triaged

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

Title:
  DepartmentsDbConcurrencyTest.ConcurrentReadWrite is incredibly slow
  and disk-usage heavy

Status in “unity-scope-click” package in Ubuntu:
  Triaged

Bug description:
  [   OK ] DepartmentsDbConcurrencyTest.ConcurrentReadWrite (111900
  ms)

  It is taking almost two whole minutes for this one test to run, and it
  is eating up several hundred KB/s of disk I/O while doing so. Our test
  suite should not be this slow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1346548/+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 1346110] Re: Needs to be internationalized as a plural string: "%u results in Ubuntu Store"

** Branch linked: lp:~dobey/unity-scope-click/plural-results

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

Title:
  Needs to be internationalized as a plural string: "%u results in
  Ubuntu Store"

Status in “unity-scope-click” package in Ubuntu:
  In Progress

Bug description:
  The following string needs to use plural forms so that it can be
  properly translated in all languages:

  %u results in Ubuntu Store

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1346110/+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 1346110] Re: Needs to be internationalized as a plural string: "%u results in Ubuntu Store"

2014-07-21 Thread Rodney Dawes

** Changed in: unity-scope-click (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Needs to be internationalized as a plural string: "%u results in
  Ubuntu Store"

Status in “unity-scope-click” package in Ubuntu:
  In Progress

Bug description:
  The following string needs to use plural forms so that it can be
  properly translated in all languages:

  %u results in Ubuntu Store

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1346110/+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 1342745] Re: USC does not turn on screen through DBus interface

2014-07-21 Thread Alberto Aguirre

** Changed in: unity-system-compositor
   Status: In Progress => Fix Released

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

Title:
  USC does not turn on screen through DBus interface

Status in Unity System Compositor:
  Fix Released
Status in “unity-system-compositor” package in Ubuntu:
  Fix Released

Bug description:
  When the screen is powered off, USC does not turn on screen from
  either the keepDisplayOn or setScreenPowerMode DBus interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1342745/+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 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

** Branch linked: lp:ubuntu/utopic-proposed/ofono

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in “ofono” package in Ubuntu:
  Fix Committed
Status in “telepathy-ofono” package in Ubuntu:
  Confirmed
Status in “telephony-service” package in Ubuntu:
  Confirmed

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1332306/+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 1346419] Re: package perl-base 5.14.2-6ubuntu2.4 failed to install/upgrade: short read on buffer copy for backend dpkg-deb during `./usr/share/perl/5.14.2/unicore/To/Na1.pl'

2014-07-21 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: failed-to-read

** Changed in: perl (Ubuntu)
   Status: New => Invalid

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

Title:
  package perl-base 5.14.2-6ubuntu2.4 failed to install/upgrade: short
  read on buffer copy for backend dpkg-deb during
  `./usr/share/perl/5.14.2/unicore/To/Na1.pl'

Status in “perl” package in Ubuntu:
  Invalid

Bug description:
  i am going to install programmes but they are not installing in pc

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: perl-base 5.14.2-6ubuntu2.4
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sun Jul 20 21:56:41 2014
  DuplicateSignature: package:perl-base:5.14.2-6ubuntu2.4:short read on buffer 
copy for backend dpkg-deb during `./usr/share/perl/5.14.2/unicore/To/Na1.pl'
  ErrorMessage: short read on buffer copy for backend dpkg-deb during 
`./usr/share/perl/5.14.2/unicore/To/Na1.pl'
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  SourcePackage: perl
  Title: package perl-base 5.14.2-6ubuntu2.4 failed to install/upgrade: short 
read on buffer copy for backend dpkg-deb during 
`./usr/share/perl/5.14.2/unicore/To/Na1.pl'
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1346419/+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 1012081] Re: util-linux needs updating to 2.24.2

2014-07-21 Thread Arion Lawrence

There is another use case for updated util-linux. Newer versions have
'nsenter' which makes poking at running Docker containers possible..

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

Title:
  util-linux needs updating to 2.24.2

Status in “util-linux” package in Ubuntu:
  Triaged
Status in “util-linux” source package in Raring:
  Won't Fix
Status in “util-linux” package in Debian:
  New

Bug description:
  Applications in the default desktop - specifically gnome-disk-utility
  - depend on behaviour only introduced in util-linux 2.21+.
  Specifically if you select "Show in user interface" in mount options,
  it adds the mount option "x-gvfs-show" to the mount options in
  /etc/fstab. Mounting of this mount point then fails because the option
  is unrecognised.

  Also reported bug from the other point of view in bug #1011257

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: util-linux 2.20.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
  Uname: Linux 3.4.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.1.1-0ubuntu2
  Architecture: amd64
  Date: Tue Jun 12 12:38:02 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to quantal on 2012-06-09 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1012081/+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 1322784]

2014-07-21 Thread L. David Baron

We ought to be able to work around this, and probably should, given the
lack of response.

If somebody has a setup that can reproduce the compiler bug, there might
be a straightforward workaround such as inserting |volatile| somewhere
or similar trivial rearrangement of code.

If not, we ought to be able to pad these arrays by 2 bytes, #ifdef linux
and gcc.

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

Title:
  Firefox crashes in flag_qsort during spellchecker initialization on
  x86 due to gcc bug

Status in The Mozilla Firefox Browser:
  Confirmed
Status in “firefox” package in Ubuntu:
  Confirmed
Status in “gcc-4.8” package in Ubuntu:
  Confirmed

Bug description:
  The most common Firefox crash on Linux in Mozilla's crash-stats system
  is crashes in the function flag_qsort.

  These crashes occur:
   * only on x86 architecture
   * only on Ubuntu packages (and not on Mozilla's builds)
   * on precise and saucy and trusty (based on kernel versions reported with 
the crashes)
  and appear to be due to a compiler bug in the compiler used to generate 
Ubuntu's builds.  (It could be a common compiler bug triggered by different 
compiler options or a compiler bug specific to Ubuntu's gcc.)

  The analysis that leads to the conclusion that this is a compiler bug
  is in https://bugzilla.mozilla.org/show_bug.cgi?id=983817 .  In
  particular, the compiler is miscompiling an access to an element of an
  array of unsigned short as a 32-bit read, and when the unsigned short
  in question is the last one in the allocation and that allocation is
  aligned so that the byte following has a different 0x10 bit, this
  can lead to crashes.

  The most recent (whenever you follow the link) 7 days of crash reports
  are available at: https://crash-
  
stats.mozilla.com/report/list?signature=flag_qsort&product=Firefox&query_type=contains&range_unit=weeks

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1322784/+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 1346502] Re: It can be very slow to load a conversation

2014-07-21 Thread Bill Filler

** Tags added: rtm14

** Also affects: messaging-app
   Importance: Undecided
   Status: New

** Changed in: messaging-app
 Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh)

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

Title:
  It can be very slow to load a conversation

Status in Messaging App:
  New
Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Have a lot of conversations in the messaging app
  2. Click on one

  Result:
  There is no feedback and after a many seconds delay the conversation opens

  Expected:
  Either the conversation opens quickly, or there is feedback that it is opening

To manage notifications about this bug go to:
https://bugs.launchpad.net/messaging-app/+bug/1346502/+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 1346502] [NEW] It can be very slow to load a conversation

2014-07-21 Thread Rick Spencer

Public bug reported:

Steps:
1. Have a lot of conversations in the messaging app
2. Click on one

Result:
There is no feedback and after a many seconds delay the conversation opens

Expected:
Either the conversation opens quickly, or there is feedback that it is opening

** Affects: messaging-app
 Importance: Undecided
 Assignee: Tiago Salem Herrmann (tiagosh)
 Status: New

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


** Tags: avengers rtm14

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

Title:
  It can be very slow to load a conversation

Status in Messaging App:
  New
Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  Steps:
  1. Have a lot of conversations in the messaging app
  2. Click on one

  Result:
  There is no feedback and after a many seconds delay the conversation opens

  Expected:
  Either the conversation opens quickly, or there is feedback that it is opening

To manage notifications about this bug go to:
https://bugs.launchpad.net/messaging-app/+bug/1346502/+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 1346490] [NEW] Only audio over HDMI in certain modes

2014-07-21 Thread Dennis

Public bug reported:

I've hooked up my computer (Ubuntu server 14.04 LTS) to my receiver
which in turn is hooked up to my TV.

The problem is that audio only works on certain modes. For instance, if
I set the mode to 1080i60 using xrandr, audio works fine. The same goes
for 1080p25. However, when I increase the framerate on the progressive
scans on the 1920x1080 resolution the audio switches off. E.g. 1080p60
(the preferred mode) shows the video just fine,  but there's no audio.

When the computer is directly connected to the TV I'm able to play audio
despite using the preferred 1080p60 mode on the built-in TV speakers.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dennis 2606 F pulseaudio
CurrentDesktop: Unity
Date: Mon Jul 21 21:10:27 2014
InstallationDate: Installed on 2013-01-10 (556 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.3)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Digital Out, HDMI
Symptom_Type: None of the above
Title: [To be filled by O.E.M., Intel PantherPoint HDMI, Digital Out, HDMI] 
Playback problem
UpgradeStatus: Upgraded to trusty on 2014-07-21 (0 days ago)
dmi.bios.date: 03/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B75M-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug kernel-sound linux 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/1346490

Title:
  Only audio over HDMI in certain modes

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  I've hooked up my computer (Ubuntu server 14.04 LTS) to my receiver
  which in turn is hooked up to my TV.

  The problem is that audio only works on certain modes. For instance,
  if I set the mode to 1080i60 using xrandr, audio works fine. The same
  goes for 1080p25. However, when I increase the framerate on the
  progressive scans on the 1920x1080 resolution the audio switches off.
  E.g. 1080p60 (the preferred mode) shows the video just fine,  but
  there's no audio.

  When the computer is directly connected to the TV I'm able to play
  audio despite using the preferred 1080p60 mode on the built-in TV
  speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 2606 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 21 21:10:27 2014
  InstallationDate: Installed on 2013-01-10 (556 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [To be filled by O.E.M., Intel PantherPoint HDMI, Digital Out, HDMI] 
Playback problem
  UpgradeStatus: Upgraded to trusty on 2014-07-21 (0 days ago)
  dmi.bios.date: 03/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:c

[Touch-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application

2014-07-21 Thread Treviño

Michele,

Well, I thought about that when implementing it, and I was a little undecided, 
but I think this is actually the correct behavior considering the way that 
workspaces are handled in unity, where they're always a "different world" (so 
this is for alt-tab, and launcher).
So, in the same way you won't be able to switch - using the mouse - to a 
secondary instance of an application that is open in a different workspace, 
using the DnD should not behave differently.

So, in terms of consistency I think we're right. Although I understand
there's a loose of functionality (and no, pressing ctrl+alt+arrow to
switch workspace when dragging something is not convenient). so I think
we maybe could allow this when pressing Ctrl when clicking/DnD'ing over
an icon, or something like that.

Feel free to open a new bug, including ayatana-design.

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

Title:
  Launcher, Window management - Dragging and holding a selection over an
  entry in the Launcher should spread out windows belonging to that
  application

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in One Hundred Papercuts:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]
  If the user drags and hold a file over a running application in the Launcher, 
all the windows of that application should be shown with the spread. The user 
should then be able to drag and drop the file in a windows in the spread to 
load the file into that specific window.

  [Test Case]
  1) Open two windows instances of the same application (say firefox)
  2) Drag a file from the file-manager or the desktop and hover the firefox icon
  3) After one second the firefox icon is hovered, the spread will occur
  4) You should be able to hover one of the firefox windows and it should
     show a spinner, after 750ms (by default) the hovered windows should be 
focused
     and raised
  5) You should now be able to drop the content you're dragging (if the selected
     application supports that content).

  [Regression Potential]
  This codepath was mostly disabled in the current compiz and unity code 
because it was buggy, so the regression potential is very low, although it 
might happen that, if some race-condition happens, when closing the scale the 
launcher might be still painted as if it would be in scale mode (desaturated) 
even if it's not the case anymore.

  *** SRU debdiff links ***
  The Unity SRU debdiff for this can be found at 
https://launchpadlibrarian.net/180013321/unity-7.2.2-trusty-sru.debdiff.

  The Compiz SRU debdiff for this can be found at
  https://launchpadlibrarian.net/180013356/compiz-0.9.11.2-trusty-
  sru.debdiff

  ###

  Bug #727903 needs to be fixed at the same time.

  ---

  History:

  This bug had been previously fixed as "buggybutclosed" for Unity on 
2011-04-18, leaving this function with other bugs:
  https://bugs.launchpad.net/ayatana-design/+bug/727903
  https://bugs.launchpad.net/ayatana-design/+bug/727904
  https://bugs.launchpad.net/ayatana-design/+bug/727902
  https://bugs.launchpad.net/ayatana-design/+bug/764424
  https://bugs.launchpad.net/ayatana-design/+bug/832988

  On 2011-10-18, it was reopened for regression in Oneiric.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/607796/+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 1227034] Re: Default Chinese font changed to fonts-arphic-ukai after completing language support installation for zh-* locales

2014-07-21 Thread Gunnar Hjalmarsson

Hmm... Maybe I misunderstood you. I assumed that you also changed the
display language to Traditional Chinese, but I realize now that you did
not say so. So, what is your display language for menus and messages?

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

Title:
  Default Chinese font changed to fonts-arphic-ukai after completing
  language support installation for zh-* locales

Status in Ubuntu Kylin:
  Fix Released
Status in “fonts-android” package in Ubuntu:
  Fix Released
Status in “fonts-takao” package in Ubuntu:
  Fix Released
Status in “language-selector” package in Ubuntu:
  Fix Released
Status in “fonts-android” package in Debian:
  Fix Committed

Bug description:
  After completing language support installation, fonts-arphic-ukai and
  fonts-arphic-uming are pulled into user's system and then fontconfig
  chooses Ukai over Droid Sans Fallback for the default sans-serif font.
  This is not the desired behavior as Ukai doesn't fit well into the
  category of screen fonts comparing to Droid Sans.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1227034/+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 1227034] Re: Default Chinese font changed to fonts-arphic-ukai after completing language support installation for zh-* locales

2014-07-21 Thread Gunnar Hjalmarsson

@Alex: Yes, a mysterious issue popped up as described in bug #1335482.
There is a fix in trusty-proposed (soon in trusty-updates), and it would
be great if you could install language-selector-common 0.129.2 and
language-selector-gnome 0.129.2 from trusty-proposed and let us know if
it fixes the issue for you.

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

Title:
  Default Chinese font changed to fonts-arphic-ukai after completing
  language support installation for zh-* locales

Status in Ubuntu Kylin:
  Fix Released
Status in “fonts-android” package in Ubuntu:
  Fix Released
Status in “fonts-takao” package in Ubuntu:
  Fix Released
Status in “language-selector” package in Ubuntu:
  Fix Released
Status in “fonts-android” package in Debian:
  Fix Committed

Bug description:
  After completing language support installation, fonts-arphic-ukai and
  fonts-arphic-uming are pulled into user's system and then fontconfig
  chooses Ukai over Droid Sans Fallback for the default sans-serif font.
  This is not the desired behavior as Ukai doesn't fit well into the
  category of screen fonts comparing to Droid Sans.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1227034/+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 1310489] Re: xorg.conf overwritten by booting system

2014-07-21 Thread Grief

Please look at this beautiful log! Everything was fine, fglrx was
enabled and loaded, amd card detected, no other cards are present... And
gpu-manager got a great idea to completely remove xorg.conf and install
mesa alternatives instead of pretty working fglrx.

This. Is. Not. Funny.
For me I decided to use 'nogpumanager' parameter as this piece of software is a 
trash. Sorry for my English.

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
Skipping "/dev/dri/card0", driven by "radeon"
Does it require offloading? no
grep dmesg status 256
dmesg status 256 == 0? No
grep dmesg status 0
dmesg status 0 == 0? Yes
Is nvidia loaded? no
Was nvidia unloaded? no
Is fglrx loaded? yes
Was fglrx unloaded? yes
Is intel loaded? no
Is radeon loaded? yes
Is nouveau loaded? yes
Vendor/Device Id: 1002:6810
BusID "PCI:1@0:0:0"
Is boot vga? yes
last cards number = 1
Has amd? yes
Has intel? no
Has nvidia? no
How many cards? 1
Has the system changed? No
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/fglrx/ld.so.conf
Is nvidia enabled? no
Is fglrx enabled? yes
Is mesa enabled? no
Is pxpress enabled? no
Is prime enabled? no
Is nvidia available? no
Is fglrx available? yes
Is mesa available? yes
Is pxpress available? yes
Is prime available? no
Single card detected
Kernel Module is not loaded
Selecting mesa
/usr/bin/update-alternatives --set x86_64-linux-gnu_gl_conf 
/usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
update-alternatives status 0
Calling ldconfig
ldconfig status 0
/usr/bin/update-alternatives --set i386-linux-gnu_gl_conf 
/usr/lib/i386-linux-gnu/mesa/ld.so.conf
update-alternatives status 0
Calling ldconfig
ldconfig status 0
Removing xorg.conf. Path: /etc/X11/xorg.conf
System configuration has changed

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

Title:
  xorg.conf overwritten by booting system

Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  Hello,

  I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI 
Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M.
  After installing fglrx I generated the xorg.conf in the terminal with 'sudo 
aticonfig --adapter=all --initial' and it looked pretty good. Up to this point 
I was able to switch between the cards with the commands 'sudo aticonfig 
--px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the 
intigrated card to save power.
  After rebooting I realized that I was no longer able to switch between the 
cards and found that the xorg.conf will be overwritten whenever I modified it 
and reboot the system. The new (by boot) generated xorg.conf contains not the 
relevant information for switing between the cards.
  I attached both configuration in one file (xorg.conf.comparison). I will also 
provide the atisysteminfo-report.txt so far I will find the place where to 
attach.

  Edit: I fixed the error --> "AIGLX error: failed to open
  /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot
  open shared object file: No such file or directory]" but it changed
  not the bug of overwriting the xorg.conf.

  Regards,
  Uwe

  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: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Mon Apr 21 08:43:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] 
[1002:990b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1985]
     Subsystem: Hewlett-Packard Company Device [103c:1985]
  InstallationDate: Installed on 2014-04-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1985
  dmi.board.vendor: Hewlett-Packard
  dmi.b

[Touch-packages] [Bug 1346110] Re: Needs to be internationalized as a plural string: "%u results in Ubuntu Store"

2014-07-21 Thread Rodney Dawes

** Changed in: unity-scope-click (Ubuntu)
 Assignee: (unassigned) => Rodney Dawes (dobey)

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

Title:
  Needs to be internationalized as a plural string: "%u results in
  Ubuntu Store"

Status in “unity-scope-click” package in Ubuntu:
  Triaged

Bug description:
  The following string needs to use plural forms so that it can be
  properly translated in all languages:

  %u results in Ubuntu Store

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1346110/+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 1303516] Re: ubiquity crashed with SIGSEGV in _int_malloc()

2014-07-21 Thread Bug Watch Updater

** Changed in: harfbuzz
   Status: Confirmed => Invalid

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

Title:
  ubiquity crashed with SIGSEGV in _int_malloc()

Status in HarfBuzz:
  Invalid
Status in “graphite2” package in Ubuntu:
  Invalid
Status in “harfbuzz” package in Ubuntu:
  Triaged
Status in “graphite2” source package in Trusty:
  Invalid
Status in “harfbuzz” source package in Trusty:
  In Progress

Bug description:
  [ Description ]

  Memory corruption when rendering Myanmar text leeds to a crash

  [ Test case ]

  IMPORTANT NOTE: below will modify currently running locale/keyboard be
  prepared to restore it, e.g. by enabling keyboard indicator to change
  keyboard back to normal.

  1. Install ubiquity on a desktop or boot from an ISO
    $ sudo apt-get install ubiquity-frontend-gtk
  2. If you run on a desktop start ubiquity with:
    $ ubiquity --greeter
  3. Scroll to the bottom of the language list, click on 5th or 4th from the 
bottom

  ACTUAL RESULT
  python3 segmentation fault:
  *** Error in `/usr/bin/python3': malloc(): memory corruption: 
0x03b33d80 ***
  Segmentation fault (core dumped)

  EXPECTED RESULT
  No crash

  [ QA ]

  Check that the test case doesn't crash after applying the SRU

  [ Original Report ]

  I was testing a daily imagine of Ubuntu Gnome 14.04 (Live Image test),
  and was just checking out the languages on the initial boot up. When i
  was trying to click on the 4th language from the bottom ubiquitity
  crashed to give me this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.17.10
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.339
  Date: Mon Apr  7 00:06:38 2014
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  InterpreterPath: /usr/bin/python3.4
  LiveMediaBuild: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f3d8a71dd71 <_int_malloc+689>:  mov
%r14,0x10(%r9)
   PC (0x7f3d8a71dd71) ok
   source "%r14" ok
   destination "0x10(%r9)" (0x18001210) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ubiquity
  StacktraceTop:
   _int_malloc (av=0x7f3d8aa5c760 , bytes=1824) at malloc.c:3489
   __GI___libc_malloc (bytes=1824) at malloc.c:2891
   ?? () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3
   gr_make_font_with_ops () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3
   gr_make_font_with_advance_fn () from 
/usr/lib/x86_64-linux-gnu/libgraphite2.so.3
  Title: ubiquity crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartUbiquity: debconf: DbDriver "templatedb": 
/var/cache/debconf/templates.dat is locked by another process: Resource 
temporarily unavailable
  UserGroups:

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

2014-07-21 Thread Freedesktop

We believe this is fixed now.  Please test.

*** This bug has been marked as a duplicate of bug 75076 ***

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

Title:
  ubiquity crashed with SIGSEGV in _int_malloc()

Status in HarfBuzz:
  Invalid
Status in “graphite2” package in Ubuntu:
  Invalid
Status in “harfbuzz” package in Ubuntu:
  Triaged
Status in “graphite2” source package in Trusty:
  Invalid
Status in “harfbuzz” source package in Trusty:
  In Progress

Bug description:
  [ Description ]

  Memory corruption when rendering Myanmar text leeds to a crash

  [ Test case ]

  IMPORTANT NOTE: below will modify currently running locale/keyboard be
  prepared to restore it, e.g. by enabling keyboard indicator to change
  keyboard back to normal.

  1. Install ubiquity on a desktop or boot from an ISO
    $ sudo apt-get install ubiquity-frontend-gtk
  2. If you run on a desktop start ubiquity with:
    $ ubiquity --greeter
  3. Scroll to the bottom of the language list, click on 5th or 4th from the 
bottom

  ACTUAL RESULT
  python3 segmentation fault:
  *** Error in `/usr/bin/python3': malloc(): memory corruption: 
0x03b33d80 ***
  Segmentation fault (core dumped)

  EXPECTED RESULT
  No crash

  [ QA ]

  Check that the test case doesn't crash after applying the SRU

  [ Original Report ]

  I was testing a daily imagine of Ubuntu Gnome 14.04 (Live Image test),
  and was just checking out the languages on the initial boot up. When i
  was trying to click on the 4th language from the bottom ubiquitity
  crashed to give me this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.17.10
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.339
  Date: Mon Apr  7 00:06:38 2014
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  InterpreterPath: /usr/bin/python3.4
  LiveMediaBuild: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f3d8a71dd71 <_int_malloc+689>:  mov
%r14,0x10(%r9)
   PC (0x7f3d8a71dd71) ok
   source "%r14" ok
   destination "0x10(%r9)" (0x18001210) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ubiquity
  StacktraceTop:
   _int_malloc (av=0x7f3d8aa5c760 , bytes=1824) at malloc.c:3489
   __GI___libc_malloc (bytes=1824) at malloc.c:2891
   ?? () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3
   gr_make_font_with_ops () from /usr/lib/x86_64-linux-gnu/libgraphite2.so.3
   gr_make_font_with_advance_fn () from 
/usr/lib/x86_64-linux-gnu/libgraphite2.so.3
  Title: ubiquity crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartUbiquity: debconf: DbDriver "templatedb": 
/var/cache/debconf/templates.dat is locked by another process: Resource 
temporarily unavailable
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/harfbuzz/+bug/1303516/+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 1346455] [NEW] Launcher overlaps desktop icons on high-res screens

2014-07-21 Thread Lars Nyström

Public bug reported:

When using the scaling factor for Unity in Ubuntu 14.04 the desktop
icons to the left of the screen are partially covered by the launcher.

I'm attaching a screenshot of the issue when using a scaling factor of
2.0. The icons have been placed there using the "Organize desktop by
name" function.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.1+14.04.20140513-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Är en katalog: 
'/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.2
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Jul 21 20:44:02 2014
DistUpgraded: 2014-04-21 16:21:56,686 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GeForce GT 650M [1043:2141]
InstallationDate: Installed on 2013-10-18 (275 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: ASUSTeK COMPUTER INC. UX51VZH
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=19e47641-ad38-44f7-a159-ce49728e097d ro persistent quiet splash 
elevator=deadline pcie_aspm=force i915.semaphores=1
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-21 (91 days ago)
dmi.bios.date: 03/06/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX51VZH.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX51VZH
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.:bvrUX51VZH.206:bd03/06/2013:svnASUSTeKCOMPUTERINC.:pnUX51VZH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX51VZH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX51VZH
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
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.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Jul 21 19:33:55 2014
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2

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


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

** Attachment added: "launcher_overlap.png"
   
https://bugs.launchpad.net/bugs/1346455/+attachment/4159337/+files/launcher_overlap.png

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

Title:
  Launcher overlaps desktop icons on high-res screens

Status in “unity” package in Ubuntu:
  New

Bug description:
  When using the scaling factor for Unity in Ubuntu 14.04 the desktop
  icons to the left of the screen are partially covered by the launcher.

  I'm attaching a screenshot of the issue when using a scaling factor of
  2.0. The icons have been placed there using the "Organize desktop by
  name" function.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Är en katalog: 
'/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

[Touch-packages] [Bug 1305175] Re: openssl 1.0.1f 'ssl handshake failure' connection failure

2014-07-21 Thread Seth Arnold

Richard, it would be best to open a new bug if you're still experiencing
this issue. Thanks!

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

Title:
  openssl 1.0.1f 'ssl handshake failure' connection failure

Status in “openssl” package in Ubuntu:
  Confirmed

Bug description:
  When attempting 'curl' or 'openssl s_client' I have been getting
  "error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake
  failure"

  openssl version
  OpenSSL 1.0.1f 6 Jan 2014

  examples:

  ```Normal connect
  # openssl s_client -connect centinel1000.cardinalcommerce.com:443 -showcerts
  CONNECTED(0003)
  140148901013152:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake 
failure:s23_lib.c:177:
  ---
  no peer certificate available
  ---
  No client certificate CA names sent
  ---
  SSL handshake has read 0 bytes and written 317 bytes
  ---
  New, (NONE), Cipher is (NONE)
  Secure Renegotiation IS NOT supported
  Compression: NONE
  Expansion: NONE
  ---

  
  ```Explicit SSLv3
  # openssl s_client -connect centinel1000.cardinalcommerce.com:443 -showcerts 
-ssl3
  CONNECTED(0003)
  depth=2 C = US, O = "thawte, Inc.", OU = Certification Services Division, OU 
= "(c) 2006 thawte, Inc. - For authorized use only", CN = thawte Primary Root CA
  verify error:num=20:unable to get local issuer certificate
  verify return:0
  ---
  Certificate chain
   0 s:/C=US/ST=Ohio/L=Mentor/O=CardinalCommerce 
Corporation/CN=*.cardinalcommerce.com
 i:/C=US/O=Thawte, Inc./CN=Thawte SSL CA
  -BEGIN CERTIFICATE-
  MIIEqjCCA5KgAwIBAgIQfI2U+db8heb8kd3m/BmmITANBgkqhkiG9w0BAQUFADA8
  MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMVGhhd3RlLCBJbmMuMRYwFAYDVQQDEw1U
  aGF3dGUgU1NMIENBMB4XDTEzMDMxOTAwMDAwMFoXDTE1MDQxODIzNTk1OVowdTEL
  MAkGA1UEBhMCVVMxDTALBgNVBAgTBE9oaW8xDzANBgNVBAcUBk1lbnRvcjElMCMG
  A1UEChQcQ2FyZGluYWxDb21tZXJjZSBDb3Jwb3JhdGlvbjEfMB0GA1UEAxQWKi5j
  YXJkaW5hbGNvbW1lcmNlLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
  ggEBAMUnIwZ0yEJa80hN4sta/wbr04ogq9XwlY7V7iWiLlfoP/wfpccPt/282+AN
  oySwuxMWE5EPHC54WXjCowoj3Kdq7fuH11R6DBoXGfuhIJ9l9L187hEPPk6bLq3H
  F1diHFxGYT0zCNshm7w7Qe/LmQ8N0WSUs21KuB/WZxEts7sIYi4xY/Ig1Mbt6dVV
  z3w3mfSqpXmdZa5ht7/QUEy3/04uGlSXAN01BVmxHbZeM5epocUCt/TwhtUzRb+N
  9S4VEe3kzP8Oz8Wphg1CueP5yH9nRQTzLct5wCBC5+N+RjdadhuRm4FPgbsO+sX4
  LHQ1jgE6CTqYquyYAeXuvdOqz6kCAwEAAaOCAW0wggFpMCEGA1UdEQQaMBiCFiou
  Y2FyZGluYWxjb21tZXJjZS5jb20wCQYDVR0TBAIwADBCBgNVHSAEOzA5MDcGCmCG
  SAGG+EUBBzYwKTAnBggrBgEFBQcCARYbaHR0cHM6Ly93d3cudGhhd3RlLmNvbS9j
  cHMvMA4GA1UdDwEB/wQEAwIFoDAfBgNVHSMEGDAWgBSnooO7NEVAPfzVME8SuT6h
  AZ/22zA6BgNVHR8EMzAxMC+gLaArhilodHRwOi8vc3ZyLW92LWNybC50aGF3dGUu
  Y29tL1RoYXd0ZU9WLmNybDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIw
  aQYIKwYBBQUHAQEEXTBbMCIGCCsGAQUFBzABhhZodHRwOi8vb2NzcC50aGF3dGUu
  Y29tMDUGCCsGAQUFBzAChilodHRwOi8vc3ZyLW92LWFpYS50aGF3dGUuY29tL1Ro
  YXd0ZU9WLmNlcjANBgkqhkiG9w0BAQUFAAOCAQEAQKaqABf0+hz+MkHwn6HhnZ6T
  3D7u3a3ePrQQgtZWFo+7A5s0C+UA6SBRcvEZDRP7TMZaU+Ft+stglyby33b3koTQ
  2X1F484ncBJGyiOBk0M/KQHIsQGUmeXKNLfZlqXhicbT2nq7SktybPR0rsPJoiqN
  gR8pNlHseb1aHM79NcV9IbpW8B71fEMFQRd7sUvmxGizqOneG4nGXCk04CRRy5H3
  raU6Xb2CRi5UdjsJPWjLjLDQZBF5aA0IgOZDi7BghU9cy+P4t2PdBBvPP0ctWI3O
  LYMF6figGyaw3kCLi4epJ0ZA4ayg8R7KrDNGA7oWI2roknlJd0YEDE3z0Fg2JA==
  -END CERTIFICATE-
   1 s:/C=US/O=Thawte, Inc./CN=Thawte SSL CA
 i:/C=US/O=thawte, Inc./OU=Certification Services Division/OU=(c) 2006 
thawte, Inc. - For authorized use only/CN=thawte Primary Root CA
  -BEGIN CERTIFICATE-
  MIIEbDCCA1SgAwIBAgIQTV8sNAiyTCDNbVB+JE3J7DANBgkqhkiG9w0BAQUFADCB
  qTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDHRoYXd0ZSwgSW5jLjEoMCYGA1UECxMf
  Q2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjE4MDYGA1UECxMvKGMpIDIw
  MDYgdGhhd3RlLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxHzAdBgNV
  BAMTFnRoYXd0ZSBQcmltYXJ5IFJvb3QgQ0EwHhcNMTAwMjA4MDAwMDAwWhcNMjAw
  MjA3MjM1OTU5WjA8MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMVGhhd3RlLCBJbmMu
  MRYwFAYDVQQDEw1UaGF3dGUgU1NMIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
  MIIBCgKCAQEAmeSFW3ZJfS8F2MWsyMip09yY5tc0pi8M8iIm2KPJFEyPBaRF6BQM
  WJAFGrfFwQalgK+7HUlrUjSIw1nn72vEJ0GMK2Yd0OCjl5gZNEtB1ZjVxwWtouTX
  7QytT8G1sCH9PlBTssSQ0NQwZ2ya8Q50xMLciuiX/8mSrgGKVgqYMrAAI+yQGmDD
  7bs6yw9jnw1EyVLhJZa/7VCViX9WFLG3YR0cB4w6LPf/gN45RdWvGtF42MdxaqMZ
  pzJQIenyDqHGEwNESNFmqFJX1xG0k4vlmZ9d53hR5U32t1m0drUJN00GOBN6HAiY
  XMRISstSoKn4sZ2Oe3mwIC88lqgRYke7EQIDAQABo4H7MIH4MDIGCCsGAQUFBwEB
  BCYwJDAiBggrBgEFBQcwAYYWaHR0cDovL29jc3AudGhhd3RlLmNvbTASBgNVHRMB
  Af8ECDAGAQH/AgEAMDQGA1UdHwQtMCswKaAnoCWGI2h0dHA6Ly9jcmwudGhhd3Rl
  LmNvbS9UaGF3dGVQQ0EuY3JsMA4GA1UdDwEB/wQEAwIBBjAoBgNVHREEITAfpB0w
  GzEZMBcGA1UEAxMQVmVyaVNpZ25NUEtJLTItOTAdBgNVHQ4EFgQUp6KDuzRFQD38
  1TBPErk+oQGf9tswHwYDVR0jBBgwFoAUe1tFz6/Oy3r9MZIaarbzRutXSFAwDQYJ
  KoZIhvcNAQEFBQADggEBAIAigOBsyJUW11cmh/NyNNvGclYnPtOW9i4lkaU+M5en
  S+Uv+yV9Lwdh+m+DdExMU3IgpHrPUVFWgYiwbR82LMgrsYiZwf5Eq0hRfNjyRGQq
  2HGn+xov+RmNNLIjv8RMVR2OROiqXZrdn/0Dx7okQ40tR0Tb9tiYyLL52u/tKVxp
  EvrRI5YPv

[Touch-packages] [Bug 1345847] Re: Impossible to disable IPv6 auto, params "accept_ra & autoconf = 0" have no effect on VLAN interfaces

2014-07-21 Thread Seth Arnold

** Information type changed from Private Security to Public

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

Title:
  Impossible to disable IPv6 auto, params "accept_ra & autoconf = 0"
  have no effect on VLAN interfaces

Status in “ifupdown” package in Ubuntu:
  New

Bug description:
  Guys,

  I'm trying to disable IPv6 autoconf (and accept_ra too) in one of my
  servers (Samba4 AC DC) and I am unable to disable it. IPv6 keep
  appearing no matter what.

  Steps to reproduce:

  1- Join a Network with a working IPv6 radvd within a tagged VLAN 10,
  for example:

  * Router Ubuntu with:

  --
  interface vlan10 {
  AdvSendAdvert on;
  MinRtrAdvInterval 5;
  MaxRtrAdvInterval 20;
  AdvLinkMTU 1500;
  AdvDefaultPreference high;
  prefix 2001:db8:1:10::/64 {
  DeprecatePrefix on;
  AdvOnLink on;
  AdvAutonomous on;
  AdvRouterAddr on;
  };
  route ::/0 {
  RemoveRoute on;
  };
  RDNSS 2001:4860:4860::8844 2001:4860:4860:: { };
  DNSSL domain.com.br { };
  };
  --

   Of course, for example, vlan10 on Ubuntu router have IPv6 addr =
  2001:db8:1:10::1/64, so radvd can work. Also, vlan10 of router have
  IPv4 172.16.0.1/24 (it is a dual-stacked router).

  -

  2- Configure your Ubuntu 14.04 server interfaces like this:

  --
  auto vlan10
  iface vlan10 inet static
vlan_raw_device eth0
accept_ra 0
autoconf 0
address 172.16.0.10
netmask 24
gateway 172.16.0.1
dns-nameservers 172.16.0.1
  --

  3- Turn it up:

  --
  ifup vlan10

  * Here is the BUG, IPv6 appear anyway! But it should not!

  -
  root@ubuntu-srv-1:~# ip -6 r
  2001:db8:1:10::/64 dev vlan10  proto kernel  metric 256  expires 86389sec
  fe80::/64 dev eth0  proto kernel  metric 256 
  fe80::/64 dev vlan10  proto kernel  metric 256 
  default via fe80::5054:ff:feae:1407 dev vlan10  proto ra  metric 1024  
expires 49sec
  -

   This is undesired and a security breach. It facilitates MITM IPv6
  attacks for tagged vlans.

  --

   As a workaround, I'm adding the following lines at my /etc/rc.local
  (of ubuntu-srv-1):

  --
  # Workaroung against IPv6 autoconf & accept_ra
  sysctl -p
  ifconfig vlan10 down ; ifconfig vlan10 up
  --

  Where "sysctl -p" returns:

  --
  root@ubuntu-srv-1:~# sysctl -p
  net.ipv6.conf.all.accept_ra = 0
  net.ipv6.conf.all.autoconf = 0
  net.ipv6.conf.eth0.accept_ra = 0
  net.ipv6.conf.eth0.autoconf = 0
  net.ipv6.conf.vlan10.accept_ra = 0
  net.ipv6.conf.vlan10.autoconf = 0
  --

  This workaround is the only way I'm seeing to completely disable IPv6
  for this server (ubuntu-srv-1).

  Best,
  Thiago

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1345847/+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 1224099] Re: [Satellite P200, Realtek ALC268, Black Headphone Out, Front] No sound at all

2014-07-21 Thread arturo

I had this problem and i fix it. Adding this line to file alsa-base.conf:
options snd-hda-intel model=inv-dmic
I add this line after the last line install.
I hope this help u

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

Title:
  [Satellite P200, Realtek ALC268, Black Headphone Out, Front] No sound
  at all

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  front headphones work perfect in ubuntu 12.04 LTS. after a fresh
  instllation of 13.04 - no sound comming out of headphones only front
  speakers are working.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ilan   4270 F pulseaudio
ilan   6673 F pulseaudio
   /dev/snd/controlC0:  ilan   4270 F pulseaudio
ilan   6673 F pulseaudio
  Date: Wed Sep 11 23:12:43 2013
  InstallationDate: Installed on 2013-09-11 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ilan   4270 F pulseaudio
ilan   6673 F pulseaudio
   /dev/snd/controlC0:  ilan   4270 F pulseaudio
ilan   6673 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Satellite P200, Realtek ALC268, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  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:pnSatelliteP200:pvrPSPB6E-10M04NEN:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite P200
  dmi.product.version: PSPB6E-10M04NEN
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1224099/+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 1213485] Re: [Satellite P200, Realtek ALC268] No headphone output

2014-07-21 Thread arturo

I had this problem and i fix it.  Adding this line to file alsa-base.conf:
options snd-hda-intel model=inv-dmic
I add this line after the last line install.
I hope this help u

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

Title:
  [Satellite P200, Realtek ALC268] No headphone output

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  My sound card is wong detected. I have one Intel HD Audio Controller on my 
laptop as i see on lspci -a
  Please i need infos on how to tell to linux to use one correct driver for 
this card.

  As result of that i have no headfone output.

  Above the result of lspci -a relatet to the card.
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pulseaudio 1:3.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ricardo1906 F pulseaudio
   /dev/snd/controlC0:  ricardo1906 F pulseaudio
  Date: Sat Aug 17 20:51:02 2013
  InstallationDate: Installed on 2013-08-14 (3 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V2.50
  dmi.board.name: ISRAA
  dmi.board.vendor: XX
  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:bvrV2.50:bd06/11/2008:svnXX:pnSatelliteP200:pvrPSPB6E-01P015SP:rvnXX:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite P200
  dmi.product.version: PSPB6E-01P015SP
  dmi.sys.vendor: XX

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1213485/+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 1345600] Re: Sudo hangs after resume

2014-07-21 Thread Seth Arnold

Stracing a setuid program changes its behaviour; in this case, sudo
doesn't run with effective uid 0, so it exits with an error message very
early in execution. You might as well delete the strace log, anyone else
can get an identical one with "strace sudo ls" (for example).

How can someone else reproduce what you've seen here? Please set the
status back to 'New' once you've replied.

Thanks

** Changed in: sudo (Ubuntu)
   Status: New => Incomplete

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

Title:
  Sudo hangs after resume

Status in “sudo” package in Ubuntu:
  Incomplete

Bug description:
  After resuming from a suspend, sudo hangs: doesn't prompt for
  password, doesn't give an error, does absolutely nothing. The entire
  terminal is blocked and Ctrl C does nothing.

  Attached strace.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1345600/+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 1346443] [NEW] System will only start or reboot from the installation disk.

2014-07-21 Thread Richard Hanson

Public bug reported:

When I try to boot/reboot the machine I get "Reboot and select proper
Boot device or insert boot media in selected Boot device and press any
key." The only way I can reboot the machine is to boot from the
installation disk and select "Boot from 1st Hard Drive" option.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.117  Tue Nov 26 21:25:36 
PST 2013
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jul 21 11:22:25 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 nvidia-304, 304.117, 3.13.0-24-generic, x86_64: installed
 nvidia-304, 304.117, 3.13.0-27-generic, x86_64: installed
 nvidia-304, 304.117, 3.13.0-29-generic, x86_64: installed
 nvidia-304, 304.117, 3.13.0-30-generic, x86_64: installed
 nvidia-304, 304.117, 3.13.0-32-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 NVIDIA Corporation C77 [GeForce 8100 / nForce 720a] [10de:084f] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Biostar Microtech Int'l Corp Device [1565:1408]
InstallationDate: Installed on 2014-06-02 (49 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: BIOSTAR Group TF720 A2+
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=72d52047-b8ae-4417-9111-4c6c2a36df2a ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: TF720 A2+
dmi.board.vendor: BIOSTAR Group
dmi.board.version: 6.x
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: 6.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/18/2008:svnBIOSTARGroup:pnTF720A2+:pvr6.x:rvnBIOSTARGroup:rnTF720A2+:rvr6.x:cvnBIOSTARGroup:ct3:cvr6.x:
dmi.product.name: TF720 A2+
dmi.product.version: 6.x
dmi.sys.vendor: BIOSTAR Group
version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
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.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Jul 21 10:49:26 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputLogitech Unifying Device. Wireless PID:401b MOUSE, id 9
 inputLogitech Unifying Device. Wireless PID:4016 KEYBOARD, id 10
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-bug 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/1346443

Title:
  System will only start or reboot from the installation disk.

Status in “xorg” package in Ubuntu:
  New

Bug description:
  When I try to boot/reboot the machine I get "Reboot and select proper
  Boot device or insert boot media in selected Boot device and press any
  key." The only way I can reboot the machine is to boot from the
  installation disk and select "Boot from 1st Hard Drive" option.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc

[Touch-packages] [Bug 1346441] [NEW] Bluetooth doesn't transfer audio on reconnects

2014-07-21 Thread Dave Morley

Public bug reported:

STEPS:
1. Turn on your bluetooth speaker
2. Open the settings app
3. Open the bluetooth section
4. Wait for the scan to pick the speaker
5. Connect to it
6. Play some music
7. Note music plays through the speaker as expected.
8. Reboot the phone
9. On a sucessful reconnect to the speaker play some music again
10. This time it plays through the Loud Speaker on the phone.
11. Open settings app
12. Goto bluetooth
13. Disconnect from the speaker and then reconnect
14. Now play the music
15. now it plays through the speaker once more.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: bluez 4.101-0ubuntu17
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.4-0ubuntu2
Architecture: armhf
Date: Mon Jul 21 19:18:27 2014
InstallationDate: Installed on 2014-07-21 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140721-020205)
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
ProcKernelCmdLine: console=ttyHSL0,115200,n8 androidboot.hardware=mako 
lpj=67677 user_debug=31 uart_console=enable lcd_maker_id=primary lge.hreset=off 
lge.reset=mode_reset gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 
androidboot.emmc=true androidboot.serialno=01c7d0fad74c8ee3 
androidboot.bootloader=MAKOZ30d androidboot.baseband=mdm bootreason=reboot
ProcModules:
 
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
hciconfig:
 hci0:  Type: BR/EDR  Bus: UNKNOWN
BD Address: 98:D6:F7:32:C5:59  ACL MTU: 1024:6  SCO MTU: 50:8
UP RUNNING PSCAN ISCAN 
RX bytes:0 acl:113 sco:0 events:25027 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
syslog: Jul 21 18:07:47 ubuntu-phablet bluetoothd[2456]: Discovery session 
0xb8093a60 with :1.72 activated

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


** Tags: apport-bug armhf utopic

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

Title:
  Bluetooth doesn't transfer audio on reconnects

Status in “bluez” package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Turn on your bluetooth speaker
  2. Open the settings app
  3. Open the bluetooth section
  4. Wait for the scan to pick the speaker
  5. Connect to it
  6. Play some music
  7. Note music plays through the speaker as expected.
  8. Reboot the phone
  9. On a sucessful reconnect to the speaker play some music again
  10. This time it plays through the Loud Speaker on the phone.
  11. Open settings app
  12. Goto bluetooth
  13. Disconnect from the speaker and then reconnect
  14. Now play the music
  15. now it plays through the speaker once more.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu17
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Mon Jul 21 19:18:27 2014
  InstallationDate: Installed on 2014-07-21 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140721-020205)
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  ProcKernelCmdLine: console=ttyHSL0,115200,n8 androidboot.hardware=mako 
lpj=67677 user_debug=31 uart_console=enable lcd_maker_id=primary lge.hreset=off 
lge.reset=mode_reset gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 
androidboot.emmc=true androidboot.serialno=01c7d0fad74c8ee3 
androidboot.bootloader=MAKOZ30d androidboot.baseband=mdm bootreason=reboot
  ProcModules:
   
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  hciconfig:
   hci0:Type: BR/EDR  Bus: UNKNOWN
BD Address: 98:D6:F7:32:C5:59  ACL MTU: 1024:6  SCO MTU: 50:8
UP RUNNING PSCAN ISCAN 
RX bytes:0 acl:113 sco:0 events:25027 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
  syslog: Jul 21 18:07:47 ubuntu-phablet bluetoothd[2456]: Discovery session 
0xb8093a60 with :1.72 activated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1346441/+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 1283775] Re: Launcher: icon pips are not always updated properly

2014-07-21 Thread Jorge Morais

Unity version from trusty-proposed fixes this issue.  I have tested it
for several days and did not notice and regression.

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

Title:
  Launcher: icon pips are not always updated properly

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

Bug description:
  [Impact]

  The number of pips next to the Launcher icon may not be accurate and
  lead the user to believe that the number of open windows for a
  particular app is not what is true in reality.

  [Test Case]

  1. Open up 2 Firefox windows.
  2. Close one of the windows.

  Pips (the little arrows) next to the Launcher icon should reflect the
  number of open windows.

  [Regression potential]

  None identified.

  Original Description:

  Only occurs when there is just 1 app's windows (unmaxed),  assumes multiple 
workspaces is enabled
  Test case:
  Open nautilus (1 pip shows up
  R. click nautilus icon > open another nautilus window (a 2nd pip does not 
show, likely due to Bug 1281816
  Drag the 2nd naut window fully into current ws, 2nd pip still not shown
  Click on Desktop, 2nd pip shows up

  Close one of the naut windows, icon still shows 2 pips.
  Click again on Desktop, 2nd pip is then removed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Feb 23 12:28:18 2014
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1283775/+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 1011647] Re: Unity Alt+F2 "Run a command" does not run anything

This bug affects me too, it seems as though "Run command" instead of
interpreting the input with a shell, tries to interpret the command
itself and find a matching previous command or a desktop launcher. I
know what I just said is not accurate, but what is accurate is that in
my end (and in lealcy's, I suppose), "Run command" doesn't behave as
expected.

** Tags added: apport-collected 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/1011647

Title:
  Unity Alt+F2 "Run a command" does not run anything

Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity-lens-applications” package in Ubuntu:
  Confirmed

Bug description:
  I press ALT-F2, type some command like gedit or gnome-system-monitor,
  press ENTER and nothing happens. I'm using Ubuntu 12.04 up to date. It
  shows like it is searching something but the search ends and nothing
  is showed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1011647/+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 1346435] [NEW] Cannot enter name for new folder, can't make folder

2014-07-21 Thread Roger Davis

Public bug reported:

I select "new folder", window appears, but cannot enter name in text box
to create new folder.

It seems that some users have this problem, some not.  XFE has no
variants, so I'm guessing the problem arises within Ubuntu and
variations in Ubuntu setup.

Please see
http://ubuntuforums.org/showthread.php?t=2235440&p=13078735#post13078735

Ubuntu 14.04, Gnome Flashback Metacity, XFE 1.37

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: Unity
Date: Mon Jul 21 11:05:55 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750 / R7 
250E] [1002:683f] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e213]
InstallationDate: Installed on 2014-07-07 (14 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
dmi.board.name: DZ77BH-55K
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39008-400
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Jul 21 10:27:47 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech Unifying Device. Wireless PID:101b MOUSE, id 8
 inputLogitech Unifying Device. Wireless PID:200a KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug 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/1346435

Title:
  Cannot enter name for new folder, can't make folder

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I select "new folder", window appears, but cannot enter name in text
  box to create new folder.

  It seems that some users have this problem, some not.  XFE has no
  variants, so I'm guessing the problem arises within Ubuntu and
  variations in Ubuntu setup.

  Please see
  http://ubuntuforums.org/showthread.php?t=2235440&p=13078735#post13078735

  Ubuntu 14.04, Gnome Flashback Metacity, XFE 1.37

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Mon Jul 21 11:05:55 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750 / R7 
250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e213]
  InstallationDate: Installed on 2014-07-07 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeS

[Touch-packages] [Bug 1011647] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1011647/+attachment/4159287/+files/ProcEnviron.txt

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

Title:
  Unity Alt+F2 "Run a command" does not run anything

Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity-lens-applications” package in Ubuntu:
  Confirmed

Bug description:
  I press ALT-F2, type some command like gedit or gnome-system-monitor,
  press ENTER and nothing happens. I'm using Ubuntu 12.04 up to date. It
  shows like it is searching something but the search ends and nothing
  is showed.

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

ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2013-09-29 (295 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424)
NonfreeKernelModules: nvidia wl
Package: unity-lens-applications
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Tags:  trusty
Uname: Linux 3.13.0-32-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-04-19 (93 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

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

Title:
  Unity Alt+F2 "Run a command" does not run anything

Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity-lens-applications” package in Ubuntu:
  Confirmed

Bug description:
  I press ALT-F2, type some command like gedit or gnome-system-monitor,
  press ENTER and nothing happens. I'm using Ubuntu 12.04 up to date. It
  shows like it is searching something but the search ends and nothing
  is showed.

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

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1011647/+attachment/4159285/+files/Dependencies.txt

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

Title:
  Unity Alt+F2 "Run a command" does not run anything

Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity-lens-applications” package in Ubuntu:
  Confirmed

Bug description:
  I press ALT-F2, type some command like gedit or gnome-system-monitor,
  press ENTER and nothing happens. I'm using Ubuntu 12.04 up to date. It
  shows like it is searching something but the search ends and nothing
  is showed.

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