[Touch-packages] [Bug 1610835] [NEW] starting in upstart mode

[Dharmendra Mishra]

Public bug reported:

ubuntu 16.04.1 starts in upstart mode and not in normal mode. please
help.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Aug  8 11:01:59 2016
DistUpgraded: 2016-08-02 12:13:30,790 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation 82G33/G31 Express Integrated Graphics 
Controller [1849:29c2]
InstallationDate: Installed on 2016-05-29 (70 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=247ca8e0-230b-4661-8e58-f7c781c801fa ro plymouth:debug=1 
init=/sbin/upstart
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-08-02 (5 days ago)
dmi.bios.date: 07/08/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: G31M-S.
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.80:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-S.: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.
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Aug  8 10:54:18 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech Dell Wireless Mouse WM123 MOUSE, id 8
 inputLogitech Dell Wireless Mouse WM123 KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 630 
 vendor ACR
xserver.version: 2:1.18.3-1ubuntu2.3

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


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

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

Title:
  starting in upstart mode

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu 16.04.1 starts in upstart mode and not in normal mode. please
  help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Aug  8 11:01:59 2016
  DistUpgraded: 2016-08-02 12:13:30,790 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 82G33/G31 Express Integrated Graphics 
Controller [1849:29c2]
  InstallationDate: Installed on 2016-05-29 (70 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: To Be 

[Touch-packages] [Bug 1607799] Re: Dash freezes after U1 login

[Selene Scriven]

As far as I can tell, this is when the bug started:
https://requests.ci-train.ubuntu.com/#/ticket/1582
https://code.launchpad.net/~mardy/libsignon-glib/unregistered-lp1593805/+merge/298096

I ran into the issue today and tracked it down to that specific image
(and that landing seems the most likely candidate), which led me to this
bug.

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

Title:
  Dash freezes after U1 login

Status in Canonical System Image:
  In Progress
Status in libsignon-glib package in Ubuntu:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  Incomplete
Status in unity-scopes-shell package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - Without U1 account, go to Ubuntu Store.
  - Tap on an app.
  - Tap on the install button.
  - Introduce credentials.

  Expected result.
  - After credentials, the app is installed.

  Actual result.
  - Dash is frozen. Cannot go back to the scopes. Launcher and indicators do 
work, though. There is no crash.

  current build number: 389
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

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

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

[Touch-packages] [Bug 1363946] Re: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale

[Daniel van Vugt]

This is still one of the top Unity8 crashes apparently...
https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb

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

Title:
  unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect
  locale

Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Fix Released

Bug description:
  unity8-dash gets into a respawn loop when the selected locale is
  unavailable. While it's understood that incorrect locale might result
  in unexpected behaviour, but aborting feels excessive.

  .log file mentions:

  ERROR! Caught unity::scopes::ConfigException: Cannot instantiate run time for 
client, config file: :
  unity::scopes::MiddlewareException: cannot initialize zmq middleware for 
scope c-17178aae:
  locale::facet::_S_create_c_locale name not

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20140828.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Mon Sep  1 11:55:15 2014
  ExecutablePath: /usr/bin/unity8-dash
  ExecutableTimestamp: 1409258182
  InstallationDate: Installed on 2014-09-01 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140901-020204)
  LocalLibraries: /android/system/lib/libGLES_trace.so 
/android/system/lib/libstlport.so /android/system/lib/libgccdemangle.so 
/android/system/lib/libm.so /android/system/lib/libcorkscrew.so 
/android/system/lib/liblog.so /android/system/lib/libstdc++.so 
/android/system/lib/libutils.so /android/system/lib/libc.so 
/android/system/lib/libcutils.so /android/system/lib/libGLESv2.so 
/android/system/lib/libEGL.so /android/system/lib/libdsyscalls.so
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcCwd: /home/phablet
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /lib/arm-linux-gnueabihf/libc.so.6
   raise () from /lib/arm-linux-gnueabihf/libc.so.6
   abort () from /lib/arm-linux-gnueabihf/libc.so.6
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
   ?? () from 
/usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  Title: unity8-dash crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1363946/+subscriptions

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

[Touch-packages] [Bug 1539811] Re: Mir/unity-system-compositor crashed with std::exception::what: Couldn't clear output eDP-1 (drmModeSetCrtc = -13)

[Daniel van Vugt]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

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

Title:
  Mir/unity-system-compositor crashed with std::exception::what:
  Couldn't clear output eDP-1 (drmModeSetCrtc = -13)

Status in Canonical System Image:
  New
Status in Mir:
  Confirmed
Status in Unity System Compositor:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  This is a live USB environment (16.04, 2016-01-29 image). HP Envy x360
  hybrid notebook. Package installed: 1.0.12+15.10.20150609-0ubuntu1 .

  After installing the mir desktop session package and choosing
  "logout", the greeter correctly shows Unity8 as a login option. After
  entering "ubuntu" and a blank password, the screen goes to black (with
  backight), the fan runs for a few seconds of high activity, and no
  graphical session ever actually starts.  The other tty screens remain
  available, and lightdm is eventually able to restart (though only
  after some time, and it is unclear if the commands to restart it are
  actually helping).

  Some selected error messages from the time of session login:

  *From lightdm.log*:
  [+158.12s] DEBUG: Session pid=6899: Greeter requests session unity8-mir
  [+158.12s] CRITICAL: g_dbus_connection_call_sync_internal: assertion 
'object_path != NULL && g_variant_is_object_path (object_path)' failed

  *From unity-system-compositor.log*:
  dm_connection_start
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: write: Broken pipe
  ...
  Closing session GDK-Mir
  ERROR: 
/build/mir-UeyFew/mir-0.19.0+16.04.20160128/src/common/fatal/fatal.cpp(55): 
Throw in function void mir::fatal_error_except(const char*, ...)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Couldn't clear output eDP-1 (drmModeSetCrtc = -13)

  *From syslog*:
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: Failed to connect 
to Mir: Failed to connect to server socket: No such file or directory
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: Unable to init 
server: Could not connect: Connection refused
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: 
(notify-osd:7672): Gtk-WARNING **: cannot open display:
  Jan 29 22:40:42 ubuntu dbus[1325]: [system] Activating service 
name='com.canonical.SystemImage' (using servicehelper)
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: usage: 
system-image-dbus [-h] [--version] [-C DIRECTORY] [-v]
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: system-image-dbus: 
error:
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: Configuration 
directory not found: .load() requires a directory: /etc/system-image/config.d
  Jan 29 22:40:42 ubuntu dbus[1325]: [system] Activated service 
'com.canonical.SystemImage' failed: Launcher could not run (out of memory)

  The Unity8.log and Unity8-dash.log files are just repetitions of:
  QXcbConnection: Could not connect to display .

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

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

[Touch-packages] [Bug 1578127] Re: Sometimes WLAN detects no SSID after s3

[Chih-Hsyuan Ho]

On the Dell platform where this bug was originally reported on, with the
latest network manager package, the issue was no longer seen.

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

Title:
  Sometimes WLAN detects no SSID after s3

Status in NetworkManager:
  New
Status in OEM Priority Project:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  1. Boot into OS
  2. Do s3 a few times
  3. Check if wifi is still working after s3

  [Expected results]
  wifi still working correctly after s3

  [Actual results]
  1. Wifi shows "disconnected" in network-manager (both in applet and from 
command "nmcli d status")
  2. Only one random SSID is displayed in network-manager applet, but wifi 
connection cannot be established at all with this SSID. Clicking on the SSID 
results in pop up window in the comment #2 below
  3. "nmcli d wifi rescan" does not resolve issue
  4.  "iwlist [interface] scan" returns nothing and does not reolve issue
  5. "nmcli d wifi connect [any SSID that you know should exist]" results in 
SSID not found and does not resolve issue
  6. "sudo service network-manager restart", warm boot, cold boot resolves issue

  [Details]
  OS: Xenial based OEM image
  WLAN module: Marvel [11ab:2b38]
  network-manager:
  - 1.2.0-0ubuntu0.16.04.1 (fail rate 1/20~ 1/15)
  - 1.1.93 (fail rate 1/15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1578127/+subscriptions

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

[Touch-packages] [Bug 1610828] Re: /usr/sbin/unity-system-compositor:7:util_fill_rect:util_fill_box:lp_rast_clear_color:do_rasterize_bin:rasterize_bin

[Daniel van Vugt]

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

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

Title:
  /usr/sbin/unity-system-
  
compositor:7:util_fill_rect:util_fill_box:lp_rast_clear_color:do_rasterize_bin:rasterize_bin

Status in mesa package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.4.3+16.04.20160323-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/da25ea8387d82ab51ac1e8bcc507d7a7c35a101f
  contains more details.

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

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

[Touch-packages] [Bug 1610829] Re: /usr/sbin/unity-system-compositor:*** Error in `/usr/sbin/unity-system-compositor': malloc(): memory corruption: ADDR ***

[Daniel van Vugt]

** Also affects: unity-system-compositor
   Importance: Undecided
   Status: New

** Also affects: mir
   Importance: Undecided
   Status: New

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

Title:
  /usr/sbin/unity-system-compositor:*** Error in `/usr/sbin/unity-
  system-compositor': malloc(): memory corruption: ADDR ***

Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.6.0+16.04.20160609-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ff42d7ab6d4e7a23379607f8a5375a837b3a10bd
  contains more details.

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

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

[Touch-packages] [Bug 1610828] [NEW] /usr/sbin/unity-system-compositor:7:util_fill_rect:util_fill_box:lp_rast_clear_color:do_rasterize_bin:rasterize_bin

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity-system-compositor.  This problem was most recently seen
with version 0.4.3+16.04.20160323-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/da25ea8387d82ab51ac1e8bcc507d7a7c35a101f
contains more details.

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

** Affects: unity-system-compositor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: utopic vivid wily xenial

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

Title:
  /usr/sbin/unity-system-
  
compositor:7:util_fill_rect:util_fill_box:lp_rast_clear_color:do_rasterize_bin:rasterize_bin

Status in mesa package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.4.3+16.04.20160323-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/da25ea8387d82ab51ac1e8bcc507d7a7c35a101f
  contains more details.

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

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

[Touch-packages] [Bug 1610827] Re: /usr/sbin/unity-system-compositor:6:mir::fatal_error_abort:mir::graphics::mesa::DisplayBuffer::post:mir::compositor::CompositingFunctor::operator:std::function:execu

[Daniel van Vugt]

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

This is either a duplicate of bug 1489689 or bug 1584894.

Most likely bug 1584894 but it's hard to verify people are using
Virtualbox on errors.ubuntu.com

** This bug has been marked a duplicate of bug 1584894
   unity-system-compositor crashes on start-up with "Mir fatal error: Failed to 
schedule page flip" on VirtualBox Graphics Adapter

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

Title:
  /usr/sbin/unity-system-
  
compositor:6:mir::fatal_error_abort:mir::graphics::mesa::DisplayBuffer::post:mir::compositor::CompositingFunctor::operator:std::function:execute

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.5.1+16.04.20160428-0ubuntu2, the problem page at
  https://errors.ubuntu.com/problem/09ddeeebc6aebbd4f391f218915aa28545ac8226
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1610827/+subscriptions

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

[Touch-packages] [Bug 1610829] [NEW] /usr/sbin/unity-system-compositor:*** Error in `/usr/sbin/unity-system-compositor': malloc(): memory corruption: ADDR ***

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity-system-compositor.  This problem was most recently seen
with version 0.6.0+16.04.20160609-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/ff42d7ab6d4e7a23379607f8a5375a837b3a10bd
contains more details.

** Affects: mir
 Importance: Undecided
 Status: New

** Affects: unity-system-compositor
 Importance: Undecided
 Status: New

** Affects: unity-system-compositor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

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

Title:
  /usr/sbin/unity-system-compositor:*** Error in `/usr/sbin/unity-
  system-compositor': malloc(): memory corruption: ADDR ***

Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.6.0+16.04.20160609-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ff42d7ab6d4e7a23379607f8a5375a837b3a10bd
  contains more details.

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

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

[Touch-packages] [Bug 1584894] Re: unity-system-compositor crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter

[Daniel van Vugt]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

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

Title:
  unity-system-compositor crashes on start-up with "Mir fatal error:
  Failed to schedule page flip" on VirtualBox Graphics Adapter

Status in Canonical System Image:
  New
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  (separated from bug 1118903)
  unity-system-compositor crashes on start-up with "Mir fatal error: Failed to 
schedule page flip" on VirtualBox Graphics Adapter

  ---

  can not login to Unity8

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-system-compositor 0.4.3+16.04.20160323-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Mon May 23 19:20:43 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-05-19 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160519)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file 
/run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:

  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   mir::fatal_error_abort(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.8
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGABRT in 
mir::fatal_error_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  version.libdrm: libdrm2 2.4.68-1
  version.lightdm: lightdm 1.19.0-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1610830] Re: /usr/sbin/unity-system-compositor:6:mir::fatal_error_abort:mir::graphics::mesa::RealKMSOutput::clear_crtc:operator:std::_Function_handler:std::function

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1539811
   Mir/unity-system-compositor crashed with std::exception::what: Couldn't 
clear output eDP-1 (drmModeSetCrtc = -13)

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

Title:
  /usr/sbin/unity-system-
  
compositor:6:mir::fatal_error_abort:mir::graphics::mesa::RealKMSOutput::clear_crtc:operator:std::_Function_handler:std::function

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.6.0+16.10.20160609-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/694be93fb95afa349e8c1d0581399fb488edd26a
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1610830/+subscriptions

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

[Touch-packages] [Bug 1610830] [NEW] /usr/sbin/unity-system-compositor:6:mir::fatal_error_abort:mir::graphics::mesa::RealKMSOutput::clear_crtc:operator:std::_Function_handler:std::function

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity-system-compositor.  This problem was most recently seen
with version 0.6.0+16.10.20160609-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/694be93fb95afa349e8c1d0581399fb488edd26a
contains more details.

** Affects: unity-system-compositor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: yakkety

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

Title:
  /usr/sbin/unity-system-
  
compositor:6:mir::fatal_error_abort:mir::graphics::mesa::RealKMSOutput::clear_crtc:operator:std::_Function_handler:std::function

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.6.0+16.10.20160609-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/694be93fb95afa349e8c1d0581399fb488edd26a
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1610830/+subscriptions

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

[Touch-packages] [Bug 1610827] [NEW] /usr/sbin/unity-system-compositor:6:mir::fatal_error_abort:mir::graphics::mesa::DisplayBuffer::post:mir::compositor::CompositingFunctor::operator:std::function:exe

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity-system-compositor.  This problem was most recently seen
with version 0.5.1+16.04.20160428-0ubuntu2, the problem page at
https://errors.ubuntu.com/problem/09ddeeebc6aebbd4f391f218915aa28545ac8226
contains more details.

** Affects: unity-system-compositor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial yakkety

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

Title:
  /usr/sbin/unity-system-
  
compositor:6:mir::fatal_error_abort:mir::graphics::mesa::DisplayBuffer::post:mir::compositor::CompositingFunctor::operator:std::function:execute

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.5.1+16.04.20160428-0ubuntu2, the problem page at
  https://errors.ubuntu.com/problem/09ddeeebc6aebbd4f391f218915aa28545ac8226
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1610827/+subscriptions

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

[Touch-packages] [Bug 1605991] Re: Multiseat login stopped working

[Robert Ancell]

** Changed in: lightdm (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Multiseat login stopped working

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  After installing version 1.18.2-0ubuntu1 of the lightdm package, only one 
seat can login on my multiseat setup. (2 seats)
  Reverting to version 1.18.1-0ubuntu1 resolves the issue.

  syslog shows the following errors:

  console-kit-daemon[4783]: (process:16634): GLib-CRITICAL **: 
g_slice_set_config: assertion 'sys_page_size == 0' failed
  lightdm[16617]: ** (lightdm:16617): CRITICAL **: 
session_get_login1_session_id: assertion 'session != NULL' failed

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

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

[Touch-packages] [Bug 1560501] Re: /usr/bin/unity8:11:QScopedPointer:qGetPtrHelper:QQuickItem::d_func:QQuickItem::setWidth:ShellView::onWidthChanged

[Daniel van Vugt]

Nominated for xenial. errors.ubuntu.com shows this is still one of the
top Unity8 crashes even today.

Maybe the fix is just missing from xenial?

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

Title:
  
/usr/bin/unity8:11:QScopedPointer:qGetPtrHelper:QQuickItem::d_func:QQuickItem::setWidth:ShellView::onWidthChanged

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+16.04.20160310.4-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/90e7e901e2b03e8f75d9d4c72e9130f7d4b35c83
  contains more details.

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

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

[Touch-packages] [Bug 1535297] Re: Unity8 crashes on logout with "Error in `unity8': double free or corruption" called from libprotobuf.so.9, called from libprotobuf-lite.so.9

[Daniel van Vugt]

I was wondering why we don't get more heat from users on this crash
since it happens every time you log out of Unity8. Turns out we do get
the crash reports and nobody noticed...

https://errors.ubuntu.com/problem/72327e33abf9e9da2cd9ed1ac28b9d843c18b5bb

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

Title:
  Unity8 crashes on logout with "Error in `unity8': double free or
  corruption" called from libprotobuf.so.9, called from libprotobuf-
  lite.so.9

Status in Canonical System Image:
  New
Status in Mesa:
  New
Status in Mir:
  Confirmed
Status in libphonenumber package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This is happening on a fresh setup, which is basically:
  Xenial 17Jan iso + unity8-desktop-session-mir package

  When I logout, I get a black screen. Turns out unity8 is crashing with
  a "double free or linked list corruption"

  Please find unity8.log attached

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

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

[Touch-packages] [Bug 1610825] Re: /usr/bin/unity8:6:__libc_message:malloc_printerr:_int_free:__GI___libc_free:operator

[Daniel van Vugt]

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

Duplicate of bug 1535297. We've known about this for a long time.

** This bug has been marked a duplicate of bug 1535297
   Unity8 crashes on logout with "Error in `unity8': double free or corruption" 
called from libprotobuf.so.9, called from libprotobuf-lite.so.9

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

Title:
  
/usr/bin/unity8:6:__libc_message:malloc_printerr:_int_free:__GI___libc_free:operator

Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.13+16.10.20160714-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/72327e33abf9e9da2cd9ed1ac28b9d843c18b5bb
  contains more details.

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

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

[Touch-packages] [Bug 1610825] [NEW] /usr/bin/unity8:6:__libc_message:malloc_printerr:_int_free:__GI___libc_free:operator

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity8.  This problem was most recently seen with version
8.13+16.10.20160714-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/72327e33abf9e9da2cd9ed1ac28b9d843c18b5bb
contains more details.

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


** Tags: xenial yakkety

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

Title:
  
/usr/bin/unity8:6:__libc_message:malloc_printerr:_int_free:__GI___libc_free:operator

Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.13+16.10.20160714-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/72327e33abf9e9da2cd9ed1ac28b9d843c18b5bb
  contains more details.

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

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

[Touch-packages] [Bug 1568485] Re: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13

[Mathew Hodson]

** Changed in: isc-dhcp (Ubuntu Wily)
   Status: Invalid => Won't Fix

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

Title:
  kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in isc-dhcp source package in Wily:
  Won't Fix

Bug description:
  Get this logged on a fully upgraded 64 desktop (proposed archive
  enabled)

  kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/sbin/dhclient" name="run/systemd/journal/dev-log"
  pid=1102 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0
  ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr 10 12:23:56 2016
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1568485/+subscriptions

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

[Touch-packages] [Bug 1588597] Re: Some ads permanetly block webpages, even unrelated pages.

[Launchpad Bug Tracker]

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

** Changed in: webbrowser-app (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Some ads permanetly block webpages, even unrelated pages.

Status in webbrowser-app package in Ubuntu:
  Expired

Bug description:
  This is a strange intermittent problem. It seems that full page, or
  perhaps page covering ads on web pages will not only block the web
  page underneath in opaque black, but block everything in the browser.
  This includes other web pages and hitting the back button to escape
  the screen. When this happens, there will also be slim white
  rectangles on the right-side edge of the screen when scrolling.
  Screenshots are attached.

  http://imgur.com/a/yLWGj

  I'm using a Meizu Pro 5 (turbo) OTA 11 from the stable "meizu.en"
  channel. I can attest that this same behavior appeared in OTA 10.2 as
  well.

  EXPECTATIONS:
  1 - When an ad or other element blocks the web page, I expect to be able to 
close or hide it.
  2 - If I go back a page, I expect the element to be stop blocking the 
webpages.

  REALITY:
  A - They are unclosable.
  B - Even hitting back or navigating to a different web page doesn't make the 
black overlay disappear.

  webbrowser app is 0.23+15.04.20160509.3-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1588597/+subscriptions

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

[Touch-packages] [Bug 1528735] Re: Suspend reboots every second time on Lenovo G50-45

[Brad]

Next I'll test with a fresh live-USB version of Linux Mint 17.3 (kernel
3.19) to try to narrow down the problem.  I'm not expecting it to work
since I've already reproduced the problem on LM 17.3 installed to HD.

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

Title:
  Suspend reboots every second time on Lenovo G50-45

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1528735/+subscriptions

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

[Touch-packages] [Bug 1528735] Re: Suspend reboots every second time on Lenovo G50-45

[Brad]

OK, I just tested with a Live-USB disk of Linux Mint 17.2 Cinnamon
(kernel 3.16) newly burned from the ISO file and suspend/resume works
great. Multiple times in a row, from the shutdown icon, from the power
button, and from the notebook lid close/open. So this is either Kernel
or distro dependant and perhaps not related to the BIOS version as I
thought. I tested this from a Live-USB of Linux Mint 18 Cinnamon (kernel
4.4) and it DOES NOT work, it has the same problem - first
suspend/resume works fine, then upon second suspend it displays the
yellow text warning and reboots the system at the BIOS level.

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

Title:
  Suspend reboots every second time on Lenovo G50-45

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1528735/+subscriptions

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

[Touch-packages] [Bug 1610619] Re: Xscreen saver and lightdm prevent use of operating system (total lockout) after guest session screen lock

[Gunnar Hjalmarsson]

Well, if this only happens on Linux Mint, you are on the wrong bug
tracker. I added the Linux Mint task to the report.

With that said, the lightdm developers are possibly willing to add
whatever is required to address this issue, but in that case they need
to know - really know - what would be required. Myself is working with
Ubuntu and sometimes the official flavors, so I can't help there.

As regards your ideas in comment #5, the first one is already there in
/usr/lib/lightdm/guest-session-auto.sh. When I had a quick look in
Xubuntu, I got the impression that the xscreensaver settings are saved
in ~/.xscreensaver rather than as gsettings values, but I may not have
got the whole picture.

So the ball is in your court again. ;)

** Also affects: linuxmint
   Importance: Undecided
   Status: New

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

Title:
  Xscreen saver and lightdm prevent use of operating system (total
  lockout) after guest session screen lock

Status in Linux Mint:
  New
Status in xscreensaver:
  New
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce bug:

  1)  Install xubuntu or mint xfce
  2)  download and set lightdm as desktop manager
  3)  sign in to a guest session and either close your laptop lid or allow 
timeout to start screen lock

  Why this is a bug:

  xscreensaver will not accept a blank/null password, and with a
  blank/null password assigned to the guest session, the xscreensaver
  client will not allow the user to continue their session or login as a
  new user (because you cannot login as a new user as xscreensaver does
  not support lightdm for this feature.

  Why this is severe:

  when xscreensaver locks the guest user out of their session, all other
  users are similarly locked out.  Being so locked out, the computer
  most be hard-reset/rebooted and any documents and processes not saved
  prior to the guest session being logged in is lost.

  Why this is a lightdm bug:

  Because lightdm is not setting the gconf setting to disable the lock
  screen feature for guest sessions

  Why this is a xscreensaver bug:

  xscreensaver does not support any dm other than mdm

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

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

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

[Bob Goates]

Public bug reported:

Seems similar to #1578762 but this error message says "initramfs-tools
0.122ubuntu8.1".  This error first appeared when attempting to upgrade
my distribution.  After the failure to upgrade which this error message
announced my system is in fairly flaky condition.  uname -a returns
"Linux  4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13
00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux".

I will now do a fresh installation, if I can get my machine to download
16.04.1.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Aug  7 17:13:03 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-02 (127 days ago)
InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-08-08 (0 days ago)
mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T15:22:01

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


** Tags: amd64 apport-package xenial

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Seems similar to #1578762 but this error message says "initramfs-tools
  0.122ubuntu8.1".  This error first appeared when attempting to upgrade
  my distribution.  After the failure to upgrade which this error
  message announced my system is in fairly flaky condition.  uname -a
  returns "Linux  4.4.0-31-generic #50-Ubuntu SMP Wed
  Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux".

  I will now do a fresh installation, if I can get my machine to
  download 16.04.1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug  7 17:13:03 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-02 (127 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (0 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T15:22:01

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

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

[Touch-packages] [Bug 1610772] [NEW] [drm] stuck on render ring

[Mikhail]

Public bug reported:

The problem is similiar to the one discrabed in #1547800

It was happen once in a while. Now it always happens when returning from
sleep.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog: /dev/sda6: clean, 278496/3727360 files, 2012554/14884352 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sun Aug  7 22:04:40 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: kubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
InstallationDate: Installed on 2016-06-26 (42 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP EliteBook 8470p
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=1126bf38-027a-410d-a905-5dbbd05a6b4d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68ICF Ver. F.45
dmi.board.name: 179B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 42.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8470p
dmi.product.version: A1029D1102
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jul 25 07:40:00 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5236 
 vendor CMN
xserver.version: 2:1.18.3-1ubuntu2.2

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


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

Title:
  [drm] stuck on render ring

Status in xorg package in Ubuntu:
  New

Bug description:
  The problem is similiar to the one discrabed in #1547800

  It was happen once in a while. Now it always happens when returning
  from sleep.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: /dev/sda6: clean, 278496/3727360 files, 2012554/14884352 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Aug  7 22:04:40 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
  InstallationDate: Installed on 2016-06-26 (42 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=1126bf38-027a-410d-a905-5dbbd05a6b4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.45
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1607185] Re: It's difficult to close the launcher without tapping on something you didn't want to

[Daniel van Vugt]

This is kind of another use case we need pointer grabs for -- to safely
close a pop-up without affecting anything else. See bug 1506713.

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

Title:
  It's difficult to close the launcher without tapping on something you
  didn't want to

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  It's difficult to close the launcher without tapping on something you
  didn't want to.

  Test case:
1. Open an app.
2. Open the launcher swiping from the left.
3. Close the launcher without triggering any touches in the app.

  Expected: Tapping outside the launcher will close it without touches reaching 
the app.
  Observed: Tapping outside the launcher closes it but unwanted touches reach 
the app.

  You can close the launcher by swiping it back off the side, but it's
  too small to do that very easily without also accidentally touching
  the top-most app.

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

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

[Touch-packages] [Bug 1603183] Re: Bottom right area of touchpad no longer treated as right click

[Daniel van Vugt]

Weird. Another bug marked Fix Released or Committed when the actual code
change hasn't landed yet(!?)

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

Title:
  Bottom right area of touchpad no longer treated as right click

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Triaged
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in libinput package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Using the touchpad I was not able to trigger any right click (with a
  single finger in the bottom right area), and I tought it was a problem
  of how unity8 handled the right clicks. Instead I just tried with a
  mouse and right click trigger different actions from left clicks.

  In the end the problem is that my touchpad right click is considered a
  left click by the system. This does not happen with an usb mouse.

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

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

[Touch-packages] [Bug 1604701] Re: Animated cursors don't animate in Unity8

[Daniel van Vugt]

In progress still. Nothing has been committed yet.

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

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

Title:
  Animated cursors don't animate in Unity8

Status in Canonical System Image:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Animated cursors don't animate in Unity8.

  Test case:
   mir_demo_client_animated_cursor -- --desktop_file_hint=unity8

  Works in Mir demo servers but not in Unity8.

  I mentioned this in bug 1447839 but that one appears to have closed
  prematurely.

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

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

[Touch-packages] [Bug 1604014] Re: the mouse pointer in unity8 is huge compared to unity7

[Daniel van Vugt]

In progress actually.

Although Unity7 recently got "fixed" so it does have a larger cursor
that scales with everything else. So I'm not sure if that makes this bug
Invalid, Won't Fix, or just a matter of fine tuning.

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

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

Title:
  the mouse pointer in unity8 is huge compared to unity7

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in Ubuntu UX:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  the mouse pointer in unity8 is huge compared to unity7

  screenshot attached (it's twice as big)

  ubuntu 16.10 unity8 desktop 
  1680x1050 pixels (445x278 millimeters)
  96x96 dots per inch

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

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

[Touch-packages] [Bug 1577641] Re: Unity8 creates a blank black window for windowless apps

[Daniel van Vugt]

Unity8 needs this bug fixing for one simple reason:
Even apps that do display a window "immediately" will get a splash screen of 
the wrong size displayed before a window of the correct size appears. This will 
be particularly important after bug 1606501 gets fully fixed.

And no, it's not invalid for Xmir to not create a window on start-up in
rootless mode, it is correct behaviour. It's a server and has no windows
until the X client creates one. It's distracting and confusing for
Unity8 to create a black window where there should be no window at all.

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

** Changed in: mir
   Status: New => Invalid

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

Title:
  Unity8 creates a blank black window for windowless apps

Status in Canonical System Image:
  New
Status in Mir:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 creates a blank black window for windowless apps.

  Windowless apps are closer thank you think:   Xmir -rootless
  is one such example while no X apps have started yet.

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

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

[Touch-packages] [Bug 1610619] Re: Xscreen saver and lightdm prevent use of operating system (total lockout) after guest session screen lock

[Omadas]

Some ideas for the guest session:
gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true'
or
gsettings set org.gnome.desktop.screensaver ubuntu-lock-on-suspend 'false'

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

Title:
  Xscreen saver and lightdm prevent use of operating system (total
  lockout) after guest session screen lock

Status in xscreensaver:
  New
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce bug:

  1)  Install xubuntu or mint xfce
  2)  download and set lightdm as desktop manager
  3)  sign in to a guest session and either close your laptop lid or allow 
timeout to start screen lock

  Why this is a bug:

  xscreensaver will not accept a blank/null password, and with a
  blank/null password assigned to the guest session, the xscreensaver
  client will not allow the user to continue their session or login as a
  new user (because you cannot login as a new user as xscreensaver does
  not support lightdm for this feature.

  Why this is severe:

  when xscreensaver locks the guest user out of their session, all other
  users are similarly locked out.  Being so locked out, the computer
  most be hard-reset/rebooted and any documents and processes not saved
  prior to the guest session being logged in is lost.

  Why this is a lightdm bug:

  Because lightdm is not setting the gconf setting to disable the lock
  screen feature for guest sessions

  Why this is a xscreensaver bug:

  xscreensaver does not support any dm other than mdm

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

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

[Touch-packages] [Bug 1610619] Re: Xscreen saver and lightdm prevent use of operating system (total lockout) after guest session screen lock

[Omadas]

After the reinstall xscreensaver is still locking by default.  I can disable 
this feature in Settings and it is now fine (Because it does not lock).  
However, I wanted this locking feature, it is still a bug in that enabling this 
locking feature still locks the screen for the guest account, which uses a 
blank password to sign in (which then cannot be used by xscreensaver because it 
does not accept null/blank passwords. 
   I would suggest that fresh installs of xscreensaver disable screenlock by 
default.  I believe as far as light-dm is concerned, after a quick google 
search i found that the setting or flag it needs to enable to prevent 
screenlocking might be available in gconf...  but i dont know the specific area 
where this would need to be implemented without looking...

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

Title:
  Xscreen saver and lightdm prevent use of operating system (total
  lockout) after guest session screen lock

Status in xscreensaver:
  New
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce bug:

  1)  Install xubuntu or mint xfce
  2)  download and set lightdm as desktop manager
  3)  sign in to a guest session and either close your laptop lid or allow 
timeout to start screen lock

  Why this is a bug:

  xscreensaver will not accept a blank/null password, and with a
  blank/null password assigned to the guest session, the xscreensaver
  client will not allow the user to continue their session or login as a
  new user (because you cannot login as a new user as xscreensaver does
  not support lightdm for this feature.

  Why this is severe:

  when xscreensaver locks the guest user out of their session, all other
  users are similarly locked out.  Being so locked out, the computer
  most be hard-reset/rebooted and any documents and processes not saved
  prior to the guest session being logged in is lost.

  Why this is a lightdm bug:

  Because lightdm is not setting the gconf setting to disable the lock
  screen feature for guest sessions

  Why this is a xscreensaver bug:

  xscreensaver does not support any dm other than mdm

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

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

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

[Alberto]

I have the same problem after upgrading to 16.04 from 14.04.
I am using a Kaveri APU, that is supposed to work with both "radeon" and 
"amdgpu" drivers.
The "radeon" driver doesn't work: after the very initial steps of the 
bootstrap, the screen goes black, although a may access the system via SSH.
Setting "nomodeset" prevents the "radeon" driver to start, reverting back to 
basic driver.
However, the new "amdgpu" driver seems working fine.
I managed to fix the issue in the following way:
1. blacklist "radeon", by creating a new file 
/etc/modprobe.d/blacklist-radeon.conf having a single line "blacklist radeon";
2. force "amdgpu", by appending to /etc/modules the line "amdgpu";
3. setting the screen resolution in grub, by uncomment the line GRUB_GFXMODE, 
e.g. "GRUB_GFXMODE=1280x1024";
4. create a new file /etc/X11/xorg.conf, having a block
 Section "Device"
   Identifier  "VideoCard"
   DriveR  "amdgpu"
 EndSection
5. update initramfs, via "update-initramfs -u -k all" with sudo;
6. update grub configuration, via "update-grub" with sudo.
Maybe other user having a GCN-enabled AMD video card may fix the issue in the 
same way.

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

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

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

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

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

[Touch-packages] [Bug 1610619] Re: Xscreen saver and lightdm prevent use of operating system (total lockout) after guest session screen lock

[Omadas]

...Now I am not so sure, the system i am using still has this problem: It is 
MintXFCE.
I will purge and reinstall and see if it is a config problem somewhere.

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

Title:
  Xscreen saver and lightdm prevent use of operating system (total
  lockout) after guest session screen lock

Status in xscreensaver:
  New
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce bug:

  1)  Install xubuntu or mint xfce
  2)  download and set lightdm as desktop manager
  3)  sign in to a guest session and either close your laptop lid or allow 
