[Kernel-packages] [Bug 1838180] Re: apps use speakers when bluetooth headset is active (REGRESSION)

2019-07-28 Thread jimav
Ok, the mis-directed output seems to be fixed with a kernel 5.2.

With the stock 5.0.0-21-generic, disconnecting BT in the Ubuntu gui does
not actually disconnect immediately.  Instead, the disconnect happens
when BT is turned ON again in the gui!

(based on my BT headset's synthesized status-change messages, which say
nothing when BT is turned OFF in the gui, but say "disconnected" when BT
is turned ON in the gui).

Thereafter, sound goes to the speakers even though the gui shows the BT
headset is connected.  I found that power-cycling the headset clears the
problem, presumably because of the extraneous connection messages when
the headset comes back on.

These problem COMPLETELY GO AWAY with kernel 5.2 installed.  Now, when I
disconnect the headset in the Ubuntu gui, the headset instantly reports
being disconnected, and it re-connects propertly when the headset is
turned on again in the Ubuntu gui.

There are some remaining gui issues where the switch in the gui snaps
back by itself to "off" on the first few tries, but after a while the
headset connects correctly.  I will file a different bugrep about that
with a video.

In conclusion, it sounds like some kernel bug or api mis-match will be
resolved with kernel 5.2, but that won't be shipped for while in Ubuntu.
]

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

Title:
  apps use speakers when bluetooth headset is active (REGRESSION)

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth headset stopped working after upgrading to 19.04.  Worked
  perfectly with 18.10.

  Now, when a BT headset is connected the volume-control widget (seen
  via the speaker icon in the upper-right corner) displays a headset
  icon and a volume slider, but the slider has NO EFRFECT on volume and
  sound still comes out of the speakers.

  It seems like the BT headset is active as far as the volume-control
  GUI knows, BUT sound from apps still goes to the speakers (which were
  active before the BT headset connected).

  syslog shows: bluetoothd[1423]: connect error: Device or resource busy
  (16)

  I will attach the full syslog

  The problem does not occur with a wired headset.

  STEPS TO REPRODUCE:
  1. Reboot
 Turn Bluetooth OFF (speakericon->BTicon->Turn Off)
  2. Start Rhythmbox or other sound source; play something, set the volume low 
but audible
  (should be heard on speakers)
  3. Turn on a Bluetoogh headset
  4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On)
  If necessary, do other stuff to get the BT headset connected
 A "headset icon" should appear next the volume slider (click speaker icon 
to see it)

  RESULTS: Sound continues to come out of speakers; nothing from BT headset
   Moving the volume slider has no effect

  EXPECTED RESULTS: Switch sound to the BT headset

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluez 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 22:59:01 2019
  InstallationDate: Installed on 2018-04-05 (479 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic 
root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago)
  dmi.bios.date: 12/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0605
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 48:89:E7:CF:4F:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:14153 acl:154 sco:0 events:971 errors:0
TX bytes:429273 acl:643 sco:0 commands:229 errors:0

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

-- 
Mailing 

[Kernel-packages] [Bug 1837465] Re: WARNING: CPU: 9 PID: 129 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:277 generic_reg_wait.cold.3+0x25/0x2c [amdgpu]

2019-07-28 Thread Arash Payan
After upgrading and testing with mainline kernel 5.2.4 this crash no
longer occurs. This bug can be closed.

** Attachment removed: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837465/+attachment/5278554/+files/lspci-vnvn.log

** Attachment removed: "Last 1000 lines of syslog, captured after crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837465/+attachment/5278555/+files/sys.log

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

Title:
  WARNING: CPU: 9 PID: 129 at
  drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:277
  generic_reg_wait.cold.3+0x25/0x2c [amdgpu]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever I run a game that pushes my GPU harder than usual, my monitor
  loses signal from the GPU and I have to do a hard reboot (hold down
  the power button for a few seconds) of my computer. I'm able to
  reproduce the problem consistently by playing Cities Skylines at 4K.

  Please let me know if I can be of any assistance in helping to test.

  System info:
  Ubuntu Version: 18.04.2 LTS
  Kernel: 5.1.16-050116-generic

  Steps to reproduce:
  1) Run Cities Skylines from Steam at 4k
  2) Load a new map and start building a city

  Expected:
  The system should be stable

  Actual:
  Within 20 - 300 seconds, the monitor loses signal, and I have to perform a 
hard reboot.

  Notes:
  I've attached the last 1000 lines of my syslog after the moment of the crash 
until I rebooted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837465/+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 1838141] Re: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling.

2019-07-28 Thread Srijan Kumar Sharma
CPU frequency does not increase under heavy load.

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

Title:
  intel_pstate not working. CPU frequency fixed at 800MHz. No cpu
  frequency scaling.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel_pstate not working. CPU frequency fixed at 800MHz.

  I've tried to modify frequency using "cpufreq-set" and also by
  directly writing to files in "/sys/devices/system/cpu/cpu0/cpufreq/*"
  to no success.

  I tried different versions of kernel, it started working on 4.17.0 but
  stopped working soon. These are the versions I tested.

  5.2.3   - Not Working
  5.1.0   - Not Working
  4.19.60 - Not Working
  4.18.20 - Not Working
  4.17.19 - Not Working
  4.17.10 - Not Working
  4.17.5  - Not Working
  4.17.3  - Working
  4.17.2  - Working
  4.17.1  - Working
  4.17.0  - Working
  4.16.18 - Not Working
  4.15.0  - Not Working

  Please let me know if anything else is needed.
  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-55-generic 4.15.0-55.60
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srijan 2219 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Jul 27 11:34:10 2019
  InstallationDate: Installed on 2018-11-25 (243 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5621 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Predator PH315-51
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic 
root=UUID=a76bd009-8058-4e96-a8b5-a82b7fbe1ede ro acpi_backlight=vendor 
i915.modeset=1 i915.enable_guc=3 i915.enable_dc=2 i915.enable_fbc=1 
nvme_core.default_ps_max_latency_us=1800 pcie_aspm=force i915.enable_psr=2 
i915.disable_power_well=1 nmi_watchdog=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-55-generic N/A
   linux-backports-modules-4.15.0-55-generic  N/A
   linux-firmware 1.173.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Sienta_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.24
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd12/05/2018:svnAcer:pnPredatorPH315-51:pvrV1.24:rvnCFL:rnSienta_CFS:rvrV1.24:cvnAcer:ct10:cvrV1.24:
  dmi.product.family: Predator Helios 300
  dmi.product.name: Predator PH315-51
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838141/+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 1838181] Status changed to Confirmed

2019-07-28 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/1838181

Title:
  3D Application cannot run anymore

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  Since a recent update (done today 2019-07-28) I cannot start
  application that requires 3D (openGL support). It start being slow
  with degraded graphics, then freeze and finally crash with the
  following message :

   > i965: Failed to submit batchbuffer: Input/output error

  It also happened to me when I updated from Bionic Beaver to Disco. The
  Workaround was to reinstall a Bionic Beaver version. Now it does not
  work on this version anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 08:58:45 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:80df]
  InstallationDate: Installed on 2019-04-30 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.45
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DF
  dmi.board.vendor: HP
  dmi.board.version: 87.72
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook
  dmi.product.sku: W6X73EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838181/+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 1838141] Re: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling.

2019-07-28 Thread Anthony Wong
Setting specific CPU frequencies via cpufreq-set is incompatible with the 
intel_pstate driver.
Is your problem about unable to fix the CPU to specific frequencies, or the CPU 
frequencies do not increase even you are under heavy workload?

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

