[Kernel-packages] [Bug 1831037] Re: Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.

2019-06-26 Thread Daniel van Vugt
Thanks.

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

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

Title:
  Acer Aspire ES1-311 - some keyboard keys like D do not respond
  correctly.

Status in linux package in Ubuntu:
  Invalid

Bug description:
  thunderbird - send email
  keyboard from laptop 
  no physical shut down or reeboot

  tried all the information online

  have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 30 11:02:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0938]
  InstallationDate: Installed on 2015-10-28 (1309 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-311
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-311
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.11:rvnAcer:rnAspireES1-311:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: BayTrail
  dmi.product.name: Aspire ES1-311
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon May 21 13:03:46 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831037/+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 1834262] Re: Secondary screen shows a bluish color shift. White turns into a turquoise.

2019-06-25 Thread Daniel van Vugt
This sounds like likely to be a hardware fault. If not a faulty screen
then a faulty connection or faulty cable. Please try replacing the
cable.

It seems there was no secondary screen connected when you opened this
bug. Can you tell us what type of connector you are using?

** Summary changed:

- connecting a new monitor
+ Secondary screen shows a bluish color shift. White turns into a turquoise.

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

** Summary changed:

- Secondary screen shows a bluish color shift. White turns into a turquoise.
+ i915: Secondary screen shows a bluish color shift. White turns into a 
turquoise.

** 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/1834262

Title:
  i915: Secondary screen shows a bluish color shift. White turns into a
  turquoise.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The process with this pc and my tv monitor (an old Sonoko) always takes alot 
with Ubuntu. It takes even a little bit  with Windows on the same device, but 
with this distro (the only one I've ever tried, 19.04) it can even takes 
minutes and even a counter intuitive setup.
  I tried alot of days ago and I hope it can show up in the logs.
  Furthermore the screen no 2, when finally start working, has a color shift. A 
blue-ish shift. From the color the mouse cursor it seems white turns into a 
turquoise.
  I decided to report it now because I thought it was the old tv fault, but 
today I decide to plug a new laptop on that and, even if Windows colors are a 
little bit off, it's not at the same level as this issue

  lsb_release -rd

  Description:  Ubuntu 19.04
  Release:  19.04

  apt-cache policy pkgname

  N: Impossibile trovare il pacchetto pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 26 00:24:28 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.0.0-16-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.0.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0277]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0277]
  InstallationDate: Installed on 2019-06-11 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Latitude E4200
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=3530e372-e9e5-454c-915e-8fa98dfff972 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/18/2008:svnDellInc.:pnLatitudeE4200:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E4200
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834262/+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 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes

2019-06-25 Thread Daniel van Vugt
If this does not work for you:

  apport-collect 1834085

then instead please run:

  apport-cli -u 1834085

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

Title:
  Bluetooth touchpad (Apple Magic Trackpad) disconnects every few
  minutes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently got an Apple's Magic Trackpad. I paired it with Ubuntu
  18.04.2 LTS and worked out of the box, no special drivers needed.

  However, I experience frequent disconnections that last a few seconds
  (5-15 seconds usually), which are quite annoying, as the cursor stops
  responding during that interval. The trackpad connects by itself after
  that period. That usually happens every 20-40 minutes.

  I use the onboard bluetooth device of my laptop. I also have, at the
  same time, two more bluetooth devices (keyboard and mouse) and they do
  not experience that issue, just the trackpad. On ocassion I use
  bluetooth headphones which work just fine.

  First of all:

  Using the command "bluetoothctl" I get the following every time I
  experience a disconnection:

  [CHG] Device F4:1B:A1:33:F9:8D Connected: no
  [CHG] Device F4:1B:A1:33:F9:8D Connected: yes

  Checking "dmesg" I can see more information: (if I am not mistaken,
  this shows 4 disconnections)

  
  [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
  [ 1609.070797] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23
  [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 1676.917377] NET: Registered protocol family 38
  [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0
  [ 1872.815559] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24
  [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
  [ 3101.683100] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
  [ 3110.683929] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
  [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98

  
  And this is what journalctl -b shows at the moment of the 
disconnection/reconnection:

  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: removing device Apple Wireless Trackpad
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option 
"fd" "64" (1,63 m)˜
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - 
Apple Wireless Trackpad: device removed
  de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 
'array' failed
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
UnloadModule: "libinput"
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
systemd-logind: releasing fd for 13:80
  de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown 
main item tag 0x0
  de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: 
input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 
64:5d:86:86:3f:98
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input 
driver specified, ignoring this device.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This 
device may have been added with another device file.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple 
Wireless Trackpad: Applying InputClass "libinput touchpad catchall"
  de juny 13 21:37:50 

[Kernel-packages] [Bug 1834047] Re: [Nvidia Quadro P1000] Xorg driver not loaded and external monitor not recognised

2019-06-25 Thread Daniel van Vugt
I'm not sure, sorry.

I have seen a few bug reports about the new P1000 GPU you have and I
don't know how/if Linux supports it properly yet.

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

Title:
  [Nvidia Quadro P1000] Xorg driver not loaded and external monitor not
  recognised

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Incomplete

Bug description:
  I have BenQ i do not know what number, but it is connected by HDMI to DVI 
cable.
   nvidia-driver-418 is version 418.56-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 24 16:20:03 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   als, master, 5.0.0-16-generic, x86_64: installed
   als, master, 5.0.0-17-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 
[Zbook 17 G5 mobile workstation]) [103c:842f]
  MachineType: HP HP ZBook 17 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.07.00
  dmi.board.name: 842D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.37.00
  dmi.chassis.asset.tag: 5CD8501DGX
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.07.00:bd04/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.37.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 17
  dmi.product.name: HP ZBook 17 G5
  dmi.product.sku: 4QH25EA#BCM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1834047/+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 1834032] Re: Dell Latitude E6320 (Centrino 6205) loses contact with wifi, only to be repaired by restarting the computer

2019-06-25 Thread Daniel van Vugt
Thanks!

Yes indeed the last messages in your kernel log are about wifi:

[ 2136.534045] wlp2s0: deauthenticated from 38:10:d5:9a:84:64 (Reason: 
3=DEAUTH_LEAVING)
[ 2139.876380] iwlwifi :02:00.0: Radio type=0x1-0x2-0x0
[ 2140.168837] iwlwifi :02:00.0: Radio type=0x1-0x2-0x0
[ 2140.257678] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 2140.495703] e1000e: eno1 NIC Link is Down
[ 2140.716943] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 2144.284801] iwlwifi :02:00.0: Radio type=0x1-0x2-0x0
[ 2144.580189] iwlwifi :02:00.0: Radio type=0x1-0x2-0x0
[ 2144.667143] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

When wifi dies it seems the system tries to use ethernet which is also
not connected. But I think the main issue is wifi.

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

Title:
  Dell Latitude E6320 (Centrino 6205) loses contact with wifi, only to
  be repaired by restarting the computer

Status in linux package in Ubuntu:
  New

Bug description:
  Often I receive the message : Problem in ubunt, do you want to send the 
messaage?
  Often my laptop (Dell Latitude) looses contact with wifi, only to be repaired 
by restarting the computer.
  This happens for all after changing a user and a moment of computersleep

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun 24 15:02:44 2019
  DistUpgraded: 2019-05-03 22:15:55,047 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0492]
  InstallationDate: Installed on 2019-05-01 (53 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Latitude E6320
  ProcEnviron:
   LANGUAGE=nl
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=cf82673b-3d94-436d-9879-0993332233ff ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-05-03 (51 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0GJF11
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn0GJF11:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6320
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834032/+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 1820794] Re: [Dell Inspiron 3558] PCI/internal sound card not detected

2019-06-25 Thread Daniel van Vugt
In that case please run:

  sudo dpkg -P oem-audio-hda-daily-dkms

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

Title:
  [Dell Inspiron 3558] PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SOUND ONLY PLAY VIA BLUETOOTH
  AND NOT IN EARPHONE OR LAPTOP

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-168.218-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-168-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Tue Mar 19 10:08:35 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-10-29 (1236 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0XCR91
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820794/+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 1834032] Re: Dell Latitude loses contact with wifi, only to be repaired by restarting the computer

2019-06-25 Thread Daniel van Vugt
OK, next time the wifi stops working, before rebooting, please run:

  dmesg > curdmesg.txt

and send us the file 'cusdmesg.txt'.


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

** Summary changed:

- Dell Latitude loses contact with wifi, only to be repaired by restarting the 
computer
+ Dell Latitude E6320 (Centrino 6205) loses contact with wifi, only to be 
repaired by restarting the computer

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

Title:
  Dell Latitude E6320 (Centrino 6205) loses contact with wifi, only to
  be repaired by restarting the computer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Often I receive the message : Problem in ubunt, do you want to send the 
messaage?
  Often my laptop (Dell Latitude) looses contact with wifi, only to be repaired 
by restarting the computer.
  This happens for all after changing a user and a moment of computersleep

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun 24 15:02:44 2019
  DistUpgraded: 2019-05-03 22:15:55,047 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0492]
  InstallationDate: Installed on 2019-05-01 (53 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Latitude E6320
  ProcEnviron:
   LANGUAGE=nl
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=cf82673b-3d94-436d-9879-0993332233ff ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-05-03 (51 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0GJF11
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn0GJF11:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6320
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834032/+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 1834047] Re: [Nvidia Quadro P1000] Xorg driver not loaded and external monitor not recognised

2019-06-25 Thread Daniel van Vugt
** Summary changed:

- External monitor not recognised [Quadro P1000 Mobile]
+ [Nvidia Quadro P1000] Xorg driver not loaded and external monitor not 
recognised

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

Title:
  [Nvidia Quadro P1000] Xorg driver not loaded and external monitor not
  recognised

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Incomplete

Bug description:
  I have BenQ i do not know what number, but it is connected by HDMI to DVI 
cable.
   nvidia-driver-418 is version 418.56-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 24 16:20:03 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   als, master, 5.0.0-16-generic, x86_64: installed
   als, master, 5.0.0-17-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 
[Zbook 17 G5 mobile workstation]) [103c:842f]
  MachineType: HP HP ZBook 17 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.07.00
  dmi.board.name: 842D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.37.00
  dmi.chassis.asset.tag: 5CD8501DGX
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.07.00:bd04/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.37.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 17
  dmi.product.name: HP ZBook 17 G5
  dmi.product.sku: 4QH25EA#BCM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1834047/+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 1834047] Re: External monitor not recognised

2019-06-25 Thread Daniel van Vugt
OK, thanks.

Yes I can now see one 1920x1080 display is connected via eDP (laptop) to
the Intel GPU.

