date:20170530

OK, thanks for testing that. The bug is then Fix Released for current
Ubuntu. As soon as we know /what/ fixed it, we can start thinking about
getting that fix into 16.04 too.

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

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

Title:
Volume notification keeps popping up constantly (the notify-OSD bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Fix Released

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
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
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO: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.

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

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

[Touch-packages] [Bug 1546603] Re: Bluetooth mouse connects but doesn't work ("Unable to register GATT service")

Thanks. Sounds like it should be fixed by:
  http://www.bluez.org/release-of-bluez-5-42/

which means the fix entered Ubuntu in 17.04.

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

Title:
  Bluetooth mouse connects but doesn't work ("Unable to register GATT
  service")

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I have a bluetooth mouse that I can get to connect via the gnome
  bluetooth settings panel, but even after it's connected it doesn't
  move the pointer or register any clicks.

  the following shows up in the journal :

  $ $ journalctl -b 0 |grep bluetooth
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36
  Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 
initialized
  Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service 
Changed" characteristic
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be 
registered
  Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error 
(5)
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed.
  Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted 
(1)
  Feb 17 07:18:22 spiny NetworkManager[1062]:   Loaded device plugin: 
NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset 
Voice gateway: rfcomm_bind: Address already in use (98)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing 
desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str != NULL' failed
  Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x000c for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x001b for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x003f for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute 
requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: 
Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]:

[Touch-packages] [Bug 1674258] Re: lscpu crashs when /dev/mem is not stable to read

This bug was fixed in the package util-linux - 2.29-1ubuntu3

---
util-linux (2.29-1ubuntu3) artful; urgency=medium

  * Cherrypick upstream fix to prevent lscpu crash on arm64 by
accessing DMI in sysfs instead of /dev/mem. LP: #1674258

 -- Ike Panhc   Thu, 18 May 2017 10:49:34 +0800

** Changed in: util-linux (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 util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674258

Title:
  lscpu crashs when /dev/mem is not stable to read

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress
Status in util-linux source package in Yakkety:
  In Progress
Status in util-linux source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * Read from /dev/mem and scan DMI tables is dangerous, if /dev/mem is
  not stable to read, it will cause lscpu crash.

  [Test Case]

   * `sudo lscpu` shall not cause Segmentation fault (core dumped)

  [Regression Potential]

   * Reading from DMI tables is sysfs is more stable then reading from
  /dev/mem and if DMI tables is not available lscpu will use the old way
  to search in /dev/mem. I believe its low regression risk

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

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

[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error

2017-05-30 Thread Julian Andres Klode

Well, it's more like "this site is temporarily unavailable, please try
again at a later time."

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

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

[Touch-packages] [Bug 1659846] Re: /usr/bin/sudo:6:kill:main

And in fact this is covered by bug 1565332.

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

Title:
  /usr/bin/sudo:6:kill:main

Status in sudo package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
sudo.  This problem was most recently seen with package version 
1.8.19p1-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/a4dd7ca4d793ba224f7d7369ba21e84fe667efd1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1659846] Re: /usr/bin/sudo:6:kill:main

This is a false positive in sudo. What's happening is that sudo is
taking an error from the program it executed and propagating out to the
calling shell. Thus when a called application aborts (i.e. SIGABRT), it
also triggers an abort for sudo.

To demonstrate:

  $ sudo sh -c 'echo $$'

results in the following in /var/crash:

  $ ls -l /var/crash/
  total 164
  -rw-r- 1 root whoopsie  29122 May 30 15:32 _bin_dash.0.crash
  -rw-r- 1 root whoopsie 133096 May 30 15:32 _usr_bin_sudo.0.crash

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

Title:
  /usr/bin/sudo:6:kill:main

Status in sudo package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
sudo.  This problem was most recently seen with package version 
1.8.19p1-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/a4dd7ca4d793ba224f7d7369ba21e84fe667efd1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1659846] Re: /usr/bin/sudo:6:kill:main

Durr, wrong copy-pasta, the actual command is:

  $ sudo sh -c 'kill -ABRT $$'

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

Title:
  /usr/bin/sudo:6:kill:main

Status in sudo package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
sudo.  This problem was most recently seen with package version 
1.8.19p1-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/a4dd7ca4d793ba224f7d7369ba21e84fe667efd1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1694367] Re: Screen tearing in 16.10 onwards

2017-05-30 Thread Bug Watch Updater

** Changed in: mesa
   Status: Unknown => Confirmed

** Changed in: mesa
   Importance: Unknown => Medium

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

Title:
  Screen tearing in 16.10 onwards

Status in Mesa:
  Confirmed
Status in kernel-package package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  In 16.10 onwards my laptop has always shown screen tearing globally,
  additionally GL applications will not v-sync despite attempting to,
  they appear to sync slightly off from the [integrated] display.

  This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not
  entirely sure if it's a bug with either or a default miss-
  configuration in ubuntu...

  ubuntu-bug also appears to be broken...

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

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