Title:
  intel_pstate not working. CPU frequency fixed at 800MHz. No cpu
  frequency scaling.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel_pstate not working. CPU frequency fixed at 800MHz.

  I've tried to modify frequency using "cpufreq-set" and also by
  directly writing to files in "/sys/devices/system/cpu/cpu0/cpufreq/*"
  to no success.

  I tried different versions of kernel, it started working on 4.17.0 but
  stopped working soon. These are the versions I tested.

  5.2.3   - Not Working
  5.1.0   - Not Working
  4.19.60 - Not Working
  4.18.20 - Not Working
  4.17.19 - Not Working
  4.17.10 - Not Working
  4.17.5  - Not Working
  4.17.3  - Working
  4.17.2  - Working
  4.17.1  - Working
  4.17.0  - Working
  4.16.18 - Not Working
  4.15.0  - Not Working

  Please let me know if anything else is needed.
  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-55-generic 4.15.0-55.60
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srijan 2219 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Jul 27 11:34:10 2019
  InstallationDate: Installed on 2018-11-25 (243 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5621 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Predator PH315-51
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic 
root=UUID=a76bd009-8058-4e96-a8b5-a82b7fbe1ede ro acpi_backlight=vendor 
i915.modeset=1 i915.enable_guc=3 i915.enable_dc=2 i915.enable_fbc=1 
nvme_core.default_ps_max_latency_us=1800 pcie_aspm=force i915.enable_psr=2 
i915.disable_power_well=1 nmi_watchdog=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-55-generic N/A
   linux-backports-modules-4.15.0-55-generic  N/A
   linux-firmware 1.173.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Sienta_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.24
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd12/05/2018:svnAcer:pnPredatorPH315-51:pvrV1.24:rvnCFL:rnSienta_CFS:rvrV1.24:cvnAcer:ct10:cvrV1.24:
  dmi.product.family: Predator Helios 300
  dmi.product.name: Predator PH315-51
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838141/+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 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)

2019-07-28 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
  combo jack mic doesn't detect)

Status in linux package in Ubuntu:
  Expired

Bug description:
  I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple 
type. not europe type.).
  When I plug 4 pole mic into jack, It doesn't detect.
  So I can't my voice through external mic.

  My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio 
device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series High Definition Audio Controller (rev 21)).
  Internal mic works well.

  Please check 4pole external mic detection.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jimnong1441 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jimnong1441 F...m pulseaudio
   /dev/snd/controlC0:  jimnong1441 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:30:39 2019
  InstallationDate: Installed on 2017-07-27 (603 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire ES1-131
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821269/+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 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty, but not 5.0.1)

2019-07-28 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5
  faulty, but not 5.0.1)

Status in linux package in Ubuntu:
  Expired

Bug description:
  On my Laptop sound is working only after a fresh reboot. Every time I
  suspend the laptop, I can no longer use the internal speakers or any
  headphones. I tried a lot of solutions suggested online none of them
  working for me. Since this problem is very annoying I would really
  appreciate if a fix would be available.

  Thanks a lot :)

  Additional information:
  Laptop: HP 14-ma0307ng
  Ubuntu 19.04
  Audio:
  sudo lspci -v | grep -A7 -i "audio"
  00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03)
Subsystem: Hewlett-Packard Company Device 84b6
Flags: bus master, fast devsel, latency 0, IRQ 25
Memory at a131 (64-bit, non-prefetchable) [size=16K]
Memory at a100 (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [80] Vendor Specific Information: Len=14 
Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  harry  5835 F pulseaudio
   /dev/snd/pcmC0D0c:   harry  5835 F...m pulseaudio
   /dev/snd/pcmC0D0p:   harry  5835 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 18 19:12:01 2019
  InstallationDate: Installed on 2019-04-30 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84B6
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 76.17
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14-ma0xxx
  dmi.product.sku: 4DL72EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829621/+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 1838181] Re: 3D Application cannot run anymore

2019-07-28 Thread Daniel van Vugt
** Also 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/1838181

Title:
  3D Application cannot run anymore

Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Since a recent update (done today 2019-07-28) I cannot start
  application that requires 3D (openGL support). It start being slow
  with degraded graphics, then freeze and finally crash with the
  following message :

   > i965: Failed to submit batchbuffer: Input/output error

  It also happened to me when I updated from Bionic Beaver to Disco. The
  Workaround was to reinstall a Bionic Beaver version. Now it does not
  work on this version anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 08:58:45 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:80df]
  InstallationDate: Installed on 2019-04-30 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.45
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DF
  dmi.board.vendor: HP
  dmi.board.version: 87.72
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook
  dmi.product.sku: W6X73EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838181/+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 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21

2019-07-28 Thread Anthony Wong
** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => 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/1838133

Title:
  realtek r8822be kernel module fails after update to linux kernel-
  headers 5.0.0-21

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part
  of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't
  notice that wifi was no longer working because at work I exclusively
  use a wired Ethernet connection.

  Today, however, when I tried to use my realtek r8822be wireless card,
  I discovered that it was totally unresponsive and did not work with
  wpa_supplicant / wpa_cli even when invoked manually from the command
  line (let alone with NetworkManager). When the problem occurred, I was
  using 19.04's latest kernel 5.0.0-21.

  I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname
  -a" shows that I am using the previous kernel version:

  Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

  With this kernel version as well as linux-headers-5.0.0.20, linux-
  headers-5.0.0-20-generic, my realtek wireless card works fine. While
  booted into 5.0.0-20 kernel, here are the realtek kernel modules that
  are loaded:

  # lsmod | grep r8
  r8822be   692224  0
  mac80211  806912  1 r8822be
  cfg80211  671744  2 mac80211,r8822be
  r8169  81920  0

  Hopefully this realtek wireless regression can get fixed in the next
  minor kernel version. Let me know if you need any more information.

  Best Regards,
  Jun

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+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 1838156] Re: synaptics - touchpad input driver

2019-07-28 Thread Anthony Wong
Do you use edge scroll or two-finger scroll?

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

Title:
  synaptics - touchpad input driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad scrolling is not working. I have Haier Y11C.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-55-generic 4.15.0-55.60
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jawadsajid   1639 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 02:32:47 2019
  HibernationDevice: RESUME=UUID=1c3a5128-c70c-4bef-9cf7-0108e089f29c
  InstallationDate: Installed on 2019-07-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b635 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Haier Information Technology (Shen Zhen) Co.,Ltd Y11C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic 
root=UUID=090de797-9be0-41a3-87f8-fb687659760c ro quiet splash 
ivrs_ioapic[32]=00:14.0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-55-generic N/A
   linux-backports-modules-4.15.0-55-generic  N/A
   linux-firmware 1.173.9
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-27 (0 days ago)
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: LN1V
  dmi.bios.version: 1.23
  dmi.board.asset.tag: Default string
  dmi.board.name: Y11C
  dmi.board.vendor: Haier Information Technology (Shen Zhen) Co.,Ltd
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Haier Information Technology (Shen Zhen) Co.,Ltd
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnLN1V:bvr1.23:bd01/30/2018:svnHaierInformationTechnology(ShenZhen)Co.,Ltd:pnY11C:pvrDefaultstring:rvnHaierInformationTechnology(ShenZhen)Co.,Ltd:rnY11C:rvrDefaultstring:cvnHaierInformationTechnology(ShenZhen)Co.,Ltd:ct10:cvrDefaultstring:
  dmi.product.family: y series
  dmi.product.name: Y11C
  dmi.product.version: Default string
  dmi.sys.vendor: Haier Information Technology (Shen Zhen) Co.,Ltd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838156/+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 1838180] Re: apps use speakers when bluetooth headset is active (REGRESSION)