timeout to start screen lock

  Why this is a bug:

  xscreensaver will not accept a blank/null password, and with a
  blank/null password assigned to the guest session, the xscreensaver
  client will not allow the user to continue their session or login as a
  new user (because you cannot login as a new user as xscreensaver does
  not support lightdm for this feature.

  Why this is severe:

  when xscreensaver locks the guest user out of their session, all other
  users are similarly locked out.  Being so locked out, the computer
  most be hard-reset/rebooted and any documents and processes not saved
  prior to the guest session being logged in is lost.

  Why this is a lightdm bug:

  Because lightdm is not setting the gconf setting to disable the lock
  screen feature for guest sessions

  Why this is a xscreensaver bug:

  xscreensaver does not support any dm other than mdm

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

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

[Touch-packages] [Bug 1610750] [NEW] nm-applet constantly prompts for password, leaks memory

[Fengyang Wang]

Public bug reported:

Network Manager is constantly asking me for a WIFI password, as
frequently as once a minute. I do not get this problem on my phone, even
though it is using the same WIFI network. The problem does not occur on
other WIFI networks, so I suspect this is a problem with the WIFI
network itself, and is possibly not Network Manager's fault. So this is
annoying, but liveable.

However, np-applet is also leaking an absurd amount of memory each time
I enter my password and click "Connect". It's ridiculous for it to be
using up over 2 GB of resident memory, and to be constantly increasing
that number, after running for only a few hours.

This is a not a duplicate of https://bugs.launchpad.net/ubuntu/+source
/network-manager-applet/+bug/684599. In that issue, which has been
closed with a "Fix Released" status, the reports are hundreds of
megabytes of memory, not gigabytes, so I suspect this is a fundamentally
different problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.0-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug  7 19:08:52 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-08-26 (1077 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
 default via 10.2.61.69 dev wlan0  proto static  metric 600 
 10.0.1.4 via 10.2.61.69 dev wlan0  proto dhcp  metric 600 
 10.2.61.68/30 dev wlan0  proto kernel  scope link  src 10.2.61.70  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2016-04-26 (103 days ago)
nmcli-dev:
 DEVICE  TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH

 wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/0  EHS 
New Yorker Residence  c06e0703-cd04-4294-9f99-8624c834f389  
/org/freedesktop/NetworkManager/ActiveConnection/53 
 eth0ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/1  --  
  ----  

 lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  --  
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  nm-applet constantly prompts for password, leaks memory

Status in network-manager package in Ubuntu:
  New

Bug description:
  Network Manager is constantly asking me for a WIFI password, as
  frequently as once a minute. I do not get this problem on my phone,
  even though it is using the same WIFI network. The problem does not
  occur on other WIFI networks, so I suspect this is a problem with the
  WIFI network itself, and is possibly not Network Manager's fault. So
  this is annoying, but liveable.

  However, np-applet is also leaking an absurd amount of memory each
  time I enter my password and click "Connect". It's ridiculous for it
  to be using up over 2 GB of resident memory, and to be constantly
  increasing that number, after running for only a few hours.

  This is a not a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager-applet/+bug/684599. In that issue, which has been
  closed with a "Fix Released" status, the reports are hundreds of
  megabytes of memory, not gigabytes, so I suspect this is a
  fundamentally different problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug  7 19:08:52 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-26 (1077 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 10.2.61.69 dev wlan0  

[Touch-packages] [Bug 1610741] [NEW] Intell GPU

[Sven]

Public bug reported:

By Paying Videos and make other Things under Firefox and LibreOffice.
The GPU Stocks and make a bad framerate under my Laptop.
The GPU is Bead Supported...
Broadwell GPU.. :/

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Aug  7 23:47:04 2016
InstallationDate: Installed on 2016-07-12 (26 days ago)
InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160607
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug sarah

** Attachment added: "PC specification and Example Picture on LibreOffice"
   https://bugs.launchpad.net/bugs/1610741/+attachment/4716153/+files/PC.tar.gz

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

Title:
  Intell GPU

Status in xorg package in Ubuntu:
  New

Bug description:
  By Paying Videos and make other Things under Firefox and LibreOffice.
  The GPU Stocks and make a bad framerate under my Laptop.
  The GPU is Bead Supported...
  Broadwell GPU.. :/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Aug  7 23:47:04 2016
  InstallationDate: Installed on 2016-07-12 (26 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160607
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1610698] Re: password warning when numlock is on

[Gunnar Hjalmarsson]

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

Making it a duplicate, then.

** This bug has been marked a duplicate of bug 1526322
   Lock screen shows unnecessary warning about numlock

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

Title:
  password warning when numlock is on

Status in lightdm package in Ubuntu:
  New

Bug description:
  When logging into a gui session or unlocking the screen of an existing
  session, the password field displays  a warning notification when
  numlock is on.  This should be reversed, as the non-numeric functions
  of the numpad are irrelevant at that point to the user(home/end,
  pageup/pagedown), while the numeric input(0-9) are potentially quite
  important to the user.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug  7 10:53:51 2016
  InstallationDate: Installed on 2014-12-11 (605 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (3 days ago)

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

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

[Touch-packages] [Bug 1595963] Re: vt1-6 getting stuck or blank

[Launchpad Bug Tracker]

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

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

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

Title:
  vt1-6 getting stuck or blank

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

Bug description:
  It's happening from time to time that my vt1-6 are getting stuck
  (showing tty1 and no input) or blank (just black) completely.

  Restarting system-getty.slice or console-getty.slice doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 24 10:00:54 2016
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 12-9Q33
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: systemd 229-4ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed 
root=ZFS=/root ro root=ZFS=username-laptop/root quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1595963] Re: vt1-6 getting stuck or blank

[Launchpad Bug Tracker]

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

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

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

Title:
  vt1-6 getting stuck or blank

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

Bug description:
  It's happening from time to time that my vt1-6 are getting stuck
  (showing tty1 and no input) or blank (just black) completely.

  Restarting system-getty.slice or console-getty.slice doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 24 10:00:54 2016
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 12-9Q33
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: systemd 229-4ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed 
root=ZFS=/root ro root=ZFS=username-laptop/root quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1610698] Re: password warning when numlock is on

[Ian Nicholson]

Yep

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

Title:
  password warning when numlock is on

Status in lightdm package in Ubuntu:
  New

Bug description:
  When logging into a gui session or unlocking the screen of an existing
  session, the password field displays  a warning notification when
  numlock is on.  This should be reversed, as the non-numeric functions
  of the numpad are irrelevant at that point to the user(home/end,
  pageup/pagedown), while the numeric input(0-9) are potentially quite
  important to the user.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug  7 10:53:51 2016
  InstallationDate: Installed on 2014-12-11 (605 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (3 days ago)

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

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

[Touch-packages] [Bug 1609613] Re: microsoft mouse BluetoothMouse3600 is not work

[Launchpad Bug Tracker]

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

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

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

Title:
  microsoft mouse BluetoothMouse3600 is not work

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  microsoft mouse BluetoothMouse3600 is not work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug  4 10:34:46 2016
  InstallationDate: Installed on 2016-07-28 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. K401LB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=b7b611fb-b08f-4ff8-a1c9-d6284a1c5e98 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K401LB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K401LB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK401LB.204:bd08/26/2015:svnASUSTeKCOMPUTERINC.:pnK401LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK401LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K401LB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 80:A5:89:11:76:1E  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:376785 acl:22984 sco:0 events:511 errors:0
TX bytes:4533 acl:62 sco:0 commands:79 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2016-07-28T21:01:30.197455

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

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

[Touch-packages] [Bug 1579419] Re: Bluetooth Mouse microsoft mobile 3600 not detected in GUI

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth Mouse microsoft mobile 3600 not detected in GUI

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I turn on the bluetooth, scan for devices and can't detect the mouse, so I 
cant pair. The I opened a terminal and use bluetoothctl. It shows the mouse as 
new. Then use the pair command and the mouse start working.
  The I back to the bluetooth GUI and nothing showing about the mouse. 
  It worked fine with logitech keyboard without the need of the terminal 
command.

  lsb_release -rd shows ubuntu 15.04
  bluez 5.37-0ubuntu5~overlay1

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

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

[Touch-packages] [Bug 1610714] Re: Evince crashes with _cairo_gstate_set_dash

[Ubuntu Foundations Team Bug Bot]

The attachment "fix.patch" seems to be a debdiff.  The ubuntu-sponsors
team has been subscribed to the bug report so that they can review and
hopefully sponsor the debdiff.  If the attachment isn't a patch, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are member of the ~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Evince crashes with _cairo_gstate_set_dash

Status in poppler package in Ubuntu:
  New

Bug description:
  When opening the following PDF in Evince 
(https://dl.ubnt.com/guides/edgemax/EdgeSwitch_ES-48_QSG.pdf), it crashes with 
the following backtrace:
  Thread 7 "EvJobScheduler" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fb17ef8d700 (LWP 11109)]
  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
  542   ../../../../src/cairo-gstate.c: Bestand of map bestaat niet.
  (gdb) bt full
  #0  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
  dash_total = 0
  on_total = 0
  off_total = 0
  i = 0
  j = 0
  #1  0x7fb19c15fa92 in cairo_set_dash (cr=0x5615ded8dc70, 
dashes=, num_dashes=, offset=) at 
../../../../src/cairo.c:1080
  status = 

  
  Upstream seems to have fixed this already:
  https://bugs.freedesktop.org/show_bug.cgi?id=62905

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

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

[Touch-packages] [Bug 1610728] [NEW] package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Osiris]

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 primus: Purge
 bumblebee: Purge
 NULL: ConfigurePending
Architecture: i386
Date: Sun Aug  7 02:50:54 2016
Df:
 
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to xenial on 2016-05-15 (83 days ago)

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


** Tags: apport-package i386 third-party-packages xenial

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

Title:
  package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   primus: Purge
   bumblebee: Purge
   NULL: ConfigurePending
  Architecture: i386
  Date: Sun Aug  7 02:50:54 2016
  Df:
   
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to xenial on 2016-05-15 (83 days ago)

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

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

[Touch-packages] [Bug 1610714] Re: Evince crashes with _cairo_gstate_set_dash

[Jean-Louis Dupond]

The version in Yakkety already includes this patch.
https://cgit.freedesktop.org/poppler/poppler/commit/?id=7d8dfb09d2b9d69d4e80838ce58fdbd091bce7ec

Was committed pre 0.43.

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

Title:
  Evince crashes with _cairo_gstate_set_dash

Status in poppler package in Ubuntu:
  New

Bug description:
  When opening the following PDF in Evince 
(https://dl.ubnt.com/guides/edgemax/EdgeSwitch_ES-48_QSG.pdf), it crashes with 
the following backtrace:
  Thread 7 "EvJobScheduler" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fb17ef8d700 (LWP 11109)]
  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
  542   ../../../../src/cairo-gstate.c: Bestand of map bestaat niet.
  (gdb) bt full
  #0  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
  dash_total = 0
  on_total = 0
  off_total = 0
  i = 0
  j = 0
  #1  0x7fb19c15fa92 in cairo_set_dash (cr=0x5615ded8dc70, 
dashes=, num_dashes=, offset=) at 
../../../../src/cairo.c:1080
  status = 

  
  Upstream seems to have fixed this already:
  https://bugs.freedesktop.org/show_bug.cgi?id=62905

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

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

