[Touch-packages] [Bug 1450947] Re: [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys have no effect

2015-05-01 Thread Raymond
** Summary changed:

- [HDA-Intel - HDA Intel, playback] volume slider problem
+ [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys have 
no effect

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

Title:
  [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys
  have no effect

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since upgrade to 15.04 from 14.10, the physical volume keys (mute, up,
  down) on my ThinkPad X60 have no effect. I can adjust the volume via
  the menubar indicator, but the buttons are dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   andrew 2071 F...m pulseaudio
   /dev/snd/controlC0:  andrew 2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri May  1 19:05:06 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-12 (535 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Type: Volume slider, or mixer problems
  Title: [HDA-Intel - HDA Intel, playback] volume slider problem
  UpgradeStatus: Upgraded to vivid on 2015-05-01 (0 days ago)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BETD7WW (2.18 )
  dmi.board.name: 170686U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BETD7WW(2.18):bd11/20/2008:svnLENOVO:pn170686U:pvrThinkPadX60:rvnLENOVO:rn170686U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 170686U
  dmi.product.version: ThinkPad X60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450947/+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 1365362] Re: 10de:1080 [Intel DP67DE] Xorg Backtracing

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  10de:1080 [Intel DP67DE] Xorg Backtracing

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I notice in a backtrace in my
  https://launchpadlibrarian.net/184002264/XorgLog.txt .

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Sep  4 10:16:56 2014
  DistUpgraded: 2014-05-28 10:18:54,825 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2550]
  InstallationDate: Installed on 2013-02-27 (553 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=c07436f0-fb64-48d1-a92d-cc2a58369813 ro quiet splash rootdelay=20
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-05-28 (98 days ago)
  dmi.bios.date: 11/16/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BAP6710H.86A.0037.2010.1116.2134
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DP67DE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10217-204
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBAP6710H.86A.0037.2010.1116.2134:bd11/16/2010:svn:pn:pvr:rvnIntelCorporation:rnDP67DE:rvrAAG10217-204:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-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 N/A
  xserver.bootTime: Thu Sep  4 09:24:27 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1365362/+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 1296545] Re: appearance affected

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  appearance affected

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Sometimes can't change style and icons when desktop environment is
  switched to ubuntustudio.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Mar 24 08:17:08 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: dahdi, 2.5.0.1+dfsg-1ubuntu3, 3.11.0-19-generic, i686: installed 
(WARNING! Diff between built and installed module!)
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Mobile 945GSE Express Integrated Graphics 
Controller [8086:27ae]
 Subsystem: Intel Corporation Device [8086:27ae]
  InstallationDate: Installed on 2014-03-14 (9 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: MAGUAY eXpertBOOK 10G.02
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-generic 
root=UUID=9EF0F3A8F0F384B5 loop=/hostname/disks/root.disk ro rootflags=sync 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.name: eXpertBOOK 10G.02
  dmi.board.vendor: MAGUAY
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/18/2009:svnMAGUAY:pneXpertBOOK10G.02:pvr:rvnMAGUAY:rneXpertBOOK10G.02:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: eXpertBOOK 10G.02
  dmi.sys.vendor: MAGUAY
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Mar 24 07:56:03 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12498 
   vendor AUO
  xserver.version: 2:1.14.5-1ubuntu2~saucy1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1296545/+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 949958] Re: Full screen video corruption on nvidia betwen lightdm and desktop

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Full screen video corruption on nvidia betwen lightdm and desktop

Status in xorg package in Ubuntu:
  Expired

Bug description:
  On a clean install of Ubuntu 12.04 with the nVidia binary driver I get
  a nice checkerboard pattern.

  http://www.youtube.com/watch?v=abw1U9JdnzY

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+10ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-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  295.20  Mon Feb  6 21:07:30 
PST 2012
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu2)
  .tmp.unity.support.test.0:

  ApportVersion: 1.94-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  CurrentDmesg: [   35.088005] eth1: no IPv6 routers present
  Date: Thu Mar  8 13:59:02 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current, 295.20, 3.2.0-16-generic, x86_64: installed
   nvidia-current, 295.20, 3.2.0-18-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Giga-byte Technology Device [1458:34fc]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120215)
  JockeyStatus:
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Enabled, In use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
  MachineType: System manufacturer System Product Name
  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.2.0-18-generic 
root=UUID=2438b8df-efe6-4e65-946e-7eb9437990ec ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section Device
    Identifier  Default Device
    Option  NoLogoTrue
   EndSection
  dmi.bios.date: 04/24/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N32-E SLI ACPI BIOS Revision 1801
  dmi.board.name: P5N32-E SLI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N32-ESLIACPIBIOSRevision1801:bd04/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N32-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.6.99.901+git20120126-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/949958/+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 1231834] Re: USB Mouse clicks are unreliable (missed clicks, accidental double clicks)

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  USB Mouse clicks are unreliable (missed clicks, accidental double
  clicks)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Since I updated from 10.04 LTS to 12.04 LTS my USB mouse has been
  behaving strangely: clicks are often not recognized properly.

  The most frequent problem is that clicks are not recognized at all. I
  have to click two or three times before a click get recognized. After
  that, the next three or four clicks are recognized without problems.
  Another problem is that simple clicks are misunderstood for double
  clicks.

  This happens with a Logitech USB mouse and other USB mice. All these
  mice are properly working, as I tested them on other computers.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20
  Uname: Linux 3.5.0-40-generic i686
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  Date: Fri Sep 27 09:13:45 2013
  DistUpgraded: 2013-05-25 01:41:11,103 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 10.04.2 LTS Lucid Lynx - Release i386 (20110211.1)
  MachineType: To Be Filled By O.E.M. MS-7276
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-40-generic 
root=UUID=713376ab-3ede-44a9-9d52-87292eb7b2ff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to precise on 2013-05-24 (125 days ago)
  dmi.bios.date: 101507
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.5
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7276
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.5:bd101507:svnToBeFilledByO.E.M.:pnMS-7276:pvr1.0:rvnMSI:rnMS-7276:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7276
  dmi.product.version: 1.0
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.7.12-0ubuntu2
  version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1231834/+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 975175] Re: 1366x768 over VGA generic problems

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  1366x768 over VGA generic problems

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I'm filing this as hopefully a generic/master bug (if any one knows of
  another please add).

  I've got two entirely distinct set ups that won't do the 1366x768 that the 
monitor/display is capable of over VGA;
  I suspect this is related to the discussion here:

  http://mjg59.dreamwidth.org/8705.html

  which describes how EDID can't represent 1366 pixels wide.

  The two setups I have are:
11.10 with a modern Intel graphics integrated VGA (on chip) to a Panasonic 
TV via VGA, it's native res is 1366x768 
12.04 with an ancient Geforce 2 (NV11) to a new Samsung B1930N monitor, 
again native res of 1366x768 (with Nouveau drivers)

  I think the best the 11.10 managed with the panasonic was 800x600 out
  of the box, and the best that 12.04 managed with the Samsung was
  1024x768.  In both cases there are no options in the Gnome display
  settings to get it closer.

  Unfortunately the work around is non-trivial; you have to add a modeline with 
xrandr - and I've not managed to find a modeline
  that works for both; so it's a lot of fiddling.

  Given 1366x768 displays aren't uncommon I think there needs to be
  something to help people with this; I'm not sure what the right answer
  is though!

  There are a whole chunk of bugs with notebooks with this resolution on
  internal displays - and I'm not sure if that's the same or a separate
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/975175/+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 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

2015-05-01 Thread Seth Arnold
Better explained here:
https://www.agwa.name/blog/post/beware_the_ipv6_dad_race_condition

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1447715/+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 1241101]

2015-05-01 Thread MiXiM
-- 
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/1241101

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1389215] Re: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver.

2015-05-01 Thread Hans Deragon
** Changed in: xorg (Ubuntu)
   Status: Incomplete = New

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

Title:
  Brightness controls are not working in Unity / Xorg because of Nvidia
  proprietary driver.

Status in xorg package in Ubuntu:
  New

Bug description:
  Brightness controls are not working in Unity / Xorg.  When pressing
  the keys fnhome and fnend on my Lenovo W510, I see the
  indicator on the screen showing the level of brightness changing, so
  key mapping is not the problem.  However, the brightness is not
  changing.

  On the kernel level, I have the single following device:

  # cd /sys/class/backlight
  # ls -l
  total 0
  lrwxrwxrwx 1 root root 0 Nov  3 17:16 acpi_video0 - 
../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0

  When playing with the fnhome and fnend, the value of
  /sys/class/backlight/brightness changes accordingly.  The screen
  brightness does not change.

  Performing:

  # echo 10 brightness

  ...does not have any effect (regardless of the value provided, 10
  being just an example).

  WORKAROUND

  There is an odd workaround.  Simply go to the console using
  CTRLALTF1 and using the fnhome and fnend keys,
  brightness then changes.  Return to Unity / Xorg with CTRLALTF7
  and the selected brightness persists.

  NON WORKING WORKAROUND

  On the web, I read that adding:

  Option RegistryDwords EnableBrightnessControl=1'

  in xorg.conf might fix the problem.  I do not have an xorg and when I
  let the proprietary Nvidia driver generate one and add this option, X
  does not start anymore.

  Ubuntu 14.04.1 LTS with latest updates as of this writing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov  4 07:38:59 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed
   tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2145]
  InstallationDate: Installed on 2014-11-01 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: LENOVO 4318CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic 
root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4318CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4318CTO
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-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.1
  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
  

[Touch-packages] [Bug 1448371] Re: package udev 219-7ubuntu4 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2015-05-01 Thread freecode
Running sudo sed -i '1 s/$/x/' /var/lib/dpkg/info/udev.postinst produced
no output for me.

Running sudo dpkg-reconfigure udev produces the message:

/usr/sbin/dpkg-reconfigure: udev is broken or not fully installed


The one proposed answer on the forums did nothing to resolve the issue sadly.

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

Title:
  package udev 219-7ubuntu4 failed to install/upgrade: le sous-processus
  script post-installation installé a retourné une erreur de sortie
  d'état 1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  the upgrade from ubuntu 14.10 vas not completely failed ... I had errors but 
the install continued.
  after reboot the screen was locked. So I rebooted and lauched a previous 
version. Now I hav ubuntu 15.04 idicated but not fully installed. sudo apt-get 
upgrade generates too much errors.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: udev 219-7ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-36.48-generic 3.16.7-ckt9
  Uname: Linux 3.16.0-36-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CustomUdevRuleFiles: 99-jlink.rules 99-input.rules 85-lpcxpresso.rules 
z010_mchp_tools.rules README.dpkg-remove z011_mchp_jlink.rules 60-vboxdrv.rules
  Date: Sat Apr 25 06:27:23 2015
  DpkgTerminalLog:
   Paramétrage de udev (219-7ubuntu4) ...
   dpkg: erreur de traitement du paquet udev (--configure) :
le sous-processus script post-installation installé a retourné une erreur 
de sortie d'état 1
  DuplicateSignature: package:udev:219-7ubuntu4:le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2013-12-11 (499 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 20263
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-36-generic 
root=UUID=16c65adb-dc63-44e2-9d93-aea9224e0bab ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: systemd
  Title: package udev 219-7ubuntu4 failed to install/upgrade: le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 1
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BCN21WW(V1.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G500s Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BCN21WW(V1.05):bd04/18/2013:svnLENOVO:pn20263:pvrLenovoG500sTouch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG500sTouch:
  dmi.product.name: 20263
  dmi.product.version: Lenovo G500s Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448371/+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 1434557] UdevDb.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1434557/+attachment/4389448/+files/UdevDb.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: /usr/bin/X 

[Touch-packages] [Bug 1434557] XorgLog.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: XorgLog.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389450/+files/XorgLog.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: /usr/bin/X 

[Touch-packages] [Bug 1426957] Re: bug report

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  bug report

Status in xorg package in Ubuntu:
  Expired

Bug description:
  i am not sure

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Mar  1 20:12:53 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fb30]
  InstallationDate: Installed on 2015-02-19 (10 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA SATELLITE C850-13E
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=9968d647-a79a-4b0e-a835-58c3e89f74b6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.60:bd06/27/2012:svnTOSHIBA:pnSATELLITEC850-13E:pvrPSKC8E-052005EN:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE C850-13E
  dmi.product.version: PSKC8E-052005EN
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Mar  1 19:37:55 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12624 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1426957/+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 1426370] Re: Wrong keyboard layout after suspend

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Wrong keyboard layout after suspend

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I use several keyboards on my machine, with different layouts.

  After the machine wakes from a sleep it always comes back with the
  first configured layout instead of the one I was using before it went
  to sleep.

  This is an irritation, rather than a stopper.

  Description:  Ubuntu 12.04.5 LTS
  Release:  12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Fri Feb 27 13:26:25 2015
  DistUpgraded: 2014-09-11 22:33:29,890 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo ThinkPad T61p [17aa:20d9]
  InstallationDate: Installed on 2014-09-05 (174 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 6459CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=ea8d2b87-e06e-4df4-941a-7ca7dcab5c82 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-09-11 (168 days ago)
  dmi.bios.date: 05/11/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC6WW (2.26 )
  dmi.board.name: 6459CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn6459CTO:pvrThinkPadT61p:rvnLENOVO:rn6459CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 6459CTO
  dmi.product.version: ThinkPad T61p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Feb 26 13:28:28 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1426370/+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 1406166] Re: Kyocera FS-1320MFP printer not working