I can't tell which GPU the external monitor is wired to. Sometimes
laptops will wire an external port to the Nvidia GPU and sometimes they
are wired to the Intel GPU like the laptop screen is.

One immediate problem I can see is that the Nvidia X driver is not
loaded so if any ports were connected to the Nvidia GPU then those
monitors would indeed be missing...

Please try reinstalling the Nvidia driver using this command in a
terminal:

  sudo apt install --reinstall nvidia-driver-418

and then reboot.


** Summary changed:

- External monitor not recognised
+ External monitor not recognised [Quadro P1000 Mobile]

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

Title:
  [Nvidia Quadro P1000] Xorg driver not loaded and external monitor not
  recognised

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Incomplete

Bug description:
  I have BenQ i do not know what number, but it is connected by HDMI to DVI 
cable.
   nvidia-driver-418 is version 418.56-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 24 16:20:03 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   als, master, 5.0.0-16-generic, x86_64: installed
   als, master, 5.0.0-17-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 
[Zbook 17 G5 mobile workstation]) [103c:842f]
  MachineType: HP HP ZBook 17 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.07.00
  dmi.board.name: 842D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.37.00
  dmi.chassis.asset.tag: 5CD8501DGX
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.07.00:bd04/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.37.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 17
  dmi.product.name: HP ZBook 17 G5
  dmi.product.sku: 4QH25EA#BCM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1834047/+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 1820794] Re: [Dell Inspiron 3558] PCI/internal sound card not detected

2019-06-24 Thread Daniel van Vugt
** Tags added: xenial

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

Title:
  [Dell Inspiron 3558] PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SOUND ONLY PLAY VIA BLUETOOTH
  AND NOT IN EARPHONE OR LAPTOP

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-168.218-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-168-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Tue Mar 19 10:08:35 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-10-29 (1236 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0XCR91
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820794/+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 1834053] Re: [Inspiron 3558] PCI/internal sound card not detected

2019-06-24 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1820794 ***
https://bugs.launchpad.net/bugs/1820794

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1820794, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- PCI/internal sound card not detected
+ [Inspiron 3558] PCI/internal sound card not detected

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

** This bug has been marked a duplicate of bug 1820794
   [Dell Inspiron 3558] PCI/internal sound card not detected

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

Title:
  [Inspiron 3558] PCI/internal sound card not detected

Status in linux package in Ubuntu:
  New

Bug description:
  No sound as my pc does not detect sound hardware

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun 24 20:39:45 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2016-11-06 (960 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to xenial on 2019-06-24 (0 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0XCR91
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/06/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834053/+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 1834112] Re: the mouse stopped responding to commands

2019-06-24 Thread Daniel van Vugt
1. Which mouse is having the problem? You seem to have at least two mice
connected.

2. Please remove these from your kernel command line options:

   drm.debug=0xe plymouth:debug

   and then reboot.

3. Wait for the problem to happen again and then please immediately run:

   dmesg > newdmesg.txt

   and send us the file 'newdmesg.txt'.


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

** 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/1834112

Title:
  the mouse stopped responding to commands

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the mouse stopped responding to commands

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jun 24 21:21:31 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335]
  InstallationDate: Installed on 2019-03-27 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406
  dmi.board.name: P5N-E SLI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~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
  xserver.bootTime: Wed Apr 24 21:29:22 2019

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834112/+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 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes

2019-06-24 Thread Daniel van Vugt
Also, please try a newer kernel like:

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

or

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

and tell us if either of those improve the situation.

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