[Touch-packages] [Bug 1610714] Re: Evince crashes with _cairo_gstate_set_dash

[Jean-Louis Dupond]

And for SRU:

[Impact]

Evince crashes while opening some PDF's.

[Test Case]

Open the PDF https://dl.ubnt.com/guides/edgemax/EdgeSwitch_ES-48_QSG.pdf and 
scroll to page 7 for example.
This crashes every time.

[Regression Potential]

Should be safe. Patch also got included upstream.

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

Title:
  Evince crashes with _cairo_gstate_set_dash

Status in poppler package in Ubuntu:
  New

Bug description:
  When opening the following PDF in Evince 
(https://dl.ubnt.com/guides/edgemax/EdgeSwitch_ES-48_QSG.pdf), it crashes with 
the following backtrace:
  Thread 7 "EvJobScheduler" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fb17ef8d700 (LWP 11109)]
  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
  542   ../../../../src/cairo-gstate.c: Bestand of map bestaat niet.
  (gdb) bt full
  #0  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
  dash_total = 0
  on_total = 0
  off_total = 0
  i = 0
  j = 0
  #1  0x7fb19c15fa92 in cairo_set_dash (cr=0x5615ded8dc70, 
dashes=, num_dashes=, offset=) at 
../../../../src/cairo.c:1080
  status = 

  
  Upstream seems to have fixed this already:
  https://bugs.freedesktop.org/show_bug.cgi?id=62905

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

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