2015-05-01 Thread Launchpad Bug Tracker
[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/1406166

Title:
  Kyocera FS-1320MFP printer not working

Status in cups package in Ubuntu:
  Expired

Bug description:
  Bus 002 Device 008: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth 
Mini-card
  Bus 002 Device 007: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / 
Trackstick
  Bus 002 Device 006: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
  Bus 002 Device 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 002 Device 004: ID 187c:0512 Alienware Corporation 
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 0c45:6412 Microdia 
  Bus 001 Device 007: ID 0482:04fe Kyocera Corp. 
  Bus 001 Device 003: ID 045e:07b1 Microsoft Corp. 
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 29 13:35:28 2014
  InstallationDate: Installed on 2014-12-29 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  Lpstat: device for Kyocera_FS-1320MFP: 
usb://Kyocera/FS-1320MFP?serial=L782Y00647
  MachineType: Alienware M15x
  Papersize: a4
  PpdFiles: Kyocera_FS-1320MFP: Kyocera FS-1320D (KPDL)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=046942f9-06ef-4f8a-9ec0-5b57cce25108 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2010
  dmi.bios.vendor: Alienware
  dmi.bios.version: A08
  dmi.board.vendor: Alienware
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnAlienware:bvrA08:bd08/24/2010:svnAlienware:pnM15x:pvrA08:rvnAlienware:rn:rvrA08:cvnAlienware:ct8:cvrA08:
  dmi.product.name: M15x
  dmi.product.version: A08
  dmi.sys.vendor: Alienware
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-12-29 (1 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  Lpstat: device for Kyocera_FS-1320MFP: 
usb://Kyocera/FS-1320MFP?serial=L782Y00647
  MachineType: Alienware M15x
  Package: cups 1.7.5-3ubuntu2
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Kyocera_FS-1320MFP: Kyocera FS-1320D (KPDL)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=046942f9-06ef-4f8a-9ec0-5b57cce25108 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=046942f9-06ef-4f8a-9ec0-5b57cce25108 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2010
  dmi.bios.vendor: Alienware
  dmi.bios.version: A08
  dmi.board.vendor: Alienware
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnAlienware:bvrA08:bd08/24/2010:svnAlienware:pnM15x:pvrA08:rvnAlienware:rn:rvrA08:cvnAlienware:ct8:cvrA08:
  dmi.product.name: M15x
  dmi.product.version: A08
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1406166/+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 1450947] Re: [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys have no effect

2015-05-01 Thread Raymond
!!Module: thinkpad_acpi
brightness_enable : 2
brightness_mode : 4
dbg_bluetoothemul : 0
dbg_uwbemul : 0
dbg_wlswemul : 0
dbg_wwanemul : 0
enable : Y
experimental : 0
fan_control : N
force_load : N
id : ThinkPadEC
index : -536870912
software_mute : Y
volume_capabilities : 0
volume_control : N
volume_mode : 3


this mean bug in
volume_set_software_mute() since software_mute=Y and still have ec console

you have to file upstream ThinkPad acpi bug report

Soundcards recognised by ALSA
!!-

 0 [Intel  ]: HDA-Intel - HDA Intel
  HDA Intel at 0xee24 irq 31
29 [ThinkPadEC ]: ThinkPad EC - ThinkPad Console Audio Control
  ThinkPad Console Audio Control at EC reg 0x30, fw 
7BHT40WW-1.13

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

Title:
  [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys
  have no effect

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since upgrade to 15.04 from 14.10, the physical volume keys (mute, up,
  down) on my ThinkPad X60 have no effect. I can adjust the volume via
  the menubar indicator, but the buttons are dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   andrew 2071 F...m pulseaudio
   /dev/snd/controlC0:  andrew 2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri May  1 19:05:06 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-12 (535 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Type: Volume slider, or mixer problems
  Title: [HDA-Intel - HDA Intel, playback] volume slider problem
  UpgradeStatus: Upgraded to vivid on 2015-05-01 (0 days ago)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BETD7WW (2.18 )
  dmi.board.name: 170686U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BETD7WW(2.18):bd11/20/2008:svnLENOVO:pn170686U:pvrThinkPadX60:rvnLENOVO:rn170686U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 170686U
  dmi.product.version: ThinkPad X60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450947/+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 1435805] Re: Expose DirectionalDragArea in the UITK

2015-05-01 Thread Olivier Tilloy
Any updates on that one?

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

Title:
  Expose DirectionalDragArea in the UITK

Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  One strong principle in Ubuntu Touch’s UX is the use of edges.
  In particular, the bottom edge is reserved for applications to implement 
innovative and useful interactions.

  At the moment implementing such a gesture recognition in pure QML
  requires using an invisible mouse area at the bottom of the view to
  detect the start of a drag gesture. Unfortunately if there is content
  below that invisible drag area, it can’t be interacted with, because
  the mouse area will swallow mouse events.

  In the unity8 code base, there is a custom component called
  DirectionalDragArea (implemented in C++) that solves this issue
  nicely. Unfortunately it’s private to unity8 and can’t be reused in
  applications.

  This bug report is to request considering moving ownership of this
  component to the UITK, so that it can be exposed publicly and used by
  application developers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1435805/+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 1450790] Re: Phone not connecting to mobile data until rebooting

2015-05-01 Thread Tony Espy
@Michael

Thanks for the logs...

If you can reproduce reliably, could you add the output of 'list-modems'
( found in /usr/share/ofono/scripts ) and 'list-contexts'?

The error logs you provided show a couple of weird things...

First, I saw a whole bunch of SIM PIN errors reported by ofono.It
appears that you have two SIMs installed in the phone as well, are
either of these SIMs PIN-locked?  The indicator-network log shows an
error unlocking a SIM too.

Also, from the syslog it appears that at some point you used the APN
Editor, and there's a custom Internet APN with a blank AccessPointName
defined.  This APN looks to be the same APN that's returning errors when
NM tries to activate it ( see errors for context3 in the syslog ).

Could you try the following and see if it resolves your problems?

As root:

# stop ofono
# cd /var/lib/ofono

There should be at least two directories that are a long string of
numbers.  The numbers are the SubscriberIdentity from your SIM cards.
Ignore the dirs with trailing -, and cd into the other directories and
remove the files named 'gprs'.  Or if you'd like, you can edit these
files and just remove the offending __custom_internet_apn context.

# reboot

This will cause your phone to reprovision itself, and get rid of the
offending APN.

We actually spent quite a bit of time this past week at our sprint
working on the APN editor, and hopefully can roll out some improvements
( including the ability to force re-provisioning from the UI ) soon.


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

** Changed in: ofono (Ubuntu)
   Status: New = Incomplete

** Changed in: ofono (Ubuntu)
 Assignee: Tony Espy (awe) = Michael Zanetti (mzanetti)

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

Title:
  Phone not connecting to mobile data until rebooting

Status in the base for Ubuntu mobile products:
  New
Status in network-manager package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  Whenever I walk out of WiFi range, my phone does not connect to mobile
  data. Toggling flight mode does not help. I have to reboot the phone.
  When then I finally manage to connect after rebooting, if the signal
  strength drops and the phone would want to switch from 3G to 2G, it
  disconnects and I have to reboot again to get mobile data.

  $ system-image-cli -i
  current build number: 200
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-04-30 11:07:21
  version version: 200
  version ubuntu: 20150429
  version device: 20150326-f0c5ba5
  version custom: 20150429

  Attached you'll find the output of the forensics script

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450790/+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 1445239] Re: apt's lists/partial fills disk

2015-05-01 Thread Adam Conrad
** Also affects: apt (Ubuntu Vivid)
   Importance: High
   Status: Incomplete

** Changed in: apt (Ubuntu Vivid)
   Status: Incomplete = Confirmed

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

Title:
  apt's lists/partial fills disk

Status in APT:
  New
Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Vivid:
  Confirmed

Bug description:
  Since I upgraded to vivid, apt fills the disk space at
  /var/lib/apt/lists/partial. This was triggered by the automatic update
  every day, and as a solution I killed the processes named `http`
  spawned by apt, and removed the offending file from lists/partial
  manually. Until now, `apt-get update` and `apt-get upgrade` had been
  working. However, today, when I tried `apt-get update`, it got stuck
  in some file, continuously increasing its size when at 100%.

  I tried inspecting the file to see if there is a repetition of data,
  and there seems to be, as I have suspected.

  First of all, the file is it.archive.ubuntu
  .com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 this time, but
  I'm not sure if the previous time it was also this file.

  I used `tail` and `hexdump` to figure out whether a certain pattern
  shows up in the file. Here are some examples:

  $ tail -c 20 
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | 
hexdump | grep '\bbdf\'
  c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0010c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0020c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0030c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a

  $ tail -c 20 
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | 
hexdump | grep '\9b95\'
  c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0010c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0020c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
  0030c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a

  $ tail -c 20 
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | 
hexdump | grep '\1234\'
  0002630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd
  0012630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd
  0022630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd

  $ tail -c 20 
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | 
hexdump | grep '\76a8\'
  000fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c
  001fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c
  002fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c

  As you can see, it seems that after the error, a certain pattern seems
  to repeat every exactly 0x1 bytes. I attached a copy of those
  0x1 bytes that keep repeating (from an arbitrary offset).

  ---

  $ lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  $ apt-cache policy apt
  apt:
Installed: 1.0.9.7ubuntu4
Candidate: 1.0.9.7ubuntu4
Version table:
   *** 1.0.9.7ubuntu4 0
  500 http://it.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Do let me know if I can test further to see what could be wrong. I'll
  keep an eye next times the behavior repeat to make sure the file is
  the same / the pattern is the same and I'll report back. If you think
  the problem could be the Italy server, let me know and I'll try with a
  different one.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 17 00:04:05 2015
  SourcePackage: apt
  UpgradeStatus: Upgraded to vivid on 2015-03-28 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1445239/+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 1450790] Re: Phone not connecting to mobile data until rebooting

2015-05-01 Thread Michael Zanetti
Hi Tony,

No, I only have one SIM in there. That one is indeed PIN-locked.

list-modems: http://paste.ubuntu.com/10966553/
list-contexts: http://paste.ubuntu.com/10966559/

Also you're right that I did enter the SIM PIN wrong every once in a
while, as I often reboot during walking outside I made some typos in
entering the pin. However, IIRC I always entered the correct PIN on the
second attempt at latest.

I don't recall using the APN editor, at least I didn't enter some APN
setting somewhere. I did try to manually select the network operator
hoping I could get a connection without having to reboot - without
success.

I'll do the proposed reset now and will report back the results
tomorrow.

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

Title:
  Phone not connecting to mobile data until rebooting

Status in the base for Ubuntu mobile products:
  New
Status in network-manager package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  Whenever I walk out of WiFi range, my phone does not connect to mobile
  data. Toggling flight mode does not help. I have to reboot the phone.
  When then I finally manage to connect after rebooting, if the signal
  strength drops and the phone would want to switch from 3G to 2G, it
  disconnects and I have to reboot again to get mobile data.

  $ system-image-cli -i
  current build number: 200
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-04-30 11:07:21
  version version: 200
  version ubuntu: 20150429
  version device: 20150326-f0c5ba5
  version custom: 20150429

  Attached you'll find the output of the forensics script

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450790/+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 1426996] Re: $ Ubuntu-bug xorg

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
$ Ubuntu-bug xorg

Status in xorg package in Ubuntu:
  Expired

Bug description:
  mi da sempre errore all'apertura di ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Mar  2 00:36:32 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2015-02-23 (6 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1)
  MachineType: ACER Aspire M5630
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=8af213a4-7266-46c5-987d-53b425cfebc1 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A2
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EG31M
  dmi.board.vendor: ACER
  dmi.board.version: R01-A2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A2:bd08/10/2007:svnACER:pnAspireM5630:pvrR01-A2:rvnACER:rnEG31M:rvrR01-A2:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Aspire M5630
  dmi.product.version: R01-A2
  dmi.sys.vendor: ACER
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sun Mar  1 14:55:20 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
   NOUVEAU(0): [COPY] failed to allocate class.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.3
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1426996/+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 1450972] Re: package linux-image-3.16.0-36-generic 3.16.0-36.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2015-05-01 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-image-3.16.0-36-generic 3.16.0-36.48 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading Ubuntu 14.04 to 14.10 kernel install failed.

  Removing the syslinux package solved the problem and let the
  packages get configured, but it hangs with a black screen when I
  reboot into the new kernel.

  This is a new Dell XPS 13 that came with Ubuntu 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-36-generic 3.16.0-36.48
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yuriy  2550 F pulseaudio
   /dev/snd/controlC0:  yuriy  2550 F pulseaudio
  Date: Fri May  1 21:56:13 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DuplicateSignature: 
package:linux-image-3.16.0-36-generic:3.16.0-36.48:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=38abb4d0-3d8e-4698-abc4-204191048f6c
  InstallationDate: Installed on 2015-04-24 (8 days ago)
  InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-51-generic 
root=UUID=891dc704-43c6-427a-8885-0fa22b5817ab ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-3.16.0-36-generic 3.16.0-36.48 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to utopic on 2015-05-02 (0 days ago)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1450972/+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 1426596] Re: I get an error report popup on log-in

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  I get an error report popup on log-in

Status in xorg package in Ubuntu:
  Expired

Bug description:
  This doesn't occurr on every login, but it does occurr on the
  majority.

  From the crash report it seems to be Xorg, rather than Nautilus
  desktop.

  There are no obvious symptoms of this crash - i.e. everything seems to
  carry on regardless.

  I am reporting this against xorg, due to the existance of
  _usr_bin_Xorg.0.crash in /var/crash - I assume that all the
  information you need has been extracted below ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-46.75~precise1-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.113  Mon Dec  1 20:14:01 
PST 2014
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,resize,vpswitch,snap,imgpng,grid,regex,place,gnomecompat,compiztoolbox,unitymtgrabhandles,move,mousepoll,animation,wall,session,workarounds,expo,fade,scale,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Feb 28 00:05:49 2015
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:6502]
     Subsystem: CLEVO/KAPOK Computer Device [1558:6502]
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 
(20140204)
  JockeyStatus: xorg:nvidia_331_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Enabled, In use)
  MachineType: Notebook W65_67SF
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic 
root=UUID=9b573783-9dac-471b-ba7f-755099846d9e ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1426596/+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 1426949] Re: Xorg freezes when rendering webGL

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Xorg freezes when rendering webGL

Status in xorg package in Ubuntu:
  Expired

Bug description:
  On vivid I went to the following URL:
  http://www.ambiera.at/coppercube/demos/version5/watertest/

  When I click on switch to terrain scene my system freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar  1 14:34:06 2015
  DistUpgraded: 2015-01-24 16:21:53,459 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] 
[1002:675d] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:2b20]
  InstallationDate: Installed on 2014-07-25 (219 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. OptiPlex 7010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=e505ac2d-47bc-4eb6-8759-06d542cb82b8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  Title: Xorg freeze
  UpgradeStatus: Upgraded to vivid on 2015-01-24 (35 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0GY6Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/09/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0GY6Y8:rvrA03:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150213-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~rc2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~rc2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sun Mar  1 14:28:28 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputDell Dell USB Entry Keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.2.901-1ubuntu4
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1426949/+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 1417826] Re: display acting up. overlay .. ?

2015-05-01 Thread Christopher M. Penalver
Morten Hundevad, just to clarify, if you disable the nvidia card in BIOS
(or pull it out of the chassis if this is not an option) is this problem
reproducible?

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

Title:
   display acting up. overlay .. ?

Status in xorg package in Ubuntu:
  Expired

Bug description:
  display acting up.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Er et filkatalog: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Feb  4 01:29:47 2015
  DistUpgraded: 2014-11-11 23:22:24,600 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0571]
   NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:124d] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GeForce GT 555M [1028:0571]
  InstallationDate: Installed on 2014-10-11 (115 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Dell System XPS L702X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=81abd60b-9317-4293-accd-cf625ddbaa45 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-11-11 (84 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 0XN71K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: FAB1
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd09/07/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L702X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Feb  3 20:36:12 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5920
   vendor CMO
  xserver.version: 2:1.16.0-1ubuntu1.2
  --- 
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.76  Thu Jan 22 12:11:08 
PST 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: 2015-04-24 05:17:39,607 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.16.0-34-generic, x86_64: installed
   bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed
   nvidia-340, 340.76, 3.16.0-34-generic, x86_64: installed
   nvidia-340, 340.76, 3.19.0-15-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0571]
   NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:124d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GeForce GT 555M [1028:0571]
  InstallationDate: Installed on 2014-10-11 (202 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 

[Touch-packages] [Bug 1434557] ProcModules.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389447/+files/ProcModules.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: 

[Touch-packages] [Bug 1434557] Lsusb.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1434557/+attachment/4389443/+files/Lsusb.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: /usr/bin/X 

[Touch-packages] [Bug 1434557] ProcCpuinfo.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389444/+files/ProcCpuinfo.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: 

[Touch-packages] [Bug 1434557] XorgLogOld.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: XorgLogOld.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389451/+files/XorgLogOld.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: 

[Touch-packages] [Bug 1434557] ProcInterrupts.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389446/+files/ProcInterrupts.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 

[Touch-packages] [Bug 1434557] Xrandr.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: Xrandr.txt
   https://bugs.launchpad.net/bugs/1434557/+attachment/4389452/+files/Xrandr.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: /usr/bin/X 

[Touch-packages] [Bug 1434557] ProcEnviron.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389445/+files/ProcEnviron.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: 

[Touch-packages] [Bug 1241101]

2015-05-01 Thread Marc-andre-laperle
I can reproduce the crash using Thomas Singer's example code (comment
9), on Ubuntu 13.10 and 14.04 when UBUNTU_MENUPROXY is enabled. If I
disable UBUNTU_MENUPROXY it works. I think it's the same issue as bug
461311: radio button in the menu. Can we mark one as duplicate of the
other?

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1450947] [NEW] [HDA-Intel - HDA Intel, playback] volume slider problem

2015-05-01 Thread Andrew
Public bug reported:

Since upgrade to 15.04 from 14.10, the physical volume keys (mute, up,
down) on my ThinkPad X60 have no effect. I can adjust the volume via the
menubar indicator, but the buttons are dead.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   andrew 2071 F...m pulseaudio
 /dev/snd/controlC0:  andrew 2071 F pulseaudio
CurrentDesktop: XFCE
Date: Fri May  1 19:05:06 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-12 (535 days ago)
InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel
Symptom_Type: Volume slider, or mixer problems
Title: [HDA-Intel - HDA Intel, playback] volume slider problem
UpgradeStatus: Upgraded to vivid on 2015-05-01 (0 days ago)
dmi.bios.date: 11/20/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7BETD7WW (2.18 )
dmi.board.name: 170686U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7BETD7WW(2.18):bd11/20/2008:svnLENOVO:pn170686U:pvrThinkPadX60:rvnLENOVO:rn170686U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 170686U
dmi.product.version: ThinkPad X60
dmi.sys.vendor: LENOVO

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


** Tags: apport-bug i386 vivid

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