Re: [Touch-packages] [Bug 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

2017-05-30 Thread Philipp von der Linden

Hello, Hans!

I am sorry for not being more helpful, but I really do not have anything 
more to say than: If you think, it is covered, it is covered. If you 
think, it is all duplicates, then it will be the case, I trust.

HG, PvdL

-- 
Philipp von der Linden, M.A.
OsloerStr.93 D-13359 Wedding
eMail: "PvdL" 

On 30.05.2017 21:01, Hans Joachim Desserud wrote:
> I've read through this now, but just to double-check:
> There's various bug reports with package-conflicts for files in 
> '/etc/signon-ui/webkit-options.d/*' between account-plugins and 
> kaccounts-providers. (For instance bug 1617564)
> 
>>From what I see, this issue will remove the conflicting files from the
> account-plugins side and thus fix the issue. Does that mean that these
> other issues should all be marked as duplicates of this one?
>

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Fix Committed
Status in gnome-control-center-signon source package in Xenial:
  Fix Committed
Status in account-plugins source package in Yakkety:
  Fix Released
Status in gnome-control-center-signon source package in Yakkety:
  Fix Released

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.

  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+subscriptions

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

[Touch-packages] [Bug 1694367] Re: Screen tearing in 16.10 onwards

2017-05-30 Thread Paul

** Bug watch added: freedesktop.org Bugzilla #101229
   https://bugs.freedesktop.org/show_bug.cgi?id=101229

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=101229
   Importance: Unknown
   Status: Unknown

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

Title:
  Screen tearing in 16.10 onwards

Status in Mesa:
  Unknown
Status in kernel-package package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  In 16.10 onwards my laptop has always shown screen tearing globally,
  additionally GL applications will not v-sync despite attempting to,
  they appear to sync slightly off from the [integrated] display.

  This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not
  entirely sure if it's a bug with either or a default miss-
  configuration in ubuntu...

  ubuntu-bug also appears to be broken...

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

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

[Touch-packages] [Bug 1694542] [NEW] can't get print to work

2017-05-30 Thread Fred Hooper

Public bug reported:

i have a samsung m2070fw printer it will not respond

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
BootLog:
 [[0;1;31mFAILED[0m] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb2-2\x2d8-2\x2d8.2).
 See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\\x2d8-2\\x2d8.2.service"'
 for details.
 [[0;32m  OK  [0m] Started Network Manager Script Dispatcher Service.
 [[0;32m  OK  [0m] Started Modem Manager.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue May 30 17:32:56 2017
DistUpgraded: 2016-08-03 21:03:22,827 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 82G33/G31 Express Integrated Graphics 
Controller [103c:2a6f]
InstallationDate: Installed on 2014-11-25 (917 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: HP-Pavilion NC839AA-ABA a6838f
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=8c58f378-744f-466b-8075-ce338c5307b9 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-08-04 (299 days ago)
dmi.bios.date: 02/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.37
dmi.board.name: Benicia
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.01
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.37:bd02/23/2009:svnHP-Pavilion:pnNC839AA-ABAa6838f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: NC839AA-ABA a6838f
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue May 30 21:16:22 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft Microsoft Wheel Mouse Optical® MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   44416 
 vendor ACR
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  can't get print to work

Status in xorg package in Ubuntu:
  New

Bug description:
  i have a samsung m2070fw printer it will not respond

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  BootLog:
   [[0;1;31mFAILED[0m] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb2-2\x2d8-2\x2d8.2).
   See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\\x2d8-2\\x2d8.2.service"'
 for details.
   [[0;32m  OK  [0m] Started Network Manager Script Dispatcher Service.
   [[0;32m  OK  [0m] Started Modem Manager.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue May 30 17:32:56 2017
  DistUpgraded: 2016-08-03

[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)

2017-05-30 Thread dualshock3nerd

@vanvugt

I tested 17.04 in a live USB environment all day. This bug never showed up.
In 16.04 LTS this annoying bug pops up at least once in a couple of minutes so
I assume it's fixed in Zesty at least.
Thanks for looking into it.

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

Title:
Volume notification keeps popping up constantly (the notify-OSD bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Incomplete

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

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

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

[Touch-packages] [Bug 1694331] Re: "internal error" popup on login

2017-05-30 Thread Christopher M. Penalver

Andreas Fritiofson, to keep this report manageable, let us avoid
discussing other computers, other colleagues computers, etc. and instead
remain focused here in this report on the Asus UX32VD.

One problem, per computer setup, per report.

If you have an issue with a different computer, file a new bug report
while using that different computer.

Remaining focused on the Asus UX32VD, as per
https://wiki.ubuntu.com/Releases Ubuntu 16.10 will be EoL'ing in a
month. Hence, could you please upgrade to 17.04 and advise if Xorg
crashes still from time to time?

** Description changed:

- Sometimes (not very often), Ubuntu shows an error popup immediately
- after login (after power-on) that says Xorg has crashed. No other ill
- effects have been noticed, everything works normally after that.
- 
- The automatic error reporting does not go through because of
- "UnreportableReason: Invalid core dump: BFD: Warning
- /tmp/apport_core_5n7s8i3d is truncated: expected core file size >=
- 40902656, found: 21037056."
- 
- I was asked by Christopher M. Penalver in Bug 1426596 to submit a new
- bug using "ubuntu-bug xorg" when the error appeared. This is that
- report, although the computer I used now to generate the report is not
- the same as I mentioned in the original bug (I've seen the same issue on
- more or less all computers I've used and IIRC from at least 16.04 to
- 17.04).
+ My Asus UX32VD shows an Xorg crash from time to time (but not nearly at
+ every boot).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 29 22:31:18 2017
  DistUpgraded: 2017-04-15 01:32:04,429 DEBUG /openCache(), new cache size 85680
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.8, 4.8.0-52-generic, x86_64: installed
-  bbswitch, 0.8, 4.8.0-53-generic, x86_64: installed
+  bbswitch, 0.8, 4.8.0-52-generic, x86_64: installed
+  bbswitch, 0.8, 4.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2014-04-18 (1137 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-53-generic.efi.signed 
root=UUID=959fa127-2d15-48a5-9fa0-70f918fab2ad ro rootflags=subvol=@ quiet 
splash pcie_aspm=force nmi_watchdog=0 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2017-04-14 (44 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Mon May 29 22:28:30 2017
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version:

[Touch-packages] [Bug 1676829] Re: Mic input volume always resets (to middle/low value) on resume or restart

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

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

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

Title:
  Mic input volume always resets (to middle/low value) on resume or
  restart

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sound card: CA0106/CA0111

  Each time I start PC - mic input volume resets to some "default" value.
  This happens from 16.04 (maybe earlier). Now I have 17.04, still have it.

  Each time I run:

  1) alsamixer
  2) select input device, "Line In"
  3) set it to max.

  (Or same actions in Ubuntu GUI)

  Then (after restart or suspend) the volume goes back to some middle
  value (low for me).

  I'm pissed off setting it back again and again. Does someone else have
  this problem?

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

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

[Touch-packages] [Bug 1631782] Re: Volume and Mic controls grayed out and not working

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

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

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

Title:
  Volume and Mic controls grayed out and not working

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hallo
  testing Yakkety 08-10 buld on live session i have the controls of the volume 
locked and not working as shown in the attached screenshot. Even in sound 
setting I can-t set the desired volume, anyway it play sounds correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CurrentDesktop: Unity
  Date: Sun Oct  9 17:53:10 2016
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: H55M-S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd08/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H55M-S2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1694517] [NEW] Kernel crashes, task wpa_supplicant blocked for more than 120 seconds

2017-05-30 Thread Cerin

Public bug reported:

When using Gnome-Shell on Ubuntu 16.04, the Internet connection will
suddenly drop off, even though the network connection icon will still
indicate a connection.

Attempting to run `sudo service network-manager restart` will hang
indefinitely.

Attempting to restart Gnome-Shell via alt+F2+r, will cause Gnome-Shell
to hang indefinitely.

Switching to a terminal, I inspecting `dmesg` and found several messages
like:

[178443.199324] INFO: task wpa_supplicant:1708 blocked for more than 120 
seconds.
[178443.199332]   Tainted: G   OE   4.4.0-78-generic #99-Ubuntu
[178443.199335] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[178443.199337] wpa_supplicant  D 88085849ba38 0  1708  1 
0x
[178443.199345]  88085849ba38 88087f516e30 88001cd2da00 
880853c35a00
[178443.199350]  88085849c000 81ef8184 880853c35a00 

[178443.199354]  81ef8188 88085849ba50 8183c8f5 
81ef8180
[178443.199358] Call Trace:
[178443.199369]  [] schedule+0x35/0x80
[178443.199374]  [] schedule_preempt_disabled+0xe/0x10
[178443.199378]  [] __mutex_lock_slowpath+0xb9/0x130
[178443.199386]  [] mutex_lock+0x1f/0x30
[178443.199393]  [] rtnl_lock+0x15/0x20
[178443.199422]  [] nl80211_pre_doit+0xeb/0x180 [cfg80211]
[178443.199429]  [] genl_family_rcv_msg+0x1ad/0x3e0
[178443.199435]  [] ? __wake_up_common+0x52/0x90
[178443.199441]  [] ? genl_family_rcv_msg+0x3e0/0x3e0
[178443.199446]  [] genl_rcv_msg+0x76/0xb0
[178443.199450]  [] netlink_rcv_skb+0xa4/0xc0
[178443.199455]  [] genl_rcv+0x28/0x40
[178443.199459]  [] netlink_unicast+0x18a/0x240
[178443.199464]  [] netlink_sendmsg+0x2fb/0x3a0
[178443.199470]  [] ? aa_sock_msg_perm+0x61/0x150
[178443.199477]  [] sock_sendmsg+0x38/0x50
[178443.199480]  [] ___sys_sendmsg+0x281/0x290
[178443.199487]  [] ? __fpu__restore_sig+0xa1/0x480
[178443.199491]  [] __sys_sendmsg+0x51/0x90
[178443.199496]  [] SyS_sendmsg+0x12/0x20
[178443.199501]  [] entry_SYSCALL_64_fastpath+0x16/0x71

I see similar errors for other programs other than wpa_supplicant, so it
might not be isolated to it, but I'm not sure where else to submit this
error to.

All other `sudo` commands hung, even after 15 minutes of waiting,
leaving me no choice but to reboot. However, this has happened several
times after a recent update, and the symptoms always manifest exactly
the same. No Internet, then Gnome-Shell hangs, then all sudo commands
hang.

I managed to copy my dmesg log before the reboot, which I have attached.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: wpasupplicant 2.4-0ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue May 30 14:56:58 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2017-03-09 (81 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "dmesg log just after system begun to hang"
   https://bugs.launchpad.net/bugs/1694517/+attachment/4886316/+files/dmesg.txt

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

Title:
  Kernel crashes, task wpa_supplicant blocked for more than 120 seconds

Status in wpa package in Ubuntu:
  New

Bug description:
  When using Gnome-Shell on Ubuntu 16.04, the Internet connection will
  suddenly drop off, even though the network connection icon will still
  indicate a connection.

  Attempting to run `sudo service network-manager restart` will hang
  indefinitely.

  Attempting to restart Gnome-Shell via alt+F2+r, will cause Gnome-Shell
  to hang indefinitely.

  Switching to a terminal, I inspecting `dmesg` and found several
  messages like:

  [178443.199324] INFO: task wpa_supplicant:1708 blocked for more than 120 
seconds.
  [178443.199332]   Tainted: G   OE   4.4.0-78-generic 
#99-Ubuntu
  [178443.199335] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
  [178443.199337] wpa_supplicant  D 88085849ba38 0  1708  1 
0x
  [178443.199345]  88085849ba38 88087f516e30 88001cd2da00 
880853c35a00
  [178443.199350]  88085849c000 81ef8184 880853c35a00 

  [178443.199354]  81ef8188

[Touch-packages] [Bug 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

2017-05-30 Thread Hans Joachim Desserud

I've read through this now, but just to double-check:
There's various bug reports with package-conflicts for files in 
'/etc/signon-ui/webkit-options.d/*' between account-plugins and 
kaccounts-providers. (For instance bug 1617564)

>From what I see, this issue will remove the conflicting files from the
account-plugins side and thus fix the issue. Does that mean that these
other issues should all be marked as duplicates of this one?

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Fix Committed
Status in gnome-control-center-signon source package in Xenial:
  Fix Committed
Status in account-plugins source package in Yakkety:
  Fix Released
Status in gnome-control-center-signon source package in Yakkety:
  Fix Released

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+subscriptions

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

[Touch-packages] [Bug 1428121] Re: Intel HDMI Audio not working with IOMMU enabled

2017-05-30 Thread Zeke Laschinski

I've now tested the patch myself by patching kernel 4.10.0.21.23.
Unfortunately, it does not fix the problem.

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

Title:
  Intel HDMI Audio not working with IOMMU enabled

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an
  Nvidia GTX 650.

  Host uses Intel IGD for video and HDMI audio out.

  When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on'
  HDMI audio no longer functions although the device and modules seem to
  load and I cannot locate any error messages.  In this configuration
  IOMMU functions as expected and I can successfully pass the Nvidia
  card through to a KVM guest using VFIO.

  As per this
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug
  report and the linked bugzilla thread I attempted to use kernel flag
  'intel_iommu=on,igfx_off'.  This resolves the HDMI audio out but
  breaks IOMMU as in VGA pass through generates DMA errors.

  I'm running from a clean installation of 14.10 with no modifications
  to the kernel or kvm, qemu, libvirt or virt-manager.

  In either scenario above the analogue audio out continues to function,
  I haven't tested the optical out as I have no hardware to do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kelvin 3468 F pulseaudio
   /dev/snd/controlC3:  kelvin 3468 F pulseaudio
   /dev/snd/controlC0:  kelvin 3468 F pulseaudio
   /dev/snd/controlC1:  kelvin 3468 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:53:17 2015
  HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout 
intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  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.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr: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.

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

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

[Touch-packages] [Bug 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM

2017-05-30 Thread Vinson Lee

** Tags added: artful

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

Title:
  sudo returns exit code 0 if child is killed with SIGTERM

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Triaged

Bug description:
  Please backport upstream sudo changeset 10917:50b988d0c97f "The fix
  for Bug #722 contained a typo/thinko that resulted in the" to xenial,
  yakkety, and zesty versions of sudo.

  This will fix a regression documented by this upstream bug report:
  https://bugzilla.sudo.ws/show_bug.cgi?id=784

  sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is
  running is killed by a signal, sudo will" introduced a regression
  where the exit status is always 0 when a command is killed by a signal
  other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1

  This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f
  "The fix for Bug #722 contained a typo/thinko that resulted in the".
  https://www.sudo.ws/repos/sudo/rev/50b988d0c97f

  trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo
  based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty
  sudo based off 1.8.19 need the fix.

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

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

[Touch-packages] [Bug 1316873] Re: Left mouse button stops working

2017-05-30 Thread Guilden_NL - Joop deBruin

Never had it until a recent Mint Linux Mint 18.1 Serena update.
However.. I installed OpenSuSE KDE Plasma and it exists there.

I dropped kernel version back to 4.4.0-21 and it occurs much less than
with new kernels, if it is of any help.

Note that all mouse debugging tools result in the left click not
recognized, nothing in the logs at all.  All other keys, including mouse
wheel and right click work fine.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 1607666] Re: sudo fails with host netgroup returned from freeipa

As part of https://www.ubuntu.com/usn/usn-3304-1/ , the sudo in yakkety-
proposed has been superceded by sudo 1.8.16-0ubuntu3.2 in yakkety-
security. Please upload a new version to yakkety-proposed that
incorporates the security fix from the update.

Thanks!

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

Title:
  sudo fails with host netgroup returned from freeipa

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Released
Status in sudo source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Sudo currently fails to validate netgroups against host netgroups returned 
from the sss plugin, see https://fedorahosted.org/freeipa/ticket/6139 for the 
glory details.

  This was fixed in sudo 1.8.17
  (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which
  I'd very much like to see backported to Ubuntu 16.04. If possible,
  updating sudo completely to 1.8.17 would be nice, since there have
  been quite a few improvements with regards to sss and freeipa and it
  would be a shame if we could not benefit from them given that 16.04 is
  LTS.

  [Test case]
  install the update, test that sudo works on a freeipa installation that uses 
netgroups

  [Regression potential]
   I looked at upstream commits to sssd.c, and there were no commits 
that touch this area, so chance of regressions should be slim

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

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

[Touch-packages] [Bug 1546603] Re: Bluetooth mouse connects but doesn't work ("Unable to register GATT service")

2017-05-30 Thread Joe Barnett

the workaround works.  i haven't tried newer version w/out the
workaround.

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

Title:
  Bluetooth mouse connects but doesn't work ("Unable to register GATT
  service")

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I have a bluetooth mouse that I can get to connect via the gnome
  bluetooth settings panel, but even after it's connected it doesn't
  move the pointer or register any clicks.

  the following shows up in the journal :

  $ $ journalctl -b 0 |grep bluetooth
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36
  Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 
initialized
  Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service 
Changed" characteristic
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be 
registered
  Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error 
(5)
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed.
  Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted 
(1)
  Feb 17 07:18:22 spiny NetworkManager[1062]:   Loaded device plugin: 
NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset 
Voice gateway: rfcomm_bind: Address already in use (98)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing 
desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str != NULL' failed
  Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x000c for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x001b for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x003f for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute 
requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: 
Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str

[Touch-packages] [Bug 1694083] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-30 Thread Richard

Perhaps this may be a regression?
I'm seeing this in 17-04 Zesty.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  i stuck in ubuntu sofware center for downloading aplication

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sun May 28 06:28:38 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-23 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1605798] Re: Unity + Skylake + Hyper-V xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)

2017-05-30 Thread Joseph Salisbury

Thanks for the update, Mark.  Would you say this bug is resolved?

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

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

Title:
  Unity + Skylake + Hyper-V xf86EnableIOPorts: failed to set IOPL for
  I/O (Operation not permitted)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Customer using Lenovo P50 (Skylake) and Surface Book (Skylake) laptops
  tried to start unity in a guest VM on Hyper-V. Kernel 4.4.0-31 started
  as expected, Hyper-V drivers loaded as expected including the
  framebuffer driver, plenty of memory and vCPUs allocated, but x.org
  fails with xf86EnableIOPorts: failed to set IOPL for I/O (Operation
  not permitted), resulting in "no screens found".

  However, when customer used KDE (kubuntu 16.04 with similar kernel) on
  these same systems got a UI as expected. Customer also has no issues
  on non-skylake laptop.

  No unexpected messages seen in dmesg and syslog.

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

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

[Touch-packages] [Bug 1644975] Re: Resume from disk (swapfile) fails

2017-05-30 Thread Wladimir Palant

I can confirm that the following statement in
https://help.ubuntu.com/community/SwapFaq#Why_do_I_need_swap.3F is
wrong:

>  The hibernation implementation currently used in Ubuntu, swsusp,
needs a swap or suspend partition. It cannot use a swap file on an
active file system.

In fact, swsusp supports offsets just fine, and so does initramfs-tools
- mostly. The only thing blocking hibernation to a swap file from
working is that check in /usr/share/initramfs-tools/scripts/local-
premount/resume script. It calls wait-for-root which returns "ext4"
because no offset has been passed in. So the script will just assume
that no hibernation occurred and continue without resuming. While I
opted for simply removing the check, I strongly suspect that Ryo's patch
will fix the issue just as well.

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

2017-05-30 Thread redman

Same problem here:

Google-chrome is affected.
Skypeforlinux doesn't remember the password anymore
UnityMail is affected

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

Title:
  gnome-keyring not unlocked on boot

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 91867] Re: [PATCH] allow resume from LUKS encrypted swap partition

2017-05-30 Thread Wladimir Palant

By now (definitely xenial and above), this functionality has been
implemented via the cryptsetup package. It will take care of unlocking
resume devices so that one can simply use "resume=/dev/mapper/foo" for
the parameter.

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

Title:
  [PATCH] allow resume from LUKS encrypted swap partition

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: initramfs-tools

  The attached patch allows to suspend and resume to a LUKS encrypted
  swap partition. This means that all data (including passwords) that
  would otherwise be written to disk in plain text will be encrypted.

  To make use of the patch, you must 
  * create a  LUKS encrypted partition
  * activate the device with cryptsetup luksOpen
  * run mkswap on it and enter it in fstab as swap
  * change your kernel's resume=* line to 
  resume=LUKS=/name/of/harddiskpartition:devicemapper name (actual process 
depends on the bootloader used)
  For example resume=LUKS=/dev/hda3:cryptswap
  * then run update-initramfs to build a new initramfs.

  You will then be asked to provide the password for the swap partition
  upon boot and the script will try to resume from it. If it can't find
  swsuspend signatures, boot will continue. The script will also
  automatically setup correct suspend device for swsuspend.

  I have extensively tested this on Feisty.

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

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

[Touch-packages] [Bug 1694457] [NEW] Unable to Open Files With Totem After Upgrade to 17.04

2017-05-30 Thread Plamen

Public bug reported:

I can't open .mkv and .mp3 files with Totem. This behavior appeared after 
upgrade to 17.04.
After I double click a file a loading indication in the title bar appears. 
After a few seconds it simply disappears and the player is not showing.

If I start a Terminal and type "totem " the file is opened
normally.


>> lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

>> apt-cache policy totem
totem:
  Installed: 3.24.0-0ubuntu1
  Candidate: 3.24.0-0ubuntu1
  Version table:
 *** 3.24.0-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libgstreamer1.0-0 1.10.4-1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue May 30 17:33:05 2017
InstallationDate: Installed on 2015-06-17 (713 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gstreamer1.0
UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages zesty

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

Title:
  Unable to Open Files With Totem After Upgrade to 17.04

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I can't open .mkv and .mp3 files with Totem. This behavior appeared after 
upgrade to 17.04.
  After I double click a file a loading indication in the title bar appears. 
After a few seconds it simply disappears and the player is not showing.

  If I start a Terminal and type "totem " the file is
  opened normally.

  
  >> lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  >> apt-cache policy totem
  totem:
Installed: 3.24.0-0ubuntu1
Candidate: 3.24.0-0ubuntu1
Version table:
   *** 3.24.0-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libgstreamer1.0-0 1.10.4-1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 30 17:33:05 2017
  InstallationDate: Installed on 2015-06-17 (713 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1694457/+subscriptions

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

[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error

2017-05-30 Thread Jens Elkner

Hmmm, IMHO 'Err:' and 'W: Failed to fetch' indicate, that it was not
able to update properly and thus the result of the operation is
unreliable. So its like "your connection is secured, but may be not". I
guess most people wouldn't do any financial transaction when reading
this ... ;-)

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

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

[Touch-packages] [Bug 1670036] Re: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files

This bug was fixed in the package tiff - 4.0.3-7ubuntu0.7

---
tiff (4.0.3-7ubuntu0.7) trusty-security; urgency=medium

  * SECURITY REGRESSION: JPEG tiff read and write issue due to misapplied
patches (LP: #1670036)
- debian/patches/CVE-2016-9297_and_CVE-2016-9448_correct.patch: replace
  two previous patches with one that applies fix to correct location.
- Thanks to John Cupitt and Even Rouault

 -- Marc Deslauriers   Mon, 29 May 2017
07:35:17 -0400

** Changed in: tiff (Ubuntu Trusty)
   Status: Confirmed => Fix Released

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

Title:
  Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG
  compressed files

Status in LibTIFF:
  New
Status in tiff package in Ubuntu:
  Invalid
Status in tiff source package in Trusty:
  Fix Released
Status in tiff source package in Xenial:
  Fix Released
Status in tiff source package in Yakkety:
  Fix Released

Bug description:
  The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break
  JPEG tiff read and write.

  To reproduce:

  $ tiffcp -c jpeg k2a.tif x.tif

  (where k2a.tif is a simple uncompressed RGB strip tiff) appears to
  work. However, x.tif, the output, will now not read without warnings:

  $ tiffcp x.tif y.tif
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  JPEGLib: Warning, Premature end of JPEG file.

  This was working fine until a couple of days ago, so I guess it's one
  of the most recent patches.

  Some packages using libtiff seem to be broken too. For example,
  openslide, which uses libtiff to load jp2k-compressed slide images, is
  no longer working:

  $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it ... repeats 8 more times
  openslide-write-png: Premature end of JPEG file

  and x.png is not a valid PNG image.  The test .svs image may be
  downloaded here:

  http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/

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

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

[Touch-packages] [Bug 1670036] Re: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files

This bug was fixed in the package tiff - 4.0.6-2ubuntu0.2

---
tiff (4.0.6-2ubuntu0.2) yakkety-security; urgency=medium

  * SECURITY REGRESSION: JPEG tiff read and write issue due to misapplied
patches (LP: #1670036)
- debian/patches/CVE-2016-9297_and_CVE-2016-9448_correct.patch: replace
  two previous patches with one that applies fix to correct location.
- Thanks to John Cupitt and Even Rouault

 -- Marc Deslauriers   Mon, 29 May 2017
07:29:06 -0400

** Changed in: tiff (Ubuntu Yakkety)
   Status: Confirmed => Fix Released

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

Title:
  Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG
  compressed files

Status in LibTIFF:
  New
Status in tiff package in Ubuntu:
  Invalid
Status in tiff source package in Trusty:
  Fix Released
Status in tiff source package in Xenial:
  Fix Released
Status in tiff source package in Yakkety:
  Fix Released

Bug description:
  The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break
  JPEG tiff read and write.

  To reproduce:

  $ tiffcp -c jpeg k2a.tif x.tif

  (where k2a.tif is a simple uncompressed RGB strip tiff) appears to
  work. However, x.tif, the output, will now not read without warnings:

  $ tiffcp x.tif y.tif
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  JPEGLib: Warning, Premature end of JPEG file.

  This was working fine until a couple of days ago, so I guess it's one
  of the most recent patches.

  Some packages using libtiff seem to be broken too. For example,
  openslide, which uses libtiff to load jp2k-compressed slide images, is
  no longer working:

  $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it ... repeats 8 more times
  openslide-write-png: Premature end of JPEG file

  and x.png is not a valid PNG image.  The test .svs image may be
  downloaded here:

  http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/

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

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

[Touch-packages] [Bug 1694439] Re: Nano corrupts its buffer when adding newlines

2017-05-30 Thread Jussi Lind

Marked this as invalid because it was my terminal that had gone crazy.

** Description changed:

  Steps to reproduce
- 1) Open nano
+ 1) Open nano in a terminal (Ubuntu's default terminal)
  2) Write, let's say, 10 lines of text. Content doesn't matter
  3) Go to the beginning of, for example, line 5 and continue hitting enter
  
  What should happen:
  - New empty lines are added and the remaining lines are pushed down
  
  What happens instead:
  - Only a couple of new lines are added then the cursor just starts to move 
over the lines. Trying to add new lines now randomly sometimes works, sometimes 
doesn't. Usually the whole buffer gets messed up and also deleting lines does 
unexpected things
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nano 2.5.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 30 16:19:26 2017
  InstallationDate: Installed on 2016-09-13 (259 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  Nano corrupts its buffer when adding newlines

Status in nano package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce
  1) Open nano in a terminal (Ubuntu's default terminal)
  2) Write, let's say, 10 lines of text. Content doesn't matter
  3) Go to the beginning of, for example, line 5 and continue hitting enter

  What should happen:
  - New empty lines are added and the remaining lines are pushed down

  What happens instead:
  - Only a couple of new lines are added then the cursor just starts to move 
over the lines. Trying to add new lines now randomly sometimes works, sometimes 
doesn't. Usually the whole buffer gets messed up and also deleting lines does 
unexpected things

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nano 2.5.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 30 16:19:26 2017
  InstallationDate: Installed on 2016-09-13 (259 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1694438] Re: [16.04] Cannot download packages whilst offline - when using ifupdown

2017-05-30 Thread Martin Pitt

This also affects PackageKit 1.0.1-2 in Debian Jessie.

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

Title:
  [16.04] Cannot download packages whilst offline - when using ifupdown

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  New

Bug description:
  I am using 16.04 with the main ethernet interface being managed by
  ifupdown, and others by NetworkManager. Apparently PK's
  pk_network_get_network_state() does not properly recognize this and
  thinks it is offline:

  # pkcon update
  Getting updates   [=] 
  [...]
  Fatal error: Cannot download packages whilst offline

  A workaround is to change /etc/NetworkManager/NetworkManager.conf
  [ifupdown] managed= from "false" to "true", then "eth0" appears in
  "nmcli d" and PackageKit is happy.

  In 17.04 this is no problem any more, PackageKit works out of the box
  with the same ifupdown configuration and managed=false. Interestingly,
  "nmcli d" shows

  eth0ethernet  unmanaged  --

  there, while eth0 is entirely absent in 16.04. There doesn't seem to
  be an nmcli command to show what PackageKit looks at; the closest is
  "nmcli g" but in all three cases above that says

  STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
  connected  full  enabled  enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1670036] Re: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files

This bug was fixed in the package tiff - 4.0.6-1ubuntu0.2

---
tiff (4.0.6-1ubuntu0.2) xenial-security; urgency=medium

  * SECURITY REGRESSION: JPEG tiff read and write issue due to misapplied
patches (LP: #1670036)
- debian/patches/CVE-2016-9297_and_CVE-2016-9448_correct.patch: replace
  two previous patches with one that applies fix to correct location.
- Thanks to John Cupitt and Even Rouault

 -- Marc Deslauriers   Mon, 29 May 2017
07:33:56 -0400

** Changed in: tiff (Ubuntu Xenial)
   Status: Confirmed => Fix Released

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

Title:
  Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG
  compressed files

Status in LibTIFF:
  New
Status in tiff package in Ubuntu:
  Invalid
Status in tiff source package in Trusty:
  Confirmed
Status in tiff source package in Xenial:
  Fix Released
Status in tiff source package in Yakkety:
  Confirmed

Bug description:
  The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break
  JPEG tiff read and write.

  To reproduce:

  $ tiffcp -c jpeg k2a.tif x.tif

  (where k2a.tif is a simple uncompressed RGB strip tiff) appears to
  work. However, x.tif, the output, will now not read without warnings:

  $ tiffcp x.tif y.tif
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  JPEGLib: Warning, Premature end of JPEG file.

  This was working fine until a couple of days ago, so I guess it's one
  of the most recent patches.

  Some packages using libtiff seem to be broken too. For example,
  openslide, which uses libtiff to load jp2k-compressed slide images, is
  no longer working:

  $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it ... repeats 8 more times
  openslide-write-png: Premature end of JPEG file

  and x.png is not a valid PNG image.  The test .svs image may be
  downloaded here:

  http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/

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

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

[Touch-packages] [Bug 1694438] [NEW] [16.04] Cannot download packages whilst offline - when using ifupdown

2017-05-30 Thread Martin Pitt

Public bug reported:

I am using 16.04 with the main ethernet interface being managed by
ifupdown, and others by NetworkManager. Apparently PK's
pk_network_get_network_state() does not properly recognize this and
thinks it is offline:

# pkcon update
Getting updates   [=] 
[...]
Fatal error: Cannot download packages whilst offline

A workaround is to change /etc/NetworkManager/NetworkManager.conf
[ifupdown] managed= from "false" to "true", then "eth0" appears in
"nmcli d" and PackageKit is happy.

In 17.04 this is no problem any more, PackageKit works out of the box
with the same ifupdown configuration and managed=false. Interestingly,
"nmcli d" shows

eth0ethernet  unmanaged  --

there, while eth0 is entirely absent in 16.04. There doesn't seem to be
an nmcli command to show what PackageKit looks at; the closest is "nmcli
g" but in all three cases above that says

STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
connected  full  enabled  enabled  enabled  enabled

** Affects: packagekit (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: packagekit (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Also affects: packagekit (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

Title:
  [16.04] Cannot download packages whilst offline - when using ifupdown

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  New

Bug description:
  I am using 16.04 with the main ethernet interface being managed by
  ifupdown, and others by NetworkManager. Apparently PK's
  pk_network_get_network_state() does not properly recognize this and
  thinks it is offline:

  # pkcon update
  Getting updates   [=] 
  [...]
  Fatal error: Cannot download packages whilst offline

  A workaround is to change /etc/NetworkManager/NetworkManager.conf
  [ifupdown] managed= from "false" to "true", then "eth0" appears in
  "nmcli d" and PackageKit is happy.

  In 17.04 this is no problem any more, PackageKit works out of the box
  with the same ifupdown configuration and managed=false. Interestingly,
  "nmcli d" shows

  eth0ethernet  unmanaged  --

  there, while eth0 is entirely absent in 16.04. There doesn't seem to
  be an nmcli command to show what PackageKit looks at; the closest is
  "nmcli g" but in all three cases above that says

  STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
  connected  full  enabled  enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1694439] [NEW] Nano corrupts its buffer when adding newlines

2017-05-30 Thread Jussi Lind

Public bug reported:

Steps to reproduce
1) Open nano
2) Write, let's say, 10 lines of text. Content doesn't matter
3) Go to the beginning of, for example, line 5 and continue hitting enter

What should happen:
- New empty lines are added and the remaining lines are pushed down

What happens instead:
- Only a couple of new lines are added then the cursor just starts to move over 
the lines. Trying to add new lines now randomly sometimes works, sometimes 
doesn't. Usually the whole buffer gets messed up and also deleting lines does 
unexpected things

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nano 2.5.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
Uname: Linux 4.4.0-65-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 30 16:19:26 2017
InstallationDate: Installed on 2016-09-13 (259 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: nano
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Nano corrupts its buffer when adding newlines

Status in nano package in Ubuntu:
  New

Bug description:
  Steps to reproduce
  1) Open nano
  2) Write, let's say, 10 lines of text. Content doesn't matter
  3) Go to the beginning of, for example, line 5 and continue hitting enter

  What should happen:
  - New empty lines are added and the remaining lines are pushed down

  What happens instead:
  - Only a couple of new lines are added then the cursor just starts to move 
over the lines. Trying to add new lines now randomly sometimes works, sometimes 
doesn't. Usually the whole buffer gets messed up and also deleting lines does 
unexpected things

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nano 2.5.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 30 16:19:26 2017
  InstallationDate: Installed on 2016-09-13 (259 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error

2017-05-30 Thread Julian Andres Klode

Well, it did not fail, it re-used the existing information. Transient
network errors do not cause the update to fail, because they are
expected to be temporary. It's always been like this. I'm open to
possibly changing this, but such a change could cause huge issues.

** Changed in: apt (Ubuntu)
   Importance: Undecided => Wishlist

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

** Changed in: apt (Ubuntu)
   Importance: Wishlist => Low

** Changed in: apt (Ubuntu)
   Importance: Low => Wishlist

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

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

[Touch-packages] [Bug 1694331] Re: "internal error" popup on login

2017-05-30 Thread Andreas Fritiofson

Christopher, I have since upgraded that Dell Precision to 17.04 and
while I still often get the error popup on that computer I cannot
confirm that it is actually Xorg that crashed, because now that I
looked, the crash popup on 17.04 today was about some unrelated software
(unity-settings-something) so I can't really be sure if I have ever seen
Xorg crash on 17.04. It used to be Xorg when the Dell computer had
16.10, though.

The UX32VD that still runs 16.10 continues to show the Xorg crash from
time to time (but not nearly at every boot).

Also I checked with my co-workers and those (2) who run 16.10 all
regularly see an error popup but none can verify that it's still
actually about Xorg (it happens frequently enough that no-one bothers to
look anymore). A co-worker who's still on 16.04 says he hasn't seen the
error.

So in summary I can only definitely say that 16.10 shows that Xorg crash
and that it has happened on more or less every computer I or my co-
workers have used with 16.10.

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

Title:
  "internal error" popup on login

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes (not very often), Ubuntu shows an error popup immediately
  after login (after power-on) that says Xorg has crashed. No other ill
  effects have been noticed, everything works normally after that.

  The automatic error reporting does not go through because of
  "UnreportableReason: Invalid core dump: BFD: Warning
  /tmp/apport_core_5n7s8i3d is truncated: expected core file size >=
  40902656, found: 21037056."

  I was asked by Christopher M. Penalver in Bug 1426596 to submit a new
  bug using "ubuntu-bug xorg" when the error appeared. This is that
  report, although the computer I used now to generate the report is not
  the same as I mentioned in the original bug (I've seen the same issue
  on more or less all computers I've used and IIRC from at least 16.04
  to 17.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 29 22:31:18 2017
  DistUpgraded: 2017-04-15 01:32:04,429 DEBUG /openCache(), new cache size 85680
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-52-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2014-04-18 (1137 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-53-generic.efi.signed 
root=UUID=959fa127-2d15-48a5-9fa0-70f918fab2ad ro rootflags=subvol=@ quiet 
splash pcie_aspm=force nmi_watchdog=0 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2017-04-14 (44 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel:

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-05-30 Thread Zhanglei Mao

For the mainline kernel (general kernel from Ubuntu 16.04.02 AM64) was
not tested in case we are not supported for Hisilicon D05 board.

We also do some basic fbdev and modesetting testing on this kerenl by
pass Xserver, it seems works well and so we tend to think this is caused
by Xorg or driver of Xorg.

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-05-30 Thread Zhanglei Mao

The below is testing after remove of "xserver-xorg-video-fbdev package"

ubuntu@ubuntu:/usr/lib/xorg/modules/drivers$ sudo /usr/lib/xorg/Xorg

X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
Current Operating System: Linux ubuntu 4.10.0-20.22-generic #22+pearl.2-Ubuntu 
SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
Build Date: 02 November 2016  10:05:28PM
xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue May 30 17:45:40 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) no screens found(EE) 
(EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
ubuntu@ubuntu:/usr/lib/xorg/modules/drivers$ 

ubuntu@ubuntu:/usr/lib/xorg/modules/drivers$ less /var/log/Xorg.0.log
[1029553.709] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[1029553.709] X Protocol Version 11, Revision 0
[1029553.709] Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
[1029553.709] Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
[1029553.709] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
[1029553.709] Build Date: 02 November 2016  10:05:28PM
[1029553.709] xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
[1029553.709] Current version of pixman: 0.33.6
[1029553.709]   Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[1029553.709] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[1029553.709] (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 30 17:45:40 
2017
[1029553.709] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[1029553.710] (==) No Layout section.  Using the first Screen section.
[1029553.710] (==) No screen section available. Using defaults.
[1029553.710] (**) |-->Screen "Default Screen Section" (0)
[1029553.710] (**) |   |-->Monitor ""
[1029553.710] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[1029553.710] (==) Automatically adding devices
[1029553.710] (==) Automatically enabling devices
[1029553.710] (==) Automatically adding GPU devices
[1029553.710] (==) Max clients allowed: 256, resource mask: 0x1f
[1029553.710] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[1029553.710]   Entry deleted from font path.
[1029553.710] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[1029553.710]   Entry deleted from font path.
[1029553.710] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[1029553.710]   Entry deleted from font path.
[1029553.710] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[1029553.710]   Entry deleted from font path.
[1029553.710] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[1029553.710]   Entry deleted from font path.
[1029553.710] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
les,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
s.
es.
[1029553.710] (II) Loader magic: 0xb1d99d80
[1029553.710] (II) Module ABI versions:
[1029553.710]   X.Org ANSI C Emulation: 0.4
[1029553.710]   X.Org Video Driver: 20.0
[1029553.710]   X.Org XInput driver : 22.1
[1029553.710]   X.Org Server Extension : 9.0
[1029553.711] (--) using VT number 3

ptty was not provided, disabling logind integration
[1029553.712] (II) xfree86: Adding drm device (/dev/dri/card0)
/33554432, 0x8ab00/2097152
[1029553.713] (II) LoadModule: "glx"
[1029553.713] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[1029553.714] (II) Module glx: vendor="X.Org Foundation"
[1029553.714]   compiled for 1.18.4, module version = 1.0.0
[1029553.714]   ABI class: X.Org Server Extension, version 9.0
[1029553.714] (==) AIGLX enabled

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-05-30 Thread Daniel Axtens

Hi,

What happens if you remove the fb driver - uninstall the xserver-xorg-
video-fbdev package?

Also, I'm not sure what (if any) changes have been made in the kernel
version you're running - the 'pearl' version - but are you able to try
against a mainline kernel?

Regards,
Daniel

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Touch-packages] [Bug 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Bluetooth Logitech Dinovo Keyboard/Mouse don't work

Status in Bluez Utilities:
  New
Status in Bluez-utils:
  New
Status in Linux Mint:
  Invalid
Status in Unity:
  Invalid
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix
Status in udev package in Ubuntu:
  Invalid

Bug description:
  Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will 
work until Nautilus starts.  After Nautilus starts the keyboard and mouse are 
unresponsive and do not work.
  I tried reconnecting the keyboard and mouse by using the discovery buttons on 
both the Bluetooth Dongle and Input device.  The problem still persists.
  Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. 
 Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech 
mini bluetooth receiver.

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

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

[Touch-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized