[Touch-packages] [Bug 1079784] Re: Accessible description doesn't update in 14.04

2019-07-26 Thread Charlie Jonshon
I was facing the face problem then I visited
https://oniton.com/blog/windows-10-startup-folder-not-working/ and after
that I got the appropriate solution to resolve this problem.

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

Title:
  Accessible description doesn't update in 14.04

Status in indicator-power:
  New
Status in indicator-power package in Ubuntu:
  New

Bug description:
  Compare to bug 891932.

  While running tests for indicator-power, an error pops up for a
  missing accessible description:

  (process:14724): libindicator-WARNING **: IndicatorObject class does
  not have an accessible description.

  While running IndicatorTest.GObjectNew and IndicatorTest.NoDevices.

  I think this should be investigated. Could just be a false positive,
  but we really should have accessible descriptions for everything if
  possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1079784/+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 1833823] Re: Text box appeared on the main screen of desktop and no way to get rid of it.

2019-06-22 Thread Charlie Luna
solved it. It was a mistakenly placed sticky note widget. I'll be
removing this bug report if that's something I can do.

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

Title:
  Text box appeared on the main screen of desktop and no way to get rid
  of it.

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not sure what happened here. I just downloaded phpbb to work on my
  own forum and now this text box appeared on my main screen of my
  laptop and I can't make it go away, even after a restart and complete
  shutdown and startup. Not sure if it's a problem with xorg/wayland or
  whatever.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-23.24~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Jun 22 11:47:58 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1d30]
  InstallationDate: Installed on 2019-06-19 (3 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 13d3:5a07 IMC Networks 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X510UAR
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-23-generic 
root=UUID=fee9ef1f-d467-48de-8ddd-824920256181 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X510UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X510UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX510UAR.309:bd07/24/2018:svnASUSTeKCOMPUTERINC.:pnX510UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X510UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  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/1833823/+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 1833823] [NEW] Text box appeared on the main screen of desktop and no way to get rid of it.

2019-06-22 Thread Charlie Luna
Public bug reported:

I'm not sure what happened here. I just downloaded phpbb to work on my
own forum and now this text box appeared on my main screen of my laptop
and I can't make it go away, even after a restart and complete shutdown
and startup. Not sure if it's a problem with xorg/wayland or whatever.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-23.24~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Sat Jun 22 11:47:58 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1d30]
InstallationDate: Installed on 2019-06-19 (3 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 003: ID 13d3:5a07 IMC Networks 
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X510UAR
ProcEnviron:
 LANGUAGE=
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-23-generic 
root=UUID=fee9ef1f-d467-48de-8ddd-824920256181 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X510UAR.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X510UAR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX510UAR.309:bd07/24/2018:svnASUSTeKCOMPUTERINC.:pnX510UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: X510UAR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
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

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "The attached pic is a screen print of my main screen."
   
https://bugs.launchpad.net/bugs/1833823/+attachment/5272381/+files/Screenshot_20190622_114919.png

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

Title:
  Text box appeared on the main screen of desktop and no way to get rid
  of it.

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not sure what happened here. I just downloaded phpbb to work on my
  own forum and now this text box appeared on my main screen of my
  laptop and I can't make it go away, even after a restart and complete
  shutdown and startup. Not sure if it's a problem with xorg/wayland or
  whatever.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-23.24~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Jun 22 11:47:58 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1d30]
  InstallationDate: Installed on 2019-06-19 (3 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 13d3:5a07 IMC Networks 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X510UAR
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vm

[Touch-packages] [Bug 997758] Re: gnome battery indicator missing in 12.04/12.10

2019-05-23 Thread Charlie Jonshon
Can anyone tell me that the daemon version 0.9.17 is compatible with
windows 10 because I am getting windows update error 80070103
continuously for that I also checked https://errorcode0x.com/windows-
update-error-80070103/ but did not get the valid solution to fix this.

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

Title:
  gnome battery indicator missing in 12.04/12.10

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  This is 12.04 Precise, with Unity turned off, using Gnome.

  Multiple users are reporting the panel battery indicator is missing.
  http://ubuntuforums.org/showthread.php?p=11924048#post11924048

  indicator-power is installed

  Perhaps realated: 
   System Settings -> Power
   Show battery status in the menu bar

  is blank when the window opens, but non-blank values don't take.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-power 2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic i686
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  Date: Thu May 10 20:56:22 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to precise on 2012-05-09 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/997758/+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 1788321] Re: swapon failed: invalid argument

2018-08-24 Thread charlie
the changes that broke this seem to be related to the L1 terminal
patches.  i've linked the CVE numbers.  maybe that will get us some
help.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3620

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3646

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

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

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

Title:
  swapon failed: invalid argument

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

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1788321] Re: swapon failed: invalid argument

2018-08-24 Thread charlie
i'm running debian.

i'm using 686 (32 bit) and pae.  what kernel are you running?