Title:
  [HDA-Intel - HDA Intel, playback] volume slider problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since upgrade to 15.04 from 14.10, the physical volume keys (mute, up,
  down) on my ThinkPad X60 have no effect. I can adjust the volume via
  the menubar indicator, but the buttons are dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   andrew 2071 F...m pulseaudio
   /dev/snd/controlC0:  andrew 2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri May  1 19:05:06 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-12 (535 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Type: Volume slider, or mixer problems
  Title: [HDA-Intel - HDA Intel, playback] volume slider problem
  UpgradeStatus: Upgraded to vivid on 2015-05-01 (0 days ago)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BETD7WW (2.18 )
  dmi.board.name: 170686U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BETD7WW(2.18):bd11/20/2008:svnLENOVO:pn170686U:pvrThinkPadX60:rvnLENOVO:rn170686U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 170686U
  dmi.product.version: ThinkPad X60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450947/+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 1434557] DpkgLog.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: DpkgLog.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389439/+files/DpkgLog.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: /usr/bin/X 

[Touch-packages] [Bug 1434557] LightdmDisplayLog.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: LightdmDisplayLog.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389440/+files/LightdmDisplayLog.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  

[Touch-packages] [Bug 1434557] CurrentDmesg.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389436/+files/CurrentDmesg.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: 

[Touch-packages] [Bug 1434557] DkmsStatus.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: DkmsStatus.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389438/+files/DkmsStatus.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: 

[Touch-packages] [Bug 1434557] Dependencies.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389437/+files/Dependencies.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: 

[Touch-packages] [Bug 1434557] Re: frozen desktop

2015-05-01 Thread brad haack
apport information

** Tags added: apport-collected third-party-packages trusty ubuntu

** Description changed:

  Very often (about once/day) I'm experiencing a frozen desktop.  minimal
  response from keyboard or mouse, usually degrades to no response.   No
  response from ^-alt-F1 or ^-alt-esc.  Here's today's
  Xorg.0.log.old:
  
  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  [ 11472.953] [mi] EQ processing has resumed after 132 dropped events.
  [ 11473.029] [mi] This may be caused my a misbehaving driver monopolizing the 
server's resources.
+ 
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.9
+ Architecture: i386
+ 

[Touch-packages] [Bug 1434557] BootLog.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: BootLog.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389435/+files/BootLog.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: /usr/bin/X 

[Touch-packages] [Bug 1389215] Re: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver.

2015-05-01 Thread Christopher M. Penalver
Hans Deragon, not testing at least a live environment is largely going
to further delay your issue from being addressed (as it has already).

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

Title:
  Brightness controls are not working in Unity / Xorg because of Nvidia
  proprietary driver.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Brightness controls are not working in Unity / Xorg.  When pressing
  the keys fnhome and fnend on my Lenovo W510, I see the
  indicator on the screen showing the level of brightness changing, so
  key mapping is not the problem.  However, the brightness is not
  changing.

  On the kernel level, I have the single following device:

  # cd /sys/class/backlight
  # ls -l
  total 0
  lrwxrwxrwx 1 root root 0 Nov  3 17:16 acpi_video0 - 
../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0

  When playing with the fnhome and fnend, the value of
  /sys/class/backlight/brightness changes accordingly.  The screen
  brightness does not change.

  Performing:

  # echo 10 brightness

  ...does not have any effect (regardless of the value provided, 10
  being just an example).

  WORKAROUND

  There is an odd workaround.  Simply go to the console using
  CTRLALTF1 and using the fnhome and fnend keys,
  brightness then changes.  Return to Unity / Xorg with CTRLALTF7
  and the selected brightness persists.

  NON WORKING WORKAROUND

  On the web, I read that adding:

  Option RegistryDwords EnableBrightnessControl=1'

  in xorg.conf might fix the problem.  I do not have an xorg and when I
  let the proprietary Nvidia driver generate one and add this option, X
  does not start anymore.

  Ubuntu 14.04.1 LTS with latest updates as of this writing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov  4 07:38:59 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed
   tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2145]
  InstallationDate: Installed on 2014-11-01 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: LENOVO 4318CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic 
root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4318CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4318CTO
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-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.1
  

[Touch-packages] [Bug 1450947] Re: [HDA-Intel - HDA Intel, playback] volume slider problem

2015-05-01 Thread Raymond
do you mean regression of these patches ?

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/thinkpad_helper.c?id=b317b032d2dcb5e518cc9630cc6f1c7c24afedfc


http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?id=9a417ec0c9d1f7af5394333411fc4d98adb8761b

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

Title:
  [HDA-Intel - HDA Intel, playback] volume slider problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since upgrade to 15.04 from 14.10, the physical volume keys (mute, up,
  down) on my ThinkPad X60 have no effect. I can adjust the volume via
  the menubar indicator, but the buttons are dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   andrew 2071 F...m pulseaudio
   /dev/snd/controlC0:  andrew 2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri May  1 19:05:06 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-12 (535 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Type: Volume slider, or mixer problems
  Title: [HDA-Intel - HDA Intel, playback] volume slider problem
  UpgradeStatus: Upgraded to vivid on 2015-05-01 (0 days ago)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BETD7WW (2.18 )
  dmi.board.name: 170686U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BETD7WW(2.18):bd11/20/2008:svnLENOVO:pn170686U:pvrThinkPadX60:rvnLENOVO:rn170686U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 170686U
  dmi.product.version: ThinkPad X60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450947/+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 1448371] Re: package udev 219-7ubuntu4 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2015-05-01 Thread freecode
Figured it out - removed PostgreSQL 9.3 and then deleted the input
group. Ran the process again and udev installs without issue. Seems
insserv was causing monit and PostgreSQL 9.3 to conflict and that
prevented udev from installation in addition to the inout group already
existing.

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

Title:
  package udev 219-7ubuntu4 failed to install/upgrade: le sous-processus
  script post-installation installé a retourné une erreur de sortie
  d'état 1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  the upgrade from ubuntu 14.10 vas not completely failed ... I had errors but 
the install continued.
  after reboot the screen was locked. So I rebooted and lauched a previous 
version. Now I hav ubuntu 15.04 idicated but not fully installed. sudo apt-get 
upgrade generates too much errors.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: udev 219-7ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-36.48-generic 3.16.7-ckt9
  Uname: Linux 3.16.0-36-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CustomUdevRuleFiles: 99-jlink.rules 99-input.rules 85-lpcxpresso.rules 
z010_mchp_tools.rules README.dpkg-remove z011_mchp_jlink.rules 60-vboxdrv.rules
  Date: Sat Apr 25 06:27:23 2015
  DpkgTerminalLog:
   Paramétrage de udev (219-7ubuntu4) ...
   dpkg: erreur de traitement du paquet udev (--configure) :
le sous-processus script post-installation installé a retourné une erreur 
de sortie d'état 1
  DuplicateSignature: package:udev:219-7ubuntu4:le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2013-12-11 (499 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: LENOVO 20263
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-36-generic 
root=UUID=16c65adb-dc63-44e2-9d93-aea9224e0bab ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: systemd
  Title: package udev 219-7ubuntu4 failed to install/upgrade: le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 1
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BCN21WW(V1.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G500s Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BCN21WW(V1.05):bd04/18/2013:svnLENOVO:pn20263:pvrLenovoG500sTouch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG500sTouch:
  dmi.product.name: 20263
  dmi.product.version: Lenovo G500s Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448371/+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 1450966] [NEW] apt-get install segfault

2015-05-01 Thread Brian
Public bug reported:

Package: apt
Version: apt-0.8.16~exp12ubuntu10.22
root@0fb5fe4c0c0f:/build/apt-0.8.16~exp12ubuntu10.22# lsb_release -rd
Description:Ubuntu 12.04.5 LTS
Release:12.04

Expected to happen: running apt-get install [ package ] installs the
package

What happened: running apt-get install [ package ] encounters a
segfault

Debug notes:

This occurred while installing a package that depends on many other
packages.  The package I was installing had Section defined, while the
offending dependent package did not have Section defined.

I built apt from source with debug symbols and located found the issue
occurs because a NULL value is being passed to strcmp (frame 1).  This
happens because a prior function (frame 2) assumes that if the parent
package has Section defined, then the defendant package will also have
Section defined as well.

Adding the Section field to the offending package works around the
segfault issue.

Given that the policy manual (https://www.debian.org/doc/debian-policy
/ch-controlfields.html) states that section is recommended it's
technically correct to have a packge omit the Section field, and as
such, apt should tolerate this situation.

GDB:

Program received signal SIGSEGV, Segmentation fault.
__strcmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:163
163 ../sysdeps/x86_64/multiarch/strcmp-sse42.S: No such file or directory.
(gdb) where
#0  __strcmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:163
#1  0x77ad7479 in ConfigValueInSubTree (SubTree=0x77b85879 
APT::Never-MarkAuto-Sections, needle=0x0) at depcache.cc:53
#2  0x77adcb54 in pkgDepCache::MarkInstall (this=0x668fb0, Pkg=..., 
AutoInst=true, Depth=0, FromUser=true,
ForceImportantDeps=false) at depcache.cc:1208
#3  0x00431259 in TryToInstall::doAutoInstall (this=0x7fffd710) at 
apt-get.cc:878
#4  0x004218a7 in DoInstall (CmdL=...) at apt-get.cc:1901
#5  0x77abe322 in CommandLine::DispatchArg (this=0x7fffe5f0, 
Map=0x7fffe4b0, NoMatch=true) at contrib/cmndline.cc:337
#6  0x0042c109 in main (argc=5, argv=0x7fffe738) at apt-get.cc:3523

Frame 1, NULL value getting passed to strcmp

(gdb) f 1 
#1  0x77ad7479 in ConfigValueInSubTree (SubTree=0x77b85879 
APT::Never-MarkAuto-Sections, needle=0x0) at depcache.cc:53
53   if (strcmp(needle, Opts-Value.c_str()) == 0)
(gdb) p needle
$4 = 0x0
(gdb) list
48Opts = Opts-Child;
49for (; Opts != 0; Opts = Opts-Next)
50{
51   if (Opts-Value.empty() == true)
52  continue;
53   if (strcmp(needle, Opts-Value.c_str()) == 0)
54  return true;
55}
56 }
57 return false;


Frame 2, code assumes InstVer.Section() is non-null if Pkg.Section() evaluates 
to true.