Title:
  Bluetooth touchpad (Apple Magic Trackpad) disconnects every few
  minutes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently got an Apple's Magic Trackpad. I paired it with Ubuntu
  18.04.2 LTS and worked out of the box, no special drivers needed.

  However, I experience frequent disconnections that last a few seconds
  (5-15 seconds usually), which are quite annoying, as the cursor stops
  responding during that interval. The trackpad connects by itself after
  that period. That usually happens every 20-40 minutes.

  I use the onboard bluetooth device of my laptop. I also have, at the
  same time, two more bluetooth devices (keyboard and mouse) and they do
  not experience that issue, just the trackpad. On ocassion I use
  bluetooth headphones which work just fine.

  First of all:

  Using the command "bluetoothctl" I get the following every time I
  experience a disconnection:

  [CHG] Device F4:1B:A1:33:F9:8D Connected: no
  [CHG] Device F4:1B:A1:33:F9:8D Connected: yes

  Checking "dmesg" I can see more information: (if I am not mistaken,
  this shows 4 disconnections)

  
  [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
  [ 1609.070797] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23
  [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 1676.917377] NET: Registered protocol family 38
  [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0
  [ 1872.815559] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24
  [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
  [ 3101.683100] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
  [ 3110.683929] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
  [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98

  
  And this is what journalctl -b shows at the moment of the 
disconnection/reconnection:

  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: removing device Apple Wireless Trackpad
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option 
"fd" "64" (1,63 m)˜
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - 
Apple Wireless Trackpad: device removed
  de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 
'array' failed
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
UnloadModule: "libinput"
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
systemd-logind: releasing fd for 13:80
  de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown 
main item tag 0x0
  de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: 
input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 
64:5d:86:86:3f:98
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input 
driver specified, ignoring this device.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This 
device may have been added with another device file.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16)
  de juny 13 21:37:50 TM1703 

[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes

2019-06-24 Thread Daniel van Vugt
The above log looks like a kernel issue (if not a hardware issue).


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

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

Title:
  Bluetooth touchpad (Apple Magic Trackpad) disconnects every few
  minutes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently got an Apple's Magic Trackpad. I paired it with Ubuntu
  18.04.2 LTS and worked out of the box, no special drivers needed.

  However, I experience frequent disconnections that last a few seconds
  (5-15 seconds usually), which are quite annoying, as the cursor stops
  responding during that interval. The trackpad connects by itself after
  that period. That usually happens every 20-40 minutes.

  I use the onboard bluetooth device of my laptop. I also have, at the
  same time, two more bluetooth devices (keyboard and mouse) and they do
  not experience that issue, just the trackpad. On ocassion I use
  bluetooth headphones which work just fine.

  First of all:

  Using the command "bluetoothctl" I get the following every time I
  experience a disconnection:

  [CHG] Device F4:1B:A1:33:F9:8D Connected: no
  [CHG] Device F4:1B:A1:33:F9:8D Connected: yes

  Checking "dmesg" I can see more information: (if I am not mistaken,
  this shows 4 disconnections)

  
  [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
  [ 1609.070797] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23
  [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 1676.917377] NET: Registered protocol family 38
  [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0
  [ 1872.815559] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24
  [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
  [ 3101.683100] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
  [ 3110.683929] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
  [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98

  
  And this is what journalctl -b shows at the moment of the 
disconnection/reconnection:

  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: removing device Apple Wireless Trackpad
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option 
"fd" "64" (1,63 m)˜
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - 
Apple Wireless Trackpad: device removed
  de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 
'array' failed
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
UnloadModule: "libinput"
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
systemd-logind: releasing fd for 13:80
  de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown 
main item tag 0x0
  de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: 
input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 
64:5d:86:86:3f:98
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input 
driver specified, ignoring this device.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This 
device may have been added with another device file.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple 
Wireless Trackpad: Applying InputClass "libinput touchpad catchall"
  de 

[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes

2019-06-24 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1834085

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.


** 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/1834085

Title:
  Bluetooth touchpad (Apple Magic Trackpad) disconnects every few
  minutes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently got an Apple's Magic Trackpad. I paired it with Ubuntu
  18.04.2 LTS and worked out of the box, no special drivers needed.

  However, I experience frequent disconnections that last a few seconds
  (5-15 seconds usually), which are quite annoying, as the cursor stops
  responding during that interval. The trackpad connects by itself after
  that period. That usually happens every 20-40 minutes.

  I use the onboard bluetooth device of my laptop. I also have, at the
  same time, two more bluetooth devices (keyboard and mouse) and they do
  not experience that issue, just the trackpad. On ocassion I use
  bluetooth headphones which work just fine.

  First of all:

  Using the command "bluetoothctl" I get the following every time I
  experience a disconnection:

  [CHG] Device F4:1B:A1:33:F9:8D Connected: no
  [CHG] Device F4:1B:A1:33:F9:8D Connected: yes

  Checking "dmesg" I can see more information: (if I am not mistaken,
  this shows 4 disconnections)

  
  [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
  [ 1609.070797] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23
  [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 1676.917377] NET: Registered protocol family 38
  [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0
  [ 1872.815559] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24
  [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
  [ 3101.683100] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
  [ 3110.683929] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
  [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98

  
  And this is what journalctl -b shows at the moment of the 
disconnection/reconnection:

  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: removing device Apple Wireless Trackpad
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option 
"fd" "64" (1,63 m)˜
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - 
Apple Wireless Trackpad: device removed
  de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 
'array' failed
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
UnloadModule: "libinput"
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
systemd-logind: releasing fd for 13:80
  de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown 
main item tag 0x0
  de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: 
input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 
64:5d:86:86:3f:98
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input 
driver specified, ignoring this device.
  de juny 13 21:37:50 TM1703 

[Kernel-packages] [Bug 1834047] Re: External monitor not recognised

2019-06-24 Thread Daniel van Vugt
> I have BenQ i do not know what number, but it is connected by HDMI to
DVI cable.

Does that mean you are trying to connect two monitors or only one?
Because the system is recognising one 1920x1080 monitor on a
DisplayPort.

** Tags added: nvidia

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-418
(Ubuntu)

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: New => Incomplete

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

Title:
  External monitor not recognised

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Incomplete

Bug description:
  I have BenQ i do not know what number, but it is connected by HDMI to DVI 
cable.
   nvidia-driver-418 is version 418.56-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 24 16:20:03 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   als, master, 5.0.0-16-generic, x86_64: installed
   als, master, 5.0.0-17-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 
[Zbook 17 G5 mobile workstation]) [103c:842f]
  MachineType: HP HP ZBook 17 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.07.00
  dmi.board.name: 842D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.37.00
  dmi.chassis.asset.tag: 5CD8501DGX
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.07.00:bd04/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.37.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 17
  dmi.product.name: HP ZBook 17 G5
  dmi.product.sku: 4QH25EA#BCM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1834047/+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 1833617] Re: [amdgpu] screen freeze after suspend

2019-06-24 Thread Daniel van Vugt
Recovery mode should work, but that does sound like a different bug.

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

Title:
  [amdgpu] screen freeze after suspend

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  It's most likely amdgup driver needs an upgrade. Problem occurs since
  kernel upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2019-06-06 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  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/1833617/+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 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-24 Thread Daniel van Vugt
Upstream is against changing mutter for this, so "Won't Fix" to mutter.
But the fix for gdm3 has landed and that's enough to resolve the bug.

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

** Changed in: mutter (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in GNOME Shell:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.

  * Add a line to /usr/lib/udev/rules.d/61-gdm.rules:
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1705369/+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 1833855] Re: video card

2019-06-23 Thread Daniel van Vugt
There is a slight chance this is a kernel bug, so I am assigning it
there.

I've seen a few reports of people having trouble with analogue VGA
connections not detecting EDIDs, resulting in low resolution.

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

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

** Summary changed:

- video card
+ i915: EDID not detected on VGA resulting in low resolution

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

Title:
  i915: EDID not detected on VGA resulting in low resolution

Status in linux package in Ubuntu:
  New

Bug description:
  hi!  some problem.  i have an video intel graphic card Q965 but i dont
  have any hi-resolution like 1080.  i'm in vga mode only.  Can you help
  me?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 23 09:58:42 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da]
 Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da]
  InstallationDate: Installed on 2019-06-18 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. OptiPlex 745
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=017d360b-c7a7-47e3-8d37-669b93a45647 ro quiet splash 
video=hyperv_fb:1280x720 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.4
  dmi.board.name: 0GW726
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.4:bd03/01/2010:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0GW726:rvr:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.98+git1906111830.5db0f7~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906191930.9c19d0~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1906191930.9c19d0~oibaf~b
  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/1833855/+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 1833829] Re: High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390

2019-06-23 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia
  390

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  After some continued use of the system (Kubuntu (18.04)) Xorg
  accumulates a lot of RAM space. From that the space only increments
  and doesn't decrease.

  Hardware Specs :

  1. Intel core-i5 6300 HQ
  2. Nvidia GTX 960M

  Software Specs :

  1. Kubuntu 18.04
  2. KDE Plasma shell version 5.12.7

  Something interesting to note is that I have not experienced the same
  behavior from Xorg when I switch the GPU to Intel's Integrated
  graphics. It is entirely possible that I might not have been able to
  trigger those situation with Intel, because after seeing logs I
  couldn't make out why this was happening.

  Also for the timeline I have used the system for over an year without
  any such issue arising. It was the second week of June 2019 to present
  day I have seen this problem.

  Xorg log : http://paste.ubuntu.com/p/nc3pMF4xsb/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Jun 23 05:06:48 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.116, 4.18.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:0706]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706]
  InstallationDate: Installed on 2019-06-21 (1 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 413c:301a Dell Computer Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=f046965f-7377-42b2-86ba-febdbcabfc9b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0H87XC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.7:bd12/13/2017:svnDellInc.:pnInspiron7559:pvr1.2.7:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.sku: 0706
  dmi.product.version: 1.2.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1833829/+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 1833617] Re: [amdgpu] screen freeze after suspend

2019-06-23 Thread Daniel van Vugt
Thanks. That kernel log seems to show the machine never wakes up!

Jun 21 08:44:15 meiradmin-Inspiron-3180 systemd[1]: Reached target Sleep.
Jun 21 08:44:15 meiradmin-Inspiron-3180 systemd[1]: Starting Suspend...
Jun 21 08:44:15 meiradmin-Inspiron-3180 systemd-sleep[2384]: Suspending 
system...
Jun 21 08:44:15 meiradmin-Inspiron-3180 kernel: PM: suspend entry (deep)

So I will assign this to the kernel too.

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Incomplete => New

** 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/1833617

Title:
  [amdgpu] screen freeze after suspend

Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  It's most likely amdgup driver needs an upgrade. Problem occurs since
  kernel upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2019-06-06 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  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/1833617/+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 1832436] Re: login page first appears sideways for Lenovo miix 510 ubuntu 18.04 and 18.10

2019-06-23 Thread Daniel van Vugt
** Package changed: gdm3 (Ubuntu) => linux (Ubuntu)

** No longer affects: ubuntu

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

Title:
  login page first appears sideways  for Lenovo miix 510 ubuntu 18.04
  and 18.10

Status in linux package in Ubuntu:
  New

Bug description:
  I have experienced this for ubuntu 18.04 and 18.10 on a Lenovo Miix
  510 laptop. This problem is fixed on ubuntu 19.04

  The login page appears sideways (the mouse orientation is sideways
  also). After logging in the screen is corrected. I believe the issue
  lies with the detection of the accelerometer or perhaps the driver of
  the accelerometer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832436/+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 1832133] Re: Mouse unresponsive on Ubuntu 18.04

2019-06-23 Thread Daniel van Vugt
Thanks for that kernel log. It looks like a faulty mouse (or port) to
me.

Try a different USB port. Then if the problem still happens I would
recommend replacing the mouse.

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

Title:
  Mouse unresponsive on Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi there,

  I submitted this bug report following advice in
  https://wiki.ubuntu.com/DebuggingMouseDetection

  I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart
  15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
  rarely boot up Windows.

  I use an optical mouse attached to my computer by USB cable. It works
  perfectly on Windows. But on Ubuntu, it will work OK for a couple of
  seconds, but then become less and less responsive, to the point where
  it barely works at all.

  I have a touchpad that works perfectly in both Windows and Ubuntu.

  Result of lsb_release -rd: Description:   Ubuntu 18.04.2 LTS. Release:
18.04
  I am using Xdiagnose version 3.8.8

  Please help!

  Tom.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 17:03:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b]
  InstallationDate: Installed on 2018-01-22 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct 31 01:15:25 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832133/+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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Daniel van Vugt
In isolation I don't think it's correct to say that Wayland sessions
have "no external monitors". Wayland sessions do work with external
monitors on the Nvidia driver if you have nvidia-drm.modeset=1. I've
confirmed this on a desktop at least.

It sounds like you're describing some other laptop-specific or Optimus-
specific bug. So I think to avoid confusion that should have its own
separate bug report.

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-06-20 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640

** This bug has been marked a duplicate of bug 1793640
   Pulseaudio fails to detect sound card, while timidity is installed

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Daniel van Vugt
Actually, maybe those other DMs don't run as root. My memory is failing.
So again maybe we do want a similar workaround in gdm3. But that doesn't
seem to be the root cause of the bug.

** Changed in: gdm3 (Ubuntu)
   Status: Invalid => Opinion

** No longer affects: mutter (Ubuntu)

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Daniel van Vugt
> If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)

I don't understand the question, sorry. The statement "it won't work" is
wrong. Wayland does work. This bug is about Xorg, not Wayland.

> So it looks like a gdm3 bug.

Yes I understand that's how it looks, but we have established the root
cause of this bug is in the Nvidia driver. Maybe we will be able to work
around it with some gdm3 change, but that's not where the root cause of
the problem is.

Other display managers are managing to work around the Nvidia driver bug
here because they run as root. gdm3 does not run as root because it is
trying to be more secure and avoid running as root. Calling this a gdm3
bug is probably wrong. I can reproduce the bug without gdm3.

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Daniel van Vugt
Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind
of pointless. It's pointless because the most common reason for using
nvidia-drm.modeset=1 is to get Wayland support. I know there are other
reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in
PRIME setups. But mostly if people use modeset=1 it is to get Wayland
support.

If we can't get a fix from Nvidia then some kind of workaround that runs
Xorg as root (like comment #26) is probably the next best option.

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Daniel van Vugt
Workaround for mutter proposed here:

https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1833514] Re: System shutting down

2019-06-20 Thread Daniel van Vugt
Please:

  1. Wait till the problem happens again and let the system shut down.

  2. Power up the system and then run:

 journalctl -b-1 > prevboot.txt

  3. Attach the file 'prevboot.txt' to this bug.

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

** 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/1833514

Title:
  System shutting down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the system shuts down automatically withouot  any warnings. using sony
  vaio laptop with only ubuntu installed on it.

  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: Thu Jun 20 14:27:14 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [104d:90a8]
  InstallationDate: Installed on 2019-05-30 (20 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Sony Corporation SVT13113ENS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=6918c007-6332-40ec-bbb1-a5d8ff4c287a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0190E4
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0190E4:bd04/30/2012:svnSonyCorporation:pnSVT13113ENS:pvrC903CUWG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVT13113ENS
  dmi.product.sku: N/A
  dmi.product.version: C903CUWG
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~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/1833514/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Daniel van Vugt
And the problem is indeed the kernel advertising
DRM_CAP_TIMESTAMP_MONOTONIC but instead of using CLOCK_MONOTONIC it is
really using CLOCK_REALTIME. This confirms kernel commit 37efe80ce85f is
the fix, but it may well have some prerequisite commits we haven't fully
worked out...

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

I'll see if I can hack around it, but the simplicity of the mistake in
the vmwgfx kernel code makes me think we should be preferring a kernel
fix still.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Daniel van Vugt
I am now able to reproduce and debug the problem. Indeed it is what I
said in comment #31.

The vmwgfx driver in this old kernel is telling lies. It says the next
screen refresh is in 49 years from now. It should be within 16.6
milliseconds.


** Summary changed:

- Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or 
using WaylandEnable=false) fixes it
+ Login screen never appears on vmwgfx using bionic kernel 4.15

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1760729] Re: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez]

2019-06-20 Thread Daniel van Vugt
Yeah it doesn't matter it comment #8 is wrong here. I was going to wait
till the commit is released and then confirm the crash has stopped
happening.

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

Title:
  pulseaudio crashed during playback with SIGABRT in set_nonblock() from
  pa_make_fd_nonblock() from setup_stream() [bluez] from
  setup_transport_and_stream() [bluez]

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c
  https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d
  https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d

  ---

  Pulseaudio crashed randomly while watching a YouTube video in
  fullscreen. When crashing the last 1 second or so of audio looped for
  a few seconds, then cut out. I am using PulseEffects as well, which
  crashed around the same time. Whether that was the cause or a result
  of the PulseAudio crash is unclear.

  I am using Bionic because the video drivers for my AMD Raven Ridge
  iGPU are not supported by earlier versions.

  ~ $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  ~ $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:11.1-1ubuntu7
    Candidate: 1:11.1-1ubuntu7
    Version table:
   *** 1:11.1-1ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ben3375 F pulseaudio
   /dev/snd/controlC0:  ben3375 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Apr  2 19:23:48 2018
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2018-03-25 (8 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
   ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
   ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
   ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  Title: pulseaudio crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350N-Gaming WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/01/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350N-Gaming WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1760729/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-20 Thread Daniel van Vugt
It seems I stumbled on a workaround. Just install the kernel that comes
in the 18.04.2 ISO:

https://launchpad.net/ubuntu/+source/linux-hwe

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

** Changed in: linux-hwe (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: linux-hwe (Ubuntu Eoan)
   Status: New => Invalid

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-20 Thread Daniel van Vugt
Using VirtualBox 6 and VMSVGA as recommended by Eric I still can't
reproduce the bug. But I think I can see why now: Ubuntu 18.04.2 comes
with kernel 4.18

Let me try 18.04.1...

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-19 Thread Daniel van Vugt
It also sounds like VirtualBox might allow me to reproduce the bug...

** Changed in: mutter (Ubuntu Bionic)
   Status: Incomplete => In Progress

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-19 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Bionic)
   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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in mutter source package in Bionic:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-19 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Bionic)
   Status: Won't Fix => 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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in mutter source package in Bionic:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-19 Thread Daniel van Vugt
> Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?

Technically it was a whole point release. The trigger could be any
change that went into mutter 3.28.4 as well as any Ubuntu patch. As
mentioned in comment #31, my suspicion is this specific change:
https://gitlab.gnome.org/GNOME/mutter/commit/e9e4b2b72

> Just to look at our option (since a kernel fix might be not end up
being trivial) does a revert of the change could be a possibility here ?

If the issue turns out to be commit e9e4b2b72 above then no. Because too
many people benefit vs the possible number of people affected by this
bug. But we also aren't completely sure that's the relevant mutter
commit.

If only I could reproduce this bug I could probably write a workaround
(or fix) for it in mutter.

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in mutter source package in Bionic:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working

2019-06-19 Thread Daniel van Vugt
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

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

[Kernel-packages] [Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-19 Thread Daniel van Vugt
** Description changed:

  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).
  
  WORKAROUNDS (you only need one):
  
  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf
  
  * Disable integrated graphics/GPU in your BIOS
  
  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.
+ 
+ * Add a line to /usr/lib/udev/rules.d/61-gdm.rules:
+   DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
  
  ORIGINAL DESCRIPTION:
  
  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.
  
  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.
  
  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04
  
  I am using Nvidia GTX 1080 and Intel i7-4790K
  
  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  
  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  
  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in GNOME Shell:
  New
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.

  * Add a line to /usr/lib/udev/rules.d/61-gdm.rules:
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1705369/+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 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-19 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu)
   Status: Won't Fix => In Progress

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in GNOME Shell:
  New
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1705369/+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 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-19 Thread Daniel van Vugt
Oops. It appears upstream already fixed this bug. And we removed their
fix in Ubuntu (revert_nvidia_wayland_blacklist.patch in gdm3). If you
revert that revert then the bug is fixed.

** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gdm3 (Ubuntu)
   Status: Invalid => In Progress

** Changed in: gdm3 (Ubuntu)
   Importance: Undecided => High

** Changed in: mutter (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in GNOME Shell:
  New
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1705369/+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 1760729] Re: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez]

2019-06-18 Thread Daniel van Vugt
It looks like commit 4762aa45d9ea2f5146a135eda6b840bf3964b317 is the fix
here. Not sure. It's not in any official PulseAudio release yet.

** Description changed:

+ https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c
+ https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d
+ https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d
+ 
+ ---
+ 
  Pulseaudio crashed randomly while watching a YouTube video in
  fullscreen. When crashing the last 1 second or so of audio looped for a
  few seconds, then cut out. I am using PulseEffects as well, which
  crashed around the same time. Whether that was the cause or a result of
  the PulseAudio crash is unclear.
  
  I am using Bionic because the video drivers for my AMD Raven Ridge iGPU
  are not supported by earlier versions.
  
  ~ $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  
  ~ $ apt-cache policy pulseaudio
  pulseaudio:
-   Installed: 1:11.1-1ubuntu7
-   Candidate: 1:11.1-1ubuntu7
-   Version table:
-  *** 1:11.1-1ubuntu7 500
- 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1:11.1-1ubuntu7
+   Candidate: 1:11.1-1ubuntu7
+   Version table:
+  *** 1:11.1-1ubuntu7 500
+ 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  ben3375 F pulseaudio
-  /dev/snd/controlC0:  ben3375 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  ben3375 F pulseaudio
+  /dev/snd/controlC0:  ben3375 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Apr  2 19:23:48 2018
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2018-03-25 (8 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
-  ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
-  ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
-  ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
-  ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
-  ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
+  ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
+  ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
+  ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
+  ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
+  ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  Title: pulseaudio crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350N-Gaming WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/01/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350N-Gaming WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Tags added: disco

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

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

Title:
  pulseaudio crashed during playback with SIGABRT in set_nonblock() from
  pa_make_fd_nonblock() from setup_stream() [bluez] from
  setup_transport_and_stream() [bluez]

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c
  https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d
  https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d

  ---

  Pulseaudio crashed randomly 

[Kernel-packages] [Bug 1760729] Re: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez]

2019-06-18 Thread Daniel van Vugt
** Information type changed from Private to Public

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

Title:
  pulseaudio crashed during playback with SIGABRT in set_nonblock() from
  pa_make_fd_nonblock() from setup_stream() [bluez] from
  setup_transport_and_stream() [bluez]

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c
  https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d
  https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d

  ---

  Pulseaudio crashed randomly while watching a YouTube video in
  fullscreen. When crashing the last 1 second or so of audio looped for
  a few seconds, then cut out. I am using PulseEffects as well, which
  crashed around the same time. Whether that was the cause or a result
  of the PulseAudio crash is unclear.

  I am using Bionic because the video drivers for my AMD Raven Ridge
  iGPU are not supported by earlier versions.

  ~ $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  ~ $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:11.1-1ubuntu7
    Candidate: 1:11.1-1ubuntu7
    Version table:
   *** 1:11.1-1ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ben3375 F pulseaudio
   /dev/snd/controlC0:  ben3375 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Apr  2 19:23:48 2018
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2018-03-25 (8 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
   ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
   ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
   ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  Title: pulseaudio crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350N-Gaming WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/01/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350N-Gaming WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1760729/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-18 Thread Daniel van Vugt
Thanks Pat.

That seems to confirm the 'regression-update' tag here. Although I
wouldn't be able to debug and fix the mutter change because I can't
reproduce the bug, using VMware. Mine just works :/

It sounds like good progress is being made in the kernel anyway. So I
think a fix there would be preferable. Otherwise I would just be hunting
for a way to cripple mutter to work around apparent VMware driver bugs.

** Changed in: mutter (Ubuntu Bionic)
   Status: Incomplete => Won't 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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in mutter source package in Bionic:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-18 Thread Daniel van Vugt
Card archived: https://trello.com/c/gn0J5Qgb

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in mutter source package in Bionic:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1831037] Re: Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.

2019-06-18 Thread Daniel van Vugt
The information we have here is based on what you said in comment #3:

When I press on the keyboard then
a = a
s= s
d = refresh 

Can you elaborate on that?

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

Title:
  Acer Aspire ES1-311 - some keyboard keys like D do not respond
  correctly.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  thunderbird - send email
  keyboard from laptop 
  no physical shut down or reeboot

  tried all the information online

  have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 30 11:02:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0938]
  InstallationDate: Installed on 2015-10-28 (1309 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-311
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-311
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.11:rvnAcer:rnAspireES1-311:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: BayTrail
  dmi.product.name: Aspire ES1-311
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon May 21 13:03:46 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831037/+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 1833265] Re: computer takes ages to start