kernel 4.9.0-5 works and 4.9.0-8 is broken (didn't check others).

apt-get changelog linux-image-4.9.0-8-686-pae has lots of swap related
notes so they definitely borked something.

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

Title:
  swapon failed: invalid argument

Status in util-linux package in Ubuntu:
  New

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1788321/+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 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-06 Thread Charlie Bravo
In response to my previous comment, switching to SMPlayer improves the
symptom, but does not seem to resolve it.

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC 
Controller (rev 05)
Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC 
Controller
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family 6 port SATA AHCI Controller (rev 05)

[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-06 Thread Charlie Bravo
If I am reading this commentary, and that in
https://bugs.launchpad.net/ubuntu/+source/clutter-1.0/+bug/1698270  it's
looking like uninstalling totem and changing to another player might be
the best answer, am I correct?

Thanks!

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC 
Controller (rev 05)
Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC 
Controller
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
  

[Touch-packages] [Bug 1704660] Re: Xorg freeze

2018-02-16 Thread Charlie
Christopher, I am currently running Ubuntu 17.10 64 bit, Mate 1.18.0,
kernel 4.13.0-30-generic X86_64. I have not seen this problem for a long
time and it's so long ago now I'm afraid that I don't recall whether it
occurred after an update. I have attached current Xorg log.

I am also running Ubuntu 18.04 in Vbox and not seeing the issue.

Sorry I can't be of more help but can upload more current logs if of any
use.

** Attachment added: "Xorg0_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704660/+attachment/5056567/+files/Xorg0_log.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/1704660

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using two monitors:

  1. Moved an image from picture folder to primary secondary monitor
  desktop

  2. Opened a folder on primary monitor

  3. Tried to drag image file into - file 'declines and mouse curser is
  now a fist icon and mouse clicks on image have no effect.

  4. Logged out and right click mouse menu is back and I can send the
  image to rubbish bin and return to the desktop but issue still occurs
  and is repeatable.

  I realize that this may not be a Xorg problem but not sure what is
  causing my issue. Happy to carry out more tests/supply more
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic i686
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Jul 16 17:20:37 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0M9KCM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704660/+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 1741986] Re: Please merge lvm2 from Debian unstable for lvmlockd and sanlock support

2018-01-23 Thread Charlie Smurthwaite
I have raised another bug with Debian regarding user permissions in
sanlock that relates to this. This is not critical (or necessarily even
relevant) to this merge, but I thought I'd mention it in case the fix
can be pulled in at the same time: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=888102

** Bug watch added: Debian Bug tracker #888102
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888102

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

Title:
  Please merge lvm2 from Debian unstable for lvmlockd and sanlock
  support

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I am extremely interesting in utilizing the following stack to host
  disks for KVM virtual machines:

  * lvm2
  * lvmlockd
  * sanlock

  I believe in order to use lvmlockd, the lvm2 sources will need to be
  merged from Debian and the lvm2-lockd binary package will need to be
  built. Please could I request that this merge happen prior to the
  release of Beaver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1741986/+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 1741986] [NEW] Please merge lvm2 from Debian unstable for lvmlockd and sanlock support

2018-01-08 Thread Charlie Smurthwaite
Public bug reported:

I am extremely interesting in utilizing the following stack to host
disks for KVM virtual machines:

* lvm2
* lvmlockd
* sanlock

I believe in order to use lvmlockd, the lvm2 sources will need to be
merged from Debian and the lvm2-lockd binary package will need to be
built. Please could I request that this merge happen prior to the
release of Beaver.

** Affects: lvm2 (Ubuntu)
 Importance: Wishlist
 Assignee: Nish Aravamudan (nacc)
 Status: Confirmed

** Summary changed:

- Please merge lvmlockd with sanlock support
+ Please merge lvmlockd and sanlock support

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

Title:
  Please merge lvm2 from Debian unstable for lvmlockd and sanlock
  support

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I am extremely interesting in utilizing the following stack to host
  disks for KVM virtual machines:

  * lvm2
  * lvmlockd
  * sanlock

  I believe in order to use lvmlockd, the lvm2 sources will need to be
  merged from Debian and the lvm2-lockd binary package will need to be
  built. Please could I request that this merge happen prior to the
  release of Beaver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1741986/+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 1712011] [NEW] Unable to close Printer properties

2017-08-21 Thread Charlie
Public bug reported:

>From settings I open Printers and click on settings (gear icon) for my
printer which bring up a pop-up with printer details (name , location,
address, etc). There is no way to close this pop-up. Instead of a top
toolbar there is thin dark line. The pop-up cannot be moved.

Occurs using 17.10 default and Wayland.

Screenshot added

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic i686
ApportVersion: 2.20.6-0ubuntu6
Architecture: i386
BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 21 08:55:08 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
   Subsystem: Dell Radeon HD 6670 [1028:0b0e]