(gdb) f 2
#2  0x77adcb54 in pkgDepCache::MarkInstall (this=0x668fb0, Pkg=..., 
AutoInst=true, Depth=0, FromUser=true, 
ForceImportantDeps=false) at depcache.cc:1208
1208if(Pkg.Section()  
ConfigValueInSubTree(APT::Never-MarkAuto-Sections, InstVer.Section()))
(gdb) p Pkg.Section()
$2 = 0x75b1325e Optional
(gdb) p InstVer.Section()
$6 = 0x0
(gdb) list
1203if(DebugAutoInstall == true)
1204   std::clog  OutputInDepth(Depth)  Installing   
InstPkg.Name()
1205   as   Start.DepType()   of   
Pkg.Name()
1206  std::endl;
1207// now check if we should consider it a automatic 
dependency or not
1208if(Pkg.Section()  
ConfigValueInSubTree(APT::Never-MarkAuto-Sections, InstVer.Section()))
1209{
1210   if(DebugAutoInstall == true)
1211  std::clog  OutputInDepth(Depth)  Setting NOT as 
auto-installed (direct 
1212 Start.DepType()   of pkg in 
APT::Never-MarkAuto-Sections)  std::endl;

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

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

Title:
  apt-get install segfault

Status in apt package in Ubuntu:
  New

Bug description:
  Package: apt
  Version: apt-0.8.16~exp12ubuntu10.22
  root@0fb5fe4c0c0f:/build/apt-0.8.16~exp12ubuntu10.22# lsb_release -rd
  Description:Ubuntu 12.04.5 LTS
  Release:12.04

  Expected to happen: running apt-get install [ package ] installs the
  package

  What happened: running apt-get install [ package ] encounters a
  segfault

  Debug notes:

  This occurred while installing a package that depends on many other
  packages.  The package I was installing had Section defined, while
  the offending dependent package did not have Section defined.

  I built apt from source with debug symbols and located found the issue
  occurs because a NULL 

[Touch-packages] [Bug 1450947] Re: [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys have no effect

2015-05-01 Thread Andrew
Hi Raymond,
Seems reasonable to me that this is related to those patches.

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

Title:
  [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys
  have no effect

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since upgrade to 15.04 from 14.10, the physical volume keys (mute, up,
  down) on my ThinkPad X60 have no effect. I can adjust the volume via
  the menubar indicator, but the buttons are dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   andrew 2071 F...m pulseaudio
   /dev/snd/controlC0:  andrew 2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri May  1 19:05:06 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-12 (535 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Type: Volume slider, or mixer problems
  Title: [HDA-Intel - HDA Intel, playback] volume slider problem
  UpgradeStatus: Upgraded to vivid on 2015-05-01 (0 days ago)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BETD7WW (2.18 )
  dmi.board.name: 170686U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BETD7WW(2.18):bd11/20/2008:svnLENOVO:pn170686U:pvrThinkPadX60:rvnLENOVO:rn170686U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 170686U
  dmi.product.version: ThinkPad X60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450947/+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 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

2015-05-01 Thread Rafael David Tinoco
** Changed in: ifupdown (Ubuntu)
 Assignee: Rafael David Tinoco (inaddy) = (unassigned)

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

Title:
  Precise, Trusty, Utopic - ifupdown initialization problems caused by
  race condition

Status in ifupdown package in Ubuntu:
  In Progress
Status in ifupdown package in Debian:
  New

Bug description:
  * please consider my bonding examples are using eth1 and eth2 as slave
   interfaces.

  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.

  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
1-1. Wait for locking ifstate.lock
file.
  1-2. Read ifstate file to check
   the target NIC.
  1-3. close(=release) ifstate.lock
   file.
  1-4. Judge that the target NIC
   isn't processed.
1-2. Read ifstate file to check
 the target NIC.
1-3. close(=release) ifstate.lock
 file.
1-4. Judge that the target NIC
 isn't processed.
  2. Lock and update ifstate file.
 Release the lock.
2. Lock and update ifstate file.
   Release the lock.
  !!!

  to be explained

  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
 /sys/class/net/bond0/bonding
 /slaves then NIC gets up
4. Link down the target NIC.
5. Fails to write NIC id to
   /sys/class/net/bond0/bonding/
   slaves it is already written.
  !!!

  #

   My setup:

  root@provisioned:~# cat /etc/modprobe.d/bonding.conf
  alias bond0 bonding options bonding mode=1 arp_interval=2000

  Both, /etc/init.d/networking and upstart network-interface begin
  enabled.

   Beginning:

  root@provisioned:~# cat /etc/network/interfaces
  # /etc/network/interfaces

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

  I'm able to boot with both scripts (networking and network-interface
  enabled) with no problem. I can also boot with only networking 
  script enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface stop/waiting
  networking start/running
  ---

  OR only the script network-interface enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface (eth2) start/running
  network-interface (lo) start/running
  network-interface (eth0) start/running
  network-interface (eth1) start/running
  ---

   Enabling bonding:

  Following ifenslave configuration example (/usr/share/doc/ifenslave/
  examples/two_hotplug_ethernet), my /etc/network/interfaces has to 
  look like this:

  ---
  auto eth1
  iface eth1 inet manual
  bond-master bond0

  auto eth2
  iface eth2 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  bond-mode 1
  bond-miimon 100
  bond-primary eth1 eth2
address 192.168.169.1
netmask 255.255.255.0
broadcast 192.168.169.255
  ---

  Having both scripts running does not make any difference since we
  are missing bond-slaves keyword on slave interfaces, for ifenslave
  to work, and they are set to manual.

  Ifenslave code:

  
  for slave in $BOND_SLAVES ; do
  ...
  # Ensure $slave is down.
  ip link set $slave down 2/dev/null
  if ! sysfs_add slaves $slave 2/dev/null ; then
echo Failed to enslave $slave to $BOND_MASTER. Is $BOND_MASTER 
ready and a bonding interface ? 2
  else
# Bring up slave if it is the target of an allow-bondX stanza.
# This is usefull to bring up slaves that need extra setup.
if [ -z $(which ifquery) ] || ifquery --allow \$BOND_MASTER\ 
--list | grep -q $slave; then
ifup $v --allow $BOND_MASTER $slave
fi
  

  Without the keyword bond-slaves on the master interface declaration,
  ifenslave will NOT bring any slave interface up on the master 
  interface ifup invocation. 

  *** Part 1

  So, having networking sysv init script AND upstart network-interface
  script running together... the following 

[Touch-packages] [Bug 1450972] Re: package linux-image-3.16.0-36-generic 3.16.0-36.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2015-05-01 Thread Ubuntu Foundations Team Bug Bot
** Attachment removed: VarLogDistupgradeTermlog.gz
   
https://bugs.launchpad.net/bugs/1450972/+attachment/4389426/+files/VarLogDistupgradeTermlog.gz

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

Title:
  package linux-image-3.16.0-36-generic 3.16.0-36.48 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading Ubuntu 14.04 to 14.10 kernel install failed.

  Removing the syslinux package solved the problem and let the
  packages get configured, but it hangs with a black screen when I
  reboot into the new kernel.

  This is a new Dell XPS 13 that came with Ubuntu 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-36-generic 3.16.0-36.48
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yuriy  2550 F pulseaudio
   /dev/snd/controlC0:  yuriy  2550 F pulseaudio
  Date: Fri May  1 21:56:13 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DuplicateSignature: 
package:linux-image-3.16.0-36-generic:3.16.0-36.48:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=38abb4d0-3d8e-4698-abc4-204191048f6c
  InstallationDate: Installed on 2015-04-24 (8 days ago)
  InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-51-generic 
root=UUID=891dc704-43c6-427a-8885-0fa22b5817ab ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-3.16.0-36-generic 3.16.0-36.48 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to utopic on 2015-05-02 (0 days ago)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1450972/+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 914713] Re: virtual display memory too small, primary display resolution incorrect

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  virtual display memory too small, primary display resolution incorrect

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Occurs when adding a secondary display to the system. Both screens
  have been set to there standard resolution. When applying changes the
  following error message occurs:

  required virtual size does not fit available size: requested=(3600,
  1080), minimum=(320, 200), maximum=(1920, 1920)

  I am looking to create an extended desktop. The system does not pick
  up on all graphics cards properly, i.e. does not recognise the two
  secondary graphics cards. It seems like the system is attempting to
  create one screen width wise and two screens vertically based on the
  size of the requested display compared to the actual requested size.

  The main monitor should be 1920 x 1080 @ 60Hz and the second monitor
  that is being added should be 1280x1024 @ 60Hz.

  The primary monitor, with secondary turned off looses 45mm of screen
  space widthwise and 26mm screen space vertically. It is centered the
  display is 24 inches from bottom left to top right.

  It would be first a benefit to get the secondary display working
  regardless of display size.

  When reducing resolution of the secondary display as much as possible
  it will accept the changes but display the secondary desktop in a
  small box embedded into the desktop on the primary monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,vpswitch,snap,move,grid,regex,mousepoll,place,resize,gnomecompat,unitymtgrabhandles,animation,workarounds,wall,session,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Wed Jan 11 11:15:52 2012
  DistUpgraded: Log time: 2011-12-02 21:05:11.819557
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 8.881, 3.0.0-13-generic, x86_64: installed
   fglrx, 8.881, 3.0.0-14-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  JockeyStatus:
   xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release 
updates) (Proprietary, Disabled, Not in use)
   xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, 
Enabled, In use)
  MachineType: Gigabyte Technology Co., Ltd. EX58-UD5
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic 
root=UUID=81fb1d57-7b0d-4922-b420-39c7618c1776 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to oneiric on 2011-12-02 (39 days ago)
  dmi.bios.date: 03/11/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F12
  dmi.board.name: EX58-UD5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnEX58-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX58-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EX58-UD5
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs 20090808ubuntu26
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.15.901-1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Touch-packages] [Bug 1450947] Re: [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys have no effect

2015-05-01 Thread Raymond
y 01 18:57:15 hostname pulseaudio[2071]: [pulseaudio] rtsp_client.c: failed to 
connect to server 'fe80::ba27:ebff:febb:21e8:3'
May 01 18:57:15 hostname pulseaudio[2071]: [pulseaudio] module-raop-sink.c: 
Failed to connect to server.
May 01 18:57:15 hostname pulseaudio[2071]: [pulseaudio] module.c: Failed to 
load module module-raop-sink (argument: 
server=[fe80::ba27:ebff:febb:21e8]:3 sink_name=raop.raspbmc.local 
sink_properties='device.description=Kodi (raspbmc)'): initialization failed.
May 01 18:57:15 hostname pulseaudio[2071]: [pulseaudio] rtsp_client.c: failed 
to connect to server 'fe80::ba27:ebff:febb:21e8:3'
May 01 18:57:15 hostname pulseaudio[2071]: [pulseaudio] module-raop-sink.c: 
Failed to connect to server.
May 01 18:57:15 hostname pulseaudio[2071]: [pulseaudio] module.c: Failed to 
load module module-raop-sink (argument: 
server=[fe80::ba27:ebff:febb:21e8]:3 sink_name=raop.raspbmc.local 
sink_properties='device.description=Kodi (raspbmc)'): initialization failed.
May 01 18:57:17 hostname pulseaudio[2071]: [pulseaudio] rtsp_client.c: 
Unexpected response: RTSP/1.0 453 Not Enough Bandwidth
May 01 18:57:17 hostname pulseaudio[2071]: [pulseaudio] rtsp_client.c: 
Unexpected response: Server: AirTunes/105.1
May 01 18:57:17 hostname pulseaudio[2071]: [pulseaudio] rtsp_client.c: 
Unexpected response: CSeq: 2
May 01 18:57:17 hostname pulseaudio[2071]: [pulseaudio] rtsp_client.c: 
Unexpected response:

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

Title:
  [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys
  have no effect

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since upgrade to 15.04 from 14.10, the physical volume keys (mute, up,
  down) on my ThinkPad X60 have no effect. I can adjust the volume via
  the menubar indicator, but the buttons are dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   andrew 2071 F...m pulseaudio
   /dev/snd/controlC0:  andrew 2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri May  1 19:05:06 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-12 (535 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Type: Volume slider, or mixer problems
  Title: [HDA-Intel - HDA Intel, playback] volume slider problem
  UpgradeStatus: Upgraded to vivid on 2015-05-01 (0 days ago)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BETD7WW (2.18 )
  dmi.board.name: 170686U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BETD7WW(2.18):bd11/20/2008:svnLENOVO:pn170686U:pvrThinkPadX60:rvnLENOVO:rn170686U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 170686U
  dmi.product.version: ThinkPad X60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450947/+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 1450947] Re: [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys have no effect

2015-05-01 Thread Raymond
9.559421] thinkpad_acpi: ThinkPad ACPI Extras v0.25
[9.559426] thinkpad_acpi: http://ibm-acpi.sf.net/
[9.559428] thinkpad_acpi: ThinkPad BIOS 7BETD7WW (2.18 ), EC 7BHT40WW-1.13
[9.559430] thinkpad_acpi: Lenovo ThinkPad X60, model 170686U
[9.562798] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
[9.563440] thinkpad_acpi: ACPI backlight control delay disabled
[9.567150] thinkpad_acpi: radio switch found; radios are enabled
[9.567181] thinkpad_acpi: This ThinkPad has standard ACPI backlight 
brightness control, supported by the ACPI video driver
[9.567183] thinkpad_acpi: Disabling thinkpad-acpi brightness events by 
default...
[9.574003] cfg80211: Calling CRDA to update world regulatory domain
[9.574081] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is 
blocked
[9.594563] thinkpad_acpi: Standard ACPI backlight interface available, not 
loading native one
[9.608736] thinkpad_acpi: Console audio control enabled, mode: monitor 
(read only)
[9.639273] intel_rng: FWH not detected
[9.640794] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection 
driver for Linux, in-tree:s
[9.640798] iwl3945: Copyright(c) 2003-2011 Intel Corporation
[9.640866] iwl3945 :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[9.657234] yenta_cardbus :15:00.0: CardBus bridge found [17aa:201c]
[9.671746] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input8
[9.696917] iwl3945 :03:00.0: Tunable channels: 11 802.11bg, 13 802.11a 
channels
[9.696924] iwl3945 :03:00.0: Detected Intel Wireless WiFi Link 3945ABG
[9.724992] ACPI Warning: SystemIO range 0x1028-0x102f conflicts 
with OpRegion 0x1000-0x107f (\_SB_.PCI0.LPC_.PMIO) 
(20141107/utaddress-258)
[9.725004] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[9.725009] ACPI Warning: SystemIO range 0x11b0-0x11bf conflicts 
with OpRegion 0x1180-0x11bf (\_SB_.PCI0.LPC_.LPIO) 
(20141107/utaddress-258)
[9.725015] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[9.725018] ACPI Warning: SystemIO range 0x1180-0x11af conflicts 
with OpRegion 0x1180-0x11bf (\_SB_.PCI0.LPC_.LPIO) 
(20141107/utaddress-258)
[9.725023] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[9.725026] lpc_ich: Resource conflict(s) found affecting gpio_ich
[9.735651] leds_ss4200: no LED devices found
[9.744740] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
[9.784940] yenta_cardbus :15:00.0: ISA IRQ mask 0x0cb0, PCI irq 16
[9.784955] yenta_cardbus :15:00.0: Socket status: 3006
[9.784965] yenta_cardbus :15:00.0: pcmcia: parent PCI bridge window: 
[io  0x9000-0xcfff]
[9.784969] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x9000-0xcfff:
[9.793739]  excluding 0x9000-0x90ff 0x9400-0x94ff
[9.842514] snd_hda_intel :00:1b.0: probe_mask set to 0x1 for device 
17aa:2010
[9.881226] sound hdaudioC0D0: autoconfig: line_outs=1 (0x5/0x0/0x0/0x0/0x0) 
type:speaker
[9.881233] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[9.881237] sound hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
[9.881240] sound hdaudioC0D0:mono: mono_out=0x0
[9.881243] sound hdaudioC0D0:inputs:
[9.881247] sound hdaudioC0D0:  Mic=0x8
[9.881250] sound hdaudioC0D0:  CD=0x19

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

Title:
  [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys
  have no effect

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Since upgrade to 15.04 from 14.10, the physical volume keys (mute, up,
  down) on my ThinkPad X60 have no effect. I can adjust the volume via
  the menubar indicator, but the buttons are dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   andrew 2071 F...m pulseaudio
   /dev/snd/controlC0:  andrew 2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri May  1 19:05:06 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-12 (535 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  

[Touch-packages] [Bug 1244994] Re: second battery icon is different

2015-05-01 Thread Daniel Fore
** No longer affects: elementaryos

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

Title:
  second battery icon is different

Status in elementary Icons:
  Invalid
Status in indicator-power package in Ubuntu:
  Invalid

Bug description:
  hey,

  i have a notebook with 1 build in battery and 1 hot plug battery.
  the second battery icon is different then the first: 
http://i.imgur.com/ZaCOM9C.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryicons/+bug/1244994/+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 1450846] Re: [Suggestion] Changing the font / font size...

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

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New = Confirmed

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

Title:
  [Suggestion] Changing the font / font size...

Status in the base for Ubuntu mobile products:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  It would be usefull if the font and the font size could be changed
  espacially for elderly users and  for people with visual problems. So
  content could be read easily.

  Changing colors, features like home screen simplification, large
  icons... would be great, too.

  Should be found in system settings → background

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450846/+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 1450972] [NEW] package linux-image-3.16.0-36-generic 3.16.0-36.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2015-05-01 Thread Yuriy Kozlov
Public bug reported:

Upgrading Ubuntu 14.04 to 14.10 kernel install failed.

Removing the syslinux package solved the problem and let the packages
get configured, but it hangs with a black screen when I reboot into the
new kernel.

This is a new Dell XPS 13 that came with Ubuntu 14.04

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-36-generic 3.16.0-36.48
ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
Uname: Linux 3.13.0-51-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  yuriy  2550 F pulseaudio
 /dev/snd/controlC0:  yuriy  2550 F pulseaudio
Date: Fri May  1 21:56:13 2015
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
DuplicateSignature: 
package:linux-image-3.16.0-36-generic:3.16.0-36.48:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=38abb4d0-3d8e-4698-abc4-204191048f6c
InstallationDate: Installed on 2015-04-24 (8 days ago)
InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20140620-04:25
MachineType: Dell Inc. XPS 13 9343
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-51-generic 
root=UUID=891dc704-43c6-427a-8885-0fa22b5817ab ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-3.16.0-36-generic 3.16.0-36.48 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to utopic on 2015-05-02 (0 days ago)
dmi.bios.date: 03/25/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0TM99H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package dist-upgrade need-duplicate-check utopic

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

Title:
  package linux-image-3.16.0-36-generic 3.16.0-36.48 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading Ubuntu 14.04 to 14.10 kernel install failed.

  Removing the syslinux package solved the problem and let the
  packages get configured, but it hangs with a black screen when I
  reboot into the new kernel.

  This is a new Dell XPS 13 that came with Ubuntu 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-36-generic 3.16.0-36.48
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yuriy  2550 F pulseaudio
   /dev/snd/controlC0:  yuriy  2550 F pulseaudio
  Date: Fri May  1 21:56:13 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DuplicateSignature: 
package:linux-image-3.16.0-36-generic:3.16.0-36.48:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=38abb4d0-3d8e-4698-abc4-204191048f6c
  InstallationDate: Installed on 2015-04-24 (8 days ago)
  InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-51-generic 
root=UUID=891dc704-43c6-427a-8885-0fa22b5817ab ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: 

[Touch-packages] [Bug 1450846] Re: [Suggestion] Changing the font / font size...

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

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

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

Title:
  [Suggestion] Changing the font / font size...

Status in the base for Ubuntu mobile products:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  It would be usefull if the font and the font size could be changed
  espacially for elderly users and  for people with visual problems. So
  content could be read easily.

  Changing colors, features like home screen simplification, large
  icons... would be great, too.

  Should be found in system settings → background

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

2015-05-01 Thread brad haack
apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1434557/+attachment/4389442/+files/Lspci.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: /usr/bin/X 

[Touch-packages] [Bug 1434557] LightdmLog.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: LightdmLog.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389441/+files/LightdmLog.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: 

[Touch-packages] [Bug 1434557] UdevLog.txt

2015-05-01 Thread brad haack
apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1434557/+attachment/4389449/+files/UdevLog.txt

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

Title:
  frozen desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Very often (about once/day) I'm experiencing a frozen desktop.
  minimal response from keyboard or mouse, usually degrades to no
  response.   No response from ^-alt-F1 or ^-alt-esc.  Here's
  today's  Xorg.0.log.old:

  [47.809] (II) intel(0): Modeline 1280x1024x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [47.809] (II) intel(0): Modeline 1280x960x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [  3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [  9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
  [  9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 
0, position (0, 0), rotation normal, reflection none
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
  (EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
  (EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
  (EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
  (EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
  (EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
  (EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
  (EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
  (EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) 
[0xb6e1698f]
  (EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
  (EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
  (EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
  (EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
  (EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
  (EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
  (EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
  (EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
  (EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
  (EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
  (EE) 19: /usr/bin/X 

[Touch-packages] [Bug 1294071] Re: window have a black background after resume from suspend

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  window have a black background after resume from suspend

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I close the macbook for while,then open it and login I see the all window 
have black background/frame.
  do unity --replace in the terminal will fix!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia wl
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Mar 18 19:32:39 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.141+bdcom, 3.13.0-16-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-17-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-17-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00fb]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00fc]
  InstallationDate: Installed on 2014-03-08 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307)
  MachineType: Apple Inc. MacBookPro9,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed 
root=UUID=025c21aa-7414-4f4d-820d-186b0cb78d9e ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D3.B08.1208081132
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-4B7AC7E43945597E
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-4B7AC7E43945597E
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E:
  dmi.product.name: MacBookPro9,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Mar 18 13:19:28 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1294071/+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 1276564] Re: [Toshiba Satellite Pro N10] Black screen during boot

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [Toshiba Satellite Pro N10] Black screen during boot

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I helped a user set up his Toshiba Satellite Pro N10 during FOSDEM (so
  I cannot easily do further tests).

  Default installation of saucy from USB media, after reboot, screen
  turns purple for five seconds, then black (backlight off). No logo is
  shown on purple background.

  Forums suggest that backlight control and kernel mode switching on
  this hardware do not work together well. Disabling kernel mode switch
  and removing quiet and splash options shows normal boot, but X
  refuses to start (Screens present but no usable configuration).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1276564/+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 1267421] Re: [Clevo P15SM] System freeze 2-3 times daily with Unity

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [Clevo P15SM] System freeze 2-3 times daily with Unity

Status in xorg package in Ubuntu:
  Expired

Bug description:
  My system freezes with Unity up to 2-3 times a day. With Gnome it happens 
much less frequently. Backtrace:
  https://launchpadlibrarian.net/161997766/XorgLogOld.txt

  In 14.04, I tried nvidia-331-updates drivers and I still get freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan  9 10:40:11 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.2.16, 3.11.0-14-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!)
   virtualbox, 4.2.16, 3.11.0-15-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:5106]
   NVIDIA Corporation GK106M [GeForce GTX 770M] [10de:11e0] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:5106]
  InstallationDate: Installed on 2013-11-29 (40 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Notebook P15SM
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed 
root=UUID=366334f2-a6b1-45f4-82f5-791a962fd448 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P15SM
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/06/2013:svnNotebook:pnP15SM:pvrNotApplicable:rvnNotebook:rnP15SM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: P15SM
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Thu Jan  9 08:29:48 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
   NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0)
   NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16562
   vendor LEN
  xserver.version: 2:1.14.3-3ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1267421/+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 1403275] Re: i915 display driver causes crash back to login window

2015-05-01 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  i915 display driver causes crash back to login window

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I've just installed Ubuntu 14.04 server on Dell Latitude E7440 and
  then installed Cinnamon 2.4.5 on top of it. The laptop has an external
  monitor connected through Display Port and a docking station.

  On the first day the system worked perfectly.

  On the second day, the system booted to the login screen (leaving the
  external screen empty but otherwise seemed to be under X11's control),
  it then let me type my username and password but then X exits, shows a
  bit of VT1 with errors then gets back to the login page.

  I found the following error in /var/log/kern.log:

  [drm:intel_dp_complete_link_train] ERROR failed to train DP, aborting

  I found a page which claims to solve this error for 12.04 in the
  second comment in
  https://www.libreoffice.org/bugzilla/show_bug.cgi?id=73694#c2.

  I found that the file linux-
  source-3.13.0/drivers/gpu/drm/i915/intel_dp.c, which is included in
  the tar file /usr/src/linux-source-3.13.0.tar.bz2 (also copied in
  /usr/src/linux-source-3.13.0/linux-source-3.13.0.tar.bz2), from the
  kernel source package linux-source-3.13.0, contains the pre-patch
  lines mentioned in the fix above.

  Would you please consider including this fix in the Ubuntu kernel?

  Thanks,

  --Amos

  For completeness, the patch pointed to from the link above is:

  Link: https://www.libreoffice.org/bugzilla/attachment.cgi?id=92231

  diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
  index 8f17f8fbd0b1..5631cfb874db 100644
  --- a/drivers/gpu/drm/i915/intel_dp.c
  +++ b/drivers/gpu/drm/i915/intel_dp.c
  @@ -847,8 +847,8 @@ intel_dp_compute_config(struct intel_encoder *encoder,
mode_rate = intel_dp_link_required(adjusted_mode-crtc_clock,
   bpp);
   
  - for (clock = 0; clock = max_clock; clock++) {
  - for (lane_count = 1; lane_count = max_lane_count; 
lane_count = 1) {
  + for (lane_count = 1; lane_count = max_lane_count; lane_count 
= 1) {
  + for (clock = 0; clock = max_clock; clock++) {
link_clock = 
drm_dp_bw_code_to_link_rate(bws[clock]);
link_avail = intel_dp_max_data_rate(link_clock,
lane_count);

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Dec 17 12:57:10 2014
  InstallationDate: Installed on 2014-12-15 (1 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403275/+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 1450978] [NEW] package linux-image-extra-3.16.0-30-generic 3.16.0-30.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2015-05-01 Thread Celtic Music
Public bug reported:

The issue occurs when checking for updates. the /boot predefined by the
Ubuntu installation is not large enough to handle several versions of
linux-image-extra-3.xx.x-xx.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: linux-image-extra-3.16.0-30-generic 3.16.0-30.40
ProcVersionSignature: Ubuntu 3.16.0-36.48-generic 3.16.7-ckt9
Uname: Linux 3.16.0-36-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  stephen2670 F pulseaudio
Date: Fri May  1 06:12:16 2015
DuplicateSignature: 
package:linux-image-extra-3.16.0-30-generic:3.16.0-30.40:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=f1508200-3972-4805-9b49-2cacfd67f6ba
InstallationDate: Installed on 2015-03-05 (58 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
MachineType: Dell Inc. Latitude E6520
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-extra-3.16.0-30-generic 3.16.0-30.40 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to utopic on 2015-05-02 (0 days ago)
dmi.bios.date: 07/11/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0NVF5K
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package dist-upgrade need-duplicate-check utopic

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

Title:
  package linux-image-extra-3.16.0-30-generic 3.16.0-30.40 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The issue occurs when checking for updates. the /boot predefined by
  the Ubuntu installation is not large enough to handle several versions
  of linux-image-extra-3.xx.x-xx.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-extra-3.16.0-30-generic 3.16.0-30.40
  ProcVersionSignature: Ubuntu 3.16.0-36.48-generic 3.16.7-ckt9
  Uname: Linux 3.16.0-36-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stephen2670 F pulseaudio
  Date: Fri May  1 06:12:16 2015
  DuplicateSignature: 
package:linux-image-extra-3.16.0-30-generic:3.16.0-30.40:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=f1508200-3972-4805-9b49-2cacfd67f6ba
  InstallationDate: Installed on 2015-03-05 (58 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Latitude E6520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.16.0-30-generic 3.16.0-30.40 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to utopic on 2015-05-02 (0 days ago)
  dmi.bios.date: 07/11/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post 

[Touch-packages] [Bug 1450562] Re: libdrm-intel1 2.4.60 breaks Valvle/Steam games

2015-05-01 Thread Timo Aaltonen
** Bug watch added: freedesktop.org Bugzilla #86043
   https://bugs.freedesktop.org/show_bug.cgi?id=86043

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=86043
   Importance: Unknown
   Status: Unknown

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

Title:
  libdrm-intel1 2.4.60 breaks Valvle/Steam games

Status in X.Org X server:
  Unknown
Status in libdrm package in Ubuntu:
  New

Bug description:
  Referring to this bug: https://github.com/ValveSoftware/steam-for-
  linux/issues/3506

  The only option to get games working again is to take the libdrm-intel
  2.4.56 lib files from the .deb and copy them to your local steam
  install as an override for 2.4.60 system lib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1450562/+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 1450811] [NEW] cmake-extras should be used for coverage testing

2015-05-01 Thread Kyle Fazzari
Public bug reported:

unity-scope-click currently includes cmake modules for coverage testing,
but the modules it uses are already included in cmake-extras. unity-
scope-click should be updated to use cmake-extras in order to keep those
modules consistent between packages.

** Affects: unity-scope-click (Ubuntu)
 Importance: Undecided
 Assignee: Kyle Fazzari (kyle.f)
 Status: New

** Changed in: unity-scope-click (Ubuntu)
 Assignee: (unassigned) = Kyle Fazzari (kyle.f)

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

Title:
  cmake-extras should be used for coverage testing

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  unity-scope-click currently includes cmake modules for coverage
  testing, but the modules it uses are already included in cmake-extras.
  unity-scope-click should be updated to use cmake-extras in order to
  keep those modules consistent between packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1450811/+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 1408110] Re: [XPS13 9333, Realtek ALC3661, Speaker, Internal] fails after a while

2015-05-01 Thread Raymond
20:19:13 david-XPS13-9333 pulseaudio[7977]: [pulseaudio] pid.c: Daemon already 
running.
Jan  6 20:19:13 david-XPS13-9333 pulseaudio[7980]: [pulseaudio] pid.c: Daemon 
already running.
Jan  6 20:21:48 david-XPS13-9333 pulseaudio[8578]: [pulseaudio] pid.c: Daemon 
already running.
Jan  6 20:58:09 david-XPS13-9333 pulseaudio[1523]: [pulseaudio] pid.c: Daemon 
already running.
Jan  6 20:58:15 david-XPS13-9333 pulseaudio[2301]: [pulseaudio] main.c: 
User-configured server at 
{cc26a2cbbf58a8a4a0f3a0e35489ffc9}unix:/run/user/1000/pulse/native, which 
appears to be local. Probing deeper.
Jan  6 20:58:15 david-XPS13-9333 pulseaudio[2325]: [pulseaudio] pid.c: Daemon 
already running.

seem auto spawn frequently

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

Title:
  [XPS13 9333, Realtek ALC3661, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When playing a video via the Videos app, the sound through the
  internal speakers develops crackles and sometimes disappears
  completely.

  I collected the data for the bug report at the instance that the sound
  had failed.

  Using the Sound panel in Systems Settings to test the sound produces
  no response.

  I have also selected the Volume Control app and attempted to switch
  the sound using the Configuration tab and switching the built-in audio
  between Off and Analogue Stereo Output. Sometimes this works and
  sometimes is does not.

  Having left the Videos app running whist typing this, I have noticed
  that the sound seems to start and stop whilst typing via the keyboard.

  I note that the Playback tab in the Volume Control window shows that
  the sound is being produced by the Videos app (the lower ribbon moves
  with the sound amplitude).

  This bug might be associated with intermittent recognition of the
  hardware on startup. The Sound window sometimes shows no audio device.
  At other times, the speakers are given the HDMI menu dropdown but this
  can be corrected by plugging in a pair of headphones and switching
  back to the speakers which then show the correct Test Sound legend.

  I have noticed several instances of the sound cutting out and cutting
  back in whilst typing this report as if the interrupts from the
  keyboard strokes are interrupting the sound connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   david  2288 F...m pulseaudio
   /dev/snd/controlC0:  david  2288 F pulseaudio
   /dev/snd/pcmC1D0p:   david  2288 F...m pulseaudio
   /dev/snd/controlC1:  david  2288 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan  6 21:15:39 2015
  InstallationDate: Installed on 2014-12-11 (26 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS13 9333, Realtek ALC3661, Speaker, Internal] fails after a while
  UpgradeStatus: Upgraded to utopic on 2014-12-11 (25 days ago)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0D13CR
  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.:bvrA05:bd09/11/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1408110/+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 1448775] Re: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash

2015-05-01 Thread Jakub Nietrzeba
I have removed Intel microcode driver from my machine and installed
Nvidia driver and unity with Compiz went up and running. Should I thank
Nvidia or blame Intel?

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

Title:
  Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash

Status in Compiz:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  After upgrade from working machine with 14.10 to 15.10 I'm unable to
  login. Right after password screen I see loading of desktop and I'm
  returned to password prompt again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,imgpng,unitymtgrabhandles,move,compiztoolbox,place,grid,wall,vpswitch,regex,resize,gnomecompat,snap,session,animation,expo,workarounds,ezoom,fade,scale,unityshell]
  Date: Sun Apr 26 23:07:55 2015
  DistUpgraded: 2015-04-26 22:20:44,130 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.26: added
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Toshiba America Info Systems GeForce 315M [1179:fd71]
  InstallationDate: Installed on 2014-11-07 (170 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA SATELLITE C670-10V
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic 
root=UUID=28cea712-ba61-42af-a038-545501a067f8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: TKBSC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.40
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/20/2011:svnTOSHIBA:pnSATELLITEC670-10V:pvrPSC3QE-00700JPL:rvnTOSHIBA:rnTKBSC:rvr1.40:cvnTOSHIBA:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: SATELLITE C670-10V
  dmi.product.version: PSC3QE-00700JPL
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sun Apr 26 23:07:32 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1448775/+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 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.

2015-05-01 Thread Matías Guzmán
Serious question: I understand that this is consider a low priority
issue, but how hard is to update sudo? why can't it just be pushed with
the next update?

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

Title:
  Users can change the clock without authenticating, allowing them to
  locally exploit sudo.

Status in GNOME Control Center:
  Unknown
Status in sudo:
  Unknown
Status in Unity:
  Invalid
Status in policykit-desktop-privileges package in Ubuntu:
  Opinion
Status in sudo package in Ubuntu:
  Triaged
Status in policykit-desktop-privileges source package in Precise:
  Opinion
Status in sudo source package in Precise:
  Triaged
Status in policykit-desktop-privileges source package in Trusty:
  Opinion
Status in sudo source package in Trusty:
  Triaged
Status in policykit-desktop-privileges source package in Utopic:
  Opinion
Status in sudo source package in Utopic:
  Triaged
Status in policykit-desktop-privileges source package in Vivid:
  Opinion
Status in sudo source package in Vivid:
  Triaged

Bug description:
  Under unity and cinnamon, it is possible for a user to turn off
  network-syncronized time and then change the time on the system. It is
  also possible to cat /var/log/auth.log and find the last time a user
  authenticated with sudo, along with which pty they used. If a user had
  used a terminal and successfully authenticated with sudo anytime in
  the past, and left the sudo file in /var/lib/sudo/username/, a
  malicious user could walk up to an unlocked, logged in machine and
  gain sudo without knowing the password for the computer.

  To do this, a user would only need to launch a few terminals, figure
  out which pty they were on via tty, find the an instance in
  /var/log/auth.log where sudo was used on that PTY, and set the clock
  to that time. Once this is done, they can run (for example) sudo -s
  and have a full access terminal.

  1) This has been observed on Ubuntu 13.04, and may work on other versions.
  2) This may have an effect on various window managers, but I confirmed it on 
Unity and Cinnamon
  3) I expected to have to authenticate when I changed the time and date, as I 
do on Gnome and KDE. I also expected to be denied permission to auth.log
  4) I was able to change the system time to whatever I wanted, and view 
auth.log. This was sufficient to access sudo without having to type my password.

  Note: This bug also affects any version of OS X, though the mechanism
  is different. Some versions don't require you to authenticate to
  change the time through the GUI, but some do. No version I've seen
  requires authentication to use the systemsetup command, which can
  alter the time from the command line. This may be an overall bug in
  sudo. Why can I bypass security by changing the time?!

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+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 1373255] Re: Bluetooth indicator is shown twice in the upper panel

2015-05-01 Thread Alberto Salvia Novella
** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

** Changed in: hundredpapercuts
   Status: New = Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided = Medium

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

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

Title:
  Bluetooth indicator is shown twice in the upper panel

Status in One Hundred Papercuts:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth indicator is shown two times in the panel. After disabling
  bluetooth in System - Settings, there is still one indicator being
  shown. Should this come from some ubuntu-touch bluetooth package? I
  have also ubuntu8 installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-bluetooth 0.0.6+14.10.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 24 08:50:17 2014
  InstallationDate: Installed on 2013-11-28 (299 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: Upgraded to utopic on 2014-09-08 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1373255/+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 1450809] Re: DashContent::test_mainNavigation unstable

2015-05-01 Thread Albert Astals Cid
** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Albert Astals Cid (aacid)

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

Title:
  DashContent::test_mainNavigation unstable

Status in unity8 package in Ubuntu:
  New

Bug description:
  While working on the QmlTest refactor / autopkgtest I've noticed that
  the test_mainNavigation test is somewhat flaky:

  testcase result=fail name=DashContent::test_mainNavigation
  failure message=property navigationId
 Actual   (): childmiddle27
 Expected (): childmiddle22 result=fail/
  /testcase

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150423-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  1 16:38:59 2015
  SourcePackage: unity8
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1450809/+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 1443178] Re: Accounts Service always relies on language fallback if never set by the user

2015-05-01 Thread Gunnar Hjalmarsson
I wrote a patch which makes accountsservice set the Language and
FormatsLocale properties automatically as soon as possible and updates
~/.pam_environment accordingly. I built a test version of
accountsservice in my PPA at

https://launchpad.net/~gunnarhj/+archive/ubuntu/accountsservice-test

@Ricardo:
Can you possibly test this version on the phone, and confirm that the fix 
addresses the issue?

@Sebastien:
This means that the behaviour (behind the scenes) changes for everyone. 
Language and regional formats are set for every user, based on 
/etc/default/locale, before the users have touched a GUI for the purpose. I 
made some code rearrangement to achieve it, and the most 'hackish' part is that 
it happens in the user_get_property() function.

I'd appreciate your eyes on it before uploading. Especially:
1. Do you see any drawback with enforcing user settings of language and
   regional formats?
2. Is this an acceptable way to do it?

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

Title:
  Accounts Service always relies on language fallback if never set by
  the user

Status in the base for Ubuntu mobile products:
  New
Status in accountsservice package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  current build number: 169
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-04-12 20:38:14
  version version: 169
  version ubuntu: 20150412
  version device: 20150210
  version custom: 20150412

  This causes a bad side effect when changing volume via indicator-
  sound, as that will cause a sync to accountsservice in order to sync
  the volume. Once that sync happens, it will request the user
  properties, and in case the user doesn't have a valid language at
  /var/lib/AccountsService/users/user, it will always rely on the
  fallback, which would be fine if calculating the fallback wasn't 't so
  cpu or i/o intensive (and that happens multiple times).

  As a test, just flash latest vivid image on mako, don't set any
  language when the wizard shows up, run top and then change the volume
  by pressing volume up/down. This is what I see with mako:

   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  2609 phablet   20   0  499660 121220  52688 S   7.6  6.5   0:41.69 unity8
  5600 phablet   20   03676   1760   1288 R   6.0  0.1   0:00.19 
language-option
  1312 root  20   0  211532  15572  11344 S   1.9  0.8   0:07.25 
unity-system-co
  1316 phablet   20   0   36532   3792   2928 S   1.3  0.2   0:01.66 
accounts-daemon

  And the reason why:
  src/user.c
  ...
  static void
  user_get_property (GObject*object,
 guint   param_id,
 GValue *value,
 GParamSpec *pspec)
  {
  User *user = USER (object);
  ...
  case PROP_LANGUAGE:
  if (user-language)
  g_value_set_string (value, user-language);
  else 
  g_value_set_string (value, user_get_fallback_value 
(user, Language));
  break;
  case PROP_FORMATS_LOCALE:
  if (user-formats_locale)
  g_value_set_string (value, user-formats_locale);
  else 
  g_value_set_string (value, user_get_fallback_value 
(user, FormatsLocale));
  break;

  user_set_property never gets called unless the user changes the system
  language from system-settings or wizard.

  Once you change the language, it will set a valid language at
  /var/lib/AccountsService/users/user, causing this behavior to stop.

  Another bad side effect of this issue is that it takes quite a while
  for accountsservice to reply back to indicator-sound when the sync
  happens, possibly causing sync aborts (as indicator-sound only waits 1
  second before triggering another sync).

  Some possible ways to fix this issue:
  1) Make wizard to set language even when the selected language is already the 
default one;
  2) Change accountsservice to save the fallback value at the first time it 
gets that from the system;

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443178/+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 1447056] Re: Favourite scopes forcefully refreshed when opened from Manage Dash

2015-05-01 Thread Alberto Salvia Novella
@ Pawel Stolowski

You shall mark a bug as in progress only after assigning it to
yourself.

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

** No longer affects: unity-scopes-shell (Ubuntu)

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

Title:
  Favourite scopes forcefully refreshed when opened from Manage Dash

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps:
  * swipe left/right through all favourite scopes to trigger a refresh where 
needed
  * bottom-swipe to Manage Dash
  * select one of the favourite scopes

  Expected:
  * the scope is opened pre-populated

  Current:
  * the scope is refreshed on open

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150409.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 11:46:36 2015
  SourcePackage: unity8
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1447056/+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 1408110] Re: [XPS13 9333, Realtek ALC3661, Speaker, Internal] fails after a while

2015-05-01 Thread Alberto Salvia Novella
** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  [XPS13 9333, Realtek ALC3661, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When playing a video via the Videos app, the sound through the
  internal speakers develops crackles and sometimes disappears
  completely.

  I collected the data for the bug report at the instance that the sound
  had failed.

  Using the Sound panel in Systems Settings to test the sound produces
  no response.

  I have also selected the Volume Control app and attempted to switch
  the sound using the Configuration tab and switching the built-in audio
  between Off and Analogue Stereo Output. Sometimes this works and
  sometimes is does not.

  Having left the Videos app running whist typing this, I have noticed
  that the sound seems to start and stop whilst typing via the keyboard.

  I note that the Playback tab in the Volume Control window shows that
  the sound is being produced by the Videos app (the lower ribbon moves
  with the sound amplitude).

  This bug might be associated with intermittent recognition of the
  hardware on startup. The Sound window sometimes shows no audio device.
  At other times, the speakers are given the HDMI menu dropdown but this
  can be corrected by plugging in a pair of headphones and switching
  back to the speakers which then show the correct Test Sound legend.

  I have noticed several instances of the sound cutting out and cutting
  back in whilst typing this report as if the interrupts from the
  keyboard strokes are interrupting the sound connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   david  2288 F...m pulseaudio
   /dev/snd/controlC0:  david  2288 F pulseaudio
   /dev/snd/pcmC1D0p:   david  2288 F...m pulseaudio
   /dev/snd/controlC1:  david  2288 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan  6 21:15:39 2015
  InstallationDate: Installed on 2014-12-11 (26 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS13 9333, Realtek ALC3661, Speaker, Internal] fails after a while
  UpgradeStatus: Upgraded to utopic on 2014-12-11 (25 days ago)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0D13CR
  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.:bvrA05:bd09/11/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1408110/+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 1450013] Re: dbus puts system to sleep every 30 seconds

2015-05-01 Thread Alberto Salvia Novella
** Changed in: dbus (Ubuntu)
   Importance: Undecided = Critical

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

Title:
  dbus puts system to sleep every 30 seconds

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 14.10 to 15.04, I found that the system was going
  to sleep every 30 seconds. This behavior does not manifest once I log
  into the graphical desktop (Lubuntu), but if I switch over to a
  virtual console, it manifests again.

  A temporary fix has been to make /sys/power/state non-writable.

  At first, I believed the problem was with systemd, but the problem
  continues after switching to upstart.

  I believe the problem is in the dbus package, because I see this every
  30 seconds in /var/log/syslog, coinciding with the laptop going to
  sleep:

  Apr 29 07:46:58 socrates dbus[701]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Apr 29 07:46:58 socrates dbus[701]: [system] Successfully activated service 
'org.freedesktop.systemd1'
  Apr 29 07:46:58 socrates kernel: [  529.289164] init: anacron main process 
(17760) killed by TERM signal
  Apr 29 07:47:01 socrates anacron[18796]: Anacron 2.3 started on 2015-04-29
  Apr 29 07:47:01 socrates anacron[18796]: Will run job `cron.daily' in 5 min.
  Apr 29 07:47:01 socrates anacron[18796]: Will run job `cron.weekly' in 10 min.
  Apr 29 07:47:01 socrates anacron[18796]: Jobs will be executed sequentially
  Apr 29 07:47:30 socrates acpid: client connected from 19009[0:0]
  Apr 29 07:47:30 socrates acpid: 1 client rule loaded

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Apr 29 07:53:42 2015
  InstallationDate: Installed on 2010-04-30 (1824 days ago)
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to vivid on 2015-04-27 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1450013/+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 1450811] Re: cmake-extras should be used for coverage testing

2015-05-01 Thread Launchpad Bug Tracker
** Branch linked: lp:~kyle.f/unity-scope-click/utilize_cmake_extras

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

Title:
  cmake-extras should be used for coverage testing

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  unity-scope-click currently includes cmake modules for coverage
  testing, but the modules it uses are already included in cmake-extras.
  unity-scope-click should be updated to use cmake-extras in order to
  keep those modules consistent between packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1450811/+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 1324142] Re: Support providing fallback images

2015-05-01 Thread Michael Zanetti
** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Albert Astals Cid (aacid)

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

Title:
  Support providing fallback images

Status in Thumbnail generator for all kinds of files:
  New
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  If the URI for a scope result icon can not be loaded, the scope result
  is not easily visible.

  To counter this, the shell should replace the result image with a
  fallback image if the Image QML component changes to the Error state.
  At a minimum a single standard fallback image would be sufficient, but
  letting the scope pick a custom fallback via the category renderer
  template would be better.

  One reason I'd like to see this is so we can switch the album art
  image provider to stop returning a fallback image.  This has been
  requested by the music-app guys, and seems sensible since we might
  want different fallbacks in different contexts:

  https://code.launchpad.net/~jamesh/thumbnailer/no-fallback-
  albumart/+merge/219460

  It might also be useful for remote scopes using http: URIs for result
  icons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thumbnailer/+bug/1324142/+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 542668] Re: cups unable to get connection from remote system on port 631

2015-05-01 Thread Pascal De Vuyst
By default no iptables firewall rules apply in Ubuntu, you can check with the 
following command: sudo iptables -L (a basic tutorial can be found here: 
https://help.ubuntu.com/community/IptablesHowTo)
Ubuntu 10.04 is no longer supported, please upgrade to a supported release 
Ubuntu 14.04 LTS or higher and let us know if this still is a problem in that 
case provide the output of the above command.

** Changed in: cups (Ubuntu)
   Status: New = Incomplete

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

Title:
  cups unable to get connection from remote system on port 631

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  Running on Lucid i386 I have been unable to access the cups interface
  from a remote system using:

  http://servername:631/

  The browser would report no connection available and not receive
  anything from the host machine.

  The local machine would login correctly. I had enabled remote
  administation and shared the printer with Internet printing enabled.

  This was solved by installing firestarter and then looking for
  connections from the remote system and telling it to allow connections
  from all for this port.

  I am a little bit unsure of the internals but I know this has not been
  a problem on previous versions of cups/ubuntu.

  cups:
Installed: 1.4.2-9
Candidate: 1.4.2-9
Version table:
   *** 1.4.2-9 0
  500 http://gb.archive.ubuntu.com/ubuntu/ lucid/main Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: i386
  Date: Sat Mar 20 12:38:14 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318)
  Lpstat:
   device for LBP3010: ccp://localhost:59687
   device for LBP3010-LBP3018-LBP3050: usb://Canon/LBP3010/LBP3018/LBP3050
  Package: cups 1.4.2-9
  Papersize: a4
  PpdFiles:
   LBP3010: Canon LBP3010/LBP3018/LBP3050 CAPT (UK)
   LBP3010-LBP3018-LBP3050: Canon LBP3010/LBP3018/LBP3050 CAPT (UK)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic 
root=UUID=84de763d-0e1f-4c77-b91a-e32343dae65e ro quiet splash
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SourcePackage: cups
  Uname: Linux 2.6.32-16-generic i686
  dmi.bios.date: 01/09/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: NF-MCP61
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2007:svn:pn:pvr:rvn:rnNF-MCP61:rvr:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/542668/+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 1450808] [NEW] Meta-key shortcuts do not work with Qt 5.4.1

2015-05-01 Thread Kåre Särs
Public bug reported:

Meta-key shortcuts do not work with the xcb platform plugin. The issue
is fixed upstream and will be released with qtbase 5.4.2, but that
version is not released yet.

Upstream bug report:
https://bugreports.qt.io/browse/QTBUG-43572

Upstram not yet released fix:
https://codereview.qt-project.org/#/c/104506/

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Meta-key shortcuts do not work with Qt 5.4.1

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Meta-key shortcuts do not work with the xcb platform plugin. The issue
  is fixed upstream and will be released with qtbase 5.4.2, but that
  version is not released yet.

  Upstream bug report:
  https://bugreports.qt.io/browse/QTBUG-43572

  Upstram not yet released fix:
  https://codereview.qt-project.org/#/c/104506/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1450808/+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 1399734] Re: Current tab is not highlighted

2015-05-01 Thread Alberto Salvia Novella
** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided = High

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

Title:
  Current tab is not highlighted

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  With the Ambiance or Radiance theme, in windows using a GtkNotebook
  the current tab is not highlighted to distinguish it from hidden tabs.
  In some apps you can just about see a faint line under the inactive
  tabs, but some apps, such as roxterm, don't use the border option, so
  it's impossible to tell which tab is selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: light-themes 14.04+14.10.20141015-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec  5 17:27:41 2014
  InstallationDate: Installed on 2014-06-13 (174 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1399734/+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 1450809] [NEW] DashContent::test_mainNavigation unstable

2015-05-01 Thread Michał Sawicz
Public bug reported:

While working on the QmlTest refactor / autopkgtest I've noticed that
the test_mainNavigation test is somewhat flaky:

testcase result=fail name=DashContent::test_mainNavigation
failure message=property navigationId
   Actual   (): childmiddle27
   Expected (): childmiddle22 result=fail/
/testcase

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity8 8.02+15.04.20150423-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
Uname: Linux 3.19.0-14-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May  1 16:38:59 2015
SourcePackage: unity8
SystemImageInfo:
 current build number: 0
 device name: 
 channel: daily
 last update: Unknown
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

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

Title:
  DashContent::test_mainNavigation unstable

Status in unity8 package in Ubuntu:
  New

Bug description:
  While working on the QmlTest refactor / autopkgtest I've noticed that
  the test_mainNavigation test is somewhat flaky:

  testcase result=fail name=DashContent::test_mainNavigation
  failure message=property navigationId
 Actual   (): childmiddle27
 Expected (): childmiddle22 result=fail/
  /testcase

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150423-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  1 16:38:59 2015
  SourcePackage: unity8
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1450809/+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 777271] Re: Cannot print with Samsung ML-1910

2015-05-01 Thread Pascal De Vuyst
Probably only supported with the proprietary Samsung driver if the splix driver 
does not work.
Not a cups bug.

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

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

Title:
  Cannot print with Samsung ML-1910

Status in cups package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: cups

  For some reason i cannot print to my new Samsung ML-1910.

  I have connected the printer via USB to my headless 10.04 server.
  I added the printer via the webinterface of CUPS, and supplied the Samsung 
ppd file.
  I'm printing to the printer through a Samba share with my Windows laptops.
  This used to go fine with my old Samsung ML-2010 printer, but that one broke 
down the other day.

  The printer accepts the print jobs, sound arises from the printer, job
  is completed according to CUPS, but no print out of the printer.

  I then added the rastertosamsungspl to /usr/lib/cups/filter, like detailed 
here: http://forums.debian.net/viewtopic.php?f=16t=57364
  Restarted the smbd and cups services, but still only sound, no print.

  I then tried the three Splix  ppd's, of which one should support the
  ML-1910,
  https://launchpad.net/ubuntu/natty/+source/splix/2.0.0+20110219-0ubuntu1

  Is it a problem that I use natty splix drivers? Because still no joy:
  only sound, but no print.

  On another sad note, directly connecting it to a Windows XP/7 machine
  makes it not only make sound, but print as well. So the printer seems
  to be fine.

  Details: Ubuntu 10.04.2 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/777271/+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 1426589] Re: tc class statistics rates are all zero after upgrade to Trusty

2015-05-01 Thread JuanJo Ciarlante
As per comment #13, I've added the following tags:
* kernel-fixed-upstream-3.10 
* kernel-bug-exists-upstream kernel-bug-exists-upstream-3.11rc1 
kernel-bug-exists-upstream-4.1-rc1

Please correct them if I misunderstood the naming convention,

FYI my narrowed bisect corresponds to:
*** OK ***:
linux (3.10.76-031076.201504291035) saucy; urgency=low

  * Mainline build at commit: v3.10.76


*** BAD ***:
linux (3.11.0-031100rc1.201307141935) saucy; urgency=low

  * Mainline build at commit: v3.11-rc1

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

Title:
  tc class statistics rates are all zero after upgrade to Trusty

Status in iproute2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading an Ubuntu server from Lucid - Precise - Trusty the command:
  tc -s class show dev eth0
  no longer shows rates for my classification bands. This worked in Lucid, but 
not sure if something changed, or if I need to set some system configuration to 
make it work again. My current non-working version is:

  $ dpkg -s iproute2
  Package: iproute2
  Status: install ok installed
  Priority: important
  Section: net
  Installed-Size: 1147
  Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
  Architecture: amd64
  Multi-Arch: foreign
  Version: 3.12.0-2
  Replaces: iproute
  Provides: arpd
  Depends: libc6 (= 2.14), libdb5.3
  Recommends: libatm1 (= 2.4.1-17~), libxtables10
  Suggests: iproute2-doc
  Conflicts: arpd, iproute ( 2013-1)
  Conffiles:
   /etc/iproute2/group 3aea2c0e0dd75e13a5f8f48f2936915f
   /etc/iproute2/ematch_map b91e7f9b26918449bade9573f8871d61
   /etc/iproute2/rt_realms 7137bdf40e8d58c87ac7e3bba503767f
   /etc/iproute2/rt_tables a1313318d6778fe6b8c680248ef5a463
   /etc/iproute2/rt_dsfield 4264d5c7c8298300185aa04e1a736934
   /etc/iproute2/rt_protos 95ce0b4b5b79f5a8a45941fb418a904c
   /etc/iproute2/rt_scopes 6298b8df09e9bda23ea7da49021ca457
  Description: networking and traffic control tools
   The iproute2 suite is a collection of utilities for networking and
   traffic control.
   .
   These tools communicate with the Linux kernel via the (rt)netlink
   interface, providing advanced features not available through the
   legacy net-tools commands 'ifconfig' and 'route'.
  Original-Maintainer: Debian iproute2 Maintainers ah-ipro...@debian.org
  Homepage: http://www.linux-foundation.org/en/Net:Iproute2

  Here is the current output of the command, note that 'rate 0bit 0pps'
  is common to all classes, in Lucid this would produce non-zero values
  for active traffic:

  $ tc -s class show dev eth0
  class htb 2:1 root rate 4000Kbit ceil 1Kbit burst 1600b cburst 1600b
   Sent 140162776 bytes 377793 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 23022 borrowed: 0 giants: 0
   tokens: 46812 ctokens: 18725

  class htb 2:2 parent 2:1 leaf 3: prio 0 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 2021584 bytes 6949 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 6505 borrowed: 189 giants: 0
   tokens: 187250 ctokens: 46812

  class htb 2:3 parent 2:1 leaf 4: prio 1 rate 2000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 16695548 bytes 216855 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 216846 borrowed: 9 giants: 0
   tokens: 94375 ctokens: 47187

  class htb 2:4 parent 2:1 leaf 5: prio 2 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 2963040 bytes 46619 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 46619 borrowed: 0 giants: 0
   tokens: 193250 ctokens: 48312

  class htb 2:5 parent 2:1 leaf 6: prio 3 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 6 bytes 745 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 745 borrowed: 0 giants: 0
   tokens: 183000 ctokens: 45750

  class htb 2:6 parent 2:1 leaf 7: prio 4 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 80608262 bytes 79347 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 50544 borrowed: 13902 giants: 0
   tokens: 190750 ctokens: 47687

  class htb 2:7 parent 2:1 leaf 8: prio 5 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 37606539 bytes 26129 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 5617 borrowed: 8922 giants: 0
   tokens: -178485 ctokens: 24056

  class htb 2:8 parent 2:1 leaf 9: prio 6 rate 512000bit ceil 1000Kbit burst 
1600b cburst 1600b
   Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 0 borrowed: 0 giants: 0
   tokens: 390625 ctokens: 20

  class htb 2:9 parent 

[Touch-packages] [Bug 1450712] [NEW] its lots of little things that keep going wrong

2015-05-01 Thread Miss Wendy
Public bug reported:

Browsers never work properly(regaurdless of which) . . . . Movie players
always play up ...constant freezing of display

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
Uname: Linux 3.16.0-26-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  304.125  Mon Dec  1 19:55:52 PST 
2014
 GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.7-0ubuntu8.4
Architecture: i386
BootLog:
 Loading the saved-state of the serial devices... 
  * Setting up X socket directories...    
[ OK ]
  * Restoring resolver state...    
[ OK ]
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri May  1 16:02:54 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
 ndiswrapper, 1.59, 3.16.0-26-generic, i686: installed
 nvidia-304, 304.125, 3.16.0-26-generic, i686: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0504]
 NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0505]
InstallationDate: Installed on 2014-09-13 (229 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
MachineType: Acer Aspire 5750G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=b065294c-1fc8-4a93-9c8d-86c1c4680f5d ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section Device
 Identifier Default Card 0
 BusID PCI:0@0:2:0
 EndSection
dmi.bios.date: 04/07/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.09
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE50_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.09
dmi.modalias: 
dmi:bvnAcer:bvrV1.09:bd04/07/2011:svnAcer:pnAspire5750G:pvrV1.09:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.09:
dmi.product.name: Aspire 5750G
dmi.product.version: V1.09
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.libdrm2: libdrm2 2.4.60+git20150416.0d78b37b-0ubuntu0ricotz2~utopic
version.libgl1-mesa-dri: libgl1-mesa-dri 
10.6.0~git20150423.125574d1-0ubuntu0ricotz~utopic
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
10.6.0~git20150423.125574d1-0ubuntu0ricotz~utopic
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1~utopic1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Apr 29 02:02:27 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.1.901-1ubuntu1~utopic1
xserver.video_driver: modesetting

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


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

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

Title:
  its lots of little things that keep going wrong

Status in xorg package in Ubuntu:
  New

Bug description:
  Browsers never work properly(regaurdless of which) . . . . Movie
  players always play up ...constant freezing of display

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.125  Mon Dec  1 19:55:52 
PST 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu8.4
  Architecture: i386
  BootLog:
   Loading the saved-state of the serial 

[Touch-packages] [Bug 1361610] Re: libPCRE3 8.31 regex matching is not working

2015-05-01 Thread Yoshiki Kanemoto
LD_PRELOAD=/usr/lib/libPocoFoundation.so changes the result of proof-of-
concept (Poco and boost dependent code are removed from proof-of-
concept)

$ g++ regex.cc -lpcre
$ ./a.out 
PCRE 8.31 2012-07-06
PCRE  match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE  match 123456789 to pattern ^[0-9]{10} matches? no
$ LD_PRELOAD=/usr/lib/libPocoFoundation.so ./a.out 
PCRE 8.31 2012-07-06
PCRE  match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE  match 123456789 to pattern ^[0-9]{10} matches? yes

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

Title:
  libPCRE3 8.31 regex matching is not working

Status in pcre3 package in Ubuntu:
  Confirmed
Status in poco package in Ubuntu:
  Confirmed

Bug description:
  It looks like that libPCRE3 8.31 included in Ubuntu 13.10 does not
  handle regex matching alright. This also affects the libPocoFoundation
  RegularExpression classes.

  I attached a proof-of-concept which tests a good and bad heystack
  string to a regex pattern with Poco, Boost and PCRE. I tested it on
  two different machines with the following output:

  Ubuntu 13.10 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013 
i686 i686 i686 GNU/Linux
  Poco 0x01030600 on Linux 3.11.0-13-generic @ i686
  Poco  match 1234567890 to pattern ^[0-9]{10} matches? no -- NOT CORRECT
  Poco  match 123456789 to pattern ^[0-9]{10} matches? no
  Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
  Boost match 123456789 to pattern ^[0-9]{10} matches? no
  PCRE 8.31 2012-07-06
  PCRE  match 1234567890 to pattern ^[0-9]{10} matches? yes
  PRCE  match 123456789 to pattern ^[0-9]{10} matches? yes -- NOT CORRECT

  Ubuntu 12.04.3 LTS  3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 
15:31:16 UTC 2013 i686 i686 i386 GNU/Linux
  Poco 0x01030600 on Linux 3.8.0-29-generic @ i686
  Poco  match 1234567890 to pattern ^[0-9]{10} matches? yes -- OK
  Poco  match 123456789 to pattern ^[0-9]{10} matches? no
  Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
  Boost match 123456789 to pattern ^[0-9]{10} matches? no
  PCRE 8.12 2011-01-15
  PCRE  match 1234567890 to pattern ^[0-9]{10} matches? yes
  PRCE  match 123456789 to pattern ^[0-9]{10} matches? no -- OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1361610/+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 1429041] Re: Autoremoval not working reliably

2015-05-01 Thread Michael Vogt
** Changed in: apt (Ubuntu)
   Status: New = Fix Released

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

Title:
  Autoremoval not working reliably

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Utopic:
  New

Bug description:
  [ SRU Justification ]
  The APT::Never-MarkAuto-Sections in precise is not working reliable. Apt is 
not always looking at the section of the version to be installed but instead 
may look at a random versions section.

  This breaks apt-get autoremove for no-longer-required kernels.

  [ Test Case ]
  See comment #2

  [ Regression Potential ]
  Slim to none, assuming the test case passes well.  We can't really make this 
more broken than it is, except by suddenly marking ALL things manual (or all 
things auto), which the testcase would show.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429041/+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 1450712] Re: its lots of little things that keep going wrong

2015-05-01 Thread Miss Wendy
Timestamp: 01/05/15 16:06:36
Error: TypeError: messageManager is undefined
Source File: resource://gre/modules/addons/XPIProvider.jsm - 
jar:file:///home/willowzz/.mozilla/firefox/qecsr9ro.default/extensions/jid1-qj0w91o64n7...@jetpack.xpi!/bootstrap.js
 - resource://gre/modules/commonjs/toolkit/loader.js - 
resource://gre/modules/commonjs/sdk/context-menu.js
Line: 690  
 this is a example of the constant browser issues .with java. and or 
flashadobe.

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

Title:
  its lots of little things that keep going wrong

Status in xorg package in Ubuntu:
  New

Bug description:
  Browsers never work properly(regaurdless of which) . . . . Movie
  players always play up ...constant freezing of display

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.125  Mon Dec  1 19:55:52 
PST 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu8.4
  Architecture: i386
  BootLog:
   Loading the saved-state of the serial devices... 
* Setting up X socket directories...    
[ OK ]
* Restoring resolver state...    
[ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri May  1 16:02:54 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   ndiswrapper, 1.59, 3.16.0-26-generic, i686: installed
   nvidia-304, 304.125, 3.16.0-26-generic, i686: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0504]
   NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0505]
  InstallationDate: Installed on 2014-09-13 (229 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  MachineType: Acer Aspire 5750G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=b065294c-1fc8-4a93-9c8d-86c1c4680f5d ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section Device
   Identifier Default Card 0
   BusID PCI:0@0:2:0
   EndSection
  dmi.bios.date: 04/07/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnAcer:bvrV1.09:bd04/07/2011:svnAcer:pnAspire5750G:pvrV1.09:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.09:
  dmi.product.name: Aspire 5750G
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.libdrm2: libdrm2 2.4.60+git20150416.0d78b37b-0ubuntu0ricotz2~utopic
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.6.0~git20150423.125574d1-0ubuntu0ricotz~utopic
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.6.0~git20150423.125574d1-0ubuntu0ricotz~utopic
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1~utopic1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Apr 29 02:02:27 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.1.901-1ubuntu1~utopic1
  xserver.video_driver: modesetting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1450712/+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 1361610] Re: libPCRE3 8.31 regex matching is not working

2015-05-01 Thread Yoshiki Kanemoto
In Ubuntu 14.04, libPocoFoundation.so has some global variables of pcre.
I found the executable which links both libPocoFoundation.so and libpcre.so 
outputs wrong results by pcre functions.

nm -D --defined-only /usr/lib/libPocoFoundation.so  | grep pcre
00110800 R _pcre_OP_lengths
0010f2a0 R _pcre_ucd_records
0010d0a0 R _pcre_ucd_stage1
001032a0 R _pcre_ucd_stage2
001106e0 R _pcre_ucp_gentype
001107e0 R _pcre_utf8_table1
001107d8 R _pcre_utf8_table1_size
001107c0 R _pcre_utf8_table2
001107a0 R _pcre_utf8_table3
00110760 R _pcre_utf8_table4
00110120 R _pcre_utt
001103e0 R _pcre_utt_names
00110100 R _pcre_utt_size

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

Title:
  libPCRE3 8.31 regex matching is not working

Status in pcre3 package in Ubuntu:
  Confirmed
Status in poco package in Ubuntu:
  Confirmed

Bug description:
  It looks like that libPCRE3 8.31 included in Ubuntu 13.10 does not
  handle regex matching alright. This also affects the libPocoFoundation
  RegularExpression classes.

  I attached a proof-of-concept which tests a good and bad heystack
  string to a regex pattern with Poco, Boost and PCRE. I tested it on
  two different machines with the following output:

  Ubuntu 13.10 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013 
i686 i686 i686 GNU/Linux
  Poco 0x01030600 on Linux 3.11.0-13-generic @ i686
  Poco  match 1234567890 to pattern ^[0-9]{10} matches? no -- NOT CORRECT
  Poco  match 123456789 to pattern ^[0-9]{10} matches? no
  Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
  Boost match 123456789 to pattern ^[0-9]{10} matches? no
  PCRE 8.31 2012-07-06
  PCRE  match 1234567890 to pattern ^[0-9]{10} matches? yes
  PRCE  match 123456789 to pattern ^[0-9]{10} matches? yes -- NOT CORRECT

  Ubuntu 12.04.3 LTS  3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 
15:31:16 UTC 2013 i686 i686 i386 GNU/Linux
  Poco 0x01030600 on Linux 3.8.0-29-generic @ i686
  Poco  match 1234567890 to pattern ^[0-9]{10} matches? yes -- OK
  Poco  match 123456789 to pattern ^[0-9]{10} matches? no
  Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
  Boost match 123456789 to pattern ^[0-9]{10} matches? no
  PCRE 8.12 2011-01-15
  PCRE  match 1234567890 to pattern ^[0-9]{10} matches? yes
  PRCE  match 123456789 to pattern ^[0-9]{10} matches? no -- OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1361610/+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 850798] Re: printer HP LaserJet 6P prints wrong pages (with ubuntu 8.04 work very well)

