date:20171118

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2017-11-18 Thread iBART

For disperation, I tried this kernel: http://kernel.ubuntu.com/~kernel-
ppa/mainline/drm-intel-next/2017-11-18/

And movements are OK. Tap clic is working. Clic buttons are not.

** Attachment added: "drm-intel-next"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+attachment/5011186/+files/drm-intel-next-2017-11-18

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728244

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2017-11-18 Thread iBART

So... we have to wait for this 4.15 kernel in mainline. For now, my
touchpad does not work. I bought a wireless mouse. I'll use this, until
this problem is solved. But I don't think we are gonna solve this :p

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728244

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

2017-11-18 Thread FedeX

Hi @jsalisbury,

Sorry been flat out with work!

Sure can help with that, just to double check please, do I need to
download and install all 8 deb packages in?:
http://kernel.ubuntu.com/~jsalisbury/lp1729337

Because I don't think I've ever used/installed the cloud-tools in any of
my servers though, they are all running in VMWare hypervisor if that
helps

Cheers
FedeX

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729337

Title:
  CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Committed

Bug description:
  == SRU Justification ==
  The bug reporter stated they have a cluster of servers that applied Xenial 
updates
  and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The
  same machines on 4.4.0-97 do not hit the regression.  It was found that the
  regression is fixed by mainline commit:
  4587eee04e2a ("SMB3: Validate negotiate request must always be signed").

  This fix is required in all Ubuntu supported releases.  Commit 4587eee04e2a
  landed in mailine as of 4.14-rc7.  It  was also cc'd to upstream stable,
  but it has not landed in any stable releases yet, which is the reason for
  this SRU.


  == Fix ==
  commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd
  Author: Steve French 
  Date:   Wed Oct 25 15:58:31 2017 -0500
  SMB3: Validate negotiate request must always be signed

  == Regression Potential ==
  This patch is to fix a regression.  It was also cc'd to upstream stable, so
  it received addition review upstream.

  We have a cluster of servers that applied a security update overnight
  and were unable to mount CIFS shares after upgrading to 4.4.0-98.  The
  same machines on 4.4.0-97 were fine the night before, and are fine
  after downgrading.  The only error message CIFS would report, even on
  verbose, was:

  [  257.089876] CIFS VFS: validate protocol negotiate failed: -11
  [  257.089964] CIFS VFS: cifs_mount failed w/return code = -5

  Rebooting did not help.  Nor did attempting to mount the share
  manually using mount -t cifs.

  Here's the offending line from our /etc/fstab (with hostnames
  sanitized):

  //server/share /mnt/share cifs 
rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770
  ,exec,soft,noserverino,vers=3.0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:

  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

-- 
Mailing list:

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2017-11-18 Thread PJSingh5000

Oops, I meant to write "4.14" (not "14.14")

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729389

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2017-11-18 Thread PJSingh5000

With 14.14, it only worked for a few seconds and then stopped.

$ uname -r
4.14.0-041400-generic

Here are some error messages from the logs that may help...

hid-generic 0005:03F0:084C.0006: unknown main item tag 0x0
+hid:0005:03F0:084C.0006

bluetoothd
Can't get HIDP connection info

hid-sensor-hub 001F:8086:22D8.0001: timeout waiting for response from ISHTP 
device
+hid:001F:8086:22D8.0001

bluetoothd
Failed to add UUID: Invalid Index (0x11)

wpa_supplicant
Could not read interface p2p-dev-wlo1 flags: No such device

wpa_supplicant
dbus: Failed to construct signal

Bluetooth: hci0 command 0x0c52 tx timeout

ACPI Error: Method parse/execution failed \_SB.WMID.WMAA,
AE_AML_BUFFER_LIMIT (20170728/psparse-550)

ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of
target Buffer (160 bits) (20170728/dsopcode-235)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729389

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1730762] Re: 17.10 - suspend/resume failure

2017-11-18 Thread venturia

** Summary changed:

- 17.10 - suspend/resume failure - kernel-bug-exists-upstream
+ 17.10 - suspend/resume failure

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730762