2019-06-18 Thread Daniel van Vugt
The main problem I can see here is that your kernel graphics driver
keeps crashing, which always starts with:

[   66.888620] vblank wait timed out on crtc 1


** Summary changed:

- laptop reported that there is a problem
+ computer takes ages to start

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

** Summary changed:

- computer takes ages to start
+ computer takes ages to start (Pentium T2390 + GM965)

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

Title:
  computer takes ages to start (Pentium T2390 + GM965)

Status in linux package in Ubuntu:
  New

Bug description:
  computer takes ages to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompositorRunning: None
  Date: Tue Jun 18 15:37:29 2019
  DistUpgraded: 2018-10-26 13:01:13,910 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated 
Graphics Controller (primary) [1179:ff64]
 Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated 
Graphics Controller (secondary) [1179:ff64]
  InstallationDate: Installed on 2016-03-15 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  MachineType: TOSHIBA Satellite L300
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=f510ae88-8078-4876-a589-6f3bbdcc970d ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-10-26 (235 days ago)
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.40:bd05/28/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-02H00SEN:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite L300
  dmi.product.version: PSLB0E-02H00SEN
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Oct 26 09:59:10 2018
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   14145 
   vendor SEC
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833265/+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 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-18 Thread Daniel van Vugt
Fix proposed: https://gitlab.gnome.org/GNOME/mutter/merge_requests/625

** Changed in: mutter (Ubuntu)
   Status: Triaged => In Progress

** Changed in: gdm3 (Ubuntu)
   Status: Triaged => Invalid

** Changed in: gdm3 (Ubuntu)
   Importance: High => Undecided

** Changed in: gdm3 (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in GNOME Shell:
  New
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1705369/+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 1833189] Re: drivers are installed but not working

2019-06-18 Thread Daniel van Vugt
It appears the kernel (or the modeset driver) can't detect your
monitor's EDID via the VGA cable. And an EDID is required to know the
supported resolution. Without it you will be stuck in 1024x768.

Please try a different VGA cable, or simply unplugging and replugging
it.

If you still have a problem then this is either a kernel bug or simply
too old a monitor to be automatically detected. In the latter case you
would need to manually program in the supported graphics modes, using
something like:

https://wiki.archlinux.org/index.php/Xrandr#Adding_undetected_resolutions

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

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

** Summary changed:

- drivers are installed but not working
+ EDID not detected, stuck in low resolution

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

Title:
  EDID not detected, stuck in low resolution

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Drivers are not working as the resolution is not good

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Tue Jun 18 13:52:25 2019
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Generation Core Processor Family 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2017-01-16 (882 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=2a714d7a-a02a-4edd-88fa-099a457f16aa ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-06-18 (0 days ago)
  dmi.bios.date: 04/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-CS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd04/27/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-CS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833189/+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 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-17 Thread Daniel van Vugt
** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

** Changed in: mutter (Ubuntu)
   Importance: Undecided => High

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in GNOME Shell:
  New
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1705369/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-17 Thread Daniel van Vugt
The status for mutter will remain incomplete till someone tries the
suggestion from comment #31.

Sorry, I still can't reproduce this bug myself.

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in mutter source package in Bionic:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-17 Thread Daniel van Vugt
The problem I mentioned in comment #15 is now logged as bug 1833045.
It's clearly different to this one.

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in mutter source package in Bionic:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1826516] Re: bluetooh mouse lag when use bluetooth hedphones

2019-06-16 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu)
   Status: New => Incomplete

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

Title:
  bluetooh mouse lag when use bluetooth hedphones

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