2015-05-01 Thread Pascal De Vuyst
** Package changed: cups (Ubuntu) = system-config-printer (Ubuntu)

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

Title:
  printer HP LaserJet 6P prints wrong pages (with ubuntu 8.04 work very
  well)

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  with ubuntu 11.04 and now i can confirm the problem also for 12.04 with the 
printer HP LaserJet 6P that print crazy pages!
  i can confirm that the same printer with ubuntu 10.04 work very well!

  the installed cups version is the ufficial ubuntu package (updated
  with ufficial repository)

  on ubuntu 11.04 i reported this(i don't remember how take out it on
  ubuntu 12.04):

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.4
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  Architecture: amd64
  CupsErrorLog:

  Date: Thu Sep 15 12:28:37 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  Lpstat: device for Hewlett-Packard-HP-LaserJet-6P: 
hp:/par/HP_LaserJet_6P?device=/dev/parport0
  Lsusb:
   Bus 003 Device 002: ID 0d8c:013c C-Media Electronics, Inc.
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Packard Bell NEC IMEDIA 6419
  Papersize: a4
  PpdFiles: Hewlett-Packard-HP-LaserJet-6P: HP LaserJet 6P/6MP - PostScript
  ProcEnviron:
   LANGUAGE=it_IT:en
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=15144706-9b45-47f1-98eb-54b53b977de3 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2005
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080012
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7168
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080012:bd05/04/2005:svnPackardBellNEC:pnIMEDIA6419:pvrPB34105306:rvnNECCOMPUTERSINTERNATIONAL:rnMS-7168:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: IMEDIA 6419
  dmi.product.version: PB34105306
  dmi.sys.vendor: Packard Bell NEC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/850798/+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 1443869] Re: [OOBE] New wizard in Vivid doesn't excercise indicator gesture