InstallationDate: Installed on 2017-07-14 (37 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
MachineType: Dell Inc. OptiPlex 9010
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0M9KCM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 9010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Aug 21 08:45:01 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSennheiser Sennheiser USB Headset KEYBOARD, id 8
 inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
 inputUSB OPTICAL MOUSEMOUSE, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu3
xserver.video_driver: radeon

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


** Tags: apport-bug artful i386 reproducible single-occurrence ubuntu 
wayland-session

** Attachment added: "Screenshot from 2017-08-20 20-22-10.png"
   
https://bugs.launchpad.net/bugs/1712011/+attachment/4936158/+files/Screenshot%20from%202017-08-20%2020-22-10.png

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

Title:
  Unable to close Printer properties

Status in xorg package in Ubuntu:
  New

Bug description:
  From settings I open Printers and click on settings (gear icon) for my
  printer which bring up a pop-up with printer details (name , location,
  address, etc). There is no way to close this pop-up. Instead of a top
  toolbar there is thin dark line. The pop-up cannot be moved.

  Occurs using 17.10 default and Wayland.

  Screenshot added

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: i386
  BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 08:55:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
 

[Touch-packages] [Bug 1704660] [NEW] Xorg freeze

2017-07-16 Thread Charlie
Public bug reported:

Using two monitors:

1. Moved an image from picture folder to primary secondary monitor
desktop

2. Opened a folder on primary monitor

3. Tried to drag image file into - file 'declines and mouse curser is
now a fist icon and mouse clicks on image have no effect.

4. Logged out and right click mouse menu is back and I can send the
image to rubbish bin and return to the desktop but issue still occurs
and is repeatable.

I realize that this may not be a Xorg problem but not sure what is
causing my issue. Happy to carry out more tests/supply more information.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic i686
ApportVersion: 2.20.5-0ubuntu5
Architecture: i386
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Jul 16 17:20:37 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
   Subsystem: Dell Radeon HD 6670 [1028:0b0e]
InstallationDate: Installed on 2017-07-14 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
MachineType: Dell Inc. OptiPlex 9010
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0M9KCM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 9010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.81-2
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: apport-bug artful false-gpu-hang freeze i386 reproducible 
single-occurrence ubuntu wayland-session

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Using two monitors:

  1. Moved an image from picture folder to primary secondary monitor
  desktop

  2. Opened a folder on primary monitor

  3. Tried to drag image file into - file 'declines and mouse curser is
  now a fist icon and mouse clicks on image have no effect.

  4. Logged out and right click mouse menu is back and I can send the
  image to rubbish bin and return to the desktop but issue still occurs
  and is repeatable.

  I realize that this may not be a Xorg problem but not sure what is
  causing my issue. Happy to carry out more tests/supply more
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic i686
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Jul 16 17:20:37 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: D

Re: [Touch-packages] [Bug 633361] Re: C-Media USB headset not working in maverick

2017-05-09 Thread Charlie Schluting ☃
LOL... 7 years for a response to a bug talking about how a new release
broke something.
Sounds about right.

FYI, you'd be better off silently closing things like this.

On Tue, May 9, 2017 at 3:56 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Thank you for reporting this bug to Ubuntu.
> Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
>
> See this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases
>
> Please upgrade to the latest version and re-test.
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/633361
>
> Title:
>   C-Media USB headset not working in maverick
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/633361/+subscriptions
>

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

Title:
  C-Media USB headset not working in maverick

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: pulseaudio

  This device is a generic Plantronics USB headset:

  generic-usb 0003:0D8C:0008.0009: input,hidraw3: USB HID v1.00 Device
  [C-Media USB Audio Device   ]

  It's failing to work on Maverick. When starting Ekiga and placing a
  call, I'll often get "cannot open device" errors. Re-connecting the
  USB adapter does not work (I generally restart Ekiga after doing so,
  too). I was able to get it working, finally, by restarting pulseaudio
  a few times, then starting ekiga, and then un/re-plugging in the USB
  adapter. Before I restart pulse, the USB output and input devices were
  not showing up in padevchooser. Even after they did, it took a few
  restarts and lots of futzing with to get it working again.

  The only thing I found in logs:
  Sep  8 09:46:42 polt pulseaudio[11227]: alsa-util.c: Got POLLNVAL from ALSA
  Sep  8 09:46:42 polt pulseaudio[11227]: alsa-util.c: Could not recover from 
POLLERR|POLLNVAL|POLLHUP with snd_pcm_prepare(): No such device
  Sep  8 09:46:42 polt pulseaudio[11227]: alsa-util.c: Could not recover from 
POLLERR|POLLNVAL|POLLHUP and XRUN: File descriptor in bad state

  Using:
  ii  pulseaudio 1:0.9.22~0.9.21+stable-que PulseAudio sound 
server

  This always worked perfectly in Lucid.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu17
  ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
  Uname: Linux 2.6.35-20-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  AudioDevicesInUse:
   USER    PID ACCESS COMMAND
   /dev/snd/controlC2:  charlie   12667 F.... pulseaudio
   /dev/snd/controlC3:  charlie   12667 F.... pulseaudio
   /dev/snd/controlC0:  charlie   12667 F pulseaudio
   /dev/snd/controlC1:  charlie   12667 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf070 irq 73'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,1014032b,00100200'
 Controls  : 33
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x802'/'USB Device 0x46d:0x802 at usb-:00:1d.2-2, full 
speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0802'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 6144
 Mono: Capture 6144 [100%] [30.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'default'/'C-Media USB Audio Deviceat usb-:00:1d.7-4.4, 
full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0008'
 Controls  : 5
 Simple ctrls  : 3
  Card3.Amixer.info:
   Card hw:3 'Audigy'/'SB Audigy 1 [SB0090] (rev.3, serial:0x511102) at 0x2000, 
irq 16'
 Mixer name : 'TriTech TR28602'
 Components : 'AC97a:54524123'
 Controls  : 194
 Simple ctrls  : 30
  Date: Wed Sep  8 09:49:34 2010
  ExecutablePath: /usr/bin/pulseaudio
  ProcEnviron:
   SHELL=/bin/zsh
   PATH=(custom, user)
   LANG=en_US.utf8
  SourcePackage: pulseaudio
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:1625): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:1605): GConf-CRITICAL **: gconf_value_free: assertion `value != 
NULL' failed
   (nm-applet:1630): Gdk-CRIT

[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

2017-02-11 Thread Charlie Knight
I just tried running the command to turn off le when connected to a
device and I got the same message 'status 0x0a (Busy)' so perhaps you
are already connected to something.

My suggestion is to unpair all devices (if you have any paired) and running the 
command:  
rfkill block bluetooth 

That command soft blocks the bluetooth adapter - so it won't be able to
attempt any connections. After is it blocked try running the le commannd
again (sudo btmgmt le off)

Then unblock the bluetooth adapter by: rfkill unblock bluetooth.

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough handles to register
  service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

2017-02-04 Thread Charlie Knight
@aromo Similar issue, couldn't connect UE Boom speaker was just getting
'Unable to register GATT service with handle 0x0001'. Found it strange
that even when the speaker was powered down bluetoothd kept trying to
connect (and disconnect seconds later)

What I found was, UE Boom speakers can be powered on remotely using the
mobile application - which is done through Bluetooth LE. This is why the
speaker was connected even when powered-down because of it was connected
via LE. I could be wrong but I believe the GATT service manages the
messages from LE devices - So I tried disabling Bluetooth Low Energy on
the laptop bluetooth adaptor through this command:

sudo btmgmt le off

Unpaired the speaker, restarted the laptop and afterwards I had no more
"Unable to Register GATT" or "Device is already marked connected
messages" and I was able to connect the speaker through Audio Sink.
Haven't had any issues with it since (except for having to run a2dp.py -
but that is a separate issue)

Perhaps you could try disabling le and see if it works for you too?

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough handles to register
  service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

2016-11-01 Thread Charlie McMackin
Good news: I have a had a small eureka moment that results my computer
fully booted with graphics hardware fully accelerated. Bad news: it is
still a workaround -- I still can't push power button and boot up
normally.

Here is the workaround sequence -- it requires another computer that can
ssh in:

1. Computer in OFF state, press power.
2. At boot select screen, press `e` and edit kernel line by appending 
`modprobe.blacklist=radeon`
3. Press `F10` to boot
4. At login screen, click gear icon in upper right and select `Suspend`
5. After computer is in suspended state, press any key to awaken.
6. The display does not "reawaken" and still appears off.
7. From another computer, ssh into the first.
8. Issue `sudo service lightdm stop`
9. Issue `sudo modprobe radeon`. This should succeed! \o/
10. Issue `sudo service lightdm start`

Now the computer should be using correct drm drivers and have full
resolution display. Furthermore, Suspend and Wake work successfully.

I discovered this using ubuntu mainline kernel 4.8.0-rc5 but have
verified it works with mainline 4.8.6 and also with 4.4.0-45.
Unfortunately, I am also using the oibaf/graphics-drivers PPA with more
recent mesa and libdrm drivers. I plan to test again after removing the
PPA but it may take a while. If anyone with this problem is still
watching, I'd be curious to hear if my workaround steps work for you.

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

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.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

[Touch-packages] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

2016-09-08 Thread Charlie McMackin
Thanks for the information seeker5528. Unfortunately for me, I'm not
seeing similar results. My XFX 5570 only has DVI, HDMI and HDCP outputs.
I just tested both DVI and HDMI alone and still the same issue for each.

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

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.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.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

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

[Touch-packages] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

2016-09-08 Thread Charlie McMackin
I meant XFX 5770

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

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.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.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1568429/+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 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

2016-07-26 Thread Charlie McMackin
I receive:

mount: can't find /root in /proc/mounts


`more /proc/mounts` shows:

rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=4067424k,nr_inodes-1016856,mode=755 
0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=817336k,mode=755 0 0


this is at initramfs shell on break=top

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

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.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.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:

[Touch-packages] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

2016-07-25 Thread Charlie McMackin
"debug break" => black screen, not responsive, no initramfs shell
"debug break=modules" => black screen, not responsive, no initramfs shell
"debug break=top" => initramfs shell but I haven't figured out how to mount a 
read-write filesystem to persist the initramfs.debug or dmesg output, yet.

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

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.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.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

2016-07-24 Thread Charlie McMackin
I'm still unable to boot following the linked directions by removing the
vt_handoff, quiet, and splash kernel params and also setting gfxmode to
"text". It follows nearly the same behavior black screen, constant hdd
activity light on -- the monitor however still detects an input signal,
it's just black.

I can boot by using the linked method but also supplying
radeon.modeset=0 flag. I'm attaching the dmesg log from that boot up.
I'm assuming dmesg output is the "missing information" requested. If
there is something else missing please let me know.

** Attachment added: "dmesg-debug.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1568429/+attachment/4706595/+files/dmesg-debug.log

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

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.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.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  x

[Touch-packages] [Bug 1568429] Re: Radeon won't work with KMS enabled

2016-07-24 Thread Charlie McMackin
Chistopher Penalver, it is hard to say as this is the first release
where I can no longer use Catalyst -- I have been using the the binary
drivers before this release. I remember my upgrading from 15.04 to 15.10
having a similar looking issue until I reinstalled the binary drivers. I
never tried modesetting kernel parameters at that time so I can't say
100% if the error was the same.

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

Title:
  Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have a Radeon HD 5770 GPU. After upgrading to Xenial today and
  ensuring the xorg radeon driver was enabled, my machine will no longer
  boot to a usable state. After selecting default Ubuntu option from
  GRUB menu, both monitor lose signal input and the keyboard becomes
  unresponsive. Sometimes the machine will reboot on its own, most of
  the time I have to hard reset.

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.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.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1568429] Re: Radeon won't work with KMS enabled

2016-06-28 Thread Charlie McMackin
Is there anything more I can do to help debug this? In my latest attempt
to get any useful information, I removed my usb keyboard in favor of a
ps2 one. On boot and subsequent fail, the caps lock and scroll lock
flash 10 times. I thought maybe getting a serial console going would
help but this computer doesn't have a db9/rs232 port and it appears to
be failing before the USB subsystem is initialized so USB serial console
appears to be a no-go.

I'm pretty new / green on debugging at this low a level, but I'm willing
to give it a go if anyone has ideas to try...

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

Title:
  Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a Radeon HD 5770 GPU. After upgrading to Xenial today and
  ensuring the xorg radeon driver was enabled, my machine will no longer
  boot to a usable state. After selecting default Ubuntu option from
  GRUB menu, both monitor lose signal input and the keyboard becomes
  unresponsive. Sometimes the machine will reboot on its own, most of
  the time I have to hard reset.

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.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.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

To manage not

[Touch-packages] [Bug 1596436] [NEW] delayed start up

2016-06-27 Thread charlie
Public bug reported:

delayed in start up the computer

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: hostname 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
BootLog:
 
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 Jun 27 09:43:15 2016
DistUpgraded: 2016-06-20 03:02:02,186 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Presario C700 [103c:30d9]
   Subsystem: Hewlett-Packard Company Presario C700 [103c:30d9]
InstallationDate: Installed on 2010-07-28 (2161 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Hewlett-Packard Compaq Presario C700 Notebook PC
ProcEnviron:
 LANGUAGE=es_ES
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=84991f27-b94e-4a5d-9fd8-1204dd936a63 ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-06-20 (7 days ago)
dmi.bios.date: 03/19/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.32
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 30D9
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 83.21
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.32:bd03/19/2008:svnHewlett-Packard:pnCompaqPresarioC700NotebookPC:pvrF.32:rvnHewlett-Packard:rn30D9:rvr83.21:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Compaq Presario C700 Notebook PC
dmi.product.version: F.32
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jun 27 09:13:34 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   19781 
 vendor SEC
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  delayed start up

Status in xorg package in Ubuntu:
  New

Bug description:
  delayed in start up the computer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: hostname 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog:
   
  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 Jun 27 09:43:15 2016
  DistUpgraded: 2016-06-20 03:02:02,186 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Presario C700 [103c:30d9]
 Subsystem: Hewlett-Packard Company Presario C700 [103c:30d9]
  InstallationDate: Installed on 2010-07-28 (2161 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: Hewlett-Packard Compaq Presario C700 Notebook PC
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=84991f27-b94e-4a5d-9fd8-1204dd936a63 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-20 (7 days ago)
  dmi.bios.date: 03/19/2008
  dmi.bios.vendor: Hewlett

Re: [Touch-packages] [Bug 1584356] Re: Difficulty with text selection in BQ M10 Tablet

2016-05-23 Thread Charlie Goodwin
Hi Pat,

Thanks for such a fast reply.  I don't want to sound negative because I'm
thrilled Canonical and BQ are pushing into tablet / touch and convergence
territory!

This issue as I perceive it is that selecting text through portions of a
mess like:
5G2sX.m0&j^g5D3(,M~dGt&^8hbv
can seem impossible.  My first experience of it was in trying to select a
password out of a text passage in an email I had open in the GMail app.  I
was unable to select and copy that chunk of text out of the body of an
email the other day.

To verify the issue and clarify my perceptions I replicated the test today
in the GMail app.  Several issues seem to be at play:
1.  The ability to select portions of a long complex string like the one
above is very limited.  The selected highlight jumps about - selecting too
little then too much.
2. The "handles" with which to select are too small, making the use of them
difficult.
3. Once I have a passage selected, and the passage may need to be more than
I want because selection is imprecise, the "copy" function is grayed out -
so I cannot use the selection.

Using one of the "Notes" apps, selection is very fiddly and jumpy as above,
but it does work, and the copy functionality is available.  I am still
concerned about the size of the handles and the lack of smooth
responsiveness, but I am able to get it to work, but the experience is less
than pleasant.  So, I guess my most serious issues are in using the GMail
app.  A grayed out option is no option at all.  And moody selection becomes
a real user frustration.

I apologize that I have no idea how to create a movie of the issues.

I really want to see Ubuntu Touch and Linux in general gain ground and so
am happy to answer any questions I have not communicated well on.  I
suspect much of what I speak of lies somewhere in a muddy area between bug
fixes and design, especially the size of the selection handles.

Size of controls is a UI problem.  Does Canonical have a place to send UI
thoughts about Ubuntu Touch?  I suspect design issues are something of a
distraction for you in working through real bugs.  And yet I would like to
be able to send any relevant thoughts where they could be helpful.

Thanks again,

Charlie Goodwin







On Mon, May 23, 2016 at 8:30 AM, Pat McGowan 
wrote:

> Is this in specific apps or in all cases?
> it may be helpful to provide a video.
>
> ** Also affects: ubuntu-ui-toolkit (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: canonical-devices-system-image
>Status: New => Incomplete
>
> ** Changed in: canonical-devices-system-image
>  Assignee: (unassigned) => Zoltan Balogh (bzoltan)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1584356
>
> Title:
>   Difficulty with text selection in BQ M10 Tablet
>
> Status in Canonical System Image:
>   Incomplete
> Status in ubuntu-ui-toolkit package in Ubuntu:
>   New
>
> Bug description:
>   First bug report on M10 so forgive if I am doing anything wrong.  I am
>   just having no luck on getting complex text selected - stuff like
>   mathematical expressions or passwords where there is a mix of
>   alphabetical symbols, numerals, and punctuation in plain text with no
>   spaces.  Among other reasons this is important to me is that I use
>   massive long passwords and sometimes have to copy them from one place
>   to another, and math/sql/similar expressions are a mess to handle too.
>   What selects is portions of the text, but the selection will not
>   expand to the whole thing.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584356/+subscriptions
>

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

Title:
  Difficulty with text selection in BQ M10 Tablet

Status in Canonical System Image:
  Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  First bug report on M10 so forgive if I am doing anything wrong.  I am
  just having no luck on getting complex text selected - stuff like
  mathematical expressions or passwords where there is a mix of
  alphabetical symbols, numerals, and punctuation in plain text with no
  spaces.  Among other reasons this is important to me is that I use
  massive long passwords and sometimes have to copy them from one place
  to another, and math/sql/similar expressions are a mess to handle too.
  What selects is portions of the text, but the selection will not
  expand to the whole thing.

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

[Touch-packages] [Bug 1568429] Re: Radeon won't work with KMS enabled

2016-04-22 Thread Charlie McMackin
Yes, Catalyst has been the only driver that has been working for me so
far. I don't believe the radeon driver was working before either, I
remember having a similar problem when I upgraded to 15.10.

Thanks for the debugging tip. However it didn't work. Immediately after
running the modprobe command the screens go blank, lose signal input,
and then after about 5 seconds the machine reboots. After logging in
again, I found that dmesg didn't have a chance to pipe its output to the
file either.

Definitely seems to be a bug closer to  the kernel / drm

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

Title:
  Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Radeon HD 5770 GPU. After upgrading to Xenial today and
  ensuring the xorg radeon driver was enabled, my machine will no longer
  boot to a usable state. After selecting default Ubuntu option from
  GRUB menu, both monitor lose signal input and the keyboard becomes
  unresponsive. Sometimes the machine will reboot on its own, most of
  the time I have to hard reset.

  If I add `nomodeset` or `radeon.modeset=0` to kernel line in GRUB, the
  machine will boot but the radeon driver will not load. Attempting to
  load radeon driver with `sudo modprobe radeon modeset=1` after booting
  with modesetting off results in the same fail state explained above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.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.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
htt

[Touch-packages] [Bug 1568429] [NEW] Radeon won't work with KMS enabled

2016-04-09 Thread Charlie McMackin
Public bug reported:

I have a Radeon HD 5770 GPU. After upgrading to Xenial today and
ensuring the xorg radeon driver was enabled, my machine will no longer
boot to a usable state. After selecting default Ubuntu option from GRUB
menu, both monitor lose signal input and the keyboard becomes
unresponsive. Sometimes the machine will reboot on its own, most of the
time I have to hard reset.

If I add `nomodeset` or `radeon.modeset=0` to kernel line in GRUB, the
machine will boot but the radeon driver will not load. Attempting to
load radeon driver with `sudo modprobe radeon modeset=1` after booting
with modesetting off results in the same fail state explained above.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
CompositorRunning: None
Date: Sat Apr  9 20:02:22 2016
DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
 vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] 
(prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
InstallationDate: Installed on 2013-12-29 (832 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
dmi.bios.date: 04/29/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0519
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5N7A-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.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.12.2+16.04.20160331-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Apr  9 19:49:46 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2

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


** Tags: amd64 apport-bug freeze kms radeon ubuntu xenial

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

Title:
  Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Radeon HD 5770 GPU. After upgrading to Xenial today and
  ensuring the xorg radeon driver was enabled, my machine will no longer
  boot to a usable state. After selecting default Ubuntu option from
  GRUB menu, both monitor lose signal input and the keyboard becomes
  unresponsive. Sometimes the machine will reboot on its own, most of
  the time I have to hard reset.

  If I add `nomodeset` or `radeon.modeset=0` to kernel line in GRUB, the
  machine will boot but the radeon driver will not load. Attempting to
  load radeon driver with `sudo modprobe radeon modeset=1` after booting
  w

[Touch-packages] [Bug 1445911] [NEW] Characters missing in Ubuntu 14.04

2015-04-19 Thread Charlie
Public bug reported:

Every once in a while characters appear to be missing in
menus/toolbars/windows headers/...

Sometimes just moving them around or moving the mous over them seem to
help to recover the missing characters, but most of the times I have to
close-reopen in order to get things back to normal.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8
Uname: Linux 3.16.0-34-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.10
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 Apr 19 14:31:52 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.13.0-45-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 3.13.0-46-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 3.13.0-48-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 3.13.0-49-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 3.16.0-34-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0665]
InstallationDate: Installed on 2015-02-06 (71 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. XPS 13 9343
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic 
root=UUID=0aebf329-4141-4999-bdf0-b2e1c67c706b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0310JH
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.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
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 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
xserver.bootTime: Sun Apr 19 13:29:06 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   0 
 vendor PHL
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


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

** Attachment added: "missing characters in the Sound Settings menu and in the 
header of file manager"
   
https://bugs.launchpad.net/bugs/1445911/+attachment/4379423/+files/Screenshot%20from%202015-04-19%2014%3A37%3A44.png

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

Title:
  Characters missing in Ubuntu 14.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Every once in a while characters appear to be missing in
  menus/toolbars/windows headers/...

  Sometimes just moving them around or moving the mous over them seem to
  help to recover the missing characters, but most of the times I have
  to close-reopen in order to get things back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.10
  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 Apr 19 14:31:52 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-45-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.13.0-46-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.13.0-48-generic, x86_64: in

[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted

2015-04-14 Thread Charlie Moss
I have experienced this issue when dragging something. It has occurred
on Elimentary OS Freya & Lubuntu 14.10 when installed on the same laptop

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

Title:
  mouse cursor gets corrupted

Status in elementary OS:
  Confirmed
Status in Ubuntu UX bugs:
  New
Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain
  occasions. It then looks flipped, sheared or shows fragments of a
  previous cursor.

  * when switching the cursor them forth and back in Gnome Tweak Tool
  * when drag&dropping a document icon

  Maybe related, the cursor does not always show the correct image scale
  on a high-dpi display (this was working right in 14.04). For example
  after login, or when hovering specific areas, or on mouse down to
  start a drag&drop, the cursor appears 1/4 the expected size.

  Attached is a photo of a corrupted cursor (whereas a screenshot with
  Gimp showed the uncorrupted cursor).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   
  [ OK ]
  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: Fri Nov  7 22:12:52 2014
  DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (278 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash 
acpi_backlight=vendor
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov  7 14:54:59 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970
   vendor SDC
  xserver.version: 2:1.16.0-1ubuntu1

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

2015-01-07 Thread Charlie Ott
confirming on my setup as well.

openstack VM (similar to amazon ec2)
Running GDM3 (apt-get install gnome-shell) w/ NX Server to xorg-server-dummy 
package (since vm is headless)
LDAP Authentication w/ SSSD Package


Once I connect to the server, I am able to log in the first time using my ldap 
account.  Also since i already have a home folder (PAM mkhomedir) my LDAP 
'firstName' and 'lastName' actually show up on the GDM3 login screen.  Which 
was a pleasant surprise.

however, once locked. I'm getting the error in /var/log/auth.log:
Jan  8 05:19:10 onr-geoserver gdm-password][12480]: 
pam_succeed_if(gdm-password:auth): requirement "user ingroup nopasswdlogin" not 
met by user "cott"
Jan  8 05:19:17 onr-geoserver gdm-password][12480]: 
pam_unix(gdm-password:auth): authentication failure; logname=cott uid=0 euid=0 
tty=:0 ruser= rhost=  user=cott
Jan  8 05:19:19 onr-geoserver gdm-password][12480]: pam_sss(gdm-password:auth): 
authentication success; logname=cott uid=0 euid=0 tty=:0 ruser= rhost= user=cott
Jan  8 05:19:19 onr-geoserver gdm-password][12480]: gkr-pam: unlocked login 
keyring
Jan  8 05:19:19 onr-geoserver systemd-logind[1359]: Removed session 3.
Jan  8 05:19:19 onr-geoserver gdm-password][12708]: 
pam_succeed_if(gdm-password:auth): requirement "user ingroup nopasswdlogin" not 
met by user "cott"


it seems 'pam_sss' is happy (auth. success), but 'pam_unix' is not.

This is all purely package installs from ubuntu 14.04 cloud image.  no
custom configs except for the dummy monitor in xorg.conf.  which i doubt
is related.

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

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

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

Bug description:
  My setup is:

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

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

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

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


  lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

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

  Contents of /var/log/auth.log:

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

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

[Touch-packages] [Bug 1400010] [NEW] mv fails to preserve COW on btrfs

2014-12-06 Thread Charlie Todd
Public bug reported:

the /bin/mv command fails to preserve extended attributes, specifically
the COW (lsattr; chattr +C) on btrfs, for both files and directories.
Affects virtual machine images in VirtualBox which perform POORLY if
hosted on btrfs without COW set.

Workaround:
1. Set the folder to have the COW flag (chattr +C .)
2. Back up all of the files (for c in *; do mv $c $c.old; done)
3. Copy the files to the same folder, assuming that there is space, and delete 
the backup upon success (for c in $.old; do cp $c ${c/.old/} && rm $c)

User has to copy the file to a COW flagged directory before VirtualBox
will talk correctly to the block device images.

coreutils, 8.21-1ubuntu5, amd64
btrfs-tools, 3.12-1, amd64
kernel 3.13.0-32-generic

Filesystem was created under Trusty (14.04.1 LTS).

$ apt-cache policy coreutils
coreutils:
  Installed: 8.21-1ubuntu5
  Candidate: 8.21-1ubuntu5
  Version table:
 *** 8.21-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: coreutils 8.21-1ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Dec  6 15:33:07 2014
InstallationDate: Installed on 2014-11-06 (30 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  mv fails to preserve COW on btrfs

Status in coreutils package in Ubuntu:
  New

Bug description:
  the /bin/mv command fails to preserve extended attributes,
  specifically the COW (lsattr; chattr +C) on btrfs, for both files and
  directories.  Affects virtual machine images in VirtualBox which
  perform POORLY if hosted on btrfs without COW set.

  Workaround:
  1. Set the folder to have the COW flag (chattr +C .)
  2. Back up all of the files (for c in *; do mv $c $c.old; done)
  3. Copy the files to the same folder, assuming that there is space, and 
delete the backup upon success (for c in $.old; do cp $c ${c/.old/} && rm $c)

  User has to copy the file to a COW flagged directory before VirtualBox
  will talk correctly to the block device images.

  coreutils, 8.21-1ubuntu5, amd64
  btrfs-tools, 3.12-1, amd64
  kernel 3.13.0-32-generic

  Filesystem was created under Trusty (14.04.1 LTS).

  $ apt-cache policy coreutils
  coreutils:
Installed: 8.21-1ubuntu5
Candidate: 8.21-1ubuntu5
Version table:
   *** 8.21-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: coreutils 8.21-1ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec  6 15:33:07 2014
  InstallationDate: Installed on 2014-11-06 (30 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1400010/+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 1399771] [NEW] package dbus 1.6.18-0ubuntu4.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2014-12-05 Thread Charlie Buckley
Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: dbus 1.6.18-0ubuntu4.3
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Fri Dec  5 19:32:14 2014
DuplicateSignature: package:dbus:1.6.18-0ubuntu4.3:subprocess installed 
post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2014-11-08 (27 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: dbus
Title: package dbus 1.6.18-0ubuntu4.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package dbus 1.6.18-0ubuntu4.3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in dbus package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: dbus 1.6.18-0ubuntu4.3
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Fri Dec  5 19:32:14 2014
  DuplicateSignature: package:dbus:1.6.18-0ubuntu4.3:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2014-11-08 (27 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: dbus
  Title: package dbus 1.6.18-0ubuntu4.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1399771/+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 1256196] Re: zeitgeist-fts uses a lot of memory (more than 200MB)

2014-11-09 Thread Charlie Thomsen
I'm up over 800 mb.
14.10

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

Title:
  zeitgeist-fts uses a lot of memory (more than 200MB)

Status in “zeitgeist” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I find that zeitgeist-fts process uses continuously a lot of memory
  between 10 and 20% of a 2GB laptop.

  See the attached screenshot.

  Is it a normal behavior ?

  I can provide the activity file if required.

  Nicolas

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: zeitgeist-core 0.9.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic i686
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: i386
  Date: Fri Nov 29 09:37:44 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/zeitgeist/zeitgeist-fts
  InstallationDate: Installed on 2013-06-10 (171 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: zeitgeist
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1256196/+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 1356137] [NEW] [X202E, VIA VT1802, Mic, Internal] No sound at all

2014-08-12 Thread Ps. Charlie Zayas Nieves
Public bug reported:

Ubuntu respin by Matthew Moore

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 1539 F pulseaudio
CurrentDesktop: Unity
Date: Tue Aug 12 21:02:26 2014
InstallationDate: Installed on 2014-08-13 (0 days ago)
InstallationMedia: Ubuntu-Remix 14.04 - Release amd64
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 1539 F pulseaudio
Symptom_Jack: Mic, Internal
Symptom_Type: No sound at all
Title: [X202E, VIA VT1802, Mic, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X202E.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X202E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX202E.204:bd09/19/2012:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X202E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug trusty

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

Title:
  [X202E, VIA VT1802, Mic, Internal] No sound at all

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

Bug description:
  Ubuntu respin by Matthew Moore

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1539 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 12 21:02:26 2014
  InstallationDate: Installed on 2014-08-13 (0 days ago)
  InstallationMedia: Ubuntu-Remix 14.04 - Release amd64
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1539 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X202E, VIA VT1802, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X202E.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X202E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX202E.204:bd09/19/2012:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X202E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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