Bug description:
  I have Microsoft Sculpt Comfort Mouse (bluettoh) and it works.
  When i connect my bluetooth heaset (plantronics PLT 50) mouse cursor lags 
terribly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 09:19:08 2019
  InstallationDate: Installed on 2018-12-22 (124 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20LW000YPB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.9-050009-generic 
root=UUID=74c51606-28cc-4d8f-91ac-c1d0dfd082c3 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET54W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LW000YPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET54W(1.31):bd01/21/2019:svnLENOVO:pn20LW000YPB:pvrThinkPadL580:rvnLENOVO:rn20LW000YPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L580
  dmi.product.name: 20LW000YPB
  dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580
  dmi.product.version: ThinkPad L580
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:21:6B:EA:3C:5F  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:21050738 acl:78587 sco:377825 events:21982 errors:0
TX bytes:19896288 acl:159 sco:377811 commands:5333 errors:0
  mtime.conffile..etc.bluetooth.input.conf: 2019-04-15T07:00:56.250208

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1826516/+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: Bluetooth not working

2019-06-16 Thread Daniel van Vugt
If the above command doesn't work then I would next focus on a possible
kernel problem in:

[ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38)

** Summary changed:

- Bluetooth not working
+ Intel 8260 Bluetooth not working

-- 
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:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

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
  

[Kernel-packages] [Bug 1832988] Re: Bluetooth not working

2019-06-16 Thread Daniel van Vugt
The attached RfKill.txt seems to suggest that Bluetooth is only turned
off in software. So maybe this is just a gnome-shell GUI bug, or gnome-
bluetooth.

To confirm this, please try turning it on by running this command in a
terminal:

  rfkill unblock 0


** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

** Also affects: gnome-bluetooth (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-bluetooth (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/1832988

Title:
  Intel 8260 Bluetooth not working

Status in gnome-bluetooth package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

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
  

[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-16 Thread Daniel van Vugt
Pat,

Re comment #19, your crash (hang) reports there seem to show the gnome-
shell process behaving normally (in poll) and not stuck at all. That
doesn't tell us much but it would support the theory in comment #31.

** Summary changed:

- Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes 
it
+ Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or 
using WaylandEnable=false) fixes it

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in mutter source package in Bionic:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes it

2019-06-16 Thread Daniel van Vugt
Interesting one of the commits mentioned above:

  37efe80ce85f drm/vmwgfx: use monotonic event timestamps
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f)

is related to what I changed in the latest update to mutter:

  https://gitlab.gnome.org/GNOME/mutter/commit/e9e4b2b72

The latest update to mutter requires monotonic event timestamps in the
kernel driver in order to work properly. It should kind of work without
them, but that fallback is untested...

So if that is the problem then you might find reverting to the previous
mutter version also works around the issue(?). You can download the
debs:

https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2/+build/16644915

and then try installing them together:

  dpkg -i *.deb



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

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

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

** Changed in: mutter (Ubuntu Bionic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 fixes it

Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in mutter source package in Bionic:
  Incomplete
Status in linux source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  vers

[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-16 Thread Daniel van Vugt
Indeed there was a kernel update to 18.04 around the same time as the
mutter update which I thought was causing this bug.

** No longer affects: mutter (Ubuntu)

** No longer affects: mutter (Ubuntu Bionic)

** No longer affects: mutter (Ubuntu Eoan)

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Confirmed

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

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

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

** Summary changed:

- Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
+ Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes 
it

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 fixes it

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
Nvidia 430.26 behaves a bit differently. It just fails to start as non-
root and gives reasons:

[   897.467] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not 
permitted)
...
[   897.470] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please 
see the
[   897.470] (EE) NVIDIA: system's kernel log for additional error messages 
and
[   897.470] (EE) NVIDIA: consult the NVIDIA README for details.
[   897.470] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please 
see the
[   897.470] (EE) NVIDIA: system's kernel log for additional error messages 
and
[   897.470] (EE) NVIDIA: consult the NVIDIA README for details.
[   897.470] (EE) [drm] Failed to open DRM device for (null): -2
[   897.470] (EE) [drm] Failed to open DRM device for pci::01:00.0: -2

So then the NVIDIA driver gives up and Xorg tries the modeset driver
instead. Modeset seems to detect my monitor fine (got the EDID) but then
fails with bug 1813897.

This is now a bit off-topic, but I suspect the above problem with
nvidia-430 will have the same fix as this bug.

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)

2019-06-13 Thread Daniel van Vugt
Two years later...

I am reviewing this bug again today. I can confirm it's still in Ubuntu
19.10. And I can confirm that comment #19 was right. See comment #19.

** Summary changed:

- Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an 
Intel GPU)
+ Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused 
Intel GPU)

** Description changed:

  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)
  
- WORKAROUNDS:
+ WORKAROUNDS (you only need one):
  
- * Disable integrated graphics/GPU in your BIOS; or
+ * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf
+ 
+ * Disable integrated graphics/GPU in your BIOS
  
  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
-   run:  sudo update-initramfs
-   and reboot.
+   run:  sudo update-initramfs
+   and reboot.
  
  ORIGINAL DESCRIPTION:
  
  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.
  
  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.
  
  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04
  
  I am using Nvidia GTX 1080 and Intel i7-4790K
  
  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  
  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  
  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

** Description changed:

- Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
- desktop with an Intel GPU)
+ Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
+ with an unused Intel GPU).
  
  WORKAROUNDS (you only need one):
  
  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf
  
  * Disable integrated graphics/GPU in your BIOS
  
  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.
  
  ORIGINAL DESCRIPTION:
  
  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.
  
  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.
  
  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04
  
  I am using Nvidia GTX 1080 and Intel i7-4790K
  
  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  
  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  
  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

** Changed in: gnome-shell (Ubuntu)
   Importance: High => Undecided

** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
   Importance: High => Undecided

** Changed in: gdm3 (Ubuntu)
   Status: Confirmed => Triaged

** Bug watch added: gitlab.gnome.org/GNOME/gdm/issues #492
   https://gitlab.gnome.org/GNOME/gdm/issues/492

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gdm/issues/492
   Importance: Unknown
   Status: Unknown

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in GNOME Shell:
  Unknown
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and 

[Kernel-packages] [Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)

2019-06-13 Thread Daniel van Vugt
Comment #116 appears to be linking to the wrong bug. That link is for
nvidia-drm.modeset=1 and this bug is specifically about when you don't
have that set, like the default.

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

Title:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS; or

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
run:  sudo update-initramfs
and reboot.

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)

2019-06-13 Thread Daniel van Vugt
-black
+blank

Because on Ubuntu 19.10 it's purple. Still the same bug though.

** Summary changed:

- Ubuntu boots to black screen when using Nvidia drivers (on a desktop with an 
Intel GPU)
+ Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an 
Intel GPU)

** Tags removed: aardvark gnome-17.10
** Tags added: eoan

** Tags removed: artful

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

Title:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS; or

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
run:  sudo update-initramfs
and reboot.

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
** No longer affects: gdm3 (Debian)

** Tags added: eoan

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
Not yet. I am just untangling more Nvidia bugs today.

Also, I forgot to mention that you CAN run Xorg+Nvidia and see your
monitors as non-root. But only after you have started and stopped Xorg
as root beforehand. Something gets remembered, maybe in $HOME somewhere?

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-06-13 Thread Daniel van Vugt
In a more pure development environment, I can confirm this bug without
needing hybrid GPUs, or gdm3.

Just the Nvidia driver and Xorg results in no outputs/monitors detected:

$ xrandr
Screen 0: minimum 8 x 8, current 640 x 480, maximum 16384 x 16384

To work around the problem I need to run Xorg as root. Then I get:

$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 16384 x 16384
DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 
324mm
   1920x1200 59.95*+  59.88  
   1920x1080 60.0059.9450.0023.98  
   1600x1200 60.00  
   1280x1024 75.0260.02  
   1280x720  60.0059.9450.00  
   1152x864  75.00  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x480   59.94  
   640x480   75.0059.9459.93  