2019-07-28 Thread Daniel van Vugt
It sounds like the log messages relating to the issue are:

  Jul 27 22:54:49 hostname gsd-media-keys[2755]: Unable to get default sink
  ...
  Jul 27 22:55:04 hostname bluetoothd[1423]: Unable to get Headset Voice 
gateway SDP record: Device or resource busy
  Jul 27 22:55:04 hostname bluetoothd[1423]: connect error: Device or resource 
busy (16)

Which suggests it's the kernel that's behaving differently, via
PulseAudio.

Please try some newer (or older) kernels from:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

and tell us which versions, if any, avoid the bug.

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

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

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

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

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

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

Title:
  apps use speakers when bluetooth headset is active (REGRESSION)

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth headset stopped working after upgrading to 19.04.  Worked
  perfectly with 18.10.

  Now, when a BT headset is connected the volume-control widget (seen
  via the speaker icon in the upper-right corner) displays a headset
  icon and a volume slider, but the slider has NO EFRFECT on volume and
  sound still comes out of the speakers.

  It seems like the BT headset is active as far as the volume-control
  GUI knows, BUT sound from apps still goes to the speakers (which were
  active before the BT headset connected).

  syslog shows: bluetoothd[1423]: connect error: Device or resource busy
  (16)

  I will attach the full syslog

  The problem does not occur with a wired headset.

  STEPS TO REPRODUCE:
  1. Reboot
 Turn Bluetooth OFF (speakericon->BTicon->Turn Off)
  2. Start Rhythmbox or other sound source; play something, set the volume low 
but audible
  (should be heard on speakers)
  3. Turn on a Bluetoogh headset
  4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On)
  If necessary, do other stuff to get the BT headset connected
 A "headset icon" should appear next the volume slider (click speaker icon 
to see it)

  RESULTS: Sound continues to come out of speakers; nothing from BT headset
   Moving the volume slider has no effect

  EXPECTED RESULTS: Switch sound to the BT headset

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluez 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 22:59:01 2019
  InstallationDate: Installed on 2018-04-05 (479 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic 
root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago)
  dmi.bios.date: 12/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0605
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 48:89:E7:CF:4F:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:14153 acl:154 sco:0 events:971 errors:0
TX bytes:429273 acl:643 sco:0 commands:229 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838180/+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 1838180] Re: apps use speakers when bluetooth headset is active (REGRESSION)

2019-07-28 Thread Daniel van Vugt
The strange thing here is that 18.10 and 19.04 use the same versions of
bluez and pulseaudio. So I don't think those are going to be the
problem.

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

Title:
  apps use speakers when bluetooth headset is active (REGRESSION)

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth headset stopped working after upgrading to 19.04.  Worked
  perfectly with 18.10.

  Now, when a BT headset is connected the volume-control widget (seen
  via the speaker icon in the upper-right corner) displays a headset
  icon and a volume slider, but the slider has NO EFRFECT on volume and
  sound still comes out of the speakers.

  It seems like the BT headset is active as far as the volume-control
  GUI knows, BUT sound from apps still goes to the speakers (which were
  active before the BT headset connected).

  syslog shows: bluetoothd[1423]: connect error: Device or resource busy
  (16)

  I will attach the full syslog

  The problem does not occur with a wired headset.

  STEPS TO REPRODUCE:
  1. Reboot
 Turn Bluetooth OFF (speakericon->BTicon->Turn Off)
  2. Start Rhythmbox or other sound source; play something, set the volume low 
but audible
  (should be heard on speakers)
  3. Turn on a Bluetoogh headset
  4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On)
  If necessary, do other stuff to get the BT headset connected
 A "headset icon" should appear next the volume slider (click speaker icon 
to see it)

  RESULTS: Sound continues to come out of speakers; nothing from BT headset
   Moving the volume slider has no effect

  EXPECTED RESULTS: Switch sound to the BT headset

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluez 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 22:59:01 2019
  InstallationDate: Installed on 2018-04-05 (479 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic 
root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago)
  dmi.bios.date: 12/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0605
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 48:89:E7:CF:4F:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:14153 acl:154 sco:0 events:971 errors:0
TX bytes:429273 acl:643 sco:0 commands:229 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838180/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

2019-07-28 Thread Daniel van Vugt
** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1838151

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

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

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

2019-07-28 Thread Daniel van Vugt
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: patch

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

** Changed in: pulseaudio (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/1838151

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

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

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

2019-07-28 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 1838151

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

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

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1637802] Re: ubuntu 14.04 problem between airplane mode and bluetooth

2019-07-28 Thread Daniel van Vugt
** Tags removed: trusty
** Tags added: bionic xenial

** Changed in: bluez (Ubuntu)
   Status: Won't Fix => New

** Summary changed:

- ubuntu 14.04 problem between airplane mode and bluetooth
+ Lenovo G400 problem between airplane mode and bluetooth

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

Title:
  Lenovo G400 problem between airplane mode and bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  is very strange because sometime is working but most of the time the 
bluetooth icon is absent and even if you go in System Settings you can not 
switch on bluetooth than  if you start to play with airplane mode switch and 
bluetooth switch some time bluetooth comes a life for sometime than it stop for 
good, anyway to me becomes evident that there is a relation between airplane 
mode and bluetooth, be so nice finding a solution if posible
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-05-30 (153 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: LENOVO 20235
  Package: bluez 4.101-0ubuntu13.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=c89a3965-eb84-4899-abe5-01cf184b6981 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Tags:  trusty
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 78CN16WW(V1.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G400
  dmi.modalias: 
dmi:bvnLENOVO:bvr78CN16WW(V1.04):bd04/17/2013:svnLENOVO:pn20235:pvrLenovoG400:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG400:
  dmi.product.name: 20235
  dmi.product.version: Lenovo G400
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1637802/+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 1762940] Re: hibmc-drm Causes Unreadable Display for Huawei amd64 Servers

2019-07-28 Thread Matthew Ruffell
I installed 4.15.0-56-generic to a bionic VM, with the -modules and 
-modules-extra packages. I went into /var/lib/modules/4.15.0-56/ and did a 
search for
hibmc_drm. There was no mention apart from a header Makefile. The module was not
built and not present on amd64.

I did the same for 5.0.0-22-generic in a disco VM, and the module was not
built and was not present.

4.15.0-56-generic has been installed to a amd64 based Huawei server which was
having the issues explained in this bug, and since the module was not present,
the screen was not "blurry" when a desktop environment was installed and viewed
from the remote access tool used by Huawei.

To ensure that ARM64 still has the kernel module built, I also downloaded 
linux-modules-extra for 4.15.0-56-generic for ARM64. The hibmc_drm module is
still present in 
/var/lib/modules/4.15.0-56/kernel/drivers/gpu/drm/hisilicon/hibmc
This means that Huawei's arm64 based servers will not be affected by the change.

The fixes solve the problems of the video mode not being right for amd64 based
platforms, and does not cause any regressions for ARM64. I am happy to mark this
as verified.

** Tags removed: verification-needed-bionic verification-needed-disco
** Tags added: verification-done-bionic verification-done-disco

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

Title:
  hibmc-drm Causes Unreadable Display for Huawei amd64 Servers

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1762940

  [Impact]

  amd64 based Huawei servers have problems where the display output of
  their iBMC chips is broken, resulting in a "blurry" screen when viewed
  from their in house remote kvm-like console.

  Example:

  https://launchpadlibrarian.net/365907668/creen_picture_for_blur.png

  The issue is caused by the hibmc_drm kernel module being loaded. The PCI ID 
for the iBMC chips on amd64 hardware is the same as arm64 hardware, but the 
  hibmc_drm driver was developed only for use on arm64 hardware, most notably 
for the Huawei D05 development board.

  The impact to Huawei is that their customers cannot use Ubuntu server install
  media as the screen goes "blurry" when the d-i install media or subuqity
  installer loads the hibmc_drm kernel module after language selection. 

  The only workaround for their customers is to press the "E" key during
  the very first installer menu and adding
  "modprobe.blacklist=hibmc_drm" to the kernel command line in the grub
  menu. This is not good for customer experience with their servers.

  Other problems exist for the hibmc_drm driver on amd64, such as working on 
  bios, but not uefi, and not being wayland compatible, making the screen 
blurry whenever a desktop session is started and gdm loaded.

  Huawei have asked us to remove hibmc_drm from all architectures except arm64,
  and this aligns with advice from Hisilicon.

  [Fix]

  I modified the config/annotations file to remove all architectures
  except arm64, and created a patch for Kconfig to set a firm
  requirement on ARM64 for hibmc_drm.

  I will send the Kconfig patch upstream in the coming days for a more
  permanent fix.

  [Testcase]

  Apply the patches and run:

  ubuntu-bionic/CONFIGS$ fakeroot debian/rules genconfigs
  ubuntu-bionic/CONFIGS$ grep -Rin "hibmc" .
  ./arm64-config.flavour.generic:5739:CONFIG_DRM_HISI_HIBMC=m

  You should see that only arm64 has the config option enabled.

  A test kernel has been built, and is available here:
  https://launchpad.net/~mruffell/+archive/ubuntu/sf232667-test

  Huawei requested a test d-i install iso to test server install with, which 
can be found here and uses the kernel from the ppa above:
  
https://people.canonical.com/~mruffell/sf232667_ubuntu_server_d-i_20190711b1.iso

  Both the test kernel and the custom d-i install iso have been tested on amd64
  Huawei server hardware successfully and video output is functional.

  [Regression Potential]

  Regressions will be limited to hardware containing the iBMC chips from
  Hisilicon, which I believe are exclusive to Huawei servers.

  I have taken care to ensure that hibmc_drm is enabled for ARM64 so it
  should not impact kernels built for the Huawei D05 arm64 development
  board, and d-i will still load the hibmc_drm driver during startup for
  arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+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 1637802] Re: ubuntu 14.04 problem between airplane mode and bluetooth