Title:
  17.10 - suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a failure in the resume process after the suspend.
  When I try to resume the system start, but the screen stay black while
  the disk seem be really busy.

  The only way to exit from this status is unplug the system before
  restart it.

  Let me know how to collect additional info (if necessary).

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   1948 F pulseaudio
   /dev/snd/controlC0:  alessandro   1948 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 22:59:45 2017
  HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13
  InstallationDate: Installed on 2016-07-09 (486 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp2s5no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Packard Bell NEC IMEDIA 5204
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

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

[Kernel-packages] [Bug 1733070] Re: ntp apparmor profile problem

2017-11-18 Thread Paul M

I will try collecting the log again. It's easy enough to undo the fix.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733070

Title:
  ntp apparmor profile problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the apparmor logs shows a couple of problems:

  Nov 18 13:07:45 carol kernel: [107615.254389] audit: type=1400
  audit(1511010465.396:304): apparmor="DENIED" operation="sendmsg"
  info="Failed name lookup - disconnected path" error=-13
  profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=16818
  comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  and

  Nov 18 13:07:45 carol kernel: [107615.253441] audit: type=1400
  audit(1511010465.395:300): apparmor="DENIED" operation="open"
  profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16815 comm="ntpd"
  requested_mask="r" denied_mask="r" fsuid=0 ouid=0


  I fixed these by amending /etc/apparmor.d/usr.sbin.ntpd...

  change the opening to this:
/usr/sbin/ntpd flags=(attach_disconnected) {

  
  add these:
# syslog
/run/systemd/journal/dev-log w,

# not sure why it needs this
/usr/local/bin/ r,

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

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

[Kernel-packages] [Bug 1733070] Re: ntp apparmor profile problem

2017-11-18 Thread Paul M

I quoted specific examples from the apparmor logs, was that not enough?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733070

Title:
  ntp apparmor profile problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the apparmor logs shows a couple of problems:

  Nov 18 13:07:45 carol kernel: [107615.254389] audit: type=1400
  audit(1511010465.396:304): apparmor="DENIED" operation="sendmsg"
  info="Failed name lookup - disconnected path" error=-13
  profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=16818
  comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  and

  Nov 18 13:07:45 carol kernel: [107615.253441] audit: type=1400
  audit(1511010465.395:300): apparmor="DENIED" operation="open"
  profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16815 comm="ntpd"
  requested_mask="r" denied_mask="r" fsuid=0 ouid=0


  I fixed these by amending /etc/apparmor.d/usr.sbin.ntpd...

  change the opening to this:
/usr/sbin/ntpd flags=(attach_disconnected) {

  
  add these:
# syslog
/run/systemd/journal/dev-log w,

# not sure why it needs this
/usr/local/bin/ r,

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

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

[Kernel-packages] [Bug 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled

2017-11-18 Thread James Kingdon

Also 0bc2:331a (Seagte 4TB)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584557

Title:
  Seagate external drive causes SCSI bus resets when UAS enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes
  continuous SCSI bus resets by default. As a workaround, disabling UAS
  causes the device to work fine.

  To disable UAS, I created a file in /etc/modprobe.d with the following 
contents:
  options usb-storage quirks=0bc2:02322:u

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sun May 22 22:02:26 2016
  InstallationDate: Installed on 2012-10-07 (1323 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago)

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

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

[Kernel-packages] [Bug 1688081] Re: USb-Ethernet ASIX A88772 stops working after kernel 4.10

2017-11-18 Thread Tamale

I can verify this bug.  4.10.0-38-generic didn't work but
4.10.0-28-lowlatency did.

lsusb output:
`Bus 001 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet`

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1688081

Title:
  USb-Ethernet ASIX A88772 stops working after kernel 4.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an USB-Ethernet dongle ASIX AX88772 USB 2.0 Ethernet, which
  uses the asix.ko module. I just updated from Ubuntu 16.04 to 16.10
  then 17.04. When I updated to 17.04 it just stopped initializing the
  dongle; in ethtool and mii-tool it shows no link detected, although it
  is connected and works in dual-booted Windows. I ruled out
  networkmanager idiosyncrasies of "managed" and "not managed" because I
  configured it both ways and tried also with ifupdown and directly with
  ifconfig up and dhclient. And then I changed the model to another
  ethernet USB adapter and it worked.

  This is the dmesg entry for the ASIX adapter:
  [   31.137223] usb 1-6: New USB device found, idVendor=0b95, idProduct=772a
  [   31.137225] usb 1-6: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [   31.137226] usb 1-6: Product: AX88x72A
  [   31.137227] usb 1-6: Manufacturer: ASIX Elec. Corp.
  [   31.137228] usb 1-6: SerialNumber: 02

  Model no: KY-AX88772ALF on the side of the device.

  I am currently reporting this bug without the adapter connected, because I 
would have no network. So if you need additional data from it just say what you 
need, I am using Ubuntu 17.04 64 bits.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USUÁRIO PID ACESSO COMANDO
   /dev/snd/controlC0:  patola20818 F pulseaudio
   /dev/snd/controlC1:  patola20818 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=43970c80-83be-4fe7-95d3-ff85da5efe72
  InstallationDate: Installed on 2012-11-16 (1629 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IwConfig:
   enx00e04d680249  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=/dev/mapper/raizvg-rootlv ro quiet splash crashkernel=384M-:128M 
ehci_hcd.ignore_OC=1 usbcore.autosuspend=-1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-20-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-05-03 (0 days ago)
  UserGroups: adm autopilot cdrom daemon dialout dip disk input lpadmin plugdev 
sambashare sudo tty
  _MarkForUpload: True
  dmi.bios.date: 06/12/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N68T-M LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/12/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2017-11-18 Thread stark

Still Happens in 4.10.0-38-generic.

I love ubuntu so much that I have installed as second operating system
in my macbook pro. In MacOs I used to connect to Bluetooth speaker with
out any problem and audio plays without any stuck or anyting.

Here in Ubuntu its not even connecting properly in native bluetooth. I
have installed Blueman and able to connect after many tries and even
after that I am not able to play anything properly.

Ubuntu team please fix this issue. I cant able to full use Ubuntu as my
primary machine.

Dont make me hate ubuntu.

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1589008

Title:
Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
In 16.04 when a bluetooth audio device is connected it freezes video
playback and also no sound comes from online audio only streams. Issue
does not exist with a wired headset.

This issue does not exist with 15.10. All updates have been installed
on 16.04 including backports but they have not fixed the issue.

It is not browser specific and not website specific.

It is not hardware specific as it affects my laptop with an intel 7260
card and my pc with an intel 8260 card.

The issue exists on both ubuntu and kubuntu 16.04.

I have reported it on the ubuntu support forums and after
investigation a moderator noticed changed in the kernel from 4.4 and
4.2 that may becausing the issue and asked me to file a bug report.

The ubuntu forum thread can be found here.
http://ubuntuforums.org/showthread.php?t=2326672

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-23-generic 4.4.0-23.41
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stephen1435 F pulseaudio
/dev/snd/controlC0: stephen1435 F pulseaudio
CurrentDesktop: KDE
Date: Fri Jun 3 23:50:00 2016
HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
InstallationDate: Installed on 2016-05-06 (28 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7978
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-23-generic N/A
linux-backports-modules-4.4.0-23-generic N/A
linux-firmware1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
dmi.bios.date: 05/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C.60
dmi.board.asset.tag: Default string
dmi.board.name: H170 GAMING M3 (MS-7978)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7978
dmi.product.version: 2.0
dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 362075] Re: session logout after suspend

2017-11-18 Thread Christopher M. Penalver

indigocat, it will help immensely if you use the computer the problem is 
reproducible with, file a new report with Ubuntu by first ensuring the package 
xdiagnose is installed, click the Yes button for attaching additional debugging 
information after running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

** No longer affects: linux (Ubuntu)

** Project changed: null-and-void => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/362075

Title:
  session logout after suspend

Status in linux package in Ubuntu:
  Invalid

Bug description:
  In Kubuntu 9.04 Jaunty, my laptop lid down is set to suspend via
  guidance-power-manager. After I lid up, I am at the login screen,
  instead of the unlock screen dialog.

  WORKAROUND: Disable the "Lock screen on resume" option in the power
  management settings.

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

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

[Kernel-packages] [Bug 1291258] Re: [Lenovo IdeaPad Yoga 13] Stuck keys

2017-11-18 Thread Christopher M. Penalver

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1291258

Title:
  [Lenovo IdeaPad Yoga 13] Stuck keys

Status in linux package in Ubuntu:
  Invalid

Bug description:
  On the Lenovo Yoga 13 some keys, when being held down, are not
  released (e.g. pagedn, up arrow, etc.).  Once this happens, the mouse
  cursor also starts scrolling in some or other direction (it can be
  moved with the track-pad, but keeps moving in that direction).

  Using an external keyboard fixes the problem.

  At startup, the keyboard complains about unknown key events, but I
  silence those using

  sudo setkeycodes e03e 255
  sudo setkeycodes e060 255

  The behavior described here happens irrespective of whether these
  commands were executed.

  My temporary work-around is to put the machine to sleep; after wakeup
  the keyboard works fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Mar 12 11:31:26 2014
  DistUpgraded: 2013-10-07 10:49:38,779 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.2.16, 3.11.0-14-generic, x86_64: installed
   virtualbox, 4.2.16, 3.11.0-17-generic, x86_64: installed
   virtualbox, 4.2.16, 3.11.0-18-generic, x86_64: installed
   virtualbox, 4.2.16, 3.9.0-030900rc8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2012-12-20 (447 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20175
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic.efi.signed 
root=UUID=2e1ac93a-5830-41a4-b189-27ac85d8f5a7 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-07 (156 days ago)
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN51WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN51WW:bd10/19/2012:svnLENOVO:pn20175:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 20175
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1

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

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

[Kernel-packages] [Bug 362075] [NEW] session logout after suspend

2017-11-18 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

In Kubuntu 9.04 Jaunty, my laptop lid down is set to suspend via
guidance-power-manager. After I lid up, I am at the login screen,
instead of the unlock screen dialog.

WORKAROUND: Disable the "Lock screen on resume" option in the power
management settings.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: jaunty needs-upstream-testing
-- 
session logout after suspend
https://bugs.launchpad.net/bugs/362075
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1732686] Re: Asus Fx553VD - Keyboard LED backlight controls are not working # kernel-bug-reported-upstream

2017-11-18 Thread Alexandre Pereira Nunes

I'm not sure this is entirely related, but someone should try
https://github.com/archerhush/linux-fx553vd/blob/master/kbd-
backlight.patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732686

Title:
  Asus Fx553VD - Keyboard LED backlight controls are not working #
  kernel-bug-reported-upstream

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi , i'm using this laptop with it's latest bios (V303 -
  https://www.asus.com/Laptops/ASUS-FX553VD/HelpDesk_BIOS/ )

  Kernel : 4.14.0-041400-generic x86_64

  I can't control keyboard LED backlight level with it's dedicated FN
  keys or anything else. FN keys are recognized by Linux Mint 18.2 and
  Ubuntu 16.04 but pressing them have no effect.

  Kernels from 4.10 to 4.14 are the same on that regard.

  And also i have these errors on "inxi -F && dmesg | grep -i error"

  [0.031175] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS 
(20170728/dswload-378)
  [0.040665] ACPI Error: 1 table load failures, 10 successful 
(20170728/tbxfload-246)
  [0.506425] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
  [1.694527] RAS: Correctable Errors collector initialized.
  [9.833145] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

  I'm not a developer but only a user. So if i opened that issue to the
  wrong place can you point me the correct place to open it?

  Thanks.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.2
  InstallationDate: Installed on 2017-10-22 (24 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  Tags:  sonya
  Uname: Linux 4.14.0-041400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2017-11-18 Thread Dmitrii Shcherbakov

Marcos,

#68

Regardless of fastboot on/off I get the same behavior without
pcie_aspm=off

➜  ~ uname -r
4.13.0-16-generic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1521173

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1728565] RfKill.txt

2017-11-18 Thread riban

apport information

** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1728565/+attachment/5010954/+files/RfKill.txt

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

Bug description:
I upgraded my NC10 netbook from Ubuntu Mate 16.04 to 17.04 (which worked
okay) and then to 17.10. When starting up and automatically logging in I can
see the right hand quarter of the screen but the left three quarters are mostly
black with multicolour icons repeated across the top 3mm, a light grey bar
below this 8mm high with a darker grey interruption just over half way across
and two small horizontal white lines directly below this. The mouse pointer is
displayed where ever it is positioned and the right hand menus work as
expected. The computer is unusable in this condition.
Dropping to a terminal with Ctrl+Alt+F1 has the same screen corruption and
the prompt is spread across multiple lines as a series of dots and dashes -
completely unreadable. It seems the video driver is not working for this
machine in this release. The previous release showed it was using the standard
Intel open source drivers. Issue persists when PC rebooted. Power up shows
Samsung boot screen then light grey screen with small dark grey border then the
corruption described above grey background and green pattern (probably the boot
image corrupted then clearing to corruption over black background then to the
state described, i.e. mostly black with a bit of desk top and some corrupted
stuff at top.

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

Computer is a Samsung NP-NC10 with 1GB RAM and Intel Atom CPU.
(Sorry I didn't find time to test the beta!!!)
---
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: brian 2834 F pulseaudio
CurrentDesktop: MATE
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=cf3c8f13-558d-4354-9a47-39b9837475b8
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000']
failed with exit code 1: Hint: You are currently not seeing messages from other
users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=5a407644-80ca-4e5e-9d15-2fac5a1ad8d4 ro splash quiet vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
RelatedPackageVersions:
linux-restricted-modules-4.13.0-16-generic N/A
linux-backports-modules-4.13.0-16-generic N/A
linux-firmware 1.169
Tags: artful
Uname: Linux 4.13.0-16-generic i686
UpgradeStatus: Upgraded to artful on 2017-10-30 (19 days ago)
UserGroups: audio dialout sudo
WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 09/08/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 11CA.M015.20090908.RHU
dmi.board.name: NC10
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: No Asset Tag
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr11CA.M015.20090908.RHU:bd09/08/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrNoAssetTag:
dmi.product.name: NC10
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Kernel-packages] [Bug 1728565] Re: Desktop (screen) corrupted after upgrade to 17.10

2017-11-18 Thread riban

Requested logs uploaded. Note: This was done after suspend / resume
cycle with the fault cleared because apport-collect requires web browser
confirmation, hence I needed to gain desktop access. I could re-run
apport-collect (now that permission has been granted to launchpad) from
ssh session if required. Previous comment instructed to set status to
confirmed but I don't think I have rights to do that.

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] UdevDb.txt

2017-11-18 Thread riban

apport information

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

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] ProcEnviron.txt

2017-11-18 Thread riban

apport information

** Attachment added: "ProcEnviron.txt"

https://bugs.launchpad.net/bugs/1728565/+attachment/5010950/+files/ProcEnviron.txt

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] ProcModules.txt

2017-11-18 Thread riban

apport information

** Attachment added: "ProcModules.txt"

https://bugs.launchpad.net/bugs/1728565/+attachment/5010952/+files/ProcModules.txt

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] ProcInterrupts.txt

2017-11-18 Thread riban

apport information

** Attachment added: "ProcInterrupts.txt"

https://bugs.launchpad.net/bugs/1728565/+attachment/5010951/+files/ProcInterrupts.txt

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] IwConfig.txt

2017-11-18 Thread riban

apport information

** Attachment added: "IwConfig.txt"

https://bugs.launchpad.net/bugs/1728565/+attachment/5010945/+files/IwConfig.txt

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] ProcCpuinfoMinimal.txt

2017-11-18 Thread riban

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"

https://bugs.launchpad.net/bugs/1728565/+attachment/5010949/+files/ProcCpuinfoMinimal.txt

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] ProcCpuinfo.txt