[Touch-packages] [Bug 1580537] Re: LibreOffice with ambiance theme and breeze icon style is unusable

[fprietog]

@Björn Michaelsen; the fixed pic you posted looks very nice. Hope the
fix reach the repo soon.

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

Title:
  LibreOffice with ambiance theme and breeze icon style is unusable

Status in libreoffice package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Fix Committed

Bug description:
  Until today i didn't use LibreOffice on Ubuntu 16.04. I opened it
  today and i see menu/icon bar totally unusable with Ambiance theme and
  default Breeze style. (image attached)

  The version installed is 5.1.2-0ubuntu1.

  I did upgrade from 14.04 to 16.04 with some issues.

  Changing from Breeze to Human is usable but fugly.

  No issue with Radiance theme.

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

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

[Touch-packages] [Bug 1610698] Re: password warning when numlock is on

[Gunnar Hjalmarsson]

Is this bug #1526322?

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

Title:
  password warning when numlock is on

Status in lightdm package in Ubuntu:
  New

Bug description:
  When logging into a gui session or unlocking the screen of an existing
  session, the password field displays  a warning notification when
  numlock is on.  This should be reversed, as the non-numeric functions
  of the numpad are irrelevant at that point to the user(home/end,
  pageup/pagedown), while the numeric input(0-9) are potentially quite
  important to the user.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug  7 10:53:51 2016
  InstallationDate: Installed on 2014-12-11 (605 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (3 days ago)

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

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

[Touch-packages] [Bug 1610543] Re: After upgrading to 16.04, greeter does not handle double screen anymore

[A. Scheuer]

OK, a few additional info: on 4 tries, I had only 1 unexpected sleep,
and only 1 display of the greeter (with bad dimensions). Moreover, each
time I disconnect and loose the display (black screen with only cursor),
the fan starts to work.

I will check whether the load increases (with a top in TTY 1), and which
process is on top, and send you the results tomorrow.

Good evening.

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

Title:
  After upgrading to 16.04, greeter does not handle double screen
  anymore

Status in lightdm package in Ubuntu:
  New

Bug description:
  Hello.

  I upgraded my laptop from 14.04 to 16.04 (Ubuntu 16.04.1 LTS) a few
  days ago. Since then, the login screen doe not appear anymore when I
  have a dual monitor (either connected to VGA port or docked via VGA or
  HDMI), both screen are black, showing only the cursor.

  When I switch back to one monitor (disconnecting the VGA monitor or
  undocking), the laptop turns to sleep (?!?). After waking it up, I got
  the screen, can login, connect back the second monitor and activate it
  (with xrandr).

  If I connect the second monitor when the computer sleeps, and wake it
  up, I then have the display, but without the login window (it appears
  as soon as I disconnect the monitor).

  The software lightdm is up to date (1.18.2-0ubuntu1).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Aug  6 16:50:11 2016
  InstallationDate: Installed on 2013-07-29 (1104 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (6 days ago)

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

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

[Touch-packages] [Bug 1610543] Re: After upgrading to 16.04, greeter does not handle double screen anymore

[A. Scheuer]

Hello.

There has been a few changes (even though I don't know which update
solved these problems): about this bug, the main change is that the
laptop doesn't turn to sleep anymore when I undock it.

I however still have the main problem.  I can add that everything is OK
after the first login: if I disconnect, the greeter is displayed (with
bad dimensions - right of the screen is missing).

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

Title:
  After upgrading to 16.04, greeter does not handle double screen
  anymore

Status in lightdm package in Ubuntu:
  New

Bug description:
  Hello.

  I upgraded my laptop from 14.04 to 16.04 (Ubuntu 16.04.1 LTS) a few
  days ago. Since then, the login screen doe not appear anymore when I
  have a dual monitor (either connected to VGA port or docked via VGA or
  HDMI), both screen are black, showing only the cursor.

  When I switch back to one monitor (disconnecting the VGA monitor or
  undocking), the laptop turns to sleep (?!?). After waking it up, I got
  the screen, can login, connect back the second monitor and activate it
  (with xrandr).

  If I connect the second monitor when the computer sleeps, and wake it
  up, I then have the display, but without the login window (it appears
  as soon as I disconnect the monitor).

  The software lightdm is up to date (1.18.2-0ubuntu1).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Aug  6 16:50:11 2016
  InstallationDate: Installed on 2013-07-29 (1104 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (6 days ago)

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

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

[Touch-packages] [Bug 1528735] Re: Suspend reboots every second time on Lenovo G50-45

[Brad]

This thread is indicating that it is not specific to Lenovo machines, as I 
suspected:
https://forums.linuxmint.com/viewtopic.php?t=212044

Re: Crash upon suspend. Message: Boot Script Table modified.
Postby syeager » Mon Jun 13, 2016 2:27 am

"I have been installing different linux distros on my HP Envy and all
have the same problem: sleep once, fine; sleep again, and it will not
recover with a black screen, where upon on reboot (the only option with
a hardware reboot) i get the error message 'boot script table modified'.
Not only does this happen to linux distros, i have had it happen to
windows 10 clean install. I just installed windows 10 to an ssd and
added bodhi linux as a uefi boot. Just put windows to sleep (for the
first time after rebooting) after playing an old XP game (Neverwinter
Nights) and it gave the same problem. Does that help you analyze it? I
can test theories, if anyone has one.

OK, i tried ubuntu, thinking that i heard they paid microsoft for uefi,
so maybe it would handle awaking from sleep better. No it doesn't. Then
i tried robolinux, which is a debian release but also booted up with the
cd with a legacy boot instead of uefi booting from the cd, and it can
sleep just fine. i am assuming it is the legacy boot. Thoughts?"

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

Title:
  Suspend reboots every second time on Lenovo G50-45

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1528735/+subscriptions

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

[Touch-packages] [Bug 1605813] Re: lock screen freezes while trying to wake from suspend

[A. Scheuer]

Wow, that's a fast correction: for my laptop, the bug appeared
yesterday, and was solved today!  I am back to only one button "sleep"
(under the three "logout", "reboot" or "shutdown" - sorry if the labels
are not correct, these are raw translation of the French labels I get)
which works, instead of the two ("sleep" and "deep sleep") which froze
the laptop.

Cool, thanks for the help.

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

Title:
  lock screen freezes while trying to wake from suspend

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Background:

  I am running a fully updated 16.04.1 installation of Ubuntu using open
  source nVidia drivers.  When I press the power button on my PC to wake
  the computer from suspend, the login screen appears and freezes.  The
  box around my username becomes somewhat opaque and no text box that
  would allow me to enter my password appears.  I have tried this many
  times, and it always locks up in the same way.

  Steps taken after issue occurs:

  I have found, however, that the system is not completely locked up.  I
  can use CTL + ALT + F2 to switch to TTY2.  From there I can login and
  restart the computer without issue.

  I also tried restarting lightdm via sudo service lightdm restart.
  When I tried this and switched back to the GUI, the login screen was
  loaded, and I could type my password.  Once the login screen
  disappeared, one of my monitors (dual-monitor setup) switched to my
  user account's wallpaper, and then the system locked up.  I had to
  perform a hard restart.

  Workaround:

  I have found that using the proprietary 361.42 drivers provides a work
  around for this issue.  When using the proprietary drivers, the
  computer resumes from suspend without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 22 20:53:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-08 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1610720] [NEW] Can't mount partitions in fstab after 14.04->16.04 upgrade

[Jiri Wichern]

Public bug reported:

This is either a problem with fsck/mount, the Ubuntu distribution
upgrade process or systemd. I'm not yet sure which.

I had a hell of a time trying to upgrade from 14.04 to 16.04. I managed
to get through after several single-user sessions in rescue-mode
(machine was not able to boot to multi-user level at this state and I
couldn't, then, find the problem), installing all packages until 'dpkg
--audit' gave no more problems and apt-get upgrade had nothing more to
add. I was still unable to boot using systemd but upstart did work.

Analyzing the boot journal with journalctl -xb I saw various disks
couldn't be fsck'ed or mounted. When I tried to mount one of them
manually in rescue mode I got:

root@Diamond:/etc# mount /media/sda6
mount: can't find UUID=28aa6c430061e3ca

More research:

root@Diamond:/etc# blkid /dev/sda6
/dev/sda6: LABEL="Swap" UUID="28AA6C430061E3CA" TYPE="ntfs" 
PARTUUID="000c76d0-06"
root@Diamond:/etc# cat fstab | grep sda6
# /dev/sda6
UUID=28aa6c430061e3ca   /media/sda6 ntfsdefaults,umask=007,gid=46   
01

Note the UUID as it seems booting in systemd requires fstab's UUIDs to be case 
sensitive. When booting using upstart, this is not the case. When you put an 
UUID with upper case letters in fstab, the problem (in a session booted using 
systemd) goes away.
I never manually edited /etc/fstab on this machine before so somehow Ubuntu 
once generated UUIDs with lower-case letters when I first installed it, or 
during an upgrade. However, now it needs to be upper-case.

Additional information:
root@Diamond:/etc# lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
root@Diamond:/etc# apt-cache policy util-linux
util-linux:
  Installed: 2.27.1-6ubuntu3.1
  Candidate: 2.27.1-6ubuntu3.1
  Version table:
 *** 2.27.1-6ubuntu3.1 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.27.1-6ubuntu3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mount 2.27.1-6ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug  7 19:36:58 2016
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Can't mount partitions in fstab after 14.04->16.04 upgrade

Status in util-linux package in Ubuntu:
  New

Bug description:
  This is either a problem with fsck/mount, the Ubuntu distribution
  upgrade process or systemd. I'm not yet sure which.

  I had a hell of a time trying to upgrade from 14.04 to 16.04. I
  managed to get through after several single-user sessions in rescue-
  mode (machine was not able to boot to multi-user level at this state
  and I couldn't, then, find the problem), installing all packages until
  'dpkg --audit' gave no more problems and apt-get upgrade had nothing
  more to add. I was still unable to boot using systemd but upstart did
  work.

  Analyzing the boot journal with journalctl -xb I saw various disks
  couldn't be fsck'ed or mounted. When I tried to mount one of them
  manually in rescue mode I got:

  root@Diamond:/etc# mount /media/sda6
  mount: can't find UUID=28aa6c430061e3ca

  More research:

  root@Diamond:/etc# blkid /dev/sda6
  /dev/sda6: LABEL="Swap" UUID="28AA6C430061E3CA" TYPE="ntfs" 
PARTUUID="000c76d0-06"
  root@Diamond:/etc# cat fstab | grep sda6
  # /dev/sda6
  UUID=28aa6c430061e3ca /media/sda6 ntfsdefaults,umask=007,gid=46   
01

  Note the UUID as it seems booting in systemd requires fstab's UUIDs to be 
case sensitive. When booting using upstart, this is not the case. When you put 
an UUID with upper case letters in fstab, the problem (in a session booted 
using systemd) goes away.
  I never manually edited /etc/fstab on this machine before so somehow Ubuntu 
once generated UUIDs with lower-case letters when I first installed it, or 
during an upgrade. However, now it needs to be upper-case.

  Additional information:
  root@Diamond:/etc# lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  root@Diamond:/etc# apt-cache policy util-linux
  util-linux:
Installed: 2.27.1-6ubuntu3.1
Candidate: 2.27.1-6ubuntu3.1
Version table:
   *** 2.27.1-6ubuntu3.1 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.27.1-6ubuntu3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mount 

[Touch-packages] [Bug 1528735] Re: Suspend reboots every second time on Lenovo G50-45

[Brad]

I'm seeing this problem on various versions of Linux Mint from v17.3
Cinnamon with kernel 3.19 to v18 Mate with kernel 4.4 or 4.7.  Apart
from the OP problem description of symptoms with yellow text console
warning message, I have suspicion that this problem is also causing the
more severe problem with kernel 4.7 that even the first suspend/resume
results in a system lockup/freeze upon attempting to resume.  I think it
may be important to first determine if this problem is specific to a
machine and it's BIOS version. In this case I believe we are talking
mostly, if not only, about Lenovo machines (like mine).  I think it is
possible this is a result of a BIOS update by Lenovo to fix a security
hole described below.  That said, my notebook's info is below. Note the
BIOS version and date.  Also note that the security hole (UEFI
implementations do not properly secure the EFI S3 Resume Boot Path boot
script) is not specific to Lenovo and MANY vendors would have had to
make a similar patch - which might explain suspend/resume problems
reported by various people with other notebook brands. More info can be
found on my LM formum thread:
https://forums.linuxmint.com/viewtopic.php?f=46=227168#p1199128

System:Host: G50 Kernel: 4.7.0-040700-generic x86_64 (64 bit gcc: 5.4.0)
   Desktop: MATE 1.14.1 (Gtk 3.18.9-1ubuntu3.1)
   Distro: Linux Mint 18 Sarah
Machine:   System: LENOVO product: 80E3 v: Lenovo G50-45
   Mobo: LENOVO model: Lancer 5B2 v: 31900058 STD
   Bios: LENOVO v: A2CN38WW(V2.06) date: 07/15/2015

Lenovo Advisory:
https://support.lenovo.com/br/en/product_security/s3_boot_protect

Vulnerability Note VU#976132 http://www.kb.cert.org/vuls/id/976132
UEFI implementations do not properly secure the EFI S3 Resume Boot Path boot 
script

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

Title:
  Suspend reboots every second time on Lenovo G50-45

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1528735/+subscriptions

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

[Touch-packages] [Bug 1610714] Re: Evince crashes with _cairo_gstate_set_dash

[Jean-Louis Dupond]

The following debdiff fixes the issue.

** Patch added: "fix.patch"
   
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1610714/+attachment/4716081/+files/fix.patch

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

Title:
  Evince crashes with _cairo_gstate_set_dash

Status in poppler package in Ubuntu:
  New

Bug description:
  When opening the following PDF in Evince 
(https://dl.ubnt.com/guides/edgemax/EdgeSwitch_ES-48_QSG.pdf), it crashes with 
the following backtrace:
  Thread 7 "EvJobScheduler" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fb17ef8d700 (LWP 11109)]
  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
  542   ../../../../src/cairo-gstate.c: Bestand of map bestaat niet.
  (gdb) bt full
  #0  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
  dash_total = 0
  on_total = 0
  off_total = 0
  i = 0
  j = 0
  #1  0x7fb19c15fa92 in cairo_set_dash (cr=0x5615ded8dc70, 
dashes=, num_dashes=, offset=) at 
../../../../src/cairo.c:1080
  status = 

  
  Upstream seems to have fixed this already:
  https://bugs.freedesktop.org/show_bug.cgi?id=62905

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

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

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

[mindentropy]

This bug is still present in Xenial. I have 4 different machines which
are affected by this bug.

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  This bug is resolved.  Do not follow up to this bug.  Shutdown bugs
  are specific to the software installed and its configuration.  If you
  are experiencing a shutdown hang, please file a separate bug report
  and follow the debugging instructions described in the "Debugging
  boot/shutdown problems" section of
  /usr/share/doc/systemd/README.Debian.gz to check if there are any
  hanging jobs at shutdown. Capturing a screen photo of "journalctl -b"
  in the rescue shell might be enlightening.

  [Original report]
  I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth 
shutdown screen.  Hitting esc to reveal the console showed a normal set of 
shutdown messages, ending with 'Reached target Shutdown' (paraphrased from 
memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1610714] [NEW] Evince crashes with _cairo_gstate_set_dash

[Jean-Louis Dupond]

Public bug reported:

When opening the following PDF in Evince 
(https://dl.ubnt.com/guides/edgemax/EdgeSwitch_ES-48_QSG.pdf), it crashes with 
the following backtrace:
Thread 7 "EvJobScheduler" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fb17ef8d700 (LWP 11109)]
0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, dash=0x0, 
num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
542 ../../../../src/cairo-gstate.c: Bestand of map bestaat niet.
(gdb) bt full
#0  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
dash_total = 0
on_total = 0
off_total = 0
i = 0
j = 0
#1  0x7fb19c15fa92 in cairo_set_dash (cr=0x5615ded8dc70, dashes=, num_dashes=, offset=) at 
../../../../src/cairo.c:1080
status = 


Upstream seems to have fixed this already:
https://bugs.freedesktop.org/show_bug.cgi?id=62905

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

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

Title:
  Evince crashes with _cairo_gstate_set_dash

Status in poppler package in Ubuntu:
  New

Bug description:
  When opening the following PDF in Evince 
(https://dl.ubnt.com/guides/edgemax/EdgeSwitch_ES-48_QSG.pdf), it crashes with 
the following backtrace:
  Thread 7 "EvJobScheduler" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fb17ef8d700 (LWP 11109)]
  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
  542   ../../../../src/cairo-gstate.c: Bestand of map bestaat niet.
  (gdb) bt full
  #0  0x7fb19c16c7b1 in _cairo_gstate_set_dash (gstate=0x7fb16c538d80, 
dash=0x0, num_dashes=2, offset=6.9366816791018826e-310) at 
../../../../src/cairo-gstate.c:542
  dash_total = 0
  on_total = 0
  off_total = 0
  i = 0
  j = 0
  #1  0x7fb19c15fa92 in cairo_set_dash (cr=0x5615ded8dc70, 
dashes=, num_dashes=, offset=) at 
../../../../src/cairo.c:1080
  status = 

  
  Upstream seems to have fixed this already:
  https://bugs.freedesktop.org/show_bug.cgi?id=62905

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

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

[Touch-packages] [Bug 1288786] Re: pkexec does not launch graphical authentication

[pintubigfoot]

Same happening to me too after today's update

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

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

Title:
  pkexec does not launch graphical authentication

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Installed Trusty Tahr Lubuntu Beta1 version and added xubuntu desktop.  In 
buth desktops, I tried to launch synaptic to install some packages.  If I try 
to launch from menu, nothing seems to happen.  From a terminal, I ran
pkexec "/usr/sbin/synaptic"
   and saw that it asks for password in the terminal window, instead of popping 
up an authentication window like previous Ubuntu version did.  That was why I 
saw no authentication request when launching from menu..  I have a 
workaround)launching from Terminal window), but this should be fixed before 
release.

  ralph@minnie:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)"
  ralph@minnie:~$ pkexec --version
  pkexec version 0.105

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1288786/+subscriptions

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