2019-07-28 Thread SereSte
I went up with ubuntu 16.04 than ubuntu 18.04 but the air-plane mode
problem did not stop. Every time i start ubuntu airplane mode is on than
i switch it off and usually (not every time) bluez goes on

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

Title:
  ubuntu 14.04 problem between airplane mode and bluetooth

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  is very strange because sometime is working but most of the time the 
bluetooth icon is absent and even if you go in System Settings you can not 
switch on bluetooth than  if you start to play with airplane mode switch and 
bluetooth switch some time bluetooth comes a life for sometime than it stop for 
good, anyway to me becomes evident that there is a relation between airplane 
mode and bluetooth, be so nice finding a solution if posible
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-05-30 (153 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: LENOVO 20235
  Package: bluez 4.101-0ubuntu13.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=c89a3965-eb84-4899-abe5-01cf184b6981 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Tags:  trusty
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/17/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 78CN16WW(V1.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G400
  dmi.modalias: 
dmi:bvnLENOVO:bvr78CN16WW(V1.04):bd04/17/2013:svnLENOVO:pn20235:pvrLenovoG400:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG400:
  dmi.product.name: 20235
  dmi.product.version: Lenovo G400
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1637802/+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 1836456] Re: [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend

2019-07-28 Thread Stefano Coronado
@kaihengfeng

Sorry for the delay, I have done this but seem to find little
differences between the two files.

?field.comment=@kaihengfeng

Sorry for the delay, I have done this but seem to find little
differences between the two files.


** Attachment added: "wakeup_sources_before.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836456/+attachment/5279743/+files/wakeup_sources_before.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/1836456

Title:
  [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 18.04.2 on a Lenovo ThinkPad S1 Yoga. Unfortunately
  when I suspend the machine to throw it into my bag, it immediately
  wakes up causing an issue where the machine will run hot in 85 - 90
  degree weather while I am in town.

  This is not a firmware issue as I have downgraded the BIOS and I have
  also observed how it worked fine under Arch Linux. I am not entirely
  sure which package is responsible to interact with acpi under
  Debian/Ubuntu

  $ lsb_release -rd

  Description: Ubuntu 18.04.2 LTS
  Release:  18.04

  Here is my version.log output, I will provide them as separate
  attachments per the guidelines

  Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lalo   1814 F pulseaudio
   /dev/snd/controlC1:  lalo   1814 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/sda3
  InstallationDate: Installed on 2019-07-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20C00063US
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=c9ed5b87-08bb-441b-9d27-ed5b3f05260e ro quiet splash resume=/dev/sda3 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.173.8
  Tags:  bionic
  Uname: Linux 4.18.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET43WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C00063US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET43WW(1.30):bd09/28/2018:svnLENOVO:pn20C00063US:pvrThinkPadS1Yoga:rvnLENOVO:rn20C00063US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad S1 Yoga
  dmi.product.name: 20C00063US
  dmi.product.sku: LENOVO_MT_20C0_BU_Think_FM_ThinkPad S1 Yoga
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836456/+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 1836456] Re: [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend

2019-07-28 Thread Stefano Coronado
After suspend

** Attachment added: "wakeup_sources_after.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836456/+attachment/5279744/+files/wakeup_sources_after.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/1836456

Title:
  [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 18.04.2 on a Lenovo ThinkPad S1 Yoga. Unfortunately
  when I suspend the machine to throw it into my bag, it immediately
  wakes up causing an issue where the machine will run hot in 85 - 90
  degree weather while I am in town.

  This is not a firmware issue as I have downgraded the BIOS and I have
  also observed how it worked fine under Arch Linux. I am not entirely
  sure which package is responsible to interact with acpi under
  Debian/Ubuntu

  $ lsb_release -rd

  Description: Ubuntu 18.04.2 LTS
  Release:  18.04

  Here is my version.log output, I will provide them as separate
  attachments per the guidelines

  Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lalo   1814 F pulseaudio
   /dev/snd/controlC1:  lalo   1814 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/sda3
  InstallationDate: Installed on 2019-07-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20C00063US
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=c9ed5b87-08bb-441b-9d27-ed5b3f05260e ro quiet splash resume=/dev/sda3 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.173.8
  Tags:  bionic
  Uname: Linux 4.18.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET43WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C00063US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET43WW(1.30):bd09/28/2018:svnLENOVO:pn20C00063US:pvrThinkPadS1Yoga:rvnLENOVO:rn20C00063US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad S1 Yoga
  dmi.product.name: 20C00063US
  dmi.product.sku: LENOVO_MT_20C0_BU_Think_FM_ThinkPad S1 Yoga
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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


Re: [Kernel-packages] [Bug 1810210] Re: Kernel 4.15.0-43 crashes laptop on boot

2019-07-28 Thread Aaron
Hi there,

Sorry I'm unable to help with investigating this now as I'm totally 
unable to install Ubuntu onto my laptop now, have reverted to Debian 
instead.

Aaron

On 24/07/2019 23:58, Brad Figg wrote:
> ** Tags added: cscc
>
-- 

*Aaron Mortimer

*



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

Title:
  Kernel 4.15.0-43 crashes laptop on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel from 4.15.0-33 to 4.15.0-43 my laptop no longer
  boots, it crashes when reaching the stage where it says Reached Target
  Encrypted Volumes. Have reverted to 4.15.0-33 in the meantime. Is this
  something that can be rectified?

  Using an ASUS XM553MA laptop.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1222 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-12-06 (27 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X553MA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=7fdad478-0ec8-4191-9c7e-22f837dc7af3 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  tessa
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X553MA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X553MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX553MA.211:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX553MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX553MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X553MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810210/+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 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

2019-07-28 Thread Colin Ian King
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

Status in linux package in Ubuntu:
  In Progress

Bug description:
  == SRU Justification BIONIC HWE, DISCO ==

  Installed Bionic 18.04.2 i386 Desktop (using xubuntu) on a Lenovo
  x220i and upgraded to proposed. The 5.0.0.22 kernel crashes in various
  ways with video corruption being a main visible featured.

  The CPU is a  i3-2350M CPU, a 64 bit capable CPU, being booted with
  EUFI firmware disabled, so using traditional BIOS.

  1. Crashes can be just complete hangs, no ability to switch virtual console
  2. Crashes may just result in screen turning off, no video and hang and/or 
reboot
  3. Crashes sometimes allow virtual console. Can see watchdog hang checks 
appearing on 1 or more CPUs.

  Tried the i386 https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
  kernels:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.21/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.17/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.61/ - OK

  We therefore can conclude:

  1. Issue appears between 4.19.61 and 4.20.17
  2. Issue is in upstream kernel
  3. Issue not a kernel patch per-se (e.g. security fix, ubuntu sauce patch, 
etc)

  I repeated this with a VM installation and I don't see the issue, so
  this probably is a hardware (or firmware?) specific issue.

  == Fix ==

  Backport wiggle of upstream fix

  3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167 ("mm/vmalloc: Sync unmappings
  in __purge_vmap_area_lazy()")

  == Test ==

  Without the fix, i386 xubuntu on various Lenovo platforms crash during
  early boot with random video corruption, hangs,lockups or even
  reboots.

  With the fix, it boots fine.

  == Regression Potential ==

  Higher than normal as this touches the mm sync and the fix has only
  just hit upstream so it has not much of a soak test.  Testing with
  this shows it fixes a kitten killer breakage, so I think the risk vs
  benefit is worth considering

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot

2019-07-28 Thread Peter Lustig
Hey everyone,

is there any update on the issue?
Does the bug still occur with BIOS v. 1.6.1 from 21 Jul 2019?

Thanks in advance for your help.

Regards,
Simon

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

Title:
  [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working
  at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see 
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered 
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1776113] Re: Laptop does not suspend when lid is closed

2019-07-28 Thread Mirko W
Same problem here.

Doesnt work with HandleLidSwitch=suspend commented or uncommented.

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

Title:
  Laptop does not suspend when lid is closed

Status in linux package in Ubuntu:
  Expired

Bug description:
  $ lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  In Tweaks > Power, "Suspend when laptop lid is closed" is ON, but my
  laptop does not suspend when the lid is closed.  The laptop is a
  Thinkpad P50.

  When closing the laptop lid, no events show up in dmesg.

  This is my /etc/systemd/login.conf:

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  HandleLidSwitch=suspend
  HandleLidSwitchDocked=suspend
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  #IdleAction=ignore
  #IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192
  #UserTasksMax=33%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 10 14:16:10 2018
  InstallationDate: Installed on 2018-03-26 (76 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-17 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776113/+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 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

2019-07-28 Thread Colin Ian King
Fix sent to kernel team mailing list for review:
https://lists.ubuntu.com/archives/kernel-team/2019-July/102627.html

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

Title:
  linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

Status in linux package in Ubuntu:
  In Progress

Bug description:
  == SRU Justification BIONIC HWE, DISCO ==

  Installed Bionic 18.04.2 i386 Desktop (using xubuntu) on a Lenovo
  x220i and upgraded to proposed. The 5.0.0.22 kernel crashes in various
  ways with video corruption being a main visible featured.

  The CPU is a  i3-2350M CPU, a 64 bit capable CPU, being booted with
  EUFI firmware disabled, so using traditional BIOS.

  1. Crashes can be just complete hangs, no ability to switch virtual console
  2. Crashes may just result in screen turning off, no video and hang and/or 
reboot
  3. Crashes sometimes allow virtual console. Can see watchdog hang checks 
appearing on 1 or more CPUs.

  Tried the i386 https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
  kernels:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.21/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.17/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.61/ - OK

  We therefore can conclude:

  1. Issue appears between 4.19.61 and 4.20.17
  2. Issue is in upstream kernel
  3. Issue not a kernel patch per-se (e.g. security fix, ubuntu sauce patch, 
etc)

  I repeated this with a VM installation and I don't see the issue, so
  this probably is a hardware (or firmware?) specific issue.

  == Fix ==

  Backport wiggle of upstream fix

  3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167 ("mm/vmalloc: Sync unmappings
  in __purge_vmap_area_lazy()")

  == Test ==

  Without the fix, i386 xubuntu on various Lenovo platforms crash during
  early boot with random video corruption, hangs,lockups or even
  reboots.

  With the fix, it boots fine.

  == Regression Potential ==

  Higher than normal as this touches the mm sync and the fix has only
  just hit upstream so it has not much of a soak test.  Testing with
  this shows it fixes a kitten killer breakage, so I think the risk vs
  benefit is worth considering

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+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 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

2019-07-28 Thread Colin Ian King
** Description changed:

+ == SRU Justification BIONIC HWE ==
+ 
  Installed Bionic 18.04.2 i386 Desktop (using xubuntu) on a Lenovo x220i
  and upgraded to proposed. The 5.0.0.22 kernel crashes in various ways
  with video corruption being a main visible featured.
  
  The CPU is a  i3-2350M CPU, a 64 bit capable CPU, being booted with EUFI
  firmware disabled, so using traditional BIOS.
  
  1. Crashes can be just complete hangs, no ability to switch virtual console
  2. Crashes may just result in screen turning off, no video and hang and/or 
reboot
  3. Crashes sometimes allow virtual console. Can see watchdog hang checks 
appearing on 1 or more CPUs.
  
  Tried the i386 https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
  kernels:
  
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.21/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.17/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.61/ - OK
  
  We therefore can conclude:
  
  1. Issue appears between 4.19.61 and 4.20.17
  2. Issue is in upstream kernel
  3. Issue not a kernel patch per-se (e.g. security fix, ubuntu sauce patch, 
etc)
  
  I repeated this with a VM installation and I don't see the issue, so
  this probably is a hardware (or firmware?) specific issue.
+ 
+ == Fix ==
+ 
+ Backport wiggle of upstream fix
+ 
+ 3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167 ("mm/vmalloc: Sync unmappings
+ in __purge_vmap_area_lazy()")
+ 
+ == Test ==
+ 
+ Without the fix, i386 xubuntu on various Lenovo platforms crash during
+ early boot with random video corruption, hangs,lockups or even reboots.
+ 
+ With the fix, it boots fine.
+ 
+ == Regression Potential ==
+ 
+ Higher than normal as this touches the mm sync and the fix has only just
+ hit upstream so it has not much of a soak test.  Testing with this shows
+ it fixes a kitten killer breakage, so I think the risk vs benefit is
+ worth considering

** Description changed:

- == SRU Justification BIONIC HWE ==
+ == SRU Justification BIONIC HWE, DISCO ==
  
  Installed Bionic 18.04.2 i386 Desktop (using xubuntu) on a Lenovo x220i
  and upgraded to proposed. The 5.0.0.22 kernel crashes in various ways
  with video corruption being a main visible featured.
  
  The CPU is a  i3-2350M CPU, a 64 bit capable CPU, being booted with EUFI
  firmware disabled, so using traditional BIOS.
  
  1. Crashes can be just complete hangs, no ability to switch virtual console
  2. Crashes may just result in screen turning off, no video and hang and/or 
reboot
  3. Crashes sometimes allow virtual console. Can see watchdog hang checks 
appearing on 1 or more CPUs.
  
  Tried the i386 https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
  kernels:
  
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.21/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.17/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.61/ - OK
  
  We therefore can conclude:
  
  1. Issue appears between 4.19.61 and 4.20.17
  2. Issue is in upstream kernel
  3. Issue not a kernel patch per-se (e.g. security fix, ubuntu sauce patch, 
etc)
  
  I repeated this with a VM installation and I don't see the issue, so
  this probably is a hardware (or firmware?) specific issue.
  
  == Fix ==
  
  Backport wiggle of upstream fix
  
  3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167 ("mm/vmalloc: Sync unmappings
  in __purge_vmap_area_lazy()")
  
  == Test ==
  
  Without the fix, i386 xubuntu on various Lenovo platforms crash during
  early boot with random video corruption, hangs,lockups or even reboots.
  
  With the fix, it boots fine.
  
  == Regression Potential ==
  
  Higher than normal as this touches the mm sync and the fix has only just
  hit upstream so it has not much of a soak test.  Testing with this shows
  it fixes a kitten killer breakage, so I think the risk vs benefit is
  worth considering

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

Title:
  linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

Status in linux package in Ubuntu:
  In Progress

Bug description:
  == SRU Justification BIONIC HWE, DISCO ==

  Installed Bionic 18.04.2 i386 Desktop (using xubuntu) on a Lenovo
  x220i and upgraded to proposed. The 5.0.0.22 kernel crashes in various
  ways with video corruption being a main visible featured.

  The CPU is a  i3-2350M CPU, a 64 bit capable CPU, being booted with
  EUFI firmware disabled, so using traditional BIOS.

  1. Crashes can be just complete hangs, no ability to switch virtual console
  2. Crashes may just result in screen turning off, no video and hang and/or 
reboot
  3. Crashes sometimes allow virtual console. Can see watchdog hang checks 
appearing on 1 or more CPUs.

  Tried the i386 https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
  kernels:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.21/ - 

[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2019-07-28 Thread Noname
sorry,reinstalling the kernel package helped

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36.

  [Fix]
  The commit that causes the regression works in mainline, so there are
  some functional dependencies are not in 4.15.

  Finding those dependencies can be hard since I don't have the hardware
  to test with, also pulling new commits may cause new regression. So the
  safest way to deal with this bug is to simply revert the regression
  commit.

  [Test]
  User confirmed reverting the commit can fix the issue.

  [Regression Potential]
  Low. Realtek 8723be works without this commit.

  === Original Bug Report ===
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 
4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

2019-07-28 Thread Colin Ian King
Upstream fix 3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167 resolves the issue
in linux tip:

commit 3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167
Author: Joerg Roedel 
Date:   Fri Jul 19 20:46:52 2019 +0200

mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy()

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

Title:
  linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Installed Bionic 18.04.2 i386 Desktop (using xubuntu) on a Lenovo
  x220i and upgraded to proposed. The 5.0.0.22 kernel crashes in various
  ways with video corruption being a main visible featured.

  The CPU is a  i3-2350M CPU, a 64 bit capable CPU, being booted with
  EUFI firmware disabled, so using traditional BIOS.

  1. Crashes can be just complete hangs, no ability to switch virtual console
  2. Crashes may just result in screen turning off, no video and hang and/or 
reboot
  3. Crashes sometimes allow virtual console. Can see watchdog hang checks 
appearing on 1 or more CPUs.

  Tried the i386 https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
  kernels:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.21/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.17/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.61/ - OK

  We therefore can conclude:

  1. Issue appears between 4.19.61 and 4.20.17
  2. Issue is in upstream kernel
  3. Issue not a kernel patch per-se (e.g. security fix, ubuntu sauce patch, 
etc)

  I repeated this with a VM installation and I don't see the issue, so
  this probably is a hardware (or firmware?) specific issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+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 1835677] Re: Megal33t bug: touchpad with mousewheel is broken >:]

2019-07-28 Thread klfyt
*** This bug is a duplicate of bug 1837783 ***
https://bugs.launchpad.net/bugs/1837783

** This bug has been marked a duplicate of bug 1837783
   Navigating directly back kills performance

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

Title:
  Megal33t bug: touchpad with mousewheel is broken  >:]

Status in linux package in Ubuntu:
  Invalid

Bug description:
  If you don't use mousewheel or touchpad (since reboot) everything will
  be fast and responsive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2019-07-28 Thread Noname
sudo modprobe -rvf rtl8723be
rmmod rtl8723be
rmmod rtl_pci
rmmod rtl8723_common
rmmod btcoexist
rmmod rtlwifi
rmmod mac80211
rmmod cfg80211

sudo modprobe -v rtl8723be -b
insmod /lib/modules/4.15.0-55-lowlatency/kernel/net/wireless/cfg80211.ko 
insmod /lib/modules/4.15.0-55-lowlatency/kernel/net/mac80211/mac80211.ko 
insmod 
/lib/modules/4.15.0-55-lowlatency/kernel/drivers/net/wireless/realtek/rtlwifi/rtlwifi.ko
 
insmod 
/lib/modules/4.15.0-55-lowlatency/kernel/drivers/net/wireless/realtek/rtlwifi/rtl_pci.ko
 
insmod 
/lib/modules/4.15.0-55-lowlatency/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723com/rtl8723-common.ko
 
insmod 
/lib/modules/4.15.0-55-lowlatency/kernel/drivers/net/wireless/realtek/rtlwifi/btcoexist/btcoexist.ko
 
insmod 
/lib/modules/4.15.0-55-lowlatency/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723be/rtl8723be.ko
 fwlps=0 ant_sel=2

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36.

  [Fix]
  The commit that causes the regression works in mainline, so there are
  some functional dependencies are not in 4.15.

  Finding those dependencies can be hard since I don't have the hardware
  to test with, also pulling new commits may cause new regression. So the
  safest way to deal with this bug is to simply revert the regression
  commit.

  [Test]
  User confirmed reverting the commit can fix the issue.

  [Regression Potential]
  Low. Realtek 8723be works without this commit.

  === Original Bug Report ===
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 
4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2019-07-28 Thread Noname
doesn't work on 4.15.0-55

$ lsmod|grep 8723
rtl8723be 126976  0
btcoexist 434176  1 rtl8723be
rtl8723_common 24576  1 rtl8723be
rtl_pci32768  1 rtl8723be
rtlwifi   163840  4 rtl_pci,rtl8723be,btcoexist,rtl8723_common
mac80211  790528  3 rtl_pci,rtl8723be,rtlwifi

$ modinfo rtl8723be -V
kmod version 24
-XZ -ZLIB -EXPERIMENTAL

~/rtlwifi_new$ uname -a
Linux laptop 4.15.0-55-lowlatency #60-Ubuntu SMP PREEMPT Tue Jul 2 19:11:22 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36.

  [Fix]
  The commit that causes the regression works in mainline, so there are
  some functional dependencies are not in 4.15.

  Finding those dependencies can be hard since I don't have the hardware
  to test with, also pulling new commits may cause new regression. So the
  safest way to deal with this bug is to simply revert the regression
  commit.

  [Test]
  User confirmed reverting the commit can fix the issue.

  [Regression Potential]
  Low. Realtek 8723be works without this commit.

  === Original Bug Report ===
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 
4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1832988] Re: Intel 8260 Bluetooth not working

2019-07-28 Thread Kai-Heng Feng
Can you please boot Ubuntu with default kernel, and with kernel
parameter `usbcore.dyndbg=+p`, reproduce the issue, and attach dmesg?

Thanks.

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

Title:
  Intel 8260 Bluetooth not working

Status in gnome-bluetooth package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Expected behaviour:
  I can enable bluetooth in the system settings, and pair with my other devices.

  Actual behaviour:
  Always displays as 'off' in the settings dialog, and won't turn on. 

  Bluetooth worked on the same machine with previous Ubuntu releases
  (18.10) & no hardware changes.

  "dmesg | grep -i bluetooth" reports the following:
  ```
  [   14.445902] Bluetooth: Core ver 2.22
  [   14.445918] Bluetooth: HCI device and connection manager initialized
  [   14.445921] Bluetooth: HCI socket layer initialized
  [   14.445923] Bluetooth: L2CAP socket layer initialized
  [   14.445929] Bluetooth: SCO socket layer initialized
  [   14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [   14.499050] Bluetooth: hci0: Device revision is 5
  [   14.499052] Bluetooth: hci0: Secure boot is enabled
  [   14.499053] Bluetooth: hci0: OTP lock is enabled
  [   14.499053] Bluetooth: hci0: API lock is enabled
  [   14.499054] Bluetooth: hci0: Debug lock is disabled
  [   14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [   14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [   14.558347] Bluetooth: hci0: Failed to send firmware data (-38)
  [   15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.497806] Bluetooth: BNEP filters: protocol multicast
  [   15.497810] Bluetooth: BNEP socket layer initialized
  ```

  "lsb_release -rd" reports the following:
  ```
  Description:  Ubuntu 19.04
  Release:  19.04
  ```
  "cat /proc/version_signature" reports the following:
  ```
  Ubuntu 5.0.0-16.17-generic 5.0.8
  ```

  "apt-cache policy linux-firmware" reports the following:
  ```
  linux-firmware:
Installed: 1.178.1
Candidate: 1.178.1
Version table:
   *** 1.178.1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu disco-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu disco-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.178 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 2314 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 16 12:31:07 2019
  InstallationDate: Installed on 2019-06-02 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 003: ID 5986:066d Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: PC Specialist Limited N15_17RD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N15_17RD
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N15_17RD
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2019-07-28 Thread Noname
doesn't work on 4.15.0-55

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36.

  [Fix]
  The commit that causes the regression works in mainline, so there are
  some functional dependencies are not in 4.15.

  Finding those dependencies can be hard since I don't have the hardware
  to test with, also pulling new commits may cause new regression. So the
  safest way to deal with this bug is to simply revert the regression
  commit.

  [Test]
  User confirmed reverting the commit can fix the issue.

  [Regression Potential]
  Low. Realtek 8723be works without this commit.

  === Original Bug Report ===
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 
4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1838154] Re: Simply snapping terminal window from the outside the screen fixes thermal build up

2019-07-28 Thread klfyt
** Bug watch added: Red Hat Bugzilla #1730272
   https://bugzilla.redhat.com/show_bug.cgi?id=1730272

** Also affects: fedora via
   https://bugzilla.redhat.com/show_bug.cgi?id=1730272
   Importance: Unknown
   Status: Unknown

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1838154

Title:
  Simply snapping terminal window from the outside the screen fixes
  thermal build up

Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown

Bug description:
  
  If you snap terminal window from the outside of screen area
  against the left edge of screen then heat build up stops.

  Or in other words terminal either stops heating or
  gives somehow unknown cooling benefit. Which should be
  really strange.

  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838154/+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 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled

2019-07-28 Thread Anthony Wilson
I have been searching for this bug-report for a few weeks now, and I can 
confirm that I too am experiencing this bug.
After updating from Ubuntu 16.04 LTS to Ubuntu 18.04 LTS, upon first boot I 
experienced a black screen on my laptop (HP Presario V4000 from 2014). The 
backlight was still on and so was the fan, though there was no hard-drive 
activity light. After waiting for around half an hour, I cut the power and 
rebooted.
Upon the second boot, everything worked fine, leading me to beleive it was 
simply a problem after updating. The next day, I booted the laptop again and 
experienced the black screen bug. I soon figured out that it occured every 
second boot (Roughly, sometimes I would experience the bug twice in a row).
I decided to try “Advanced options for Ubuntu”, and selected “Ubuntu, with 
Linux 4.15.0-45-generic”. This worked first try. After testing multiple times, 
I never got a failed boot.
Unfortunately I can confirm that this bug still occurs occasionally when I 
select:
“Ubuntu, with Linux 4.15.0-54-generic” or
“Ubuntu, with Linux 4.15.0-55-generic”.

I’m fine continuing with what I’m currently doing, but I need to
navigate to this option upon every boot, and if a family member were to
attempt to use this laptop, they would probably experience the black
screen and think they broke something.

I’ll wait until a fix comes out for this, until then I’ll wait and see
if anthing else happens.

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

Title:
  x86: mm: early boot problem on i386 with KPTI enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  Commit d653420532d580156c8486686899ea6a9eeb7bf0 in bionic enabled
  kernel page table isolation for x86_32, but also introduced
  regressions. One of them ("BUG_ON() condition in vmalloc_sync_one()")
  has been addressed by bug 1830433, but there are other issues reported
  on i386.

  Specifically on some i386 systems the kernel seems to fail in the
  early stage of boot (black screen and frozen keyboard) with no error
  reported on the console.

  If the kernel is booted with "mitigations=off" and "nopti" the problem
  doesn't happen (that is a clear indication of being a kernel page
  table isolation issue).

  However, users have been reported positive results with the following
  upstream fixes applied (all clean cherry picks), even with mitigations
  *and* kernel page table isolation enabled.

  [Test Case]

  Unfortuantely this problem is not easily reproducible, the kernel
  simply fails to boot (black screen and frozen keyboard) after the GRUB
  prompt, so we don't have a real test case (except asking the bug
  reporters to boot the kernel and see if it works).

  [Fix]

  The following upstream fix seems to resolve (prevent) the problem:

  1d8ca3be86ebc6a38dad8236f45c7a9c61681e78 x86/mm/fault: Allow stack access 
below %rsp
  aa37c51b9421d66f7931c5fdcb9ce80c450974be x86/mm: Break out user address space 
handling
  8fed6239058adfd8b663344e2f448aed1e7a x86/mm: Break out kernel address 
space handling
  164477c2331be75d9bd57fb76704e676b2bcd1cd x86/mm: Clarify hardware vs. 
software "error_code"
  0e664eee65337082be49fbbd2ee24aa0d111d0f2 Revert "perf/core: Make sure the 
ring-buffer is mapped in all page-tables"

  [Regression Potential]

  All upstream fixes, tested on the affected platform, backport changes
  are minimal.

  [Original bug report]

  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE:
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running.
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try 

[Kernel-packages] [Bug 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

2019-07-28 Thread Colin Ian King
Tried today's Linux tip, boots OK, so a reverse bisect to tip should
prove to be instructive on a potential 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/1838115

Title:
  linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Installed Bionic 18.04.2 i386 Desktop (using xubuntu) on a Lenovo
  x220i and upgraded to proposed. The 5.0.0.22 kernel crashes in various
  ways with video corruption being a main visible featured.

  The CPU is a  i3-2350M CPU, a 64 bit capable CPU, being booted with
  EUFI firmware disabled, so using traditional BIOS.

  1. Crashes can be just complete hangs, no ability to switch virtual console
  2. Crashes may just result in screen turning off, no video and hang and/or 
reboot
  3. Crashes sometimes allow virtual console. Can see watchdog hang checks 
appearing on 1 or more CPUs.

  Tried the i386 https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
  kernels:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.21/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.17/ - same issue
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.61/ - OK

  We therefore can conclude:

  1. Issue appears between 4.19.61 and 4.20.17
  2. Issue is in upstream kernel
  3. Issue not a kernel patch per-se (e.g. security fix, ubuntu sauce patch, 
etc)

  I repeated this with a VM installation and I don't see the issue, so
  this probably is a hardware (or firmware?) specific issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+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 1830744] Re: Stuck in 1024x768 resolution. Modeset can't detect VGA EDID on Ivybridge.

2019-07-28 Thread Deep Jari
Daniel & Launchpad Janitor, Thanks for your response.

I am using HP workstation and checking drivers & changing display
options doesn't solved the issue.

When I installed Manjaro using different hard SSD it gave me proper
resolution.

Then I updated from 18.04 to 19.04, using updater option. It went to
18.10 first and then 19.04 & That solved the issue and now I am getting
full resolution.


Thanks for your support and response. Community rocks.

** Changed in: linux (Ubuntu)
   Status: Expired => Fix Released

** Changed in: xorg-server (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  Stuck in 1024x768 resolution. Modeset can't detect VGA EDID on
  Ivybridge.

Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Hey Support ,

  I am not able to get resolution of my Monitor which is 1080P, I
  checked with the cables and its all good. I think drivers are causing
  this issue. Might need help with that.

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 28 20:04:43 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:339a]
  InstallationDate: Installed on 2019-03-12 (77 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Hewlett-Packard HP Compaq Pro 6300 SFF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.90
  dmi.board.asset.tag: SGH333S866
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: SGH333S866
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqPro6300SFF:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Pro 6300 SFF
  dmi.product.sku: QV985AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830744/+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 1837626] Re: bionic/linux: 4.15.0-56.62 -proposed tracker

2019-07-28 Thread Dmitry S. Fedorov
Problem exists in kernel 4.15.0-56.62. Servers worked fine about 1 day
and then unresponsible. I cant to log in via ssh, just only can print
screen via ipmi.


** Attachment added: "2019-07-28_11-12-11.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837626/+attachment/5279713/+files/2019-07-28_11-12-11.png

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

Title:
  bionic/linux: 4.15.0-56.62 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1837622 (xenial/linux-azure), bug 1837625 (xenial/linux-hwe)
  derivatives: bug 1837582 (pc-kernel), bug 1837583 (pc-lowlatency-kernel), bug 
1837586 (linux-raspi2), bug 1837590 (linux-snapdragon), bug 1837593 
(linux-oem), bug 1837599 (linux-aws), bug 1837608 (linux-gcp), bug 1837612 
(linux-gke-4.15), bug 1837613 (linux-kvm), bug 1837614 (linux-ibm-gt), bug 
1837616 (linux-oracle), bug 1837617 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 26. July 2019 09:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1837599
bionic/linux-fips: bug 1837617
bionic/linux-gcp: bug 1837608
bionic/linux-gke-4.15: bug 1837612
bionic/linux-ibm-gt: bug 1837614
bionic/linux-kvm: bug 1837613
bionic/linux-oem: bug 1837593
bionic/linux-oracle: bug 1837616
bionic/linux-raspi2: bug 1837586
bionic/linux-snapdragon: bug 1837590
bionic/linux/pc-kernel: bug 1837582
bionic/linux/pc-lowlatency-kernel: bug 1837583
xenial/linux-azure: bug 1837622
xenial/linux-hwe: bug 1837625
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837626/+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 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21

2019-07-28 Thread Jun Go
Hi Aaron~

I have attached a file containing the output of dmesg and lscpi from kernel 
5.0.0-21
Please let me know if I you need me to provide add'l info.

Thanks,
Jun

** Attachment added: "contains output of dmesg and lscpi requested by Canonical"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+attachment/5279689/+files/disco_19.04_linux-5.0.0-21_dmesg_lspci.md

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

Title:
  realtek r8822be kernel module fails after update to linux kernel-
  headers 5.0.0-21

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part
  of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't
  notice that wifi was no longer working because at work I exclusively
  use a wired Ethernet connection.

  Today, however, when I tried to use my realtek r8822be wireless card,
  I discovered that it was totally unresponsive and did not work with
  wpa_supplicant / wpa_cli even when invoked manually from the command
  line (let alone with NetworkManager). When the problem occurred, I was
  using 19.04's latest kernel 5.0.0-21.

  I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname
  -a" shows that I am using the previous kernel version:

  Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

  With this kernel version as well as linux-headers-5.0.0.20, linux-
  headers-5.0.0-20-generic, my realtek wireless card works fine. While
  booted into 5.0.0-20 kernel, here are the realtek kernel modules that
  are loaded:

  # lsmod | grep r8
  r8822be   692224  0
  mac80211  806912  1 r8822be
  cfg80211  671744  2 mac80211,r8822be
  r8169  81920  0

  Hopefully this realtek wireless regression can get fixed in the next
  minor kernel version. Let me know if you need any more information.

  Best Regards,
  Jun

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+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 1838180] [NEW] apps use speakers when bluetooth headset is active (REGRESSION)

2019-07-28 Thread jimav
Public bug reported:

Bluetooth headset stopped working after upgrading to 19.04.  Worked
perfectly with 18.10.

Now, when a BT headset is connected the volume-control widget (seen via
the speaker icon in the upper-right corner) displays a headset icon and
a volume slider, but the slider has NO EFRFECT on volume and sound still
comes out of the speakers.

It seems like the BT headset is active as far as the volume-control GUI
knows, BUT sound from apps still goes to the speakers (which were active
before the BT headset connected).

syslog shows: bluetoothd[1423]: connect error: Device or resource busy
(16)

I will attach the full syslog

The problem does not occur with a wired headset.

STEPS TO REPRODUCE:
1. Reboot
   Turn Bluetooth OFF (speakericon->BTicon->Turn Off)
2. Start Rhythmbox or other sound source; play something, set the volume low 
but audible
(should be heard on speakers)
3. Turn on a Bluetoogh headset
4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On)
If necessary, do other stuff to get the BT headset connected
   A "headset icon" should appear next the volume slider (click speaker icon to 
see it)

RESULTS: Sound continues to come out of speakers; nothing from BT headset
 Moving the volume slider has no effect

EXPECTED RESULTS: Switch sound to the BT headset

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: bluez 5.50-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 27 22:59:01 2019
InstallationDate: Installed on 2018-04-05 (479 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic 
root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago)
dmi.bios.date: 12/01/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0605
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 48:89:E7:CF:4F:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:14153 acl:154 sco:0 events:971 errors:0
TX bytes:429273 acl:643 sco:0 commands:229 errors:0

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


** Tags: amd64 apport-bug disco

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1838180/+attachment/5279675/+files/syslog

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

Title:
  apps use speakers when bluetooth headset is active (REGRESSION)

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth headset stopped working after upgrading to 19.04.  Worked
  perfectly with 18.10.

  Now, when a BT headset is connected the volume-control widget (seen
  via the speaker icon in the upper-right corner) displays a headset
  icon and a volume slider, but the slider has NO EFRFECT on volume and
  sound still comes out of the speakers.

  It seems like the BT headset is active as far as the volume-control
  GUI knows, BUT sound from apps still goes to the speakers (which were
  active before the BT headset connected).

  syslog shows: bluetoothd[1423]: connect error: Device or resource busy
  (16)

  I will attach the full syslog

  The problem does not occur with a wired headset.

  STEPS TO REPRODUCE:
  1. Reboot
 Turn Bluetooth OFF (speakericon->BTicon->Turn Off)
  2. Start Rhythmbox or other sound source; play something, set the volume low 
but audible
  (should be heard on speakers)
  3. Turn on a Bluetoogh headset
  4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On)
  If necessary, do other stuff to get the BT headset connected
 A "headset icon" should appear next the volume slider (click speaker icon 
to see it)

  RESULTS: Sound continues to come out of speakers; nothing from BT headset
   Moving the volume slider has no effect

  EXPECTED RESULTS: Switch sound to the BT headset

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluez