date:20160618

[Expired for unity-scopes-shell (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unity-scopes-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Scope Manager as Black background and black text color...

Status in unity-scopes-shell package in Ubuntu:
  Expired

Bug description:
  it is not possible to read anything: /

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1568346/+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 1584469] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

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

** Changed in: hicolor-icon-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  After removing and reinstalling python3, unaware, at the time, of how
  important it was to everything else.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May 21 21:21:51 2016
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-05-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1584469/+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 1589715] Re: No sound on speakers or HDMI, do have sound headphones

2016-06-18 Thread alan.v.henne...@gmail.com

Added file with output of aplay -l

** Attachment added: "output of aplay -l"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1589715/+attachment/4686423/+files/output%20of%20aplay%20-l

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

Title:
  No sound on speakers or HDMI, do have sound headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Installed 16.4. No sound through the speaker jacks or HDMI. Ran
  trouble shooter. No luck. Not sure if sound card is being recognized
  properly: only options in sound control are for HDMI, Digital output
  and Headphones, no option for speakers. Headphones works, don't use
  digital output.

  
  Attached is the output of Alsa information script:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1589715/+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 1594050] [NEW] Network Manager wifi adapter toggle bug

2016-06-18 Thread nicolas santamaria

Public bug reported:

I have 2 wifi adapters in my system, an internal(displayed as PCI) and
an external(USB), the problem I have is that the toggles to individually
turn the adapters on/off are linked, when I turn off one of them, both
of them are switched off and vice-versa. This happens either by toggling
form settings->network of from the status menu.

System details:
Ubuntu GNOME 16.04 LTS
kernel 4.4.0-24-generic
network-manager version: 1.2.0-0ubuntu0.16.04.2 500

wifi adapters:
internal: Marvell AVASTAR 88W8897
USB: Ralink RT5572

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Network Manager wifi adapter toggle bug

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have 2 wifi adapters in my system, an internal(displayed as PCI) and
  an external(USB), the problem I have is that the toggles to
  individually turn the adapters on/off are linked, when I turn off one
  of them, both of them are switched off and vice-versa. This happens
  either by toggling form settings->network of from the status menu.

  System details:
  Ubuntu GNOME 16.04 LTS
  kernel 4.4.0-24-generic
  network-manager version: 1.2.0-0ubuntu0.16.04.2 500

  wifi adapters:
  internal: Marvell AVASTAR 88W8897
  USB: Ralink RT5572

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594050/+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 1380702] Re: No keyboards shortcuts in QT apps

2016-06-18 Thread erico_pt

Reporting that this bug doesn't affect pyqt5 on Lubuntu 16.04.
Everything works there - I thought it was the same package.

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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 1594035] Re: unable to shut down the system after suspend / resume

2016-06-18 Thread Donald Pellegrino

I confirmed that disabling encrypted swap is a work-around for the
inability to shut down. I commented out the cryptswap1 entry from
/etc/crypttab:

$ diff /etc/crypttab /etc/crypttab~
1c1
< # cryptswap1 UUID=d1bd47b1-9969-4cf6-bb7e-482a50b41ffa /dev/urandom 
swap,offset=1024,cipher=aes-xts-plain64
---
> cryptswap1 UUID=d1bd47b1-9969-4cf6-bb7e-482a50b41ffa /dev/urandom 
> swap,offset=1024,cipher=aes-xts-plain64

I also set /etc/fstab to use the swap partition directly rather than
/dev/mapper/cryptswap1:

$ diff /etc/fstab /etc/fstab~
16,17c16,17
< UUID=d1bd47b1-9969-4cf6-bb7e-482a50b41ffa none  swap  sw  0  0
< #/dev/mapper/cryptswap1 none swap sw 0 0
---
> #UUID=d1bd47b1-9969-4cf6-bb7e-482a50b41ffa none  swap  sw  0  0
> /dev/mapper/cryptswap1 none swap sw 0 0

On this machine, it seems encrypted swap was not working anyway as per
lines in the attached JournalErrors.txt:

Jun 18 17:56:14 username-Lemur systemd-cryptsetup[446]: Failed to activate with 
key file '/dev/urandom': Device or resource busy
...
Jun 18 17:56:18 username-Lemur systemd-cryptsetup[446]: Loading of 
cryptographic parameters failed: Invalid argument
Jun 18 17:56:18 username-Lemur systemd-cryptsetup[446]: Failed to activate: 
Invalid argument
Jun 18 17:56:18 username-Lemur systemd[1]: Failed to start Cryptography Setup 
for cryptswap1.
Jun 18 17:56:18 username-Lemur systemd[1]: Dependency failed for Encrypted 
Volumes.
Jun 18 17:56:18 username-Lemur systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
Jun 18 17:56:18 username-Lemur systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
Jun 18 17:56:18 username-Lemur systemd[1]: Dependency failed for Swap.
Jun 18 17:56:18 username-Lemur systemd[1]: 
systemd-cryptsetup@cryptswap1.service: Failed with result 'exit-code'.
Jun 18 17:56:18 username-Lemur systemd-cryptsetup[805]: Failed to activate with 
key file '/dev/urandom': Device or resource busy

With encrypted swap disabled as per the changes to /etc/crypttab and
/etc/fstab, the machine now shuts down as expected even when
suspend/resume cycles occur during the user session.

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

Title:
  unable to shut down the system after suspend / resume

Status in systemd package in Ubuntu:
  New

Bug description:
  In the case of a system that has gone through a suspend / resume
  cycle, the "shutdown now" command fails with the following output:

  $ shutdown now
  Failed to power off system via logind: Transaction is destructive.
  Failed to start poweroff.target: Interactive authentication required.
  See system logs and 'systemctl status poweroff.target' for details.
  Failed to open /dev/initctl: Permission denied
  Failed to talk to init daemon.

  ---

  $ systemctl status poweroff.target
  ● poweroff.target - Power-Off
 Loaded: loaded (/lib/systemd/system/poweroff.target; disabled; vendor 
preset:
 Active: inactive (dead)
   Docs: man:systemd.special(7)

  ---

  $ systemctl list-jobs
  JOB UNIT  TYPE  STATE  
  438 dev-mapper-cryptswap1.device  start running
  439 dev-mapper-cryptswap1.swapstart waiting
  436 systemd-cryptsetup@cryptswap1.service start running

  3 jobs listed.

  ---

  Steps to reproduce:

  1. Boot system
  2. User login to graphical session
  3. Close lid while on battery power triggering a suspend
  4. Open lid while on battery power triggering a resume
  5. Run "shutdown now" from a terminal. Note that the command must be run from 
the terminal to see output. Selecting "Shut Down..." from the system menu in 
the menu bar will hide the error output.
  6. Observe that the system fails to shut down

  Expected behavior:

  At step 6, the system should shut down gracefully.

  Note that the shutdown process works as expected if steps 3 and 4 are
  skipped. I suspect that something about the suspend / resume cycle
  during the session has an interaction effect with the shutdown
  process, preventing it from executing correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 18 18:04:26 2016
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b550 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=7aecd352-8a3f-4ce9-88b8-0fc048dc9660 ro quiet

[Touch-packages] [Bug 1450036] Re: Need calendar widget to render desktop menu

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Committed

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

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

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

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

Title:
  Need calendar widget to render desktop menu

Status in indicator-datetime package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  For the datetime indicator on the desktop there needs to be a calendar
  widget in the SystemComponents.

  https://wiki.ubuntu.com/SystemComponents#Calendar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1450036/+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 1547481] Re: Camera orientation wrong in windowed mode

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Camera orientation wrong in windowed mode

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Reproducible with flo on internal screen when forced to windowed mode
  or external screen.

  The camera app sets the X-Ubuntu-Rotates-Window-Contents=true flag in
  its .desktop file, which means we don't rotate it in staged mode.

  When rotating in windowed mode, however, we need to counter-rotate the
  window contents (and report orientation to the app as appropriate).

  The bug is two-fold:
  a) viewfinder contents are rotated 90° to the right
  b) camera UI thinks "bottom" is on the right edge

  FWIW long term we should probably look at using things like
  https://doc.qt.io/qt-5/qwindow.html#contentOrientation-prop to affect
  this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160212-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 12:25:06 2016
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1547481/+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 1510382] Re: Window contents (and mouse cursors) become randomly blurry (or clear) after moving around

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Window contents (and mouse cursors) become randomly blurry (or clear)
  after moving around

Status in Canonical System Image:
  Fix Committed
Status in QtMir:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using Unity8 on wily desktop, window contents become slightly blurry
  after moving/resizing the window.

  I first noticed this in Xmir. But now see you can reproduce it just by
  opening System Settings and moving/resizing the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510382/+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 1565103] Re: bottom edge first time wizard is being incorrectly displayed on dialer-app and messaging-app

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  bottom edge first time wizard is being incorrectly displayed on
  dialer-app and messaging-app

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  A new bottom edge wizard is being displayed in the recent images, but
  there are cases where it is being displayed when it shouldn't.

  Steps to reproduce:

  1) Flash the phone with --wipe.
  2) Before opening dialer-app, lock the phone and receive a call.
  3) Once you accept the call, dialer-app is launched and instead of the live 
call view, the wizard is displayed on top of it, but there is no bottom edge on 
that screen, and I believe in this case we should not display any wizards, 
specially because the phone is locked, but even if the phone was unlocked, we 
should not display the wizard if the view does not have bottom edge enabled.

  Another case is when launching messaging-app or dialer-app in a dual
  sim environment. We have a first time dialog that appears behind the
  wizard. Not sure if that's expected, but seems to cause a bad user
  experience to me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565103/+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 1585645] Re: Huge icons in network indicator

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

** Changed in: canonical-devices-system-image
   Status: Fix Released => Fix Committed

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

Title:
  Huge icons in network indicator

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-settings-components package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Flash a fresh image on turbo
  2. With the sim in slot 2
  3. Drag down the network indicator and tap on cellular
  4. In cellular change the 4g connection to 2g
  5. As soon as the cellular icon disappears from the indicator swipe down the 
indicator
  6. Switching now between 2g and 4g and 4g and 2g will now keep the big icon 
till the phone is restarted.

  EXPECTED:
  I expect the indicator to behave in the similar fashion to the other device 
which keep an empty cellular icon in play the whole time

  ACTUAL:
  See screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1585645/+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 1565236] Re: AltGr not working on external keyboards

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  In Progress
Status in Mir 0.23 series:
  Triaged
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+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 1584348] Re: Launcher thinking app is running still when it's dead

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

** Changed in: canonical-devices-system-image
Milestone: backlog => 12

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

Title:
  Launcher thinking app is running still when it's dead

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  When you let an app opened after a while (about hours) and after that you try 
to work with it the app sometimes does not respond.
  I saw it with a lot of apps (camera, dialer, facebook, telegram, webbrowser...

  Atached you'll find a video where you can see me trying to use camera
  app without any result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584348/+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 1588633] Re: Chinese input isn't selected by default after setting language in Chinese from wizard

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

** Changed in: canonical-devices-system-image
   Status: Fix Released => Fix Committed

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