[Touch-packages] [Bug 1610697] Re: package linux-image-extra-4.4.0-34-generic 4.4.0-34.53 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  wtf ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manzet 3268 F pulseaudio
  Date: Sun Aug  7 17:21:36 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=d2f327fa-110e-4968-aad7-87b542633da0
  InstallationDate: Installed on 2013-12-17 (963 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: Acer NC-E1-571G-53234
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-93-generic 
root=UUID=c049d44c-a3c3-452d-8807-a80599609127 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-34-generic 4.4.0-34.53 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (0 days ago)
  dmi.bios.date: 07/02/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.17
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: EA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.17
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.17:bd07/02/2013:svnAcer:pnNC-E1-571G-53234:pvrV2.17:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.17:
  dmi.product.name: NC-E1-571G-53234
  dmi.product.version: V2.17
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1610698] [NEW] password warning when numlock is on

[Ian Nicholson]

Public bug reported:

When logging into a gui session or unlocking the screen of an existing
session, the password field displays  a warning notification when
numlock is on.  This should be reversed, as the non-numeric functions of
the numpad are irrelevant at that point to the user(home/end,
pageup/pagedown), while the numeric input(0-9) are potentially quite
important to the user.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug  7 10:53:51 2016
InstallationDate: Installed on 2014-12-11 (605 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210)
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-08-04 (3 days ago)

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