So perhaps gdm3 is sometimes missing whatever /dev/* privileges it needs
to start Xorg on Nvidia properly. And perhaps lightdm just always does
it right.

Although a solution here in the medium term might lay in gdm3, I would
more like to see the Nvidia driver fix this bug. Because I can reproduce
it without any *dm. Just the kernel + Nvidia driver + Xorg.

** Changed in: gdm3 (Ubuntu)
   Status: Confirmed => Opinion

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: nvidia-graphics-drivers-418 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: New => Confirmed

** Also affects: nvidia-graphics-drivers-375 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
   Status: New => Confirmed

** Summary changed:

- gdm3, hybrid nvidia with modeset=1, no external monitors detected
+ nvidia-drm.modeset=1 results in no monitors detected by Xorg

** Changed in: gdm3 (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in gdm3 package in Debian:
  New

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)

2019-06-13 Thread Daniel van Vugt
Sounds like the root cause here is the same as bug 1716857.

** Changed in: gdm3 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

Status in gdm3 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Lenovo ideapad 510-15IKB
  OS: Ubuntu 18.04 bionic
  Kernel: x86_64 Linux 4.15.0-20-generic
  DE: GNOME
  CPU: Intel Core i5-7200U @ 4x 3.1GHz
  GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus)
  UEFI boot, Secure Boot disabled.

  I installed the proprietary graphics driver with Software Properties and 
Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, 
Dolphin) were working fine.
  To get rid of tearing I added nvidia-drm.modeset=1 to 
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && 
update-initramfs -u and rebooted.
  After doing that, Vulkan applications stopped working because they couldn't 
initialize the Vulkan swap chain until I reverted the changes to GRUB.

  Everything works as expected if lightdm is used instead of gdm3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
Also, it sounds like the root cause here is the same as bug 1769857.

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in gdm3 package in Debian:
  New

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
For a full list of reasons to not use nvidia-drm.modeset=1 right now, please 
see:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset

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

Title:
  nvidia-drm.modeset=1 results in no monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in gdm3 package in Debian:
  New

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1800465] Re: Vulkan error when using NVIDIA-Prime

2019-06-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1769857 ***
https://bugs.launchpad.net/bugs/1769857

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1769857, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1769857
   Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)

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

Title:
  Vulkan error when using NVIDIA-Prime

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils,
  switching to NVIDIA and then running vulkaninfo or vulkan-cube works
  perfectly.

  But when you reboot and update, then switch to Intel, then back to Nvidia, 
all Vulkan programs give an 
  "Assertion `!err' failed."

  Vulkaninfo:

  ===
  Presentable Surfaces:
  =
  GPU id   : 0 (GeForce GTX 960M)
  Surface type : VK_KHR_xcb_surface
  vulkaninfo: 
/build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253:
 AppDumpSurfaceFormats: Assertion `!err' failed.
  Annullato (core dump creato)

  
  Vulkancube:
  vulkan-cube: 
/build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: 
demo_init_vk_swapchain: Assertion `!err' failed.
  Annullato (core dump creato)

  
  I still have not found a workaround for that, the only way to get it working 
again is to reinstall everything. 

  - Install Ubuntu 18.10
  - Install proprietary 390 NVIDIA drivers
  - Switch NVIDIA-Prime to NVIDIA
  - Testing the vulkan capabilities works
  - Updating the system then switching to intel
  - Reboot
  - Switch to nvida
  - Now all Vulkan programs when using NVIDIA give that error

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+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 1832004] Re: [amdgpu] display hanging after laptop opens lid

2019-06-13 Thread Daniel van Vugt
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Incomplete => New

** 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/1832004

Title:
  [amdgpu] display hanging after laptop opens lid

Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  ubuntu 19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  7 14:56:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 5.0.0-15-generic, x86_64: installed
   anbox, 1, 5.0.0-16-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1043:1680]
  InstallationDate: Installed on 2018-08-03 (308 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. E402BA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E402BA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E402BA
  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.:bvrE402BA.311:bd09/06/2018:svnASUSTeKCOMPUTERINC.:pnE402BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: E402BA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832004/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging glxgears or glxheads

2019-06-13 Thread Daniel van Vugt
** Also affects: nvidia-graphics-drivers-418 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: New => Confirmed

** Summary changed:

- Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging glxgears 
or glxheads
+ Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL 
app windows

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

Title:
  Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
  OpenGL app windows

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Nvidia driver causes Xorg to use 100% CPU and shows high lag and
  stutter... but only when dragging glxgears/glxheads, or any window
  over them. Other apps do not exhibit the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Wed Oct 24 19:11:15 2018
  InstallationDate: Installed on 2018-05-26 (151 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799679/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn while i915 crashes repeatedly

2019-06-12 Thread Daniel van Vugt
Thanks for those logs. They show the problem happening immediately, as
soon as 2.5 seconds after the kernel starts.

This bug is now assigned to the kernel ('linux' component). I believe
this is a kernel bug, if not a hardware fault.

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

Title:
  [i915] Rotated display is overscaled and overdrawn while i915 crashes
  repeatedly

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  On my system I have two display: one in landscape, and one in
  portrait. The landscape display is fine, but the portrait display is
  corrupted. If I unplug the display from the computer for some time and
  then plug it back in it will occasionally fix the problem.

  Once the problem is fixed, the display works perfectly fine,
  indefinitely. However, as soon as I reboot the computer the display
  will come up corrupted again and never recovers without many rounds of
  plug/unplug turn off/turn on. It's extremely frustrating.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 28 15:57:02 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1813463] Re: no bluetooth intel ac 9260

2019-06-12 Thread Daniel van Vugt
Does Ubuntu 19.04 work better with this hardware?

** Tags added: bionic cosmic

** Package changed: bluez (Ubuntu) => linux (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/1813463

Title:
  no bluetooth intel ac 9260

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi All

  Using a laptop with the intel AC 9260 wireless card that also has Bluetooth 
5.0.
  Booting either ubuntu 18.04 or 18.10 with kernel 4.18.* through to 4.20.* the 
bluetooth is not detected and can't be switched on.

  hciconfig -a
  Produces no result

  $ bluetoothctl
  Agent registered
  [bluetooth]# show
  No default controller available
  [bluetooth]# devices
  No default controller available
  [bluetooth]#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813463/+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 1731699] Re: Unable to transfer files via bluetooth to paired android phone

2019-06-12 Thread Daniel van Vugt
** Tags removed: artful
** Tags added: disco

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

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

Title:
  Unable to transfer files via bluetooth to paired android phone

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to transfer files to my phone (Nexus 6P - Android 8.0) from
  Ubuntu 17.10, but when I pair the laptop and phone, I don't think it's
  pairing in a way which permits file transfers. When I pair, my phone
  gives me a checkbox "Allow xx to access your contacts and call
  history", but there is no option to allow file transfers.

  Then, when I attempt to transfer a file via Bluetooth from Ubuntu the
  transfer fails and I get the message "There was an error". My phone
  doesn't seem to recognise there's been any attempt to send a file.

  Discussed at https://ubuntuforums.org/showthread.php?t=2377286

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731699/+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 1832041] Re: The mouse stops working

2019-06-12 Thread Daniel van Vugt
Please let us know which problem you would like this bug to be about.

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

Title:
  The mouse stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime the wifi is not getting detected and the mouse is not working
  and and i am using touch instead of mouse, the external mouse is also
  not working

  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: Sat Jun  8 00:40:19 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.15.0-47-generic, x86_64: installed
   nvidia, 390.116, 4.15.0-51-generic, x86_64: installed
   nvidia, 390.116, 4.18.0-17-generic, x86_64: installed
   nvidia, 390.116, 4.18.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83ba]
 Subsystem: Hewlett-Packard Company GP108M [GeForce MX150] [103c:83ba]
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 05c8:0815 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 009: ID 03f0:0941 Hewlett-Packard 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 15-ch0xx
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=a759c10c-be50-4caf-bd43-1516b97d1c6a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83BA
  dmi.board.vendor: HP
  dmi.board.version: 57.31
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.23:bd10/15/2018:svnHP:pnHPSpectrex360Convertible15-ch0xx:pvr:rvnHP:rn83BA:rvr57.31:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-ch0xx
  dmi.product.sku: 2FW61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~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/1832041/+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 1832041] Re: The mouse stops working

2019-06-12 Thread Daniel van Vugt
The wifi problem is a kernel/firmware issue:

[20460.034389] ieee80211 phy0: Hardware restart was requested
[20461.205415] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 
0x0.

---

The mouse problem seems to be a hardware/connection/kernel issue:

[20772.768458] usb 1-3: new low-speed USB device number 7 using xhci_hcd
[20772.926068] usb 1-3: New USB device found, idVendor=03f0, idProduct=0941, 
bcdDevice= 1.00
[20772.926075] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[20772.926079] usb 1-3: Product: HP X500 USB Optical Mouse
[20772.926083] usb 1-3: Manufacturer: PixArt
[20772.930813] input: PixArt HP X500 USB Optical Mouse as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:03F0:0941.0009/input/input35
[20772.931310] hid-generic 0003:03F0:0941.0009: input,hidraw0: USB HID v1.11 
Mouse [PixArt HP X500 USB Optical Mouse] on usb-:00:14.0-3/input0
[20772.946513] usb 1-3: USB disconnect, device number 7
[20773.488475] usb 1-3: new low-speed USB device number 8 using xhci_hcd
[20773.646432] usb 1-3: New USB device found, idVendor=03f0, idProduct=0941, 
bcdDevice= 1.00
[20773.646439] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[20773.646443] usb 1-3: Product: HP X500 USB Optical Mouse
[20773.646447] usb 1-3: Manufacturer: PixArt
[20773.650364] input: PixArt HP X500 USB Optical Mouse as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:03F0:0941.000A/input/input36
[20773.651117] hid-generic 0003:03F0:0941.000A: input,hidraw0: USB HID v1.11 
Mouse [PixArt HP X500 USB Optical Mouse] on usb-:00:14.0-3/input0
[20956.341624] usb 1-3: USB disconnect, device number 8
[20960.080857] usb 1-3: new low-speed USB device number 9 using xhci_hcd
[20960.937374] usb 1-3: New USB device found, idVendor=03f0, idProduct=0941, 
bcdDevice= 1.00
[20960.937378] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[20960.937381] usb 1-3: Product: HP X500 USB Optical Mouse
[20960.937384] usb 1-3: Manufacturer: PixArt
[20960.940944] input: PixArt HP X500 USB Optical Mouse as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:03F0:0941.000B/input/input37
[20961.001941] hid-generic 0003:03F0:0941.000B: input,hidraw0: USB HID v1.11 
Mouse [PixArt HP X500 USB Optical Mouse] on usb-:00:14.0-3/input0

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

** 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/1832041

Title:
  The mouse stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime the wifi is not getting detected and the mouse is not working
  and and i am using touch instead of mouse, the external mouse is also
  not working

  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: Sat Jun  8 00:40:19 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.15.0-47-generic, x86_64: installed
   nvidia, 390.116, 4.15.0-51-generic, x86_64: installed
   nvidia, 390.116, 4.18.0-17-generic, x86_64: installed
   nvidia, 390.116, 4.18.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83ba]
 Subsystem: Hewlett-Packard Company GP108M [GeForce MX150] [103c:83ba]
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 05c8:0815 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 009: ID 03f0:0941 Hewlett-Packard 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 15-ch0xx
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=a759c10c-be50-4caf-bd43-1516b97d1c6a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83BA
  dmi.board.vendor: HP
  dmi.board.version: 57.31
  dmi.chassis.type: 31
  

[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak

2019-06-11 Thread Daniel van Vugt
** Tags added: bionic

** 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/1831751

Title:
  rtlwifi: aggresive memory leak

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI) 
the memory usage grows slowly to take all the available RAM when i let the 
computer running over the night (with just top and irssi), and i have to reboot 
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i 
was still flooded with message about pci aer taking lots of disk space in the 
logs, but pci=noaer fixed this problem and i had no memory leak.
  The computer is a common laptop: HP Pavilion.

  ---
  Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly 
disabled to capture the AERs.

  Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
  overnight booted just to console (systemd.unit=multi-user.target).

  The memory leak doesn't affect Windows but owner is going to check
  Windows Event Log for signs of AERs being logged.

  ---

  Original suspect of AER is not guilty.

  This turns out to be a bug in the rtlwifi driver where in some rare
  circumstances it fails to free an sk_buf.

  Reporter has been testing a DKMS build of rtlwfi with the fix applied
  and confirms it solves the issue.

  Upstream has the commit. Can we get this cherry-picked into all
  releases?

  commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
  Author: Larry Finger 
  Date:   Sat Nov 17 20:55:03 2018 -0600

  rtlwifi: Fix leak of skb when processing C2H_BT_INFO
  
  With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
  C2H_BT_INFO"), calling rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
  the routine returns without freeing that skb, thereby leaking it.
  
  This issue has been discussed at 
https://github.com/lwfinger/rtlwifi_new/issues/401
  and the fix tested there.
  
  Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing 
C2H_BT_INFO")
  Reported-and-tested-by: Francisco Machado Magalhães Neto 

  Cc: Francisco Machado Magalhães Neto 
  Cc: Ping-Ke Shih 
  Cc: Stable  # 4.18+
  Signed-off-by: Larry Finger 
  Signed-off-by: Kalle Valo 

  diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c 
b/drivers/net/wireless/realtek/rtlwifi/base.c
  index f4122c8fdd97..ef9b502ce576 100644
  --- a/drivers/net/wireless/realtek/rtlwifi/base.c
  +++ b/drivers/net/wireless/realtek/rtlwifi/base.c
  @@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct 
sk_buff *skb)
   
  if (rtl_c2h_fast_cmd(hw, skb)) {
  rtl_c2h_content_parsing(hw, skb);
  +   kfree_skb(skb);
  return;
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+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 1832419] Re: Xorg freeze

2019-06-11 Thread Daniel van Vugt
Does the freeze only happen when connected to wifi?

I can see a couple of errors from the kernel graphics driver suggesting
the display might freeze:

[  598.213901] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure 
on pipe A ...
[ 3696.507718] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure 
on pipe A ...

Please try logging into "Ubuntu on Wayland" and tell us if that helps.

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

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

** Summary changed:

- Xorg freeze
+ Display freezes

** Summary changed:

- Display freezes
+ Acer Chromebook [banon] display freezes

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

Title:
  Acer Chromebook [banon] display freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Freezes  when connected to wifi.  Running lsof -i and closing some of
  the processes results in black display, need to restart computer.  i
  can use the computer for very short periods when connected to the
  internet, frequently the display freezes requiring restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun 11 18:39:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: GOOGLE Banon
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic 
root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-51-generic
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.9
  dmi.board.name: Banon
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Banon
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832419/+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 1832419] Re: Acer Chromebook [banon] display freezes

2019-06-11 Thread Daniel van Vugt
Also, it looks like you have some custom firmware installed:

  dmi.bios.version: MrChromebox-4.9

I wonder if the problem occured before installing that.

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

Title:
  Acer Chromebook [banon] display freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Freezes  when connected to wifi.  Running lsof -i and closing some of
  the processes results in black display, need to restart computer.  i
  can use the computer for very short periods when connected to the
  internet, frequently the display freezes requiring restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun 11 18:39:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: GOOGLE Banon
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic 
root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-51-generic
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.9
  dmi.board.name: Banon
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Banon
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832419/+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 1832369] Re: [Thomson THN14B] Internal speaker does not work

2019-06-11 Thread Daniel van Vugt
Can you please try booting Ubuntu 19.04 from USB and tell us if that
fixes the problem?

  http://releases.ubuntu.com/19.04/

Please also note that Ubuntu 18.10 will reach end-of-life next month
(https://wiki.ubuntu.com/Releases).

** Summary changed:

- AUDIO WORK ONLY WITH AUDIO EXTERNAL. AUDIO DIDNT WORK ON INTERNAL SPEAKER
+ [Thomson THN14B] Internal speaker does not work

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

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

Title:
  [Thomson THN14B] Internal speaker does not work

Status in linux package in Ubuntu:
  New

Bug description:
  HI,

  I have a thomson THN14B with audio card rt5651 and bluetooth

  If i list a aplay -l to list all my sound card i get :

   Liste des Périphériques Matériels PLAYBACK 
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 []
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) []
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  
  I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal 
speaker sound.

  Have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sandra 1154 F pulseaudio
   /dev/snd/pcmC1D0c:   sandra 1154 F...m pulseaudio
   /dev/snd/pcmC1D0p:   sandra 1154 F...m pulseaudio
   /dev/snd/controlC0:  sandra 1154 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jun 11 17:21:59 2019
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago)
  dmi.bios.date: 01/02/2018
  dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: THN14B
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Thomson
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832369/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-06-11 Thread Daniel van Vugt
Filip,

Since you are the original reporter and no longer experience a problem
then I would prefer to keep this bug closed.

---

Gabriele,

If you are experiencing audio problems then please open a new bug by
running:

  ubuntu-bug pulseaudio

so that we can review the details of your affected machine.

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

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  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/1818802/+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 1832184] Re: nvidia-kernel-source-390 390.116-0ubuntu0.18.10.1: nvidia kernel module failed to build

2019-06-10 Thread Daniel van Vugt
during RTL pass: cprop
/var/lib/dkms/nvidia/390.116/build/nvidia-uvm/uvm8_page_tree_test.c: In 
function ‘alloc_64k_memory_kepler’:
/var/lib/dkms/nvidia/390.116/build/nvidia-uvm/uvm8_page_tree_test.c:1112:1: 
internal compiler error: Naruszenie ochrony pamięci
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.


** Package changed: nvidia-graphics-drivers-390 (Ubuntu) => gcc-8 (Ubuntu)

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

Title:
  nvidia-kernel-source-390 390.116-0ubuntu0.18.10.1: nvidia kernel
  module failed to build

Status in gcc-8 package in Ubuntu:
  New

Bug description:
  Bug showed up during normal upgrade process.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: nvidia-kernel-source-390 390.116-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  DKMSKernelVersion: 4.18.0-16-generic
  Date: Mon Jun 10 10:21:53 2019
  Dependencies:
   
  InstallationDate: Installed on 2016-07-16 (1058 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageVersion: 390.116-0ubuntu0.18.10.1
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.5
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-kernel-source-390 390.116-0ubuntu0.18.10.1: nvidia kernel 
module failed to build
  UpgradeStatus: Upgraded to cosmic on 2018-12-10 (182 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1832184/+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 1832133] Re: Mouse unresponsive on Ubuntu 18.04

2019-06-10 Thread Daniel van Vugt
Please reproduce the problem again and then immediately run this command
in a Terminal window:

  dmesg > dmesg.txt

That will create a new file called 'dmesg.txt'. We would like you to
then attach that new file to this bug in a new comment.

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

Title:
  Mouse unresponsive on Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi there,

  I submitted this bug report following advice in
  https://wiki.ubuntu.com/DebuggingMouseDetection

  I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart
  15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
  rarely boot up Windows.

  I use an optical mouse attached to my computer by USB cable. It works
  perfectly on Windows. But on Ubuntu, it will work OK for a couple of
  seconds, but then become less and less responsive, to the point where
  it barely works at all.

  I have a touchpad that works perfectly in both Windows and Ubuntu.

  Result of lsb_release -rd: Description:   Ubuntu 18.04.2 LTS. Release:
18.04
  I am using Xdiagnose version 3.8.8

  Please help!

  Tom.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 17:03:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b]
  InstallationDate: Installed on 2018-01-22 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct 31 01:15:25 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832133/+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 1831037] Re: Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.

2019-06-10 Thread Daniel van Vugt
Thanks. If you could describe the keyboard problem in more detail then
it would help.

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

Title:
  Acer Aspire ES1-311 - some keyboard keys like D do not respond
  correctly.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  thunderbird - send email
  keyboard from laptop 
  no physical shut down or reeboot

  tried all the information online

  have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 30 11:02:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0938]
  InstallationDate: Installed on 2015-10-28 (1309 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-311
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-311
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.11:rvnAcer:rnAspireES1-311:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: BayTrail
  dmi.product.name: Aspire ES1-311
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon May 21 13:03:46 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831037/+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 1831037] Re: Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.

2019-06-10 Thread Daniel van Vugt
** Summary changed:

- not working list
+ Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.

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

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

Title:
  Acer Aspire ES1-311 - some keyboard keys like D do not respond
  correctly.

Status in linux package in Ubuntu:
  New

Bug description:
  thunderbird - send email
  keyboard from laptop 
  no physical shut down or reeboot

  tried all the information online

  have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 30 11:02:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0938]
  InstallationDate: Installed on 2015-10-28 (1309 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd 
   Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-311
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=42b0d535-3af0-46de-b465-b5274842900d ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-311
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.11:rvnAcer:rnAspireES1-311:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: BayTrail
  dmi.product.name: Aspire ES1-311
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon May 21 13:03:46 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831037/+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 1832133] Re: Mouse unresponsive on Ubuntu 18.04

2019-06-09 Thread Daniel van Vugt
The only hint of a problem I can see is this from the kernel log:

[ 6402.282272] usb 5-2: USB disconnect, device number 2
[ 6405.688387] usb 5-2: new low-speed USB device number 3 using xhci_hcd
[ 6405.863785] usb 5-2: New USB device found, idVendor=1241, idProduct=
[ 6405.863792] usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 6405.884749] input: HID 1241: as 
/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.0/0003:1241:.0003/input/input19
[ 6405.885322] hid-generic 0003:1241:.0003: input,hidraw1: USB HID v1.00 
Mouse [HID 1241:] on usb-:00:10.0-2/input0

which is concurred by the Xorg log:

[  6402.353] (II) config/udev: removing device HID 1241:
[  6402.353] (**) Option "fd" "29"
[  6402.353] (II) event11 - HID 1241:: device removed
[  6402.361] (II) UnloadModule: "libinput"
[  6402.361] (II) systemd-logind: releasing fd for 13:75
[  6405.965] (II) config/udev: Adding input device HID 1241: 
(/dev/input/mouse2)
[  6405.965] (II) No input driver specified, ignoring this device.
[  6405.965] (II) This device may have been added with another device file.

That suggests the mouse got disconnected and reconnected after 1h46m.

Please reproduce the problem again and as soon as it happens run:

  dmesg > dmesg.txt

and send us the file 'dmesg.txt'.

Please also try a different mouse to see if that avoids the problem.

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

** 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/1832133

Title:
  Mouse unresponsive on Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi there,

  I submitted this bug report following advice in
  https://wiki.ubuntu.com/DebuggingMouseDetection

  I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart
  15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and
  rarely boot up Windows.

  I use an optical mouse attached to my computer by USB cable. It works
  perfectly on Windows. But on Ubuntu, it will work OK for a couple of
  seconds, but then become less and less responsive, to the point where
  it barely works at all.

  I have a touchpad that works perfectly in both Windows and Ubuntu.

  Result of lsb_release -rd: Description:   Ubuntu 18.04.2 LTS. Release:
18.04
  I am using Xdiagnose version 3.8.8

  Please help!

  Tom.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 17:03:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b]
  InstallationDate: Installed on 2018-01-22 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct 31 01:15:25 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open 

[Kernel-packages] [Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]

2019-06-09 Thread Daniel van Vugt
You kernel log is showing a problem at the kernel level:

[  349.209981] iwlwifi :05:00.0: Microcode SW error detected.  Restarting 
0x200.
[  349.210223] iwlwifi :05:00.0: Start IWL Error Log Dump:
[  349.210228] iwlwifi :05:00.0: Status: 0x0100, count: 6
[  349.210231] iwlwifi :05:00.0: Loaded firmware version: 29.1044073957.0
...

Please try this:

  sudo apt update
  sudo apt install --reinstall linux-firmware gnome-bluetooth

Then reboot.

If the problem still persists then please:

1. Run:

   dpkg -l > allpackages.txt

   and send us the file 'allpackages.txt'.

2. Reproduce the problem again and then run:
   
   journalctl -b0 > curjournal.txt

   and send us the file 'curjournal.txt'.

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

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

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

** Changed in: linux-firmware (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/1831995

Title:
  Bluetooth earphone is connected but disconnected immediately. [Intel
  3165]

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

Bug description:

  I have erased and reinstalled Pulseaudio.
  It seems like this can not be done since.

  I tried the following.
  sudo apt-get remove alsa-base pulseaudio
  sudo apt-get install alsa-base pulseaudio

  I did this again.
  sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
  sudo apt-get install linux-sound-base alsa-base alsa-utils

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluetooth 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Jun  7 20:33:05 2019
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7559
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.9
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.sku: 0706
  dmi.product.version: 1.2.9
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 58:FB:84:C1:51:50  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:125274 acl:68 sco:0 events:1720 errors:0
TX bytes:15000 acl:64 sco:0 commands:861 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831995/+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 1831995] Re: Bluetooth earphone is connected but disconnected immediately.

2019-06-09 Thread Daniel van Vugt
** Tags added: a2dp

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

** Summary changed:

- Bluetooth earphone is connected but disconnected immediately.
+ Bluetooth earphone is connected but disconnected immediately. [Intel 3165]

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

Title:
  Bluetooth earphone is connected but disconnected immediately. [Intel
  3165]

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

Bug description:

  I have erased and reinstalled Pulseaudio.
  It seems like this can not be done since.

  I tried the following.
  sudo apt-get remove alsa-base pulseaudio
  sudo apt-get install alsa-base pulseaudio

  I did this again.
  sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
  sudo apt-get install linux-sound-base alsa-base alsa-utils

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluetooth 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Jun  7 20:33:05 2019
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7559
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.9
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.sku: 0706
  dmi.product.version: 1.2.9
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 58:FB:84:C1:51:50  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:125274 acl:68 sco:0 events:1720 errors:0
TX bytes:15000 acl:64 sco:0 commands:861 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831995/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn

2019-06-06 Thread Daniel van Vugt
Thanks. You seem to have a few different crashes in the i915 kernel
driver still :(

I wonder if they are unique to your CPU/GPU generation or something else
about this machine is unusual...

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

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

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

** Summary changed:

- [i915] Rotated display is overscaled and overdrawn
+ [i915] Rotated display is overscaled and overdrawn while i915 crashes 
repeatedly

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

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

Title:
  [i915] Rotated display is overscaled and overdrawn while i915 crashes
  repeatedly

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  On my system I have two display: one in landscape, and one in
  portrait. The landscape display is fine, but the portrait display is
  corrupted. If I unplug the display from the computer for some time and
  then plug it back in it will occasionally fix the problem.

  Once the problem is fixed, the display works perfectly fine,
  indefinitely. However, as soon as I reboot the computer the display
  will come up corrupted again and never recovers without many rounds of
  plug/unplug turn off/turn on. It's extremely frustrating.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 28 15:57:02 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1827314] Re: Ubuntu 19.04 Background and lockscreen image turns into white noise after sleep and wakeup

2019-06-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1809407, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1809407
   [nvidia] Corrupted wallpaper after resuming from suspend

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

Title:
  Ubuntu 19.04 Background and lockscreen image turns into white noise
  after sleep and wakeup

Status in gnome-desktop package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 Background and lockscreen image turns into white noise after 
sleep and wakeup
  the lock screen is Disco Dingo default image and bg is custom but both turn 
into a noisy broken image
  my laptop is MSI CX627QL
  Core i5 7th gen
  Ram 12 gb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1827314/+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 1831599] Re: No display activity when coming out of powersave ("kernel BUG at mm/slub.c:296!")

2019-06-04 Thread Daniel van Vugt
It appears the 'amdgpu' kernel driver is crashing. That is part of the
kernel package 'linux'.

** Tags added: amdgpu

** Summary changed:

- No display activity when coming out of powersave ("kernel BUG at 
mm/slub.c:296!")
+ [amdgpu] No display activity when coming out of powersave ("kernel BUG at 
mm/slub.c:296!")

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

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

Title:
  [amdgpu] No display activity when coming out of powersave ("kernel BUG
  at mm/slub.c:296!")

Status in linux package in Ubuntu:
  New

Bug description:
  Since a few weeks, my displays won't wake up from display powersave.
  The machine stays responsive via SSH.

  This first occurred on Ubuntu 18.04, and keeps happening on 18.10
  (which I had updated to in the hopes of fixing the issue that way).

  The only escape I've found from this state is via magic SysRq.

  It can be triggered reliably by waiting for the screensaver to kick in
  (e.g. overnight).

  =
  Note a kernel bug warning in CurrentDmesg.txt
  =

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jun  4 13:40:47 2019
  DistUpgraded: 2019-05-22 12:26:07,943 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   spl, 0.7.9, 4.18.0-20-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed module!)
   zfs, 0.7.9, 4.18.0-20-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!)
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev ef) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1462:341b]
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic 
root=ZFS=rpool/ROOT/ubuntu ro nouveau.modeset=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to cosmic on 2019-05-22 (13 days ago)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  make.log:
   DKMS make.log for zfs-0.7.9 for kernel 5.1.4-050104-generic (x86_64)
   Do 23. Mai 18:51:15 CEST 2019
   make: *** No targets specified and no makefile found.  Stop.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1705369] Re: Ubuntu boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2019-06-04 Thread Daniel van Vugt
** Summary changed:

- Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a 
desktop with an Intel GPU)
+ Ubuntu boots to black screen when using Nvidia drivers (on a desktop with an 
Intel GPU)

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

Title:
  Ubuntu boots to black screen when using Nvidia drivers (on a desktop
  with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS; or

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
run:  sudo update-initramfs
and reboot.

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn

2019-06-03 Thread Daniel van Vugt
... then if the new kernel log continues to show similar errors we will
have at least narrowed this bug down to the kernel (or a
hardware/connection fault).

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

Title:
  [i915] Rotated display is overscaled and overdrawn

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  On my system I have two display: one in landscape, and one in
  portrait. The landscape display is fine, but the portrait display is
  corrupted. If I unplug the display from the computer for some time and
  then plug it back in it will occasionally fix the problem.

  Once the problem is fixed, the display works perfectly fine,
  indefinitely. However, as soon as I reboot the computer the display
  will come up corrupted again and never recovers without many rounds of
  plug/unplug turn off/turn on. It's extremely frustrating.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 28 15:57:02 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn

2019-06-03 Thread Daniel van Vugt
Thanks for your efforts.

If you feel you have checked the connections thoroughly then the next
step is to wait until the problem happens again and then run:

  dmesg > newdmesg.txt

and send us the file 'newdmesg.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/1830792

Title:
  [i915] Rotated display is overscaled and overdrawn

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  On my system I have two display: one in landscape, and one in
  portrait. The landscape display is fine, but the portrait display is
  corrupted. If I unplug the display from the computer for some time and
  then plug it back in it will occasionally fix the problem.

  Once the problem is fixed, the display works perfectly fine,
  indefinitely. However, as soon as I reboot the computer the display
  will come up corrupted again and never recovers without many rounds of
  plug/unplug turn off/turn on. It's extremely frustrating.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 28 15:57:02 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1820666] Re: wifi disconnects when a device connects with bluetooth to the computer

2019-06-03 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1820666

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

** 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/1820666

Title:
  wifi disconnects when a device connects with bluetooth to the computer

Status in Ubuntu MATE:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When a device connects to the computer using Bluetooth the Wi-Fi
  disconnects for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1820666/+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 1769391] Re: 18.04 Install, not detecting bluetooth

2019-06-03 Thread Daniel van Vugt
** No longer affects: bluez (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/1769391

Title:
  18.04 Install, not detecting bluetooth

Status in Ubuntu MATE:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ lspci -knn | grep Net -A3; lsusb
  01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network 
Adapter [168c:0032] (rev 01)
Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter 
[103c:1785]
Kernel driver in use: ath9k
Kernel modules: ath9k
  02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 05)
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 004: ID 0cf3:311d Atheros Communications, Inc. 
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 003: ID 058f:a001 Alcor Micro Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 0e8f:00a7 GreenAsia Inc. 
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ 
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  tyoma@HP-Pavilion-g7-Notebook-PC:~$ sudo /etc/init.d/bluetooth start
  [ ok ] Starting bluetooth (via systemctl): bluetooth.service.

  tyoma@HP-Pavilion-g7-Notebook-PC:~$ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:6 acl:0 sco:0 events:1 errors:0
TX bytes:3 acl:0 sco:0 commands:6 errors:5
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1 
Link policy: 
Link mode: SLAVE ACCEPT 

  tyoma@HP-Pavilion-g7-Notebook-PC:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1769391/+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 1812310] Re: No more sound on lenovo R61i booting MATE 16.04

2019-06-03 Thread Daniel van Vugt
** Changed in: pulseaudio (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/1812310

Title:
  No more sound on lenovo R61i booting MATE 16.04

Status in Ubuntu MATE:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I
  was able to listen to a YouTube video from the laptop when booting
  Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04

  Thanks for your consideration,
  Abu Billy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1812310/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn

2019-05-30 Thread Daniel van Vugt
Thanks. Your new kernel log shows different crashes in the i915 kernel
driver when using Wayland. In particular, the kernel driver seems to
think the monitor has been unplugged/replugged:

[2.606884]  drm_fb_helper_hotplug_event.part.38+0x97/0xc0 [drm_kms_helper]
[2.606887]  drm_fb_helper_hotplug_event+0x1c/0x30 [drm_kms_helper]
[2.606903]  intel_fbdev_output_poll_changed+0x6b/0xa0 [i915]
[2.606906]  drm_kms_helper_hotplug_event+0x2a/0x40 [drm_kms_helper]
[2.606910]  output_poll_execute+0x19a/0x1c0 [drm_kms_helper]

If you did not unplug/replug the monitor while the system was running
then this sounds like a faulty cable or faulty connection. Please try a
different cable and/or reconnecting the existing one more firmly.

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

Title:
  [i915] Rotated display is overscaled and overdrawn

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  On my system I have two display: one in landscape, and one in
  portrait. The landscape display is fine, but the portrait display is
  corrupted. If I unplug the display from the computer for some time and
  then plug it back in it will occasionally fix the problem.

  Once the problem is fixed, the display works perfectly fine,
  indefinitely. However, as soon as I reboot the computer the display
  will come up corrupted again and never recovers without many rounds of
  plug/unplug turn off/turn on. It's extremely frustrating.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 28 15:57:02 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583

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


  1   2   3   4   5   6   7   8   9   10   >