2017-11-18 Thread riban

apport information

** Attachment added: "ProcCpuinfo.txt"

https://bugs.launchpad.net/bugs/1728565/+attachment/5010948/+files/ProcCpuinfo.txt

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] CurrentDmesg.txt

2017-11-18 Thread riban

apport information

** Attachment added: "CurrentDmesg.txt"

https://bugs.launchpad.net/bugs/1728565/+attachment/5010944/+files/CurrentDmesg.txt

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] PulseList.txt

2017-11-18 Thread riban

apport information

** Attachment added: "PulseList.txt"

https://bugs.launchpad.net/bugs/1728565/+attachment/5010953/+files/PulseList.txt

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] Lspci.txt

2017-11-18 Thread riban

apport information

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

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] Lsusb.txt

2017-11-18 Thread riban

apport information

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

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] CRDA.txt

2017-11-18 Thread riban

apport information

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

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

I can probably ssh in to this machine to grab logs as required so
please let me know what I can do to help debug and get my laptop back
working.

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

[Kernel-packages] [Bug 1728565] Re: Desktop (screen) corrupted after upgrade to 17.10

2017-11-18 Thread riban

apport information

** Tags added: apport-collected artful

** Description changed:

I upgraded my NC10 netbook from Ubuntu Mate 16.04 to 17.04 (which worked
okay) and then to 17.10. When starting up and automatically logging in I can
see the right hand quarter of the screen but the left three quarters are mostly
black with multicolour icons repeated across the top 3mm, a light grey bar
below this 8mm high with a darker grey interruption just over half way across
and two small horizontal white lines directly below this. The mouse pointer is
displayed where ever it is positioned and the right hand menus work as
expected. The computer is unusable in this condition.
Dropping to a terminal with Ctrl+Alt+F1 has the same screen corruption and
the prompt is spread across multiple lines as a series of dots and dashes -
completely unreadable. It seems the video driver is not working for this
machine in this release. The previous release showed it was using the standard
Intel open source drivers. Issue persists when PC rebooted. Power up shows
Samsung boot screen then light grey screen with small dark grey border then the
corruption described above grey background and green pattern (probably the boot
image corrupted then clearing to corruption over black background then to the
state described, i.e. mostly black with a bit of desk top and some corrupted
stuff at top.

I can probably ssh in to this machine to grab logs as required so please
let me know what I can do to help debug and get my laptop back working.

Computer is a Samsung NP-NC10 with 1GB RAM and Intel Atom CPU.
(Sorry I didn't find time to test the beta!!!)
+ ---
+ ApportVersion: 2.20.7-0ubuntu3.4
+ Architecture: i386
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: brian 2834 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 17.10
+ HibernationDevice: RESUME=UUID=cf3c8f13-558d-4354-9a47-39b9837475b8
+ JournalErrors:
+ Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000']
failed with exit code 1: Hint: You are currently not seeing messages from other
users and the system.
+Users in the 'systemd-journal' group can see all messages. Pass -q to
+turn off this notice.
+ No journal files were opened due to insufficient permissions.
+ MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=5a407644-80ca-4e5e-9d15-2fac5a1ad8d4 ro splash quiet vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
+ RelatedPackageVersions:
+ linux-restricted-modules-4.13.0-16-generic N/A
+ linux-backports-modules-4.13.0-16-generic N/A
+ linux-firmware 1.169
+ Tags: artful
+ Uname: Linux 4.13.0-16-generic i686
+ UpgradeStatus: Upgraded to artful on 2017-10-30 (19 days ago)
+ UserGroups: audio dialout sudo
+ WifiSyslog:
+
+ _MarkForUpload: True
+ dmi.bios.date: 09/08/2009
+ dmi.bios.vendor: Phoenix Technologies Ltd.
+ dmi.bios.version: 11CA.M015.20090908.RHU
+ dmi.board.name: NC10
+ dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ dmi.board.version: Not Applicable
+ dmi.chassis.asset.tag: None
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ dmi.chassis.version: No Asset Tag
+ dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr11CA.M015.20090908.RHU:bd09/08/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrNoAssetTag:
+ dmi.product.name: NC10
+ dmi.product.version: Not Applicable
+ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Attachment added: "AlsaInfo.txt"

https://bugs.launchpad.net/bugs/1728565/+attachment/5010942/+files/AlsaInfo.txt

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728565

Title:
Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
Invalid
Status in linux package in Ubuntu:
Incomplete

[Kernel-packages] [Bug 1732978] Re: Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

2017-11-18 Thread Frank Heimes

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => Medium

** Changed in: ubuntu-power-systems
   Status: New => Triaged

** Changed in: ubuntu-power-systems
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732978

Title:
  Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
  fallback"

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  == Comment: #0 - Paulo Flabiano Smorigo  - 2017-11-17 
10:29:14 ==
  Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback 
cipher for CTR mode. The commit bellow fixes this problem by using the new 
structure for the generic ciphers. Please add it to the kernel package.

  
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  == Comment: #1 - VIPIN K. PARASHAR  - 2017-11-17 
13:38:05 ==
  (In reply to comment #0)
  > Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
  > cipher for CTR mode. The commit bellow fixes this problem by using the new
  > structure for the generic ciphers. Please add it to the kernel package.
  > 
  > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
  > commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  Which is commit e666d4e9ceec94

  commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
  Author: Paulo Flabiano Smorigo 
  Date:   Mon Oct 16 20:54:19 2017 -0200

  crypto: vmx - Use skcipher for ctr fallback
  
  Signed-off-by: Paulo Flabiano Smorigo 
  Signed-off-by: Herbert Xu 

  Its available with 4.14 kernel.

  
  Hello Canonical,

  Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr 
fallback"
  with Ubuntu 17.10 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1732978/+subscriptions

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

[Kernel-packages] [Bug 1732978] Re: Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

2017-11-18 Thread Joseph Salisbury

** Tags added: kernel-da-key

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

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

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Joseph Salisbury (jsalisbury)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732978

Title:
  Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
  fallback"

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  == Comment: #0 - Paulo Flabiano Smorigo  - 2017-11-17 
10:29:14 ==
  Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback 
cipher for CTR mode. The commit bellow fixes this problem by using the new 
structure for the generic ciphers. Please add it to the kernel package.

  
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  == Comment: #1 - VIPIN K. PARASHAR  - 2017-11-17 
13:38:05 ==
  (In reply to comment #0)
  > Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
  > cipher for CTR mode. The commit bellow fixes this problem by using the new
  > structure for the generic ciphers. Please add it to the kernel package.
  > 
  > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
  > commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

  Which is commit e666d4e9ceec94

  commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
  Author: Paulo Flabiano Smorigo 
  Date:   Mon Oct 16 20:54:19 2017 -0200

  crypto: vmx - Use skcipher for ctr fallback
  
  Signed-off-by: Paulo Flabiano Smorigo 
  Signed-off-by: Herbert Xu 

  Its available with 4.14 kernel.

  
  Hello Canonical,

  Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr 
fallback"
  with Ubuntu 17.10 kernel.

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

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

[Kernel-packages] [Bug 1731031] Re: Kernel Oops with 17.10

2017-11-18 Thread Joseph Salisbury

Can you try 4.13 final?  If it has the bug, we can "Reverse" bisect
between 4.13 final and 4.14-rc1.

4.13 final is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1731031

Title:
  Kernel Oops with 17.10

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  have captured dmesg just before oops

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Nov  8 20:41:14 2017
  DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to 
load user image: Failed to open file '/home/hmeyer/.face': No such file or 
directory
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B17.1602221718
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Nov  8 20:39:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

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

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

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

2017-11-18 Thread Joseph Salisbury

The fact that 4.13.8 doesn't reproduce the bug might be another
indicator that the bug was introduced by a SAUCE patch.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730717

Title:
  Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
  for 22s! [systemd:1]"

Status in linux package in Ubuntu:
  In Progress
Status in qemu-kvm package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Incomplete
Status in qemu-kvm source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress
Status in qemu-kvm source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in qemu-kvm source package in Bionic:
  Confirmed

Bug description:
  This is impacting us for ubuntu autopkgtests. Eventually the whole
  region ends up dying because each worker is hit by this bug in turn
  and backs off until the next reset (6 hourly).

  17.10 (and bionic) guests are sometimes failing to reboot. When this
  happens, you see the following in the console

    [[0;32m  OK  [0m] Reached target Shutdown.
    [  191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
    [  226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
    [  226.706093] All QSes seen, last rcu_sched kthread activity 15002 
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
    [  226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

  One host that exhibits this behaviour was:

    Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  guest running:

    Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
  (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  (Ubuntu 4.13.0-16.19-generic 4.13.4)

  The affected cloud region is running the xenial/Ocata cloud archive,
  so the version of qemu-kvm in there may also be relevant.

  Here's how I reproduced it in lcy01:

    $ for n in {1..30}; do nova boot --flavor m1.small --image 
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name 
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; 
done
    $  sudo reboot
    # wait a minute or so for the instances to all reboot
    $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} 
| tail; done

  On bad instances you'll see the "soft lockup" message - on good it'll
  reboot as normal.

  We've seen good and bad instances on multiple compute hosts - it
  doesn't feel to me like a host problem but rather a race condition
  somewhere that's somehow either triggered or triggered much more often
  by what lcy01 is running. I always saw this on the first reboot -
  never on first boot, and never on n>1th boot. (But if it's a race then
  that might not mean much.)

  I'll attach a bad and a good console-log for reference.

  If you're at Canonical then see internal rt #107135 for some other
  details.

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

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

[Kernel-packages] [Bug 1733070] Missing required logs.

2017-11-18 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1733070

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

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

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733070

Title:
  ntp apparmor profile problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the apparmor logs shows a couple of problems:

  Nov 18 13:07:45 carol kernel: [107615.254389] audit: type=1400
  audit(1511010465.396:304): apparmor="DENIED" operation="sendmsg"
  info="Failed name lookup - disconnected path" error=-13
  profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=16818
  comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  and

  Nov 18 13:07:45 carol kernel: [107615.253441] audit: type=1400
  audit(1511010465.395:300): apparmor="DENIED" operation="open"
  profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16815 comm="ntpd"
  requested_mask="r" denied_mask="r" fsuid=0 ouid=0


  I fixed these by amending /etc/apparmor.d/usr.sbin.ntpd...

  change the opening to this:
/usr/sbin/ntpd flags=(attach_disconnected) {

  
  add these:
# syslog
/run/systemd/journal/dev-log w,

# not sure why it needs this
/usr/local/bin/ r,

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

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

[Kernel-packages] [Bug 1733070] Re: ntp apparmor profile problem

2017-11-18 Thread Paul M

this exists in 17.10 xubuntu

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733070

Title:
  ntp apparmor profile problem

Status in linux package in Ubuntu:
  New

Bug description:
  the apparmor logs shows a couple of problems:

  Nov 18 13:07:45 carol kernel: [107615.254389] audit: type=1400
  audit(1511010465.396:304): apparmor="DENIED" operation="sendmsg"
  info="Failed name lookup - disconnected path" error=-13
  profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=16818
  comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  and

  Nov 18 13:07:45 carol kernel: [107615.253441] audit: type=1400
  audit(1511010465.395:300): apparmor="DENIED" operation="open"
  profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16815 comm="ntpd"
  requested_mask="r" denied_mask="r" fsuid=0 ouid=0


  I fixed these by amending /etc/apparmor.d/usr.sbin.ntpd...

  change the opening to this:
/usr/sbin/ntpd flags=(attach_disconnected) {

  
  add these:
# syslog
/run/systemd/journal/dev-log w,

# not sure why it needs this
/usr/local/bin/ r,

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

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

[Kernel-packages] [Bug 1733070] [NEW] ntp apparmor profile problem

2017-11-18 Thread Paul M

Public bug reported:

the apparmor logs shows a couple of problems:

Nov 18 13:07:45 carol kernel: [107615.254389] audit: type=1400
audit(1511010465.396:304): apparmor="DENIED" operation="sendmsg"
info="Failed name lookup - disconnected path" error=-13
profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=16818
comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0


and

Nov 18 13:07:45 carol kernel: [107615.253441] audit: type=1400
audit(1511010465.395:300): apparmor="DENIED" operation="open"
profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16815 comm="ntpd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0


I fixed these by amending /etc/apparmor.d/usr.sbin.ntpd...

change the opening to this:
  /usr/sbin/ntpd flags=(attach_disconnected) {


add these:
  # syslog
  /run/systemd/journal/dev-log w,

  # not sure why it needs this
  /usr/local/bin/ r,

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733070

Title:
  ntp apparmor profile problem

Status in linux package in Ubuntu:
  New

Bug description:
  the apparmor logs shows a couple of problems:

  Nov 18 13:07:45 carol kernel: [107615.254389] audit: type=1400
  audit(1511010465.396:304): apparmor="DENIED" operation="sendmsg"
  info="Failed name lookup - disconnected path" error=-13
  profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=16818
  comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  and

  Nov 18 13:07:45 carol kernel: [107615.253441] audit: type=1400
  audit(1511010465.395:300): apparmor="DENIED" operation="open"
  profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16815 comm="ntpd"
  requested_mask="r" denied_mask="r" fsuid=0 ouid=0


  I fixed these by amending /etc/apparmor.d/usr.sbin.ntpd...

  change the opening to this:
/usr/sbin/ntpd flags=(attach_disconnected) {

  
  add these:
# syslog
/run/systemd/journal/dev-log w,

# not sure why it needs this
/usr/local/bin/ r,

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

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

[Kernel-packages] [Bug 1733060] Status changed to Confirmed

2017-11-18 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733060

Title:
  Touchpad doesn't work after wake from sleep on HP Pavilion x2
  Detachable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After waking the laptop from screen, the touchpad does not work. It
  does not react to single finger movement or tapping, nor to two finger
  scroll, nor to pressing down the clickpad left or right. The laptop
  has a detachable screen for use as a tablet. After detaching the
  screen and reattaching the screen the touchpad works again as
  expected.

  I've tried it now a few times and I can reliably reproduce the touchpad 
problem as follows:
  - close the lid, 
  - wait for the led to indicated sleeping. 
  - Open the lid. 
  - Hit enter (otherwise the screen stays dark). 
  - Enter password to unlock using the keyboard. 
  - Try keyboard and touchpad to see whether they work. 
  - It they don't work 
- Pull the screen off of the keyboard base with the integrated touchpad. 
- Reconnect 
- Try keyboard and touchpad again  

  A few attempts below with approximate times. Should be visible in the
  syslog for Nov 18

  NB: In one of these tests the keyboard didn't work after
  disconnect/reconnect. But that is not a persistent problem. I don't
  remember having seen that before, nor was I able to reproduce it a
  second time.

  --
  close lid 10:14:55
  open 
  -> keyboard works
  -> touchpad doesnt work
  disconnect 10:25:09
  reconnect 
  -> keyboard doesnt work
  -> touchpad doesnt work
  disconnect 
  reconnect 
  -> keyboard works
  -> touchpad works 

  --
  close lid 10:39:20
  open 
  -> keyboard works
  -> touchpad doesn't work 
  disconnect 10:41:11
  reconnect 
  -> keyboard works
  -> touchpad works

  --
  close lid 10:47:50
  open 
  -> keyboard works
  -> touchpad doesnt work
  disconnect 10:48:37
  reconnect 
  -> keyboard works
  -> touchpad works

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1195 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 18 10:50:00 2017
  HibernationDevice: RESUME=UUID=ccc9dd4a-8423-499f-8e57-022be496cfa6
  InstallationDate: Installed on 2017-11-05 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: HP HP Pavilion x2 Detachable
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=c516cd88-8b77-434a-813a-799e0380a4eb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8181
  dmi.board.vendor: HP
  dmi.board.version: 42.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

2017-11-18 Thread Launchpad Bug Tracker

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1651635

Title:
  XPS 13 9360 trackpad locks into scroll mode

Status in Dell Sputnik:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm running Linux on a Dell XPS 13 (9360) laptop.

  I find that upwards of 10 times per day, my trackpad gets stuck in
  "scrolling" mode. Moving the trackpad won't move the X windows
  pointer, but will send scrolling events to the foreground window.

  When the trackpad is locked in this mode, the touchscreen will still
  let me move the mouse cursor, as will an external mouse.

  On Ubuntu 16.04 freshly restored from the Dell recovery image, I find
  that it's often difficult to get the trackpad to recover.

  I do find that the issue happens less frequently on Dell's build of
  Ubuntu 16.04 than on other linux distributions and versions, but it
  still happens enough to significantly impact my ability to do
  productive work.

  The issue does not occur when running Windows 10 on the same device.

  I suspect that the issue may be related to palm detection or
  misdetecting the user's palm as a gesture to enable scrolling mode,
  but have no proof for this.

  It seems that I'm often able to reproduce the issue by brushing the
  trackpad with my right palm.

  On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx
  4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I
  am able to get the trackpad to recover, simply by clicking the
  trackpad:

  /usr/share/X11/xorg.conf.d/99-libinput.conf:

  Section "InputClass"
  Identifier "libinput touchpad catchall"
  Driver "libinput"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Option "Tapping" "True"
  Option "DisableWhileTyping" "True"
  Option "NaturalScrolling" "False"
  Option "AccelProfile" "adaptive"
  Option "AccelSpeed" "0.05"
  Option "MiddleEmulation" "True"
  Option "ScrollMethod" "twofinger"
  # Option "ClickMethod" "clickfinger"
  Option "ClickMethod" "buttonareas"
  EndSection

  
  In my experience, the problem manifests using both the Xorg synaptics driver 
and the Xorg libinput driver.

  root@szx:/etc/modprobe.d# xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech M570   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ DLL075B:01 06CB:76AF Touchpad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=14   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]
  root@szx:/etc/modprobe.d#

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions

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

[Kernel-packages] [Bug 1733060] [NEW] Touchpad doesn't work after wake from sleep on HP Pavilion x2 Detachable

2017-11-18 Thread doniks

Public bug reported:

After waking the laptop from screen, the touchpad does not work. It does
not react to single finger movement or tapping, nor to two finger
scroll, nor to pressing down the clickpad left or right. The laptop has
a detachable screen for use as a tablet. After detaching the screen and
reattaching the screen the touchpad works again as expected.

I've tried it now a few times and I can reliably reproduce the touchpad problem 
as follows:
- close the lid, 
- wait for the led to indicated sleeping. 
- Open the lid. 
- Hit enter (otherwise the screen stays dark). 
- Enter password to unlock using the keyboard. 
- Try keyboard and touchpad to see whether they work. 
- It they don't work 
  - Pull the screen off of the keyboard base with the integrated touchpad. 
  - Reconnect 
  - Try keyboard and touchpad again  

A few attempts below with approximate times. Should be visible in the
syslog for Nov 18

NB: In one of these tests the keyboard didn't work after
disconnect/reconnect. But that is not a persistent problem. I don't
remember having seen that before, nor was I able to reproduce it a
second time.

--
close lid 10:14:55
open 
-> keyboard works
-> touchpad doesnt work
disconnect 10:25:09
reconnect 
-> keyboard doesnt work
-> touchpad doesnt work
disconnect 
reconnect 
-> keyboard works
-> touchpad works 

--
close lid 10:39:20
open 
-> keyboard works
-> touchpad doesn't work 
disconnect 10:41:11
reconnect 
-> keyboard works
-> touchpad works

--
close lid 10:47:50
open 
-> keyboard works
-> touchpad doesnt work
disconnect 10:48:37
reconnect 
-> keyboard works
-> touchpad works

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  peter  1195 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 18 10:50:00 2017
HibernationDevice: RESUME=UUID=ccc9dd4a-8423-499f-8e57-022be496cfa6
InstallationDate: Installed on 2017-11-05 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: HP HP Pavilion x2 Detachable
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=c516cd88-8b77-434a-813a-799e0380a4eb ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8181
dmi.board.vendor: HP
dmi.board.version: 42.25
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Pavilion x2 Detachable
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug artful wayland-session

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733060

Title:
  Touchpad doesn't work after wake from sleep on HP Pavilion x2
  Detachable

Status in linux package in Ubuntu:
  New

Bug description:
  After waking the laptop from screen, the touchpad does not work. It
  does not react to single finger movement or tapping, nor to two finger
  scroll, nor to pressing down the clickpad left or right. The laptop
  has a detachable screen for use as a tablet. After detaching the
  screen and reattaching the screen the touchpad works again as
  expected.

  I've tried it now a few times and I can reliably reproduce the touchpad 
problem as follows:
  - close the lid, 
  - wait for the led to indicated sleeping. 
  - Open the lid. 
  - Hit enter (otherwise the screen stays dark). 
  - Enter password to unlock using the keyboard. 
  - Try keyboard and touchpad to see whether they work. 
  - It they don't work 
- Pull the screen off of the keyboard base with the integrated touchpad. 
- Reconnect 
- Try keyboard and touchpad again  

  A few attempts below with approximate times. Should be visible in the
  syslog for Nov 18

  NB: In one of these tests the keyboard didn't work after
  disconnect/reconnect. But that is not a persistent problem. I don't
  remember having seen that before, nor was I able to reproduce it a
  second time.

  --
  close lid 10:14:55
  open 
  -> keyboard

41 matches

Mail list logo