Title:
  password warning when numlock is on

Status in lightdm package in Ubuntu:
  New

Bug description:
  When logging into a gui session or unlocking the screen of an existing
  session, the password field displays  a warning notification when
  numlock is on.  This should be reversed, as the non-numeric functions
  of the numpad are irrelevant at that point to the user(home/end,
  pageup/pagedown), while the numeric input(0-9) are potentially quite
  important to the user.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug  7 10:53:51 2016
  InstallationDate: Installed on 2014-12-11 (605 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (3 days ago)

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

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

[Touch-packages] [Bug 1610697] [NEW] package linux-image-extra-4.4.0-34-generic 4.4.0-34.53 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Andrea Bulgarelli]

Public bug reported:

wtf ?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-34-generic 4.4.0-34.53
ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
Uname: Linux 3.13.0-93-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  manzet 3268 F pulseaudio
Date: Sun Aug  7 17:21:36 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=d2f327fa-110e-4968-aad7-87b542633da0
InstallationDate: Installed on 2013-12-17 (963 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
MachineType: Acer NC-E1-571G-53234
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-93-generic 
root=UUID=c049d44c-a3c3-452d-8807-a80599609127 ro recovery nomodeset
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-34-generic 4.4.0-34.53 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to xenial on 2016-08-07 (0 days ago)
dmi.bios.date: 07/02/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.17
dmi.board.asset.tag: No Asset Tag
dmi.board.name: EA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.17
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.17:bd07/02/2013:svnAcer:pnNC-E1-571G-53234:pvrV2.17:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.17:
dmi.product.name: NC-E1-571G-53234
dmi.product.version: V2.17
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-package package-from-proposed xenial

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  wtf ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manzet 3268 F pulseaudio
  Date: Sun Aug  7 17:21:36 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=d2f327fa-110e-4968-aad7-87b542633da0
  InstallationDate: Installed on 2013-12-17 (963 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: Acer NC-E1-571G-53234
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-93-generic 
root=UUID=c049d44c-a3c3-452d-8807-a80599609127 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-34-generic 4.4.0-34.53 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (0 days ago)
  dmi.bios.date: 07/02/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.17
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: EA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.17
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.17:bd07/02/2013:svnAcer:pnNC-E1-571G-53234:pvrV2.17:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.17:
  dmi.product.name: NC-E1-571G-53234
  dmi.product.version: V2.17
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1610684] [NEW] ubuntu 16.04 won't shutdown : Reached target Shutdown[ok] also ubuntu 14.04 won't shut down : killing all procces [fail]

[Ali Zeynali]

Public bug reported:


I had ubuntu 14.04 (DELL laptop INSPIRON N-4110 ) shutdown and reboot
worked correctly and without any problem but after a long time I wasn't
able to reboot or shutdown my machine.

and that was the log message was shown by pressing Esc during shutdown:

killing all procceses  [fail]

and I tried all the tips I saw in askubuntu and others(like changing the
grub and shutdown - h now etc none of them have worked ! )

then I clean installed ubuntu 16.04 (current) but issue is not going to
solve.

now the log shows:

[ok] Reached target Shutdown 
[135.486156] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0X0 action 0x6 frozen
[135.846776] ata2.00: cmd a0/00: 00:00:00:00/00:00:00:00:00/s0 tag 4 pio 16392 
in
[135.846776] get event status notification 4a  01 00 10 00 00 00 00 00res 
40/00:00:00:00
[135.848020] ata2.00:status: { DRDY }
[141.182090] ata2.00 revalidation failed  (errno=-5)

I checked bug #1464917 and did instructions also but nothings changed .

UPDATE:

after updating to 16.04.1 (boot install) Ubuntu will shutdown if i do it
fast when OS is coming up but after a while it's not going to power off
again and Esc key won't work and does not show me log any more

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


** Tags: shutdown systemd

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

Title:
  ubuntu 16.04 won't shutdown : Reached target Shutdown[ok] also ubuntu
  14.04 won't shut down : killing all procces [fail]

Status in systemd package in Ubuntu:
  New

Bug description:

  I had ubuntu 14.04 (DELL laptop INSPIRON N-4110 ) shutdown and reboot
  worked correctly and without any problem but after a long time I
  wasn't able to reboot or shutdown my machine.

  and that was the log message was shown by pressing Esc during
  shutdown:

  killing all procceses  [fail]

  and I tried all the tips I saw in askubuntu and others(like changing
  the grub and shutdown - h now etc none of them have worked ! )

  then I clean installed ubuntu 16.04 (current) but issue is not going
  to solve.

  now the log shows:

  [ok] Reached target Shutdown 
  [135.486156] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0X0 action 0x6 frozen
  [135.846776] ata2.00: cmd a0/00: 00:00:00:00/00:00:00:00:00/s0 tag 4 pio 
16392 in
  [135.846776] get event status notification 4a  01 00 10 00 00 00 00 00res 
40/00:00:00:00
  [135.848020] ata2.00:status: { DRDY }
  [141.182090] ata2.00 revalidation failed  (errno=-5)

  I checked bug #1464917 and did instructions also but nothings changed
  .

  UPDATE:

  after updating to 16.04.1 (boot install) Ubuntu will shutdown if i do
  it fast when OS is coming up but after a while it's not going to power
  off again and Esc key won't work and does not show me log any more

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

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

[Touch-packages] [Bug 1610619] Re: Xscreen saver and lightdm prevent use of operating system (total lockout) after guest session screen lock

[Gunnar Hjalmarsson]

Started my Xubuntu system, and noticed that xscreensaver is not
installed by default. The locking mechanism seems to be provided by
light-locker. Also, xscreensaver's lock feature seems to be disabled by
default. Hence it's not clear to me how this issue can be reproduced.
Please clarify.

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

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

Title:
  Xscreen saver and lightdm prevent use of operating system (total
  lockout) after guest session screen lock

Status in xscreensaver:
  New
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce bug:

  1)  Install xubuntu or mint xfce
  2)  download and set lightdm as desktop manager
  3)  sign in to a guest session and either close your laptop lid or allow 