Title:
  Chinese input isn't selected by default after setting language in
  Chinese from wizard

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Test Env:
  current build number: 326
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh
  last update: 2016-06-03 12:45:19
  version version: 326
  version ubuntu: 20160603
  version device: 20160523-003fdb2
  version custom: 20160504-975-22-7

  Steps:
  1.Flash device with latest image
  2.During wizard select "Simplified Chinese"
  3.Finish wizard and go to system settings page
  4.Tap on search field to bring up OSK

  Actual result:
  English input is the only input method and set by default, see attached 
picture.

  Expected result:
  Chinese input should be set by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588633/+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 1570922] Re: "Placeholder" notification emits powerd notification event

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  "Placeholder" notification emits powerd notification event

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  1. In Notification.qml add:

Component.onDestruction { console.log("Notification onDestruction");
  }

and a similar log message in Component.onCompleted.
  2. Install dialer-app-autopilot on the phone. This installs a fake phone sim, 
that, among other things, creates a fake voice mail every time unity8 starts.
  3. Restart unity8.
  4. A notification is created for the voice mail,  before unity8 is fully 
drawn. No bubble can be seen, only the green envelope on top. Note that in 
~/.cache/upstart/unity8.log the notification onCompleted log message can be 
seen, but not an onDestruction message.
  5. stop unity8. Note that ~/.cache/upstart/unity8.log now contains the 
onDestruction message.

  Effectively the initial notification is somehow "leaked" and not
  destroyed until the end of the program. This presents a problem in the
  new power architecture model, where unity8 needs to report both when a
  notification is shown (it already does so) and when it is destroyed.

  Notifications sent after unity8 has completed loading are properly
  destroyed when their bubble disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1570922/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]

** Changed in: qtubuntu
   Status: In Progress => Fix Released

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

Title:
  Unity8-dash on Intel Atom graphics crashes and restarts continuously
  [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) ==
  EGL_TRUE"]

Status in Mir:
  Invalid
Status in qtubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Qt clients are failing to create an egl context when running on Intel
  Pineview systems under Mir.

  eglCreateContext fails with a EGL_BAD_MATCH error code.

  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)

  
  === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+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 1582987] Re: Have to log in to Unity8 twice (screen is locked after login from lightdm)

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Have to log in to Unity8 twice (screen is locked after login from
  lightdm)

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  You have to log in to Unity8 twice on desktop. Once in lightdm and
  again after Unity8 starts.

  The second time is seemingly just the lock screen. But the screen
  should not be locked by default on desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1582987/+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 1589060] Re: Refresh Scopes in landscape mode not possible

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Refresh Scopes in landscape mode not possible

Status in Canonical System Image:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  On bq Aquaris E4.5 one cannot refresh scopes in landscape mode since
  the scree is too small. There is not enough screen to pull down in
  order to refresh.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1589060/+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 1586219] Re: U1 login window opens behind pay-ui window

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  U1 login window opens behind pay-ui window

Status in Canonical System Image:
  Fix Committed
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  In today's phone images, a very basic test case fails: Purchasing an
  app on a freshly-flashed phone.

  Specifically, after tapping the app's price button to initiate a
  purchase, the pay-ui's "Loading..." dialog appears and never
  disappears or times out.  If I hit its "Cancel" button, I see the U1
  login window.  Completing the login then returns the view to the app's
  summary screen in the click store.

  What's supposed to happen is:
  - Tap the price button.
  - Get a U1 login window.
  - Complete the login.
  - Get a payment confirmation window.

  I'm not completely sure what causes this, but it looks like the U1 login 
window is simply appearing underneath the pay-ui dialog instead of above it.  
Dobey found this error in the logs:
  2016-05-26 20:34:53,467 - WARNING - QWindow::fromWinId(): platform plugin 
does not support foreign windows.

  This should probably be fixed before OTA12, since it's a step backward
  in the first-time app purchase flow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586219/+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 1594035] [NEW] unable to shut down the system after suspend / resume

2016-06-18 Thread Donald Pellegrino

Public bug reported:

In the case of a system that has gone through a suspend / resume cycle,
the "shutdown now" command fails with the following output:

$ shutdown now
Failed to power off system via logind: Transaction is destructive.
Failed to start poweroff.target: Interactive authentication required.
See system logs and 'systemctl status poweroff.target' for details.
Failed to open /dev/initctl: Permission denied
Failed to talk to init daemon.

---

$ systemctl status poweroff.target
● poweroff.target - Power-Off
   Loaded: loaded (/lib/systemd/system/poweroff.target; disabled; vendor preset:
   Active: inactive (dead)
 Docs: man:systemd.special(7)

---

$ systemctl list-jobs
JOB UNIT  TYPE  STATE  
438 dev-mapper-cryptswap1.device  start running
439 dev-mapper-cryptswap1.swapstart waiting
436 systemd-cryptsetup@cryptswap1.service start running

3 jobs listed.

---

Steps to reproduce:

1. Boot system
2. User login to graphical session
3. Close lid while on battery power triggering a suspend
4. Open lid while on battery power triggering a resume
5. Run "shutdown now" from a terminal. Note that the command must be run from 
the terminal to see output. Selecting "Shut Down..." from the system menu in 
the menu bar will hide the error output.
6. Observe that the system fails to shut down

Expected behavior:

At step 6, the system should shut down gracefully.

Note that the shutdown process works as expected if steps 3 and 4 are
skipped. I suspect that something about the suspend / resume cycle
during the session has an interaction effect with the shutdown process,
preventing it from executing correctly.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun 18 18:04:26 2016
EcryptfsInUse: Yes
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b550 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System76, Inc. Lemur
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=7aecd352-8a3f-4ce9-88b8-0fc048dc9660 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.06RS76
dmi.board.asset.tag: Tag 12345
dmi.board.name: Lemur
dmi.board.vendor: System76, Inc.
dmi.board.version: lemu6
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A:
dmi.product.name: Lemur
dmi.product.version: lemu6
dmi.sys.vendor: System76, Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  unable to shut down the system after suspend / resume

Status in systemd package in Ubuntu:
  New

Bug description:
  In the case of a system that has gone through a suspend / resume
  cycle, the "shutdown now" command fails with the following output:

  $ shutdown now
  Failed to power off system via logind: Transaction is destructive.
  Failed to start poweroff.target: Interactive authentication required.
  See system logs and 'systemctl status poweroff.target' for details.
  Failed to open /dev/initctl: Permission denied
  Failed to talk to init daemon.

  ---

  $ systemctl status poweroff.target
  ● poweroff.target - Power-Off
 Loaded: loaded (/lib/systemd/system/poweroff.target; disabled; vendor 
preset:
 Active: inactive (dead)
   Docs: man:systemd.special(7)

  ---

  $ systemctl list-jobs
  JOB UNIT  TYPE  STATE  
  438 dev-mapper-cryptswap1.device  start running
  439 dev-mapper-cryptswap1.swapstart waiting
  436 systemd-cryptsetup@cryptswap1.service start running

  3 jobs listed.

  ---

  Steps to reproduce:

  1. Boot system
  2. User login to graphical session
  3. Close lid while on battery power triggering a suspend
  4. Open lid while on battery power triggering a resume
  5. Run "shutdown now" from a terminal. Note that the command must be run from 
the terminal to see output. Selecting "Shut Down..." from the system menu in 
the menu bar will hide the error output.
  6. Observe that the system fails to

[Touch-packages] [Bug 1579760] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1579760/+attachment/4686385/+files/WifiSyslog.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1579760/+attachment/4686383/+files/ProcModules.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1579760/+attachment/4686384/+files/UdevDb.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1579760/+attachment/4686381/+files/ProcEnviron.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1579760/+attachment/4686382/+files/ProcInterrupts.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1579760/+attachment/4686378/+files/Lspci.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1579760/+attachment/4686379/+files/Lsusb.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1579760/+attachment/4686380/+files/ProcCpuinfo.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

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

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1579760/+attachment/4686377/+files/JournalErrors.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1579760/+attachment/4686376/+files/CurrentDmesg.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579760/+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 1579760] Re: Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

apport information

** Tags added: apport-collected xenial

** Description changed:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  
  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  
  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.
  
  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6
  
  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.
  
  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms
  
  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).
  
  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols
  
  fixes the double clicks.
  
  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  josw   1067 F kodi.bin
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
+ InstallationDate: Installed on 2014-08-24 (664 days ago)
+ InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
+ IwConfig: Error: [Errno 2] No such file or directory
+ Package: v4l-utils
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-24-generic N/A
+  linux-backports-modules-4.4.0-24-generic  N/A
+  linux-firmware1.157
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial
+ Uname: Linux 4.4.0-24-generic x86_64
+ UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
+ UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
+ _MarkForUpload: True
+ dmi.bios.date: 10/07/2011
+ dmi.bios.vendor: Intel Corp.
+ dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: DH67GD
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: AAG10206-205
+ dmi.chassis.type: 3
+ dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1579760/+attachment/4686374/+files/AlsaInfo.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms,

[Touch-packages] [Bug 1579760] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1579760/+attachment/4686375/+files/CRDA.txt

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

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

2016-06-18 Thread Brad Figg

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1579760

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Incomplete
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579760/+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 1570878] Re: GPS issue: Updates the speed field only

2016-06-18 Thread Uranicus

Well done! Thanks.

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

Title:
  GPS issue: Updates the speed field only

Status in Canonical System Image:
  Fix Committed
Status in location-service package in Ubuntu:
  Fix Released

Bug description:
  Only the speed data is updated in each new GPS position. Any other
  data, will be updated each 11 seconds.

  Testing:
  Nexus 4.
  OS: Ubuntu 15.04 (r418).
  WIFI Disabled.
  3G Enabled.
  Open Sensor Status and drive (for see how the speed changes).
  Bug: There are new GPS positions each ~800ms, but they will update only the 
Speed field. Any other field (like altitude, latitude...) will be updated each 
11 seconds.
  I tested same behavior with OpenStreetMap and uNav apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1570878/+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 1579760] Re: Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

2016-06-18 Thread Gregor Jasny

As I don't vahe a good understanding of the rc subsystem I asked on
linux-media what's going on here and according to Mauro the absence of
rc6 seems to be a kernel bug:

https://www.mail-archive.com/linux-media@vger.kernel.org/msg98286.html

> That's said, from his report:
> 
> $ sudo ir-keytable
> Found /sys/class/rc/rc0/ (/dev/input/event4) with:
>  Driver imon, table rc-imon-pad
>  Supported protocols: other
> 
> It should be listing both "other" and "RC6" protocols there.
> It sounds a Kernel regression. I remember one Kernel patch once
> broke the list of protocols. Maybe the fix patch were not applied
> on Ubuntu, or maybe some other regression happened.


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

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  New
Status in v4l-utils package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579760/+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 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just

2016-06-18 Thread igor

** Description changed:

  I've installed ntp service on the clean ubuntu 16.04 server system. 
Configured it. Checked that it works, but, after reboot, it doesn't start 
automatically.
  When I check: 'systemctl is-enabled ntp', it shows enabled.
  If I manually start it 'systemctl start ntp' it starts just fine and woks 
correctly,
  but until I manually start it, 'systemctl status ntp' shows:
  
  Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
  Active: inactive (deadi)
  