2015-05-01 Thread Magdalena Mirowicz
** Changed in: ubuntu-ux
 Assignee: (unassigned) = Andreea Pirvu (andreea-pirvu)

** Changed in: ubuntu-ux
   Importance: Undecided = Medium

** Changed in: ubuntu-ux
   Importance: Medium = High

** Changed in: ubuntu-ux
   Status: New = Triaged

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

Title:
  [OOBE] New wizard in Vivid doesn't excercise indicator gesture

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  Test case.
  - Flash the device with a recent Vivid image.
  - Complete the wizard.
  - Go through edges demo.

  Expected result.
  - Edges demo exercises the indicator gesture.

  Actual result.
  - Indicators aren't opened.

  current build number: 184
  device name: krillin
  channel: ubuntu-touch/devel-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1443869/+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 1450843] [NEW] ssh-add should print error message when entered key password is wrong

2015-05-01 Thread Karl-Philipp Richter
Public bug reported:

Currently the user has to check `echo $?` to figure out that the key
hasn't been added and very likely assumes that it has been added in case
the password was wrong and the key couldn't be added with `ssh-add`.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: openssh-client 1:6.7p1-5ubuntu1
Uname: Linux 4.0.1-040001-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May  1 18:36:37 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-04-02 (28 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions:
 ssh-askpass   N/A
 libpam-sshN/A
 keychain  N/A
 ssh-askpass-gnome 1:6.7p1-5ubuntu1
SSHClientVersion: OpenSSH_6.7p1 Ubuntu-5ubuntu1, OpenSSL 1.0.1f 6 Jan 2014
SourcePackage: openssh
SystemImageInfo:
 current build number: 0
 device name: 
 channel: daily
 last update: Unknown
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

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

Title:
  ssh-add should print error message when entered key password is wrong

Status in openssh package in Ubuntu:
  New

Bug description:
  Currently the user has to check `echo $?` to figure out that the key
  hasn't been added and very likely assumes that it has been added in
  case the password was wrong and the key couldn't be added with `ssh-
  add`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openssh-client 1:6.7p1-5ubuntu1
  Uname: Linux 4.0.1-040001-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  1 18:36:37 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-02 (28 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.7p1-5ubuntu1
  SSHClientVersion: OpenSSH_6.7p1 Ubuntu-5ubuntu1, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1450843/+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 1446298] Re: Should show power dialog when turning on screen with a long-press

2015-05-01 Thread Magdalena Mirowicz
** Changed in: ubuntu-ux
   Status: New = Triaged

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Olga Kemmet (olga-kemmet)

** Changed in: ubuntu-ux
   Importance: Undecided = Medium

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

Title:
  Should show power dialog when turning on screen with a long-press

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  To work around the power dialog appearing on resume, I implemented a
  band-aid fix [1] that prevented showing the dialog when the screen was
  off.  But I didn't think of the case where you are waking up your
  device with an intentional long-press to show the power dialog.

  Currently, we don't show the dialog, we just turn on the screen.
  Ideally we'd also show the power dialog.

  This is a break-out bug from bug 1445662.

  [1] https://code.launchpad.net/~mterry/unity8/no-shutdown-dialog-
  while-suspended/+merge/246445

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1446298/+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 1449295] Re: [Icons] Inconsistent tranparent app icon handling

2015-05-01 Thread Magdalena Mirowicz
** Summary changed:

- Inconsistent tranparent app icon handling
+ [Icons] Inconsistent tranparent app icon handling

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

Title:
  [Icons] Inconsistent tranparent app icon handling

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  I uploaded an app with an icon that had a transparent background.

  The Ubuntu Store scope renders it with a white background.
  The dash renders it transparent.
  The launcher renders it transparent.

  I think the Store is doing the right thing. But any solution is fine,
  as long as it is consistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1449295/+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 1450213] Re: {SDK] cursor handle should not be visible if field is empty

2015-05-01 Thread Magdalena Mirowicz
** Summary changed:

- cursor handle should not be visible if field is empty
+ {SDK] cursor handle should not be visible if field is empty

** Changed in: ubuntu-ux
   Status: New = Triaged

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Jouni Helminen (jounihelminen)

** Changed in: ubuntu-ux
   Importance: Undecided = Medium

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

Title:
  {SDK] cursor handle should not be visible if field is empty

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  On arale
  ui-tookit version 1.2.1485+15.04.20150429-0ubuntu1

  The big blue cursor handle should not be visible if the text field is
  empty, as dragging does nothing. It should only be displayed if the
  field has text (or spaces) in it where dragging would make sense.

  Steps to reproduce:

  1) reboot phone
  2) launch messaging-app
  3) swipe up from bottom to create new messaage

  Expected results:
  - cursor should be blinking in field
  - no text handle should be visible

  Actual results:
  - cursor is blinking in field
  - big blue cursor handle is visible

  NOTE, you can repeat this same thing by pressing the Search icon in
  the dash. The blue cursor appears even when nothing in paste buffer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450213/+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 1268673] Re: Unity Dash should propose terminal app when taping cmd

2015-05-01 Thread Launchpad Bug Tracker
** Branch linked: lp:~reversiblean/ubuntu/vivid/gnome-terminal/fix-
for-1268673

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

Title:
  Unity Dash should propose terminal app when taping cmd

Status in Unity:
  New
Status in gnome-terminal package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  New

Bug description:
  Hi

  This is not a pure bug, but an idea to made life of lot of people
  simpler. More of that I'm not sure this is more related to Gnome
  Terminal than Unity). But it's for me an ergonomy bug. I explain :

  In my job I have to use Windows terminal a lot. As I do with 'term' in
  unity, to open it I usually press Windows / Super Key and enter
  'CMD'. Here is the problem : each time (very often) I come back on
  Ubuntu I try to search 'CMD' in the dash to open gnome-terminal. Of
  course : no result ! The idea is to have Gnome terminal (and probably
  other terminal app installed on the system) being found when searching
  cmd. This would avoid people like me to every time make the mistake,
  and newcomers to Ubuntu (student in Network/Telecoms/Programming...)
  would find what they search instantly what they search : better first
  impression of being home when first days on the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Jan 13 18:46:16 2014
  InstallationDate: Installed on 2014-01-12 (1 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1268673/+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 1450207] Re: [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] volume slider problem

2015-05-01 Thread Raymond
control.6 {
iface MIXER
name 'Capture Source'
value 'Headphone Mic'
comment {
access 'read write'
type ENUMERATED
count 1
item.0 'Headphone Mic'
item.1 'Headset Mic'
item.2 'Internal Mic'
}
}


the capture source seem determine the type of combo jack plugged when codec 
cannot differentiate headset headphone or Mic

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

Title:
  [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When starting Ubuntu from boot-up, sometimes the F11 and F12 keys have
  no effect on the sound volume, even though it can be controlled by the
  slider in the Sound window.

  This can often be restored by re-booting the OS.

  When the F11 and F12 keys are working as expected, a pop is heard in
  the speakers indicating a change of volume level. The output volume
  slider in the Sound window has the same effect. However, when
  adjusting the volume using the slider in the pull-down menu at the top
  right of the desktop, the sound level is adjusted as seen by the
  slider moving in the Sound window. However, this produces no audible
  pop as occurs when the volume level is adjusted by other methods.

  Ubuntu 15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1590 F pulseaudio
   /dev/snd/controlC1:  david  1590 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 29 22:13:15 2015
  InstallationDate: Installed on 2015-04-23 (6 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Volume slider, or mixer problems
  Title: [XPS13 9333, Intel Haswell HDMI, Digital Out, HDMI] volume slider 
problem
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (6 days ago)
  dmi.bios.date: 09/11/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0D13CR
  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.:bvrA05:bd09/11/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450207/+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 1426589] Re: tc class statistics rates are all zero after upgrade to Trusty

2015-05-01 Thread JuanJo Ciarlante
FYI peeking at patch-3.11-rc1, shows

[...]
-   struct gnet_stats_rate_est  tcfc_rate_est;
+   struct gnet_stats_rate_est64tcfc_rate_est;

with its correspondent addition:

+ * struct gnet_stats_rate_est64 - rate estimator
+ * @bps: current byte rate
+ * @pps: current packet rate
+ */
+struct gnet_stats_rate_est64 {
+   __u64   bps;
+   __u64   pps;
+};


FYI modding iproute2 3.19.0 to show EST64 vs EST(32) shows
tc using EST32:
http://paste.ubuntu.com/10963208/

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

Title:
  tc class statistics rates are all zero after upgrade to Trusty

Status in iproute2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading an Ubuntu server from Lucid - Precise - Trusty the command:
  tc -s class show dev eth0
  no longer shows rates for my classification bands. This worked in Lucid, but 
not sure if something changed, or if I need to set some system configuration to 
make it work again. My current non-working version is:

  $ dpkg -s iproute2
  Package: iproute2
  Status: install ok installed
  Priority: important
  Section: net
  Installed-Size: 1147
  Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
  Architecture: amd64
  Multi-Arch: foreign
  Version: 3.12.0-2
  Replaces: iproute
  Provides: arpd
  Depends: libc6 (= 2.14), libdb5.3
  Recommends: libatm1 (= 2.4.1-17~), libxtables10
  Suggests: iproute2-doc
  Conflicts: arpd, iproute ( 2013-1)
  Conffiles:
   /etc/iproute2/group 3aea2c0e0dd75e13a5f8f48f2936915f
   /etc/iproute2/ematch_map b91e7f9b26918449bade9573f8871d61
   /etc/iproute2/rt_realms 7137bdf40e8d58c87ac7e3bba503767f
   /etc/iproute2/rt_tables a1313318d6778fe6b8c680248ef5a463
   /etc/iproute2/rt_dsfield 4264d5c7c8298300185aa04e1a736934
   /etc/iproute2/rt_protos 95ce0b4b5b79f5a8a45941fb418a904c
   /etc/iproute2/rt_scopes 6298b8df09e9bda23ea7da49021ca457
  Description: networking and traffic control tools
   The iproute2 suite is a collection of utilities for networking and
   traffic control.
   .
   These tools communicate with the Linux kernel via the (rt)netlink
   interface, providing advanced features not available through the
   legacy net-tools commands 'ifconfig' and 'route'.
  Original-Maintainer: Debian iproute2 Maintainers ah-ipro...@debian.org
  Homepage: http://www.linux-foundation.org/en/Net:Iproute2

  Here is the current output of the command, note that 'rate 0bit 0pps'
  is common to all classes, in Lucid this would produce non-zero values
  for active traffic:

  $ tc -s class show dev eth0
  class htb 2:1 root rate 4000Kbit ceil 1Kbit burst 1600b cburst 1600b
   Sent 140162776 bytes 377793 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 23022 borrowed: 0 giants: 0
   tokens: 46812 ctokens: 18725

  class htb 2:2 parent 2:1 leaf 3: prio 0 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 2021584 bytes 6949 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 6505 borrowed: 189 giants: 0
   tokens: 187250 ctokens: 46812

  class htb 2:3 parent 2:1 leaf 4: prio 1 rate 2000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 16695548 bytes 216855 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 216846 borrowed: 9 giants: 0
   tokens: 94375 ctokens: 47187

  class htb 2:4 parent 2:1 leaf 5: prio 2 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 2963040 bytes 46619 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 46619 borrowed: 0 giants: 0
   tokens: 193250 ctokens: 48312

  class htb 2:5 parent 2:1 leaf 6: prio 3 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 6 bytes 745 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 745 borrowed: 0 giants: 0
   tokens: 183000 ctokens: 45750

  class htb 2:6 parent 2:1 leaf 7: prio 4 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 80608262 bytes 79347 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 50544 borrowed: 13902 giants: 0
   tokens: 190750 ctokens: 47687

  class htb 2:7 parent 2:1 leaf 8: prio 5 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 37606539 bytes 26129 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 5617 borrowed: 8922 giants: 0
   tokens: -178485 ctokens: 24056

  class htb 2:8 parent 2:1 leaf 9: prio 6 rate 512000bit ceil 1000Kbit burst 
1600b cburst 1600b
   Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 0 borrowed: 0 giants: 0
   tokens: 390625 ctokens: 20

  class htb 2:9 parent 2:1 leaf a: 

[Touch-packages] [Bug 1368647] Re: GPS and location detection not working on Nexus 4

2015-05-01 Thread Jacques
I'm experiencing the same issue.  I have no GPS in any application, and none of 
the temporary fixes above do not work.
Device: LG Nexus 5
OS: Ubuntu 15.04 (r2)

cat /var/log/ubuntu-location-service/com.ubuntu.location.ERROR 
Log file created at: 2015/05/02 00:59:53
Running on machine: ubuntu-phablet
Log line format: [IWEF]mmdd hh:mm:ss.uu threadid file:line] msg
E0502 00:59:53.853097  4789 skeleton.cpp:180] Error creating session: Client 
lacks permissions to access the service with the given criteria

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

Title:
  GPS and location detection not working on Nexus 4

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Mako with MultiROM, utopic r239

  None of the apps I have tried including Weather, Google maps, OSM
  Touch and SensorStatus are able to use the phone's GPS. The
  SensorStatus app actually reports Found supported backend, but finds
  no position or other GPS data.

  Location detection on the other hand is doing something, but it is
  really far off when it comes to determining the actual location of the
  device. The Weather app suggests my location as Vänsjö, Jämtland,
  which is about 400 km north of Stockholm where I am at. OSM Touch
  reports no location available and Google maps Your location could
  not be determined

  I don't know if the GPS has to waken up somehow, but it has not
  shown any form of life for me on Ubuntu Touch, even though it works
  perfectly fine when booting the phone as Android.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1368647/+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 1450187] Re: kill -KILL doesn't kill process

2015-05-01 Thread Brian Murray
I was unable to recreate this:

  9:26AM ]  [ bdmurray@impulse:/tmp/prodigy-remixes ]
 $ xeyes 
[1] 3883
[  9:29AM ]  [ bdmurray@impulse:/tmp/prodigy-remixes ]
 $ kill -KILL 3883
[1]  + 3883 killed xeyes
  
[  9:29AM ]  [ bdmurray@impulse:/tmp/prodigy-remixes ]
 $ ps aux | grep xeyes
bdmurray  3896  0.0  0.0  12120  2296 pts/28   S+   09:29   0:00 grep 
--color=auto xeyes
[  9:29AM ]  [ bdmurray@impulse:/tmp/prodigy-remixes ]
 $ xeyes 
[1] 3901
[  9:29AM ]  [ bdmurray@impulse:/tmp/prodigy-remixes ]
 $ sudo kill -KILL 3901
[sudo] password for bdmurray: 
[1]  + 3901 killed xeyes


** Changed in: procps (Ubuntu)
   Status: New = Incomplete

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

Title:
  kill -KILL doesn't kill process

Status in procps package in Ubuntu:
  Incomplete

Bug description:
  scenario:

  $ ps -A | grep git 
  24530 pts/13   00:00:00 git
  $ sudo kill -KILL 24530
  $ echo $?
  0
  $ ps -A | grep git 
  24530 pts/13   00:00:00 git

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: procps 1:3.3.9-1ubuntu8
  Uname: Linux 4.0.0-04-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 29 22:09:21 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-02 (26 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: procps
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1450187/+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 1351389] Re: [SDK] power off / restart and cancel buttoms too close together

2015-05-01 Thread Magdalena Mirowicz
** Summary changed:

- power off / restart and cancel buttoms too close together
+ [SDK] power off / restart and cancel buttoms too close together

** Changed in: ubuntu-ux
   Status: New = Triaged

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Jouni Helminen (jounihelminen)

** Changed in: ubuntu-ux
   Importance: Undecided = Medium

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

Title:
  [SDK] power off / restart and cancel buttoms too close together

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  The 3 buttons are currently stacked vertically but:

  1) The spacing between them looks cramped.
  2) The height of each button is too low to be comfortable.

  If you compare this menu with the Android equivalent, on Android the
  buttons actually touch _but_ they are atleast as tall as a finger is
  wide. This seems like a good policy wrt height.

  We don't appear to be space-constrained here so I'd suggest making the
  buttoms more spaced out and taller.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1351389/+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 1450838] Re: lightdm fails to unlock with serial console configured

2015-05-01 Thread Thaddaeus Tintenfisch
** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  lightdm fails to unlock with serial console configured

Status in light-locker package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  With /etc/default/grub configured for serial console output as follows
  (seehttps://help.ubuntu.com/community/SerialConsoleHowto):

  GRUB_DEFAULT=0
  GRUB_TIMEOUT=3
  GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian`
  GRUB_CMDLINE_LINUX_DEFAULT=
  GRUB_CMDLINE_LINUX=
  GRUB_CMDLINE_LINUX=console=tty0 console=ttyS0,9600n8

  #GRUB_TERMINAL=console
  GRUB_TERMINAL=serial console
  GRUB_SERIAL_COMMAND=serial --speed=9600 --unit=0 --word=8 --parity=no 
--stop=1

  Lightdm fails to unlock a locked screen. Initial login works fine.
  But, when the screen locks, the correct password is accepted, but the
  screen does not unlock.

  If I disable serial console with the default GRUB_TERMINAL=console,
  lightdm screen unlock seems to work fine. I don't know if this is a
  problem with lightdm or light-locker.

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


  1   2   3   4   >