timeout to start screen lock

  Why this is a bug:

  xscreensaver will not accept a blank/null password, and with a
  blank/null password assigned to the guest session, the xscreensaver
  client will not allow the user to continue their session or login as a
  new user (because you cannot login as a new user as xscreensaver does
  not support lightdm for this feature.

  Why this is severe:

  when xscreensaver locks the guest user out of their session, all other
  users are similarly locked out.  Being so locked out, the computer
  most be hard-reset/rebooted and any documents and processes not saved
  prior to the guest session being logged in is lost.

  Why this is a lightdm bug:

  Because lightdm is not setting the gconf setting to disable the lock
  screen feature for guest sessions

  Why this is a xscreensaver bug:

  xscreensaver does not support any dm other than mdm

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

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

[Touch-packages] [Bug 1610666] [NEW] Mouse cursor moves choppy/doesn't update its position as it should

[Mohit Tokas]

Public bug reported:

Output of "lsb_release -rd" :

Description:Ubuntu Xenial Xerus (development branch)
Release:16.04

Output of "apt-cache policy xorg" :

xorg:
  Installed: 1:7.7+13ubuntu3
  Candidate: 1:7.7+13ubuntu3
  Version table:
 *** 1:7.7+13ubuntu3 500
500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

Q. What I expected to happen?
A. The mouse would run smoothly as it does run in windows.

Q. What happened instead?
A. The mouse lags moves choppy/doesn't update its position as it should

Additional Information :

Output of "xinput --list --short"

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ E-Signal USB Gaming Mouse id=10   [slave  pointer  (2)]
⎜   ↳ E-Signal USB Gaming Mouse id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Microsoft® LifeCam HD-3000id=9[slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=12   [slave  keyboard (3)]

Output of "xinput --list-props 11"

Device 'E-Signal USB Gaming Mouse':
Device Enabled (133):   1
Coordinate Transformation Matrix (135): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (259): 0
Device Accel Constant Deceleration (260):   1.00
Device Accel Adaptive Deceleration (261):   1.00
Device Accel Velocity Scaling (262):10.00
Device Product ID (251):1241, 41132
Device Node (252):  "/dev/input/event4"
Evdev Axis Inversion (263): 0, 0
Evdev Axes Swap (265):  0
Axis Labels (266):  "Rel X" (143), "Rel Y" (144), "Rel Horiz Wheel" 
(257), "Rel Vert Wheel" (258)
Button Labels (267):"Button Left" (136), "Button Middle" (137), 
"Button Right" (138), "Button Wheel Up" (139), "Button Wheel Down" (140), 
"Button Horiz Wheel Left" (141), "Button Horiz Wheel Right" (142), "Button 
Side" (255), "Button Extra" (256), "Button Unknown" (254), "Button Unknown" 
(254), "Button Unknown" (254), "Button Unknown" (254)
Evdev Scrolling Distance (268): 1, 1, 1
Evdev Middle Button Emulation (269):0
Evdev Middle Button Timeout (270):  50
Evdev Third Button Emulation (271): 0
Evdev Third Button Emulation Timeout (272): 1000
Evdev Third Button Emulation Button (273):  3
Evdev Third Button Emulation Threshold (274):   20
Evdev Wheel Emulation (275):0
Evdev Wheel Emulation Axes (276):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (277):10
Evdev Wheel Emulation Timeout (278):200
Evdev Wheel Emulation Button (279): 4
Evdev Drag Lock Buttons (280):  0

Output of "lsusb"

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 0bc2:3321 Seagate RSS LLC 
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 04d9:a0ac Holtek Semiconductor, Inc. 
Bus 001 Device 003: ID 045e:0779 Microsoft Corp. LifeCam HD-3000
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Note : Holtek Semiconductor, Inc. is my mouse

Also found this in dmesg :

[  292.597380] usb 1-1.4: new full-speed USB device number 5 using ehci-pci
[  293.941408] usb 1-1.4: New USB device found, idVendor=04d9, idProduct=a0ac
[  293.941413] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[  293.941416] usb 1-1.4: Product: USB Gaming Mouse
[  293.941418] usb 1-1.4: Manufacturer: E-Signal
[  294.241702] input: E-Signal USB Gaming Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:04D9:A0AC.0004/input/input16
[  294.242160] hid-generic 0003:04D9:A0AC.0004: input,hidraw0: USB HID v1.10 
Mouse [E-Signal USB Gaming Mouse] on usb-:00:1a.0-1.4/input0
[  294.841559] input: E-Signal USB Gaming Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:04D9:A0AC.0005/input/input17
[  294.897825] hid-generic 0003:04D9:A0AC.0005: input,hiddev0,hidraw1: USB HID 
v1.10 Keyboard [E-Signal USB Gaming Mouse] on 

[Touch-packages] [Bug 1604010] Re: sntp missing

[Bug Watch Updater]

** Changed in: ntp (Debian)
   Status: Unknown => New

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

Title:
  sntp missing

Status in ntp package in Ubuntu:
  Triaged
Status in ntp package in Debian:
  New

Bug description:
  In Ubuntu 16.04, the binary file /usr/bin/sntp is missing from the
  package ntp. The associated man page /usr/share/man/man1/sntp.1.gz is
  still included.

  How to reproduce:

  $ sudo apt-get install ntp
  $ dpkg-query -L ntp | grep sntp
  /usr/share/man/man1/sntp.1.gz

  Expected result:

  /usr/bin/sntp was included in Ubuntu 14.04:

  $ dpkg-query -L ntp | grep sntp
  /usr/bin/sntp
  /usr/share/man/man1/sntp.1.gz

  The sntp program remains a very useful tool for interactively testing
  on the command line the offset of the local clock to a remote NTP
  server (like "ntpdate -qu [ntp-server]" previously). It should be
  included in the same package as its man page.

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

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

[Touch-packages] [Bug 1470655] Re: Update to PackageKit 1.0

[Colin Watson]

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

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

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

Title:
  Update to PackageKit 1.0

Status in click package in Ubuntu:
  Triaged
Status in packagekit package in Ubuntu:
  Fix Committed

Bug description:
  Update to 1.0

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

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

[Touch-packages] [Bug 1610010] Re: [Scopes] ⨂ icon in search field looks jagged

[Launchpad Bug Tracker]

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

** Changed in: unity-scopes-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Scopes] ⨂ icon in search field looks jagged

Status in Ubuntu UX:
  New
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  ⨂ icon in the search field of a scope is not smooth.
  Device: E5, stable channel, OTA-12

  Screenshot:
  https://launchpadlibrarian.net/277165796/screenshot20160803_000859160.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1610010/+subscriptions

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

[Touch-packages] [Bug 1610657] [NEW] [Satellite P205, Realtek ALC268, Speaker, Internal] No sound at all

[Arun Godwin Vadlar]

Public bug reported:

Unable to hear the sound. I have dual boot and able to hear sound when
I'm on windows 10 but in Ubuntu 16.04 unable to hear sound

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   arun   3222 F...m pulseaudio
 /dev/snd/controlC0:  arun   3222 F pulseaudio
CurrentDesktop: Unity
Date: Sun Aug  7 14:49:04 2016
InstallationDate: Installed on 2016-07-24 (14 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   arun   3222 F...m pulseaudio
 /dev/snd/pcmC0D0p:   arun   3222 F...m pulseaudio
 /dev/snd/controlC0:  arun   3222 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Satellite P205, Realtek ALC268, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V2.50
dmi.board.name: ISRAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvrV2.50:bd06/11/2008:svnTOSHIBA:pnSatelliteP205:pvrPSPB3U-06700L:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite P205
dmi.product.version: PSPB3U-06700L
dmi.sys.vendor: TOSHIBA

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


** Tags: apport-bug i386 xenial

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

Title:
  [Satellite P205, Realtek ALC268, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Unable to hear the sound. I have dual boot and able to hear sound when
  I'm on windows 10 but in Ubuntu 16.04 unable to hear sound

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   arun   3222 F...m pulseaudio
   /dev/snd/controlC0:  arun   3222 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Aug  7 14:49:04 2016
  InstallationDate: Installed on 2016-07-24 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   arun   3222 F...m pulseaudio
   /dev/snd/pcmC0D0p:   arun   3222 F...m pulseaudio
   /dev/snd/controlC0:  arun   3222 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite P205, Realtek ALC268, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V2.50
  dmi.board.name: ISRAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV2.50:bd06/11/2008:svnTOSHIBA:pnSatelliteP205:pvrPSPB3U-06700L:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite P205
  dmi.product.version: PSPB3U-06700L
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Terra Nova]

The fix has been merged into systemd via:
https://github.com/systemd/systemd/pull/3676

It appears this was not a libvirt problem and the systemd 'invalid' tag
is incorrect.

Has anyone already created a systemd issue to get it updated with this
patch (I didn't find any)?

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

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

Status in libvirt package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

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

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

[Touch-packages] [Bug 1610653] Re: package python3 3.4.0-0ubuntu2 failed to install/upgrade: pre-dependency problem - not installing python3

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3 3.4.0-0ubuntu2 failed to install/upgrade: pre-
  dependency problem - not installing python3

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3 3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug  7 10:04:59 2016
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-08-10 (362 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: python3-defaults
  Title: package python3 3.4.0-0ubuntu2 failed to install/upgrade: 
pre-dependency problem - not installing python3
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1610653/+subscriptions

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

[Touch-packages] [Bug 1610653] [NEW] package python3 3.4.0-0ubuntu2 failed to install/upgrade: pre-dependency problem - not installing python3

[Mickael Brier]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python3 3.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Aug  7 10:04:59 2016
ErrorMessage: pre-dependency problem - not installing python3
InstallationDate: Installed on 2015-08-10 (362 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: python3-defaults
Title: package python3 3.4.0-0ubuntu2 failed to install/upgrade: pre-dependency 
problem - not installing python3
UpgradeStatus: Upgraded to xenial on 2016-08-07 (0 days ago)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package python3 3.4.0-0ubuntu2 failed to install/upgrade: pre-
  dependency problem - not installing python3

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3 3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug  7 10:04:59 2016
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-08-10 (362 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: python3-defaults
  Title: package python3 3.4.0-0ubuntu2 failed to install/upgrade: 
pre-dependency problem - not installing python3
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1610653/+subscriptions

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[vittorio]

missing asus support to linux, maybe it always will..
by the time I'm using bluetooth speakers.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

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

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1558753] Re: AppArmor denying CUPS authentication against PAM on AD joined system (SSSD-based)

[James Gauci]

Hi Tyler, we are experiencing this issue with a similar production
environment.

Can I submit our configurations to help with investigating this issue
further?

Please let me know.

Regards,

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

Title:
  AppArmor denying CUPS authentication against PAM on AD joined system
  (SSSD-based)

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  System information:

  OS: Ubuntu 14.04.4 LTS
  AppArmor 2.8.95~2430-0ubuntu5.3
  SSSD: 1.11.5-1ubuntu3
  CUPS: 1.7.2-0ubuntu1.7

  I believe this is a bug that belongs here rather than with SSSD or
  CUPS package; apologies if incorrect.

  The problem arises when attempting to grant non-local end user
  accounts (e.g, domain accounts) extra permissions to modify portions
  of the Admin page, so that they can add/remove printers themselves for
  instance.  There's a few ways to do this, obviously, such as adding
  extra groups or users to the SystemGroup definition in /etc/cups-
  files, or adding "Require valid-user" to the 
  location in /etc/cupsd.conf.

  Attempting to alter SystemGroup by adding "Domain Users", or by adding
  the "Require valid-user" statement to the /admin location definition
  causes the CUPS web page (http://localhost:631) to reject all network
  users credentials.  The valid-user option will cause CUPS to accept
  local user account credentials regardless of whether they have root
  access or are part of lpadmin.  Interestingly, both
  BasicAuthentication and Kerberos (Negotiate) authentication modes
  cause network accounts to be rejected .

  Digging through logs, it becomes apparent that CUPS appears to rely on PAM 
for authentication - error messages appear in /var/log/auth.log like so:
  Mar 15 07:53:41  cupsd: pam_unix(cups:auth): authentication 
failure; logname= uid=0 euid=0 tty=cups ruser= rhost=localhost user=
  Mar 15 07:53L31  cupsd: pam_sss(cups:auth): Request to sssd 
failed.  Permission denied

  The first line is expected, as a network account will not be auth'd by
  pam_unix.  The second line points to the problem: when CUPS attempts
  to talk to sssd (indirectly by invoking PAM, but it still happens)
  then CUPS is blocked with a permission denied.

  Further research turned up a prior bug report (1264548,
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1264548) that
  highlighted nearly the same problem and highlighting it as an AppArmor
  rejection.  Examining the output of `dmesg | grepDENIED.*cups`, we do
  see lines in the output:

  [21507.848482] type=1400 audit(1458067443.626:435): apparmor="DENIED"
  operation="connect" profile="/usr/sbin/cupsd"
  name="/var/lib/sss/pipes/private/pam" pid=27447 comm="cupsd"
  requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0

  Further evidence can be found in the fact that setting the CUPS
  profile to complain mode in AppArmor causes the problem to go away
  (both Kerberos and Basic authentication modes work).

  I have successfully resolved the issue locally by adding the rule 
  /var/lib/sss/pipes/private/pam rw,

  to the file /etc/apparmor.d/local/usr.sbin.cupsd.  Interestingly, this
  also resolves the kerberos issue - both 'DefaultAuthType Basic' and
  'DefaultAuthType Negotiate' will successfully allow network accounts
  to access the Administration page.

  Looking at /etc/apparmor.d/usr.sbin.cupsd, it includes the
  abstractions/authentication def file, which in turn contains a
  specific include for the abstractions/winbind file.  I don't know
  whether there should be an equivalent abstractions file for sssd; the
  one line fix above really doesn't by itself warrant a full separate
  file, but if there are perhaps other sssd specific definitions that
  contained applications may need access to, perhaps that would warrant
  a separate file.

  I also don't know what, if any, wider security issues there may be
  from granting CUPS access to /var/lib/sss/pipes/private/pam, either,
  so perhaps a different proper fix would be required?

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

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

[Touch-packages] [Bug 1207831] Re: jackd 2 64 bit does not correclty handle 32 bit clients

[Jacek Kluza]

Thanks QkiZ! Version from KXStudio repositories works!

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

Title:
  jackd 2 64 bit does not correclty handle 32 bit clients

Status in jackd2 package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 12.04.2 LTS
  Release:12.04

  
  Launch 64 bit jackd2 binary on a 64bit install.

  launch a 32bit jack client.

  
  The jackd2 server reports an invalid / incorrect value to the 
jack_get_sample_rate call, and also the client name reported by jack_lsp is 
empty.

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

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