- found bugreport on ntpd package:
+ Installed 1.29ubuntu2 version of init-systems-helper, but it didn't fix
+ the problem.
+ 
+ Found a bugreport on ntpd package:
  
  https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596
  
  led to solution that involves a change to be made in file:
  
  /etc/network/if-up.d/ntpdate
  
  of ntpdate package
  
  After changing from:
  __CODE_START__
  
  invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true
  
   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null 
|| :
  
  invoke-rc.d --quiet $service start >/dev/null 2>&1 || true
  
  __CODE_END__
  
  to:
  __CODE_START__
  
  systemctl --quiet stop $service.service >/dev/null 2>&1 || true
  
   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null 
|| :
  
  systemctl --quiet start $service.service >/dev/null 2>&1 || true
  
  __CODE_END__
  
  ntpd service started launching on boot.
  
  System Information:
  
    lsb_release -rd:
  
  Description:Ubuntu 16.04 LTS
  Release:16.04
  
    apt-cache policy ntpdate:
  
  ntpdate:
    Установлен: 1:4.2.8p4+dfsg-3ubuntu5
    Кандидат:   1:4.2.8p4+dfsg-3ubuntu5
    Таблица версий:
   *** 1:4.2.8p4+dfsg-3ubuntu5 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

Title:
  ntpdate startup routine prevents ntp service from launching up on
  Ubuntu 16.04 server on system boot; manually starting ntp service
  works: [FIX in DESCRIPTION], just need to apply it and release a new
  version

Status in ntp package in Ubuntu:
  New

Bug description:
  I've installed ntp service on the clean ubuntu 16.04 server system. 
Configured it. Checked that it works, but, after reboot, it doesn't start 
automatically.
  When I check: 'systemctl is-enabled ntp', it shows enabled.
  If I manually start it 'systemctl start ntp' it starts just fine and woks 
correctly,
  but until I manually start it, 'systemctl status ntp' shows:

  Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
  Active: inactive (deadi)

  Installed 1.29ubuntu2 version of init-systems-helper, but it didn't
  fix the problem.

  Found a bugreport on ntpd package:

  https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596

  led to solution that involves a change to be made in file:

  /etc/network/if-up.d/ntpdate

  of ntpdate package

  After changing from:
  __CODE_START__

  invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null 
|| :

  invoke-rc.d --quiet $service start >/dev/null 2>&1 || true

  __CODE_END__

  to:
  __CODE_START__

  systemctl --quiet stop $service.service >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null 
|| :

  systemctl --quiet start $service.service >/dev/null 2>&1 || true

  __CODE_END__

  ntpd service started launching on boot.

  System Information:

    lsb_release -rd:

  Description:Ubuntu 16.04 LTS
  Release:16.04

    apt-cache policy ntpdate:

  ntpdate:
    Установлен: 1:4.2.8p4+dfsg-3ubuntu5
    Кандидат:   1:4.2.8p4+dfsg-3ubuntu5
    Таблица версий:
   *** 1:4.2.8p4+dfsg-3ubuntu5 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1593907/+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 1594023] [NEW] Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2016-06-18 Thread Elio

Public bug reported:

This is about a fresh Ubuntu 16.04 install on a new laptop (asus
x540sa). After pressing the shutdown button in the start menu; the
shutdown procedure starts and in the final splash screen the system just
hangs. Tried a second time by pressing Esc once the splash screen showed
up and I saw that it reaches the line "Reached target shutdown" and just
stops there, no matter how long I leave it there the machine won't turn
off.

I also tried a Kubuntu 16.04 fresh install on the same machine and it
hanged too at the final splash screen where the pulsating logo stopped.
Then I tried with Esc only to see the exact same line in the end.

The issue seems to affect lately quite many users as shown by the google
results of the past month / week or so.

I have also tried shutting down from the console with shutdown -and all
the parameters after that suggested online- and sudo poweroff but
unfortunately they didn't do the trick. The exact same situation
occurred.

Unmounting the swap as suggested online doesn't work.

Also rebooting the system is not working either due to the same issue.

So right now the only way for me to poweroff the machine is to press the
power button on the keyboard continuously.

Reproducible: Always

Steps to Reproduce:
1.Install OS
2.Do something, anything or nothing
3.Try to shutdown or reboot

Actual Results:
The computer is not shutting down: "Reached target shutdown" and hangs there.

Expected Results:
Powering off the machine.

For what it's worth, closing the lid won't suspend the system, but using
the menu buttons for suspension will do it.

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

** Tags: xenial

** Attachment added: "The final screen as seen in kubuntu now after pressing
esc."

https://bugs.launchpad.net/bugs/1594023/+attachment/4686351/+files/IMG_20160519_122237.jpg

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

Title:
Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in systemd package in Ubuntu:
New

Bug description:
This is about a fresh Ubuntu 16.04 install on a new laptop (asus
x540sa). After pressing the shutdown button in the start menu; the
shutdown procedure starts and in the final splash screen the system
just hangs. Tried a second time by pressing Esc once the splash screen
showed up and I saw that it reaches the line "Reached target shutdown"
and just stops there, no matter how long I leave it there the machine
won't turn off.

I also tried a Kubuntu 16.04 fresh install on the same machine and it
hanged too at the final splash screen where the pulsating logo
stopped. Then I tried with Esc only to see the exact same line in the
end.

The issue seems to affect lately quite many users as shown by the
google results of the past month / week or so.

I have also tried shutting down from the console with shutdown -and
all the parameters after that suggested online- and sudo poweroff but
unfortunately they didn't do the trick. The exact same situation
occurred.

Unmounting the swap as suggested online doesn't work.

Also rebooting the system is not working either due to the same issue.

So right now the only way for me to poweroff the machine is to press
the power button on the keyboard continuously.

Reproducible: Always

Steps to Reproduce:
1.Install OS
2.Do something, anything or nothing
3.Try to shutdown or reboot

Actual Results:
The computer is not shutting down: "Reached target shutdown" and hangs there.

Expected Results:
Powering off the machine.

For what it's worth, closing the lid won't suspend the system, but
using the menu buttons for suspension will do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594023/+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 1512068] Re: Python ctypes.util , Shell Injection in find_library()

2016-06-18 Thread Bug Watch Updater

** Changed in: python
   Status: New => Fix Released

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

Title:
  Python ctypes.util , Shell Injection in find_library()

Status in Python:
  Fix Released
Status in python2.7 package in Ubuntu:
  New

Bug description:
  https://github.com/Legrandin/ctypes/issues/1

  The find_library() function can execute code when special chars like ;|`<>$ 
are in the name.
  The "os.popen()" calls in the util.py script should be replaced with 
"subprocess.Popen()".

  Demo Exploits for Linux :
  

  >>> from ctypes.util import find_library
  >>> find_library(";xeyes")# runs  xeyes 
  >>> find_library("|xterm")# runs terminal
  >>> find_library("")# runs gimp
  >>> find_library("$(nautilus)")  # runs filemanager
  >>> find_library(">test")   # creates, and if exists, 
erases a file "test"

   Traceback 

  >>> find_library("`xmessage hello`")# shows a message, press ctrl+c for 
Traceback
  ^CTraceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3.4/ctypes/util.py", line 244, in find_library
  return _findSoname_ldconfig(name) or _get_soname(_findLib_gcc(name))
File "/usr/lib/python3.4/ctypes/util.py", line 99, in _findLib_gcc
  trace = f.read()
  KeyboardInterrupt

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libpython2.7-stdlib 2.7.10-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  1 10:34:38 2015
  InstallationDate: Installed on 2015-10-09 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151009)
  SourcePackage: python2.7
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1512068/+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 1384374] Re: Dash pauses/stutters during scope switching left/right

2016-06-18 Thread Andrea Bernabei

@Albert and @Kevin: please find the full log attached.

I had a quick look, the main thread is chocking on the polish phase.
So it seems a layout performance problem, unless we're using Canvas in the QML 
code (Canvas does the rendering in the polish method, iirc)

Examples from the log:

3.4 seconds polish phase here
qt.scenegraph.renderloop: update from item QQuickView(0x7a98a0)
qt.scenegraph.renderloop: update from item QQuickView(0x7a98a0)
qt.scenegraph.time.renderloop: Frame prepared with 'threaded' renderloop, 
polish=3479, lock=0, blockedForSync=78, animations=24 - (on Gui thread) 
QQuickView(0x7a98a0)
qt.scenegraph.time.glyph: distancefield: 29 glyphs prepared in 23ms, 
rendering=15, upload=8
Pre-populating scope "com.canonical.elpais_ELPAIS"
qt.scenegraph.time.texture: atlastexture uploaded in: 0ms (94x20)

or

1.3sec polish phase
qt.scenegraph.renderloop: update from item QQuickView(0x7a98a0)
:138:1: QML Label: Binding loop detected for property "height"
qt.scenegraph.time.renderloop: Frame prepared with 'threaded' renderloop, 
polish=1297, lock=0, blockedForSync=40, animations=119 - (on Gui thread) 
QQuickView(0x7a98a0)
flushUpdates: "com.canonical.scopes.engadget_engadget" #results = 25 finalize: 
true
Adding # 25 results to category "root"
qt.scenegraph.renderloop: update from item QQuickView(0x7a98a0)

or

1.285sec polish phase
qt.scenegraph.renderloop: update from item QQuickView(0x7a98a0)
qt.scenegraph.renderloop: - lock for sync
qt.scenegraph.renderloop: - wait for sync
qt.scenegraph.renderloop: (RT) WM_RequestSync
qt.scenegraph.renderloop: (RT) --- done 
processEventsAndWaitForMore()
qt.scenegraph.renderloop: (RT) syncAndRender()
qt.scenegraph.renderloop: (RT) - updatePending, doing sync
qt.scenegraph.renderloop: (RT) sync()
qt.scenegraph.renderloop: (RT) sceneGraphChanged
qt.scenegraph.renderloop: (RT) - sync complete, waking Gui
qt.scenegraph.renderloop: (RT) - rendering started
qt.scenegraph.renderloop: - unlock after sync
qt.scenegraph.time.renderloop: Frame prepared with 'threaded' renderloop, 
polish=1285, lock=0, blockedForSync=32, animations=0 - (on Gui thread) 
QQuickView(0x7a98a0)
flushUpdates: "com.canonical.scopes.reddit" #results = 70 finalize: true
Last result index= 30 category "posts"
qt.scenegraph.renderloop: update from item QQuickView(0x7a98a0)
qt.scenegraph.renderloop: - posting update
Added # 70 results (called with 100 ), current results#= 100


See the 3+ secs polish time, that's the kind of freezes I'm seeing. There are 
also multiple 1+sec and 0.1secs+ of polish times in the log.


There are also many examples of
:128:1: QML Label: Binding loop detected for property "height"

and 
:121:2: QML Icon: Binding loop detected for property "width"

Those could be disturbing the polish phase, although they're likely not
the cause of *all* the freezes.

** Attachment added: "unity8-dash qt.scenegraph.* log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1384374/+attachment/4686325/+files/unity8-dash.log

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

Title:
  Dash pauses/stutters during scope switching left/right

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Dash pauses/stutters during scope switching left/right.

  Watching the log:   tail -f ~/.cache/upstart/unity8-dash.log

  I can see error messages flood out whenever the dash pauses/stutters
  during left/right swipes:

  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"

[Touch-packages] [Bug 1573587] Re: jerky mouse when accessing unity-control-center

2016-06-18 Thread EdiD

I use Ubuntu since 13.04 and every version until 16.04 was without this
issue.

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

Title:
  jerky mouse when accessing unity-control-center

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Fresh installation of Ubuntu 16.04 amd64 with usb roccat kone xtd
  When I access unity-control-center or things like about computer or smplayer 
- mouse moving is jerky for a while and then return to smooth, normal work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Apr 22 14:35:34 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8fecb235-f1d2-417c-b346-823e97a843c0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-A
  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.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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
  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: Fri Apr 22 13:15:43 2016
  xserver.configfile: default
  xserver.errors:

  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/1573587/+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 1570653] Re: 4K Monitor not detected properly

kelargo, to clarify, were you using the radeon or fglrx driver in 15.10?

** Description changed:

  4K monitor is not properly detected.
  
  using xfce desktop "Display" utility, my monitor is detected as
  "Goldstar Company Ltd 27" with a resolution of 3840x2160 and 60.0Hz
  
  The actual monitor is an LG 31MU97-B Black 31" with a resolution of
  4096x2160.
  
  I'm pretty sure the Monitor's resolution was properly detected in 15.10 
(4096x2160).  It was called "Goldstar Company Ltd" but
  I do not recall which size was detected.  (27" or 31")
  
  I remember seeing a 4K youtube video in 15.10 and noting the black bands
  on each side of the display, due to the difference between 3840 and
  4096.
  
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: xorg 1:7.7+13ubuntu3
- ProcVersionSignature: Ubuntu 4.4.0-18.34-lowlatency 4.4.6
- Uname: Linux 4.4.0-18-lowlatency x86_64
- ApportVersion: 2.20.1-0ubuntu2
- Architecture: amd64
- CurrentDesktop: XFCE
- Date: Thu Apr 14 20:24:44 2016
- InstallationDate: Installed on 2015-11-24 (142 days ago)
- InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
- SourcePackage: xorg
- UpgradeStatus: Upgraded to xenial on 2016-04-15 (0 days ago)
- --- 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: 2016-04-14 20:11:08,467 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
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (prog-if 00 [VGA controller])
-Subsystem: PC Partner Limited / Sapphire Technology Curacao PRO [Radeon R7 
370 / R9 270/370 OEM] [174b:e271]
+  Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (prog-if 00 [VGA controller])
+    Subsystem: PC Partner Limited / Sapphire Technology Curacao PRO [Radeon R7 
370 / R9 270/370 OEM] [174b:e271]
  InstallationDate: Installed on 2015-11-24 (204 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  LightdmGreeterLog:
-  upstart: indicator-application main process (2191) killed by TERM signal
-  Invalid MIT-MAGIC-COOKIE-1 key
+  upstart: indicator-application main process (2191) killed by TERM signal
+  Invalid MIT-MAGIC-COOKIE-1 key
  LightdmGreeterLogOld:
-  ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
-  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
-  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
-  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
-  upstart: indicator-application main process (1802) killed by TERM signal
+  ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
+  upstart: indicator-application main process (1802) killed by TERM signal
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-lowlatency 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.40-lowlatency 4.4.8
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-15 (62 days ago)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1

[Touch-packages] [Bug 1594013] [NEW] package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-06-18 Thread Anindya Saha

Public bug reported:

This happened when I am installing Ubuntu mate 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sat Jun 18 18:12:10 2016
DuplicateSignature:
 Setting up initramfs-tools (0.122ubuntu8) ...
 update-initramfs: deferring update (trigger activated)
 cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file or 
directory
 dpkg: error processing package initramfs-tools (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This happened when I am installing Ubuntu mate 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 18 18:12:10 2016
  DuplicateSignature:
   Setting up initramfs-tools (0.122ubuntu8) ...
   update-initramfs: deferring update (trigger activated)
   cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file 
or directory
   dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1594013/+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 1594012] [NEW] Pulseaudio cookie should be deleted on upgrade from trusty to xenial

2016-06-18 Thread Pilot6

Public bug reported:

After upgrades from trusty to xenial sound volume is not saved on
reboots.

That is probably because file format of the cookie has been changed.

After I deleted the cookie from ~/.config/pulse the volume started to be
saved.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pilot6 2644 F pulseaudio
 /dev/snd/controlC0:  pilot6 2644 F pulseaudio
CurrentDesktop: Unity
Date: Sat Jun 18 21:54:50 2016
InstallationDate: Installed on 2013-10-17 (975 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to xenial on 2016-04-29 (50 days ago)
dmi.bios.date: 04/02/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L LE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/02/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: do-release-upgrade trusty volume xenial

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

Title:
  Pulseaudio cookie should be deleted on upgrade from trusty to xenial

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrades from trusty to xenial sound volume is not saved on
  reboots.

  That is probably because file format of the cookie has been changed.

  After I deleted the cookie from ~/.config/pulse the volume started to
  be saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pilot6 2644 F pulseaudio
   /dev/snd/controlC0:  pilot6 2644 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jun 18 21:54:50 2016
  InstallationDate: Installed on 2013-10-17 (975 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-04-29 (50 days ago)
  dmi.bios.date: 04/02/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/02/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1594012/+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 1572587] Re: mouse cursor trails on second monitor

Dan, to clarify, which version of the driver specifically did you test?

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

Title:
  mouse cursor trails on second monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using a second monitor with my lenovo laptop. 
  The mouse cursor forms a trail only on the second monitor and slowly 
disappears after a few seconds or a right mouse click .

  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.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 20 09:46:44 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:191d] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:222e]
 Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:222e]
  InstallationDate: Installed on 2016-03-30 (20 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: LENOVO 20ENCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=5dac-b187-4366-8994-da3fb720de50 ro vga=791
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/31/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ENCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET41W(1.15):bd12/31/2015:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20ENCTO1WW
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  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-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
  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 Apr 18 14:45:37 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   39984 
   vendor VSC
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1572587/+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 1559805] Re: suspend not working with latest xenial and kernel 4.4.0

brett hassall, it will help immensely if you filed a new report (not 
apport-collect to this one) with Ubuntu by ensuring you have the package 
xdiagnose installed, and that you click the Yes button for attaching additional 
debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

** Attachment removed: "xdpyinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684644/+files/xdpyinfo.txt

** Attachment removed: "XorgLogOld.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684643/+files/XorgLogOld.txt

** Attachment removed: "XorgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684642/+files/XorgLog.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684640/+files/ProcModules.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684641/+files/UdevDb.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684638/+files/ProcCpuinfo.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684639/+files/ProcInterrupts.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684637/+files/Lsusb.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684636/+files/Lspci.txt

** Attachment removed: "LightdmLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684635/+files/LightdmLog.txt

** Attachment removed: "LightdmGreeterLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684634/+files/LightdmGreeterLog.txt

** Attachment removed: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684633/+files/LightdmDisplayLog.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684632/+files/JournalErrors.txt

** Attachment removed: "BootLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684629/+files/BootLog.txt

** Attachment removed: "DpkgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684631/+files/DpkgLog.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684630/+files/CurrentDmesg.txt

** Tags removed: apport-collected ubuntu

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

Title:
  suspend not working with latest xenial and kernel 4.4.0

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  suspend stops but never finishes and needs a reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Mar 20 22:45:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-04 (168 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-03-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+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 1370629] Re: 51-android.rules

2016-06-18 Thread Jeremy Bicha

** Also affects: android-platform-system-core (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
   51-android.rules

Status in android-platform-system-core package in Ubuntu:
  Confirmed
Status in android-tools package in Ubuntu:
  Confirmed

Bug description:
  i wish you can add the file 51-android.rules to the project,according 
http://developer.android.com/tools/device.html.
  you can find the file 51-android.rules in my project.
  https://github.com/snowdream/51-android

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-platform-system-core/+bug/1370629/+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 1370629] Re: 51-android.rules

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

** Changed in: android-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
   51-android.rules

Status in android-platform-system-core package in Ubuntu:
  Confirmed
Status in android-tools package in Ubuntu:
  Confirmed

Bug description:
  i wish you can add the file 51-android.rules to the project,according 
http://developer.android.com/tools/device.html.
  you can find the file 51-android.rules in my project.
  https://github.com/snowdream/51-android

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-platform-system-core/+bug/1370629/+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 1370629] Re: 51-android.rules

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

** Changed in: android-platform-system-core (Ubuntu)
   Status: New => Confirmed

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

Title:
   51-android.rules

Status in android-platform-system-core package in Ubuntu:
  Confirmed
Status in android-tools package in Ubuntu:
  Confirmed

Bug description:
  i wish you can add the file 51-android.rules to the project,according 
http://developer.android.com/tools/device.html.
  you can find the file 51-android.rules in my project.
  https://github.com/snowdream/51-android

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-platform-system-core/+bug/1370629/+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 1564426] Re: Import problem - Spanish (es) - glib20 in Ubuntu Xenial package "glib2.0"

2016-06-18 Thread Mathew Hodson

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Import problem - Spanish (es) - glib20 in Ubuntu Xenial package
  "glib2.0"

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Looks like there was an accidental word-wrap problem in po/es.po.

  Line 13 is really the end of line 12. I've included a patch to send
  upstream.

  Here's a copy of the email that IS has been getting for a while now:

  Hello Launchpad Translations Administrators,

  On 2016-03-18 13:50z (12 days 14 hours 16 minutes ago), you uploaded a
  file with Spanish (es) translations for glib20 in Ubuntu Xenial package
  "glib2.0" to Launchpad.

  We were unable to import the file because of errors in its format:

  Line 13: Invalid content: u', 2013, 2014, 2015, 2016.'

  If you use gettext, you can check your file for correct formatting with
  the 'msgfmt -c' command. Please fix any errors raised by msgfmt and
  upload the file again. If you check the file and you don't find any
  error in it, please look for an answer or file a question at
  https://answers.launchpad.net/rosetta/

  For your convenience, you can get the file you uploaded at:
  http://launchpadlibrarian.net/250464407/es.po

  Thank you,

  The Launchpad team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1564426/+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 1565679] Re: No console/display output after boot

Claudio Kuenzler, now that the packages is changed to something potentially 
related and you have installed, could you now please execute at a terminal:
apport-collect 1565679

Worst case scenario is boot via a live environment
http://cdimage.ubuntu.com/daily-live/current/ and then execute it.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  No console/display output after boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 BETA2 installed correctly on Dell PowerEdge 1850 server. 
  Booting seems to work correctly too (can see it on the monitor), but when I 
expect the login prompt, no output is sent to the monitor (black). 
  I documented this on the following video: 
https://www.youtube.com/watch?v=VAtnBv8uZf8

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Apr  4 12:23:48 2016
  InstallationDate: Installed on 2016-04-04 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565679/+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 1594011] [NEW] Radeon GPU driver crashes while playing games

2016-06-18 Thread Valerio

Public bug reported:

This happens every time i play Team Fortress 2. Sometimes the game
freezes completely and after 10-20 seconds it recovers itself. Looking
at dmesg output seems like the GPU driver crashes and restarts. I'm
using the open drivers with a Radeon R9 270.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libdrm-radeon1 2.4.67-1ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun 18 20:13:23 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu3
 libdrm2 2.4.67-1ubuntu0.16.04.1
 libgcc1 1:6.0.1-0ubuntu1
InstallationDate: Installed on 2016-04-22 (56 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: libdrm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug radeon xenial

** Attachment added: "dmesg output after 2-3 freezes"
   https://bugs.launchpad.net/bugs/1594011/+attachment/4686279/+files/dmesg

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

Title:
  Radeon GPU driver crashes while playing games

Status in libdrm package in Ubuntu:
  New

Bug description:
  This happens every time i play Team Fortress 2. Sometimes the game
  freezes completely and after 10-20 seconds it recovers itself. Looking
  at dmesg output seems like the GPU driver crashes and restarts. I'm
  using the open drivers with a Radeon R9 270.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdrm-radeon1 2.4.67-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 18 20:13:23 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libdrm2 2.4.67-1ubuntu0.16.04.1
   libgcc1 1:6.0.1-0ubuntu1
  InstallationDate: Installed on 2016-04-22 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libdrm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1594011/+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 1554895] Re: Erratic mouse behaviour

2016-06-18 Thread Theo

I just managed to try this.

Negative, the problem still persists even with the latest version.

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

Title:
  Erratic mouse behaviour

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 14.04 on a Lenovo Yoga 2 13 and, after a few
  minutes of working, the mouse pointer goes crazy. It goes to the
  bottom right corner of the screen and flickers, clicking stuff
  randomly.

  * Adding a USB mouse and deactivating the trackpad makes no difference.
  * Tried Kubuntu 15.10, problem still there.
  * Tried suggestions in 

  http://ubuntuforums.org/showthread.php?t=2235704
  
http://ubuntuforums.org/showthread.php?t=2229831=2=13451930#post13451930

  without success also.

  As mentioned by other users, my laptop is currently unusable. I do not
  want to switch to Windows but, given the current hardware I have, I do
  not see how I can resolve this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20150916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  9 01:44:53 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-03-07 (2 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  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
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2016-05-19 (24 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: LENOVO 20344
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 4.2.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  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 Jun 12 23:26:25 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1069 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554895/+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 1575301] Re: GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

Adam Colligan, to clarify, did this issue not occur in a release prior
to 16.04 without installing any PPAs or 3rd party packages (i.e. default
install)?

** Tags added: bios-outdated-f.33

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

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

Title:
  GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice
  dialog boxes (regression)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This behavior began sometime in April 2016 (while using Ubuntu 16.04
  Beta 2, Unity) and has continued to the present.

  Dialog boxes in LibreOffice (including the automated recovery dialog
  on LO start) started displaying garbled text and garbled or missing
  button icons. Interacting with them -- or often even their appearance
  at all -- causes a rapid crash of the whole graphical session and a
  free trip back to the login screen.  Syslog shows a GPU hang (stuck on
  render ring).

  This is an Intel Core i7-4510U with Haswell-ULT Integrated Graphics
  Controller (HP Envy x360 convertible laptop).

  Before the upgrade from 15.10 to 16.04, I had the xorg-edgers
  repository enabled and then had used the installation tool from 01.org
  to install the Intel graphics stack.  As part of troubleshooting this,
  I have removed/purged the 01.org sources/packages/modules as best I
  could (16.04 not supported) and also disabled the edgers repository.
  This has not affected the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:04:07 2016
  DistUpgraded: 2016-03-26 18:47:13,658 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
  InstallationDate: Installed on 2014-08-10 (625 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-26 (30 days ago)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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
  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 N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 26 14:02:01 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "intel" (module does not exist, 0)
   Failed to load module "intel" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver:

[Touch-packages] [Bug 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2016-06-18 Thread Thomas Mayer

I guess I know why upstream cairo never made it into Firefox: Mozilla's
version of cairo is more like a fork than a version of cairo with a few
patches applied.

Not only that: Some of the patches are documented in .patch files and a
README. And some are not documented at all with just the change in the
lib's files. E. g. https://hg.mozilla.org/mozilla-
central/rev/0edb40641826 does not have a .patch file or README entry.

These days, it would make sense to maintain a git branch of cairo with
all the patches applied. Then they would be able to simply merge. And
have a dependency to that branch.

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  New
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 1573587] Re: jerky mouse when accessing unity-control-center

EdiD, to advise, xorg is used on Launchpad as a starting point for all
things Xserver related (core, graphics, input, etc.).

Despite this, did this issue not occur for you personally in a Ubuntu
release prior to 16.04?

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

Title:
  jerky mouse when accessing unity-control-center

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Fresh installation of Ubuntu 16.04 amd64 with usb roccat kone xtd
  When I access unity-control-center or things like about computer or smplayer 
- mouse moving is jerky for a while and then return to smooth, normal work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Apr 22 14:35:34 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8fecb235-f1d2-417c-b346-823e97a843c0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-A
  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.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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
  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: Fri Apr 22 13:15:43 2016
  xserver.configfile: default
  xserver.errors:

  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/1573587/+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 1020279] Re: Sound doesn't work randomly. [700Z3A/700Z4A/700Z5A/700Z5B, Realtek ALC269VC, Speaker, Internal] No sound at all

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

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

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

Title:
  Sound doesn't work randomly. [700Z3A/700Z4A/700Z5A/700Z5B, Realtek
  ALC269VC, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sometimes audio randomly stops working. It's happened 3 times now, and 
requires a restart to fix.
  It seems like it happens when I put my headphones into the audio jack, but 
this could just be correlation, rather than causation, as I put my headphones 
in when I'm trying to listen to audio.

  Sound doesn't work for both my headphones, and my internal speakers
  when this happens, and the right audio device is selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ryan   4164 F pulseaudio
   /dev/snd/pcmC0D0p:   ryan   4164 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc080 irq 54'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:10ec0269,144dc0b3,00100202 
HDA:80862805,80860101,0010'
 Controls  : 25
 Simple ctrls  : 12
  Date: Mon Jul  2 14:17:45 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   4164  4164  ryan  F pulseaudio
   /dev/snd/pcmC0D0p:   ryan  F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [700Z3A/700Z4A/700Z5A/700Z5B, Realtek ALC269VC, Speaker, Internal] No 
sound at all
  UpgradeStatus: Upgraded to precise on 2012-06-09 (23 days ago)
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 12FD
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 700Z3A/700Z4A/700Z5A/700Z5B
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr12FD:bd03/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3A/700Z4A/700Z5A/700Z5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn700Z3A/700Z4A/700Z5A/700Z5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 700Z3A/700Z4A/700Z5A/700Z5B
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1020279/+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 1585094] Re: Random stuck keys on Lenovo Yoga 13

vak, could you please advise after which update specifically did this
problem occur or vanish with?

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

Title:
  Random stuck keys on Lenovo Yoga 13

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  pressing arrow keys leads randomly to the effect of stuck number key
  and produces output in consoles or text editors like: "22" or
  "88". Pressing some other key stops the infinite flooding.

  This may (or not) be related to the following flooding in
  /var/log/system

  May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed 
(translated set 2, code 0xbe on isa0060/serio0).
  May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes 
e03e ' to make it known.
  May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key 
released (translated set 2, code 0xbe on isa0060/serio0).
  May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes 
e03e ' to make it known.

  
  these messages are generated approximately each 200 msec. If the former is 
not related to stuck key problem, please, ignore.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 24 09:45:39 2016
  DistUpgraded: 2016-04-24 00:21:19,103 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
  InstallationDate: Installed on 2013-11-17 (918 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 2191
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=f6200601-c430-459d-abab-c6d45f1e147a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago)
  dmi.bios.date: 02/28/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN55WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 2191
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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
  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: Tue May 24 08:57:44 2016
  xserver.configfile: default
  xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 864 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1585094/+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 1569876] Re: Mouse trails disappear only on window refresh

Avishay, to clarify, which 4 different version of the nvidia drivers
specifically?

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

Title:
  Mouse trails disappear only on window refresh

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  While using nouveau, when I move the mouse it leaves trails that
  disappear when I move the mouse over them or when I refresh the
  screen. The mouse cursor is distorted when moving it slowly which
  makes it harder to click on small buttons (e.g., resizing a window) as
  it's hard to tell where exactly the mouse is located.

  WORKAROUND: Use nivida 367.18.

  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.0:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  BootLog: /dev/sda6: clean, 789425/48300032 files, 33613548/193179136 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Apr 13 15:29:36 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Skylake Integrated Graphics [17aa:222e]
   NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e]
  InstallationDate: Installed on 2016-04-01 (12 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  MachineType: LENOVO 20EN0013US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=8e0207fc-0fb8-42e7-9dfc-a301c74d2146 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET47W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN0013US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET47W(1.21):bd03/08/2016:svnLENOVO:pn20EN0013US:pvrThinkPadP50:rvnLENOVO:rn20EN0013US:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EN0013US
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  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: Wed Apr 13 07:51:19 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1569876/+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 1559952] Re: slow running pc

chris brown, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559952/comments/6
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  slow running pc

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  slow running pc

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Mar 21 09:25:49 2016
  DistUpgraded: 2015-02-10 16:45:11,631 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300] [1002:5b60] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0602]
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0603]
  InstallationDate: Installed on 2011-11-13 (1589 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: Dell Inc. Dell DM051
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic 
root=UUID=67826823-094e-43a7-9f61-885e0f605b44 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2015-02-10 (404 days ago)
  dmi.bios.date: 01/08/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0WG261
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/08/2007:svnDellInc.:pnDellDM051:pvr:rvnDellInc.:rn0WG261:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM051
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Mar 21 09:06:14 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSilverCrest STMS2017A1 KEYBOARD, id 8
   inputSilverCrest STMS2017A1 KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559952/+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 1576228] Re: Black borders around all windows

** Description changed:

- There seems to be a bug somewhere  in [ kernel OR xorg OR nvidia proprietary 
driver ] in the display stack.
- After the laptop ( dell XPS L501X ) resumes from suspend there are wide black 
borders around all windows with close/minimize/maximize buttons blacked out.
- 
- [ image attached: black border on all windows ]
- 
- It occurs inconsistently, as it doesn't happen every time the computer 
resumes.
- ( Slight possibility that it usually occurs after long suspend, i.e. resuming 
after long time ).
- 
=
+ While using the nvidia proprietary drivers in 14.04 - 16.04, my Dell XPS
+ L501X resumes from suspend, but displays wide black borders around all
+ windows with close/minimize/maximize buttons blacked out as per attached
+ screenshot. It occurs inconsistently, as it doesn't happen every time
+ the computer resumes.
  
  Also there seems to be certain amount of performance degradation as if
- the graphics driver was running at half-strength ( and I don't  mean
- software-only rendering, neither do I mean switch over to nouveau open
- source driver )
+ the graphics driver was running at half-strength. The "nVidia X Server
+ Settings" app suggests its in maximum performance mode.
  
- The "nVidia X Server Settings" app suggests its in maximum performance
- mode.
+ Adhoc Workaround: switch display layout (I have an external monitor/TV
+ attached to HDMI port) changing anything such as arrangement or
+ resolution of the displays, etc. corrects the black border issue.
  
- 
==
- 
- Adhoc Workaround: switch display layout ( I have an external monitor/TV
- attached to HDMI port ) changing anything such as arrangement or
- resolution of the displays, etcetera... corrects the black border issue
- ( and also possibly performance issue )
- 
- This bug has been present in Ubuntu 14.04, 15.04, 15.10 and now in 16.04
- as well. ( It was probably present before that as well )
- 
- 
==
- 
- p.s. this is only partial duplicate of black border issue as the black
- borders appear on every window, not just windows with new header bars or
- client side decoration...
+ WORKAROUND: Use nouveau.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
-  GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
+  GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
-  Your system is not currently configured to drive a VGA console
-  on the primary VGA device. The NVIDIA Linux graphics driver
-  requires the use of a text-mode VGA console. Use of other console
-  drivers including, but not limited to, vesafb, may result in
-  corruption and stability problems, and is not supported.
+  Your system is not currently configured to drive a VGA console
+  on the primary VGA device. The NVIDIA Linux graphics driver
+  requires the use of a text-mode VGA console. Use of other console
+  drivers including, but not limited to, vesafb, may result in
+  corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: [[0;32m  OK  [0m] Started LSB: Speech Dispatcher.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 28 18:43:37 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
-  nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
+  bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
+  nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e]
+  NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e]
  InstallationDate: Installed on 2016-04-23 (4 days ago)

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

zanonmark, to clarify, I'm referring to a past Ubuntu release on the
hardware reported about in the Bug Description (not some other hardware,
or something someone else said).

Hence, it would be helpful to rule out a regression by testing a live
environment from http://releases.ubuntu.com/ .

Could you please advise?

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

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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
  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 Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1594002] [NEW] On Ubuntu touch, when receiving call while handsfree is connected, system behaves erratically and freezes

2016-06-18 Thread AlainKnaff

Public bug reported:

This evening, I received a call in my car (Toyota Prius), while my
Aquaris E5 (Ubuntu touch) phone was connected via bluetooth handsfree
mode.

Ring tone sounded all right over the car's audio system, and call pick
up UI was displayed on central console.

However, the buttons would not react.

Buttons on the phone itself where reactive at first, but call still
wasn't connected. A short time after this phone's UI froze... and then
unfroze after a minute. Eventually two calls were shown, one being
active, and one "on hold". However, neither was connected (could not
hear other party / other party could not hear me). Eventually, other
party gave up, and tried again a minute later.

On that second call, I picked it up right on the phone's UI, and this
time it worked, with audio through car's system.

I found the following in my log:

Jun 18 12:57:18 localhost pulseaudio[2198]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
Jun 18 12:58:20 localhost bluetoothd[667]: Unable to get io data for Phone Book 
Access: getpeername: Transport endpoint is not connected (107)

=> start of unrelated trip in the morning.


Jun 18 13:20:35 localhost bluetoothd[667]: Unable to get io data for hfp_ag: 
getpeername: Transport endpoint is not connected (107)

=> end of unrelated trip in the morning

Jun 18 17:47:34 localhost bluetoothd[667]: Unable to get io data for Phone Book 
Access: getpeername: Transport endpoint is not connected (107)
Jun 18 17:47:19 localhost pulseaudio[2198]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile

=> start of trip in the evening, during which I received the call.


Jun 18 17:49:27 localhost pulseaudio[2198]: [pulseaudio] 
module-bluez5-device.c: SCO stream went down
Jun 18 17:50:07 localhost bluetoothd[667]: Unable to get io data for hfp_ag: 
getpeername: Transport endpoint is not connected (107)
Jun 18 17:50:07 localhost pulseaudio[2198]: message repeated 622601 times: [ 
[pulseaudio] module-bluez5-device.c: SCO stream went down]
Jun 18 17:50:12 localhost pulseaudio[2198]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
Jun 18 17:50:45 localhost bluetoothd[667]: Unable to get io data for Phone Book 
Access: getpeername: Transport endpoint is not connected (107)
Jun 18 17:51:11 localhost pulseaudio[2198]: [pulseaudio] 
module-bluez5-device.c: Can't resume SCO over PCM

=> the call

Jun 18 18:16:01 localhost bluetoothd[667]: Unable to get io data for
hfp_ag: getpeername: Transport endpoint is not connected (107)

=> end of trip

/var/log/auth.log had the following messages about bluez (a
...
auth.log:Jun 18 17:15:49 localhost dbus[621]: message repeated 7 times: [ 
[system] Rejected send message, 4 matched rules; type="method_return", 
sender=":1.21" (uid=0 pid=1910 comm="ofonod -P 
provision,udev*,dun*,smart*,hfp_bluez5,s") interface="(unset)" member="(unset)" 
error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=761 
comm="/usr/bin/powerd ")]
auth.log:Jun 18 17:19:40 localhost dbus[621]: [system] Rejected send message, 4 
matched rules; type="method_return", sender=":1.21" (uid=0 pid=1910 
comm="ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,s") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" 
(uid=0 pid=761 comm="/usr/bin/powerd ")
auth.log:Jun 18 17:19:40 localhost dbus[621]: [system] Rejected send message, 4 
matched rules; type="method_return", sender=":1.21" (uid=0 pid=1910 
comm="ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,s") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" 
(uid=0 pid=761 comm="/usr/bin/powerd ")
auth.log:Jun 18 17:49:07 localhost dbus[621]: [system] Rejected send message, 5 
matched rules; type="method_return", sender=":1.51" (uid=32011 pid=2198 
comm="pulseaudio --start --log-target=syslog ") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.21" 
(uid=0 pid=1910 comm="ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,s")
auth.log:Jun 18 17:49:27 localhost dbus[621]: [system] Rejected send message, 5 
matched rules; type="method_return", sender=":1.51" (uid=32011 pid=2198 
comm="pulseaudio --start --log-target=syslog ") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.21" 
(uid=0 pid=1910 comm="ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,s")
auth.log:Jun 18 17:49:46 localhost dbus[621]: [system] Rejected send message, 4 
matched rules; type="method_return", sender=":1.21" (uid=0 pid=1910 
comm="ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,s") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" 
(uid=0 pid=761 comm="/usr/bin/powerd ")
auth.log:Jun 18 17:49:46 localhost dbus[621]: [system] Rejected send message, 4 
matched rules; type="method_return",

[Touch-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

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

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

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Confirmed
Status in lxsession source package in Xenial:
  Confirmed

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+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 1181440] Re: Change to default keyboard layout in gd locale

** Package changed: ubuntu => xkeyboard-config (Ubuntu)

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

Title:
  Change to default keyboard layout in gd locale

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  I'm going round the houses with this one :) The l10n mailing list
  first pointed me at freedesktop.org where I filed a bug which was shot
  down (https://bugs.freedesktop.org/show_bug.cgi?id=64478) - not that I
  understood all of the explanation but apparently it's the wrong place
  to change the default keyboard layout for a locale.

  The request and reason for it is as follows:

  I would like to request changing the default keyboard layout for
  Scottish Gaelic (gd) which is set during first installation of Ubuntu.
  Currently the top layout is IBM 166 which is neither known in the
  community nor practical. The layout of choice is "English United
  Kingdom Extended" as it requires the least amount of instruction and
  otherwise does not differ from en-GB which is the most widely used
  layout in the Gaelic community currently.

  The impact should be low as there is a tiny number of users currently
  but we're currently conducting a major clean-up of the Ubuntu
  localization (incl. faulty locale data) and hope to grow usage but the
  current default layout is a real show stopper.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1181440/+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 1191501] Re: Galleria app crashes on edit images

** Package changed: ubuntu => gallery-app (Ubuntu)

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

Title:
  Galleria app crashes on edit images

Status in gallery-app package in Ubuntu:
  New

Bug description:
  When we edit an images the Galleria app (app of Unity next or 8) the
  program crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1191501/+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 1181440] [NEW] Change to default keyboard layout in gd locale

You have been subscribed to a public bug:

I'm going round the houses with this one :) The l10n mailing list first
pointed me at freedesktop.org where I filed a bug which was shot down
(https://bugs.freedesktop.org/show_bug.cgi?id=64478) - not that I
understood all of the explanation but apparently it's the wrong place to
change the default keyboard layout for a locale.

The request and reason for it is as follows:

I would like to request changing the default keyboard layout for
Scottish Gaelic (gd) which is set during first installation of Ubuntu.
Currently the top layout is IBM 166 which is neither known in the
community nor practical. The layout of choice is "English United Kingdom
Extended" as it requires the least amount of instruction and otherwise
does not differ from en-GB which is the most widely used layout in the
Gaelic community currently.

The impact should be low as there is a tiny number of users currently
but we're currently conducting a major clean-up of the Ubuntu
localization (incl. faulty locale data) and hope to grow usage but the
current default layout is a real show stopper.

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
Change to default keyboard layout in gd locale
https://bugs.launchpad.net/bugs/1181440
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xkeyboard-config in Ubuntu.

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

[Touch-packages] [Bug 1191501] [NEW] Galleria app crashes on edit images

You have been subscribed to a public bug:

When we edit an images the Galleria app (app of Unity next or 8) the
program crashes.

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

-- 
Galleria app crashes on edit images
https://bugs.launchpad.net/bugs/1191501
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gallery-app in Ubuntu.

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

[Touch-packages] [Bug 1593993] [NEW] Links in the UI toolkit gallery app not working

2016-06-18 Thread Paul Sonnenschein

Public bug reported:

Ubuntu version: OTA 11 (bq Aquaris m10)

Click package: com.ubuntu.developer.bzoltan.ubuntu-ui-toolkit-gallery
1.3.1918.1

Expected action: The documentation is shown whenever I click on the API
documentation links.

Action: Nothing happens when clicking on the links.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Links in the UI toolkit gallery app not working

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Ubuntu version: OTA 11 (bq Aquaris m10)

  Click package: com.ubuntu.developer.bzoltan.ubuntu-ui-toolkit-gallery
  1.3.1918.1

  Expected action: The documentation is shown whenever I click on the
  API documentation links.

  Action: Nothing happens when clicking on the links.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1593993/+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 1363897] Re: kdb5_ldap_util can not create krbContainer

2016-06-18 Thread Reinhard

The on the whole very usefully documentation in

https://help.ubuntu.com/lts/serverguide

is still not updated to Gabriel Burkholder's message from 2015-01-11:

-
https://help.ubuntu.com/lts/serverguide/kerberos-ldap.html

Next, use the kdb5_ldap_util utility to create the realm:

sudo kdb5_ldap_util -D  cn=admin,dc=example,dc=com create -subtrees \
dc=example,dc=com -r EXAMPLE.COM -s -H ldap://ldap01.example.com
--

So setting up an kerberos server on ldap in ubuntu 16.04 is still a
pain.

What is do to to fix the documention?

PS:
I collected a lot of scripts for setting up an kerberos on ldap and other 
server in:
https://github.com/edvapp/networkbox
if they are useful for more people, any useful hints to make them more known?

Thanks
Reinhard

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

Title:
  kdb5_ldap_util  can not create krbContainer

Status in krb5 package in Ubuntu:
  Confirmed

Bug description:
  Following instructions on
  https://help.ubuntu.com/10.04/serverguide/kerberos-ldap.html
  creating the initial database with kdb5_ldap_util 
  (>>sudo kdb5_ldap_util -D cn=admin,dc=app,dc=tsn create -subtrees 
dc=app,dc=tsn -r APP.TSN -s -H ldap:///ldap01.app.tsn)
  fails with error message:
  >>kdb5_ldap_util: Kerberos Container create FAILED: Object class violation 
while creating realm 'APP.TSN'

  after reading these mails
  http://comments.gmane.org/gmane.comp.encryption.kerberos.general/18509
  setting up loglevel for slapd in syslog, following error message can be found:
  --
  Sep  1 09:52:19 ldap01 slapd[1165]: ==> hdb_add: dc=app,dc=tsn
  Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_required entry (dc=app,dc=tsn), 
objectClass "krbContainer"
  Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type "objectClass"
  Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type "cn"
  Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type 
"structuralObjectClass"
  Sep  1 09:52:19 ldap01 slapd[1165]: oc_check_allowed type "dc"
  Sep  1 09:52:19 ldap01 slapd[1165]: Entry (dc=app,dc=tsn), attribute 'dc' not 
allowed
  Sep  1 09:52:19 ldap01 slapd[1165]: hdb_add: entry failed schema check: 
attribute 'dc' not allowed (65)
  ---

  System: 
  Ubuntu 14.04 LTS
  slapd  2.4.31-1+nmu amd64
  krb5-config2.3
  krb5-kdc   1.12+dfsg-2u amd64
  krb5-kdc-ldap  1.12+dfsg-2u amd64
  krb5-locales   1.12+dfsg-2u 
  krb5-user  1.12+dfsg-2u amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1363897/+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 1498732] Re: keyboard layout setup

** Package changed: ubuntu => xkeyboard-config (Ubuntu)

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

Title:
  keyboard layout setup

Status in xkeyboard-config package in Ubuntu:
  Incomplete

Bug description:
  Keyboard layout in Ubuntu 15 setup doesn't seem to work.  When
  selecting "Dvorak" manually in the F3 menu or using the automatic
  layout detection, which correctly detects Dvorak, the layout isn't
  actually set.  For instance a couple screens later when asking for the
  hostname the keyboard layout is ASCII and when the machine boots
  asking for the username/password it's ASCII.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1498732/+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 1165313] Re: Right arrow comma and circulfex keys don't work anymore

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version.

When you test it and it is still an issue, kindly upload the updated
logs by running only once:

apport-collect 1165313

and any other logs that are relevant for this particular issue.

** Summary changed:

- Right arrow comma and circulfex keys don't work anymore
+ Right arrow, comma and circumflex keys don't work anymore

** Changed in: ubuntu
   Status: New => Incomplete

** Package changed: ubuntu => xkeyboard-config (Ubuntu)

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

Title:
  Right arrow, comma and circumflex keys don't work anymore

Status in xkeyboard-config package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04

  keyboard layout as given by parameters is : "French (Alternative)"

  After todays updates several keys including "Right Arrow Key" "Comma
  Key" and "Circumflex" don't work anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1165313/+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 1578657] Re: spanish keyboard not accentuating vowels

** Package changed: ubuntu => xkeyboard-config (Ubuntu)

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

Title:
  spanish keyboard not accentuating vowels

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  I've already added the Spanish language keyboard to unity and the keyboard 
indicator at the top indicates the Spanish keyboard and I do get Ñ and ñ
  however when I go to accentuate a vowel áéíóú it's not working

  the normal process is that I press the apostrophe key (in the us keyboard it 
would be two keys toward the right from "L") then select the vowel to be 
accentuated. 
  however you're not supposed to see anything until the vowel is selected.

  what is happening instead is that I'm getting an apostrophe right away
  when I press the tilde key.

  
  NOTE0:
  I've tested also other variants of the Spanish layout with similar success..

  NOTE1:
  I have installed cinnamon also and when I login to cinnamon it works, so I'm 
only experiencing the issue in unity.

  NOTE2:
  I'm very proficient with computers and have successfully done this many times.

  NOTE3: 
  I'm working on a fairly clean setup of Ubuntu 16.04 LTS
   I've only added Cinnamon and the Intel Drivers to the system and google 
chrome 
   system is also up to date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1578657/+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 1490738] Re: Lithuanian keyboard doesn't switch on

** Package changed: ubuntu => xkeyboard-config (Ubuntu)

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

Title:
  Lithuanian keyboard doesn't switch on

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Lithuanian keyboard gives no Lithuanian symbols. Using SUPER+SPACE it
  does change language indicator on the upper right corner of the
  desktop, but there's no Lt symbols where they are supposed to be.

  Lt symbols should be on the keyboard's upper number line. The symbol
  map still claims they are there. In matter of fact, when I switch to
  Lt keyboard, it still uses Finnish symbols. Finnish is my main
  keyboard at the moment.

  Before that, there were Russian symbols instead of Lt. So I
  uninstalled Rus keyboard. That caused Lt keyboard to show English
  symbols. After uninstalling Eng, now Lt keyboard is sticking with Fin.
  Adding new languages doesn't change behaviour (still Fi).

  Other languages on keyboard work fine. Uninstalling all keyboards
  except Lt, still makes no Lithuanian symbols.

  I tried uninstall Lithuanian keyboard (with reboot) and install again.
  Also tried different Lithuanian keyboards.

  Ubuntu 14.04.3 LTS 64-bit on MSI GE620DX laptop.

  (That's my first bug report, hope I'm doing it as it's supposed to be
  done.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1490738/+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 1490738] [NEW] Lithuanian keyboard doesn't switch on

You have been subscribed to a public bug:

Lithuanian keyboard gives no Lithuanian symbols. Using SUPER+SPACE it
does change language indicator on the upper right corner of the desktop,
but there's no Lt symbols where they are supposed to be.

Lt symbols should be on the keyboard's upper number line. The symbol map
still claims they are there. In matter of fact, when I switch to Lt
keyboard, it still uses Finnish symbols. Finnish is my main keyboard at
the moment.

Before that, there were Russian symbols instead of Lt. So I uninstalled
Rus keyboard. That caused Lt keyboard to show English symbols. After
uninstalling Eng, now Lt keyboard is sticking with Fin. Adding new
languages doesn't change behaviour (still Fi).

Other languages on keyboard work fine. Uninstalling all keyboards except
Lt, still makes no Lithuanian symbols.

I tried uninstall Lithuanian keyboard (with reboot) and install again.
Also tried different Lithuanian keyboards.

Ubuntu 14.04.3 LTS 64-bit on MSI GE620DX laptop.

(That's my first bug report, hope I'm doing it as it's supposed to be
done.)

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: keyboard lithuanian
-- 
Lithuanian keyboard doesn't switch on
https://bugs.launchpad.net/bugs/1490738
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xkeyboard-config in Ubuntu.

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

[Touch-packages] [Bug 1578657] [NEW] spanish keyboard not accentuating vowels

You have been subscribed to a public bug:

I've already added the Spanish language keyboard to unity and the keyboard 
indicator at the top indicates the Spanish keyboard and I do get Ñ and ñ
however when I go to accentuate a vowel áéíóú it's not working

the normal process is that I press the apostrophe key (in the us keyboard it 
would be two keys toward the right from "L") then select the vowel to be 
accentuated. 
however you're not supposed to see anything until the vowel is selected.

what is happening instead is that I'm getting an apostrophe right away
when I press the tilde key.


NOTE0:
I've tested also other variants of the Spanish layout with similar success..

NOTE1:
I have installed cinnamon also and when I login to cinnamon it works, so I'm 
only experiencing the issue in unity.

NOTE2:
I'm very proficient with computers and have successfully done this many times.

NOTE3: 
I'm working on a fairly clean setup of Ubuntu 16.04 LTS
 I've only added Cinnamon and the Intel Drivers to the system and google chrome 
 system is also up to date.

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 16.04 bot-comment keyboard language layout ubuntu
-- 
spanish keyboard not accentuating vowels
https://bugs.launchpad.net/bugs/1578657
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xkeyboard-config in Ubuntu.

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

[Touch-packages] [Bug 1165313] [NEW] Right arrow, comma and circumflex keys don't work anymore

You have been subscribed to a public bug:

$ lsb_release -rd
Description:Ubuntu Raring Ringtail (development branch)
Release:13.04

keyboard layout as given by parameters is : "French (Alternative)"

After todays updates several keys including "Right Arrow Key" "Comma
Key" and "Circumflex" don't work anymore

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
Right arrow, comma and circumflex keys don't work anymore
https://bugs.launchpad.net/bugs/1165313
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xkeyboard-config in Ubuntu.

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

[Touch-packages] [Bug 1498732] [NEW] keyboard layout setup

You have been subscribed to a public bug:

Keyboard layout in Ubuntu 15 setup doesn't seem to work.  When selecting
"Dvorak" manually in the F3 menu or using the automatic layout
detection, which correctly detects Dvorak, the layout isn't actually
set.  For instance a couple screens later when asking for the hostname
the keyboard layout is ASCII and when the machine boots asking for the
username/password it's ASCII.

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: bot-comment
-- 
keyboard layout setup
https://bugs.launchpad.net/bugs/1498732
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xkeyboard-config in Ubuntu.

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

[Touch-packages] [Bug 1593981] Re: pm-utils suspend fails every 2nd time with gyro-sensors enabled

Disabling sensors in Bios makes Suspend work again

STM Micro HID Sensor HUB, working through IIO HID

accelerometer sensor
rotation sensor
magnetometer sensor
angular velocity sensor (aka gyroscope)
inclination sensor
ambient light sensor

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

Title:
  pm-utils suspend fails every 2nd time with gyro-sensors enabled

Status in pm-utils package in Ubuntu:
  New

Bug description:
  If I turn on sensors (connected to usb) in the BIOS of my Lenovo
  Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time.
  Disabling async doesn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1392176] Re: mounts cgroups unconditionally which causes undesired effects with cpu hotplug

2016-06-18 Thread Serge Hallyn

I recommend opening new bugs against libvirt and docker.  Libvirt moves
VMS into a cpuset by default.  I assume docker does the same.  (My
xenial laptop runs upstart, so this is not systemd's doing)

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

Title:
  mounts cgroups unconditionally which causes undesired effects with cpu
  hotplug

Status in cgmanager package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Preeti U. Murthy  - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1392176/+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 1593981] Re: pm-utils suspend fails every 2nd time with gyro-sensors enabled

** Attachment added: "lsusb"
   
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+attachment/4686163/+files/lsusb

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

Title:
  pm-utils suspend fails every 2nd time with gyro-sensors enabled

Status in pm-utils package in Ubuntu:
  New

Bug description:
  If I turn on sensors (connected to usb) in the BIOS of my Lenovo
  Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time.
  Disabling async doesn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1592862] Re: Merge e2fsprogs from Debian 1.43.1-1

2016-06-18 Thread Theodore Ts'o

You may want to recheck the merge, or at least the remaining changes,
since  Debian e2fsprogs 1.43.1 now:

a) Uses dh_update_autotools_config to update config.guess / config.guess
b) No longer uses dietlibc
c) Generates dbgsym packages if the underlying package infrastructure supports 
them


At the very least the changes to remove dietlibc are definitely no longer 
needed for Ubuntu, and if Ubuntu now supports the Debian methods for generating 
dbgsym and updating config.{guess,sub} files, it may be possible for Ubuntu 
remove (a) and (c) as well.

BTW, note that if you run "make -f debian/rules mrproper ; make -f
debian/rules debian-files" the debian/rules file will automatically
reprobe the underlying build infrastructure and update various debian
files automatically to automate rebuilding e2fsprogs on legacy
distributions.   For example, this should allow e2fsprogs to be rebuilt
on Debian Stable and (probably, although I haven't tested it) Ubuntu LTS
distributions.

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

Title:
  Merge e2fsprogs from Debian 1.43.1-1

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Merge e2fsprogs from Debian 1.43.1-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1592862/+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 1593981] Re: pm-utils suspend fails every 2nd time with gyro-sensors enabled

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+attachment/4686162/+files/lspci

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

Title:
  pm-utils suspend fails every 2nd time with gyro-sensors enabled

Status in pm-utils package in Ubuntu:
  New

Bug description:
  If I turn on sensors (connected to usb) in the BIOS of my Lenovo
  Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time.
  Disabling async doesn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1593981] Re: pm-utils suspend fails every 2nd time with gyro-sensors enabled

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+attachment/4686161/+files/dmesg

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

Title:
  pm-utils suspend fails every 2nd time with gyro-sensors enabled

Status in pm-utils package in Ubuntu:
  New

Bug description:
  If I turn on sensors (connected to usb) in the BIOS of my Lenovo
  Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time.
  Disabling async doesn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1593981] Re: pm-utils suspend fails every 2nd time with gyro-sensors enabled

sudo pm-suspend from commandline works, closing the lid or using KDEs
suspend button won't

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

Title:
  pm-utils suspend fails every 2nd time with gyro-sensors enabled

Status in pm-utils package in Ubuntu:
  New

Bug description:
  If I turn on sensors (connected to usb) in the BIOS of my Lenovo
  Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time.
  Disabling async doesn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1593981] [NEW] pm-utils suspend fails every 2nd time with gyro-sensors enabled

Public bug reported:

If I turn on sensors (connected to usb) in the BIOS of my Lenovo
Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time.
Disabling async doesn't help.

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  pm-utils suspend fails every 2nd time with gyro-sensors enabled

Status in pm-utils package in Ubuntu:
  New

Bug description:
  If I turn on sensors (connected to usb) in the BIOS of my Lenovo
  Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time.
  Disabling async doesn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1585723] Re: UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

2016-06-18 Thread Emanuele Antonio Faraone

I tried to use unity8 after updating Qtubuntu and I encountered these
problems if I try to open the app crashes unity8 (I can use only the
scopes), the pointer is giant, the system is very slow.

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

Title:
  UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I'm digging into unity8 performance problems on older generation Intel
  GPUs - specifically i915 Atom GPUs.

  I've tested a simple QML file with a single empty UbuntuShape in it:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Rectangle {
  width: 400
  height: 300
  color: "blue"

  UbuntuShape {}
  }

  Running it with INTEL_DEBUG=perf env var set, I get this output:

  i915_program_error: Exceeded max ALU instructions (76 out of 64)
  ENTER FALLBACK 1: Program
  Mapping a busy BO, causing a stall on the GPU.

  which implies that MESA was unable to compile one of the UbuntuShape
  shaders as it created more ALU instructions than the GPU could deal
  with. MESA falls back to CPU rendering as a result.

  The GPU stall message I guess is related to that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1585723/+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 1392176] Comment bridged from LTC Bugzilla

2016-06-18 Thread bugproxy

--- Comment From shg...@cn.ibm.com 2016-06-18 09:49 EDT---
(In reply to comment #77)
> "LXC cases, like docker and KVM" - did you mean non-lxc cases?
>
> xenial by default should now be using libpam-cgfs, should not be using
> cgmanager, and should not be creating cpusets.

Thanks for the info. However what I cares is the docker/KVM case. For
example, when I created docker on xenial 16.04, the container process
will still be added into /sys/fs/cgroup/cpuset/docker; When creating
KVM, the KVM process will be added into sub cpuset cgroup as well. As a
result, the issue can still impact those tasks.

For the above, is it already covered(on higher xenial version) or does
it need more consideration?

Regards,
- Simon

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

Title:
  mounts cgroups unconditionally which causes undesired effects with cpu
  hotplug

Status in cgmanager package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Preeti U. Murthy  - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1392176/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]

2016-06-18 Thread Emanuele Antonio Faraone

I've Tried it but is very very slow!

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

Title:
  Unity8-dash on Intel Atom graphics crashes and restarts continuously
  [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) ==
  EGL_TRUE"]

Status in Mir:
  Invalid
Status in qtubuntu:
  In Progress
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Qt clients are failing to create an egl context when running on Intel
  Pineview systems under Mir.

  eglCreateContext fails with a EGL_BAD_MATCH error code.

  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)

  
  === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+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 1593976] [NEW] USB optical mouse not working when connected.

2016-06-18 Thread Ashwin

Public bug reported:

The USB optical mouse doesn't work both, when connected after boot or
before boot.

I am currently using the following commands after which it is working
fine:

sudo rmmod usbhid
sudo modprobe usbhid

I am running these commands every time after reconnecting the mouse, or every 
time after starting the PC.
I am looking for a permanent solution/fix

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Jun 18 19:05:11 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
InstallationDate: Installed on 2016-06-17 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. Inspiron 5559
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=baa2ee47-9c12-4ec3-a0a5-5226897ca264 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 0K64R6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0K64R6:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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
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: Sun Jun 19 00:26:43 2016
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   19528 
 vendor SDC
xserver.version: 2:1.18.3-1ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 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/1593976

Title:
  USB optical mouse not working when connected.

Status in xorg package in Ubuntu:
  New

Bug description:
  The USB optical mouse doesn't work both, when connected after boot or
  before boot.

  I am currently using the following commands after which it is working
  fine:

  sudo rmmod usbhid
  sudo modprobe usbhid

  I am running these commands every time after reconnecting the mouse, or every 
time after starting the PC.
  I am looking for a permanent solution/fix

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 18 19:05:11 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-06-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=baa2ee47-9c12-4ec3-a0a5-5226897ca264 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No

[Touch-packages] [Bug 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2016-06-18 Thread Till Kamppeter

Thomas, probably it is possible to build FF and TB with the system's
libcairo. I do not know why the maintainers of these packages stick to
stone-old libraries which have many bugs which are already fixed in the
current version.

But I will not do this fix as I am not the maintainer of FF and TB. The
bug is also assigned to these packages so the actual maintainers will
see this discussion and hopefully apply the fix. You can help them by
attaching patches/debdiffs.

So as we know the solution now and that it is in FF and TB and not in
cups and cups-filters, I am closing the appropriate tasks.

Thank you very much for investigating this.

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

** Changed in: firefox (Ubuntu)
   Importance: Undecided => High

** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => High

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  New
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 1593953] [NEW] EC_KEY_generate_key() causes FIPS self-test failure

2016-06-18 Thread Kazuki Yamaguchi

Public bug reported:

EC_KEY_generate_key() internally calls fips_pkey_signature_test() which
performs a pairwise check by ECDSA signing/verifying, but some groups
don't support ECDSA.

For example, `openssl ecparam -genkey -name Oakley-EC2N-4` fails.
Unfortunately `openssl ecparam` doesn't give any useful information so I
modified a bit:

~~~
diff --git a/apps/ecparam.c b/apps/ecparam.c
index 71b67f4..db89c2f 100644
--- a/apps/ecparam.c
+++ b/apps/ecparam.c
@@ -585,6 +585,7 @@ int MAIN(int argc, char **argv)
 
 if (!EC_KEY_generate_key(eckey)) {
 EC_KEY_free(eckey);
+ERR_print_errors(bio_err);
 goto end;
 }
 if (outformat == FORMAT_ASN1)
~~~

And I got:

~~~
$ LD_LIBRARY_PATH=$(pwd)/target/lib ./target/bin/openssl ecparam -genkey -name 
Oakley-EC2N-4
-BEGIN EC PARAMETERS-
BgA=
-END EC PARAMETERS-
140614096975512:error:0306E06C:bignum routines:BN_mod_inverse:no 
inverse:bn_gcd.c:525:
140614096975512:error:0306E06C:bignum routines:BN_mod_inverse:no 
inverse:bn_gcd.c:525:
140614096975512:error:2A067003:lib(42):ECDSA_sign_setup:BN lib:ecs_ossl.c:206:
140614096975512:error:2A06502A:lib(42):ECDSA_do_sign:reason(42):ecs_ossl.c:302:
140614096975512:error:2D079089:FIPS routines:fips_pkey_signature_test:test 
failure:fips_post.c:166:
140614096975512:error:2D06A07F:FIPS routines:FIPS_CHECK_EC:pairwise test 
failed:ec_key.c:249:
~~~

I'm using Ubuntu 16.04 and openssl 1.0.2g-1ubuntu4.1.


This was originally reported at Ruby's issue tracker:

https://bugs.ruby-lang.org/issues/12504

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


** Tags: xenial

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

Title:
  EC_KEY_generate_key() causes FIPS self-test failure

Status in openssl package in Ubuntu:
  New

Bug description:
  EC_KEY_generate_key() internally calls fips_pkey_signature_test()
  which performs a pairwise check by ECDSA signing/verifying, but some
  groups don't support ECDSA.

  For example, `openssl ecparam -genkey -name Oakley-EC2N-4` fails.
  Unfortunately `openssl ecparam` doesn't give any useful information so
  I modified a bit:

  ~~~
  diff --git a/apps/ecparam.c b/apps/ecparam.c
  index 71b67f4..db89c2f 100644
  --- a/apps/ecparam.c
  +++ b/apps/ecparam.c
  @@ -585,6 +585,7 @@ int MAIN(int argc, char **argv)
   
   if (!EC_KEY_generate_key(eckey)) {
   EC_KEY_free(eckey);
  +ERR_print_errors(bio_err);
   goto end;
   }
   if (outformat == FORMAT_ASN1)
  ~~~

  And I got:

  ~~~
  $ LD_LIBRARY_PATH=$(pwd)/target/lib ./target/bin/openssl ecparam -genkey 
-name Oakley-EC2N-4
  -BEGIN EC PARAMETERS-
  BgA=
  -END EC PARAMETERS-
  140614096975512:error:0306E06C:bignum routines:BN_mod_inverse:no 
inverse:bn_gcd.c:525:
  140614096975512:error:0306E06C:bignum routines:BN_mod_inverse:no 
inverse:bn_gcd.c:525:
  140614096975512:error:2A067003:lib(42):ECDSA_sign_setup:BN lib:ecs_ossl.c:206:
  
140614096975512:error:2A06502A:lib(42):ECDSA_do_sign:reason(42):ecs_ossl.c:302:
  140614096975512:error:2D079089:FIPS routines:fips_pkey_signature_test:test 
failure:fips_post.c:166:
  140614096975512:error:2D06A07F:FIPS routines:FIPS_CHECK_EC:pairwise test 
failed:ec_key.c:249:
  ~~~

  I'm using Ubuntu 16.04 and openssl 1.0.2g-1ubuntu4.1.

  
  This was originally reported at Ruby's issue tracker:

  https://bugs.ruby-lang.org/issues/12504

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1593953/+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 1579760] Re: Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)