[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device

2021-01-31 Thread Piyush Santosh Mhatre
Thankyou @Daniel I ran command given by you and It replied that the 
linux-generic-hwe-20.04 is already installed. Then I ran the last command that 
you have given and it says that I have two versions of blueman one is stable 
directs to launch pad web site and gives me this :-
[
Lost something?
This page does not exist, or you may not have permission to see it.

If you have been to this page before, it is possible it has been
removed.

Check that you are logged in with the correct account, or that you entered the 
address correctly, or search for it:
]
The other versions bug is submitted succesfully.

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

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.930261] audit: type=1400 audit(1611909043.623:63): 
apparmor="DENIED" operation="connect" pr

[Kernel-packages] [Bug 1914007] [NEW] RT3290 Bluetooth not finding any device

2021-01-31 Thread Piyush Santosh Mhatre
Public bug reported:

Ubuntu :- 20.04
Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
Outout of command :- service bluetooth status

● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre>
 Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
   Docs: man:bluetoothd(8)
   Main PID: 1389 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4514)
 Memory: 2.0M
 CGroup: /system.slice/bluetooth.service
 └─1389 /usr/lib/bluetooth/bluetoothd

Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.>
Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66>
Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66>
lines 1-18/18 (END)

Output of command :- sudo btmgmt info

Index list with 1 item
hci0: Primary controller
addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
current settings: powered bondable ssp br/edr
name Piyush-X55C

Output of command :- bluetoothctl

Agent registered
[bluetooth]# scan on
[bluetooth]# discoverable on
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# discoverable on
Changing discoverable on succeeded
[bluetooth]#

Output of command :- sudo btmgmt find

Unable to start discovery. status 0x0c (Not Supported)

Output of command :- lspci -knn | grep Net -A3; lsusb

02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
Kernel driver in use: rt2800pci
Kernel modules: rt2800pci
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of command :-dmesg | grep -i bluetooth

 [ 12.851854] Bluetooth: Core ver 2.22
[ 12.851883] Bluetooth: HCI device and connection manager initialized
[ 12.851888] Bluetooth: HCI socket layer initialized
[ 12.851889] Bluetooth: L2CAP socket layer initialized
[ 12.851893] Bluetooth: SCO socket layer initialized
[ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
[ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
[ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
[ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
[ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
[ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1102 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
[ 81.668783] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 81.668785] Bluetooth: BNEP filters: protocol multicast
[ 81.668791] Bluetooth: BNEP socket layer initialized
[ 1965.556683] Bluetooth: RTBT_Tb: vendor=0x1814, device=0x3298
[ 1965.556685] Bluetooth: RTBT_Tb: vendor=0x0, device=0x0
[ 1965.556687] Bluetooth: DynamicAlloc pci_device_id table at 
0x000

[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

2021-01-31 Thread Henrik Juul Hansen
I tried the ~khfeng/lp1912057-bridge-d0-2.

Before suspend/resume:
Powertop: around 1.4W - pc2,3,7,8,10
ASPM L1 enabled for all controllers

After suspend/resume:
Powertop: around 4.6W - pc2,3
ASPM Disabled for NVMe

Attached dmesg after "echo 'file drivers/pci/* +p' >
/sys/kernel/debug/dynamic_debug/control" and suspend/resume.

** Attachment added: "dmesg.5.11.0-6_v2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5458688/+files/dmesg.5.11.0-6_v2

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

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After boot the idle power consumption is around 2.3 W but after suspend it is 
4.7 W.
  The measurement is 5-10 min after boot/resume - looking at "top" to see 
system was idle.
  This is consistent - I have tried more that 10 times. 
  BIOS is updated to latest version.
  I have checked power consumption with external meter - and confirmed that it 
is higher.

  I have attached output of:
  sudo powertop -t 60 -r --html=before.html  (and after)

  I have noticed that Package C-state 6 is reached before suspend but
  not after.

  I expect that idle power consumption after suspend should be the same
  as before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-38-generic 5.8.0-38.43
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hjh1448 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 15:49:32 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-01-03 (13 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-38-generic N/A
   linux-backports-modules-5.8.0-38-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425JA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425JA
  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.ec.firmware.release: 3.4
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425JA_UX425JA
  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/1912057/+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 1913859] Re: RT3290 Bluetooth not finding any device

2021-01-31 Thread Piyush Santosh Mhatre
I ran the command apport-collect 1913859 and it gives me no additional
info collected. @Jeremy(wa113y3s)

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

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.930261] audit: type=1400 audit(1611909043.623:63): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   68.194380] audit: type=1400 audit(1611909043.887:65): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   68.194710] audit: type=1400 audit(1611909043.887:66): 
apparmor="DENIED" operation="connect" profile="sn

[Kernel-packages] [Bug 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup

2021-01-31 Thread Daniel van Vugt
Please try:

* Selecting 'Ubuntu on Wayland' on the login screen, instead of Xorg; or

* An older kernel series like https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.4.94/

** Summary changed:

- Cursor flickering on dual screen setup
+ [Cherry Trail] [modeset] Cursor flickering on dual screen setup

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Tags added: multimonitor

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

** Package changed: linux (Ubuntu) => linux-signed-hwe-5.8 (Ubuntu)

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: New => Incomplete

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Package changed: linux-signed-hwe-5.8 (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/1913963

Title:
  [Cherry Trail] [modeset] Cursor flickering on dual screen setup

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When running on dual screen config, the cursor is heavily flickering.
  Makes it a very unpleasant experience, if not renders it unusable. If
  switched to only single screen, cursor is completely stable.

  When issuing 
  xrandr --output HDMI-2 --scale 0.99x0.99
  again cursor is stable. Switching to 200% scaling in the desktop settings, 
doesn't help.

  I tried to catch the effect in a movie. However, because of frame
  rate, it is not possible to show the effect. If if its helpful, let me
  know and I'll try harder.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu56
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jan 31 19:55:12 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2021-01-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210115)
  MachineType: BESSTAR (HK) LIMITED Z83-F
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 08/13/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A
  dmi.board.asset.tag: Default string
  dmi.board.name: T3 MRD
  dmi.board.vendor: BESSTAR Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z83-F
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: BESSTAR (HK) LIMITED
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913963/+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 1913963] [NEW] [Cherry Trail] [modeset] Cursor flickering on dual screen setup

2021-01-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When running on dual screen config, the cursor is heavily flickering.
Makes it a very unpleasant experience, if not renders it unusable. If
switched to only single screen, cursor is completely stable.

When issuing 
xrandr --output HDMI-2 --scale 0.99x0.99
again cursor is stable. Switching to 200% scaling in the desktop settings, 
doesn't help.

I tried to catch the effect in a movie. However, because of frame rate,
it is not possible to show the effect. If if its helpful, let me know
and I'll try harder.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu56
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
Date: Sun Jan 31 19:55:12 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
InstallationDate: Installed on 2021-01-30 (0 days ago)
InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115)
MachineType: BESSTAR (HK) LIMITED Z83-F
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
dmi.bios.date: 08/13/2019
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A
dmi.board.asset.tag: Default string
dmi.board.name: T3 MRD
dmi.board.vendor: BESSTAR Tech
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z83-F
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: BESSTAR (HK) LIMITED
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug has-workaround hirsute multimonitor reproducible 
ubuntu
-- 
[Cherry Trail] [modeset] Cursor flickering on dual screen setup
https://bugs.launchpad.net/bugs/1913963
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1913947] Re: [CMT-SBT20, playback] Underruns, dropouts or crackling sound

2021-01-31 Thread Daniel van Vugt
Thanks for the bug report.

It looks like you are using Bluetooth audio and also experiencing lots
of kernel crashes in the rtw88_core module.

Just in case the kernel crashes are not related, please check that you
don't still have the Settings window open as that can cause some audio
quality problems.

Next, please try disabling wifi. Because 2.4GHz wifi networks can
directly interfere with Bluetooth signal quality.

Please also run:

  lspci > lspci.txt
  lsusb > lsusb.txt

and attach the resulting text files here.

** Summary changed:

- [CMT-SBT20, playback] Underruns, dropouts or crackling sound
+ Bluetooth audio underruns, dropouts or crackling sound

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

** Tags added: a2dp

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

Title:
  Bluetooth audio underruns, dropouts or crackling sound

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The audio isn't in sync with video (ex. with youtube).
  Sometimes the audio is missing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  simone 2131 F pulseaudio
   /dev/snd/controlC0:  simone 2131 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 15:56:52 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: CMT-SBT20
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [CMT-SBT20, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DK.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DK
  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.:bvrX512DK.305:bd07/16/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DK_X512DK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DK_X512DK
  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/1913947/+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 1913947] [NEW] Bluetooth audio underruns, dropouts or crackling sound

2021-01-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The audio isn't in sync with video (ex. with youtube).
Sometimes the audio is missing

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2.3
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  simone 2131 F pulseaudio
 /dev/snd/controlC0:  simone 2131 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 31 15:56:52 2021
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: CMT-SBT20
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [CMT-SBT20, playback] Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X512DK.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X512DK
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.:bvrX512DK.305:bd07/16/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DK_X512DK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X512DK_X512DK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: a2dp amd64 apport-bug groovy
-- 
Bluetooth audio underruns, dropouts or crackling sound
https://bugs.launchpad.net/bugs/1913947
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device

2021-01-31 Thread Daniel van Vugt
Thanks for the bug report.

Indeed if you installed the driver yourself then we can't support it via
an Ubuntu task, so that makes it 'Invalid'. But it looks like Ubuntu
20.04.1 does have the 'rt2800pci' driver built-in if you install its
latest 5.8 kernel. Please try that via:

  sudo apt update
  sudo apt install linux-generic-hwe-20.04
  Reboot.

Then if you still have any issues, please open a new bug by running:

  ubuntu-bug bluez


** No longer affects: ubuntu

** Tags added: focal

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

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

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.930261] audit: type=1400 audit(1611909043.623:63): 
apparmor="DENIED" opera

[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors

2021-01-31 Thread koba
Hi, here's test kernel with the patch figureed out the suspend&resume issue 
against wd19tb.
https://drive.google.com/drive/folders/1-x2-IbsqcGJ_SICPyZuOXnplMKTUGWGu?usp=sharing

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

Title:
  Thunderbolt Dock Loses Monitors

Status in linux package in Ubuntu:
  In Progress

Bug description:
  After a suspend or locking the only way to regain external monitors is
  to unplug and replug the thunderbolt dock back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   2682 F pulseaudio
   /dev/snd/controlC0:  john   2682 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 00:22:26 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2020-07-13 (15 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.11
  dmi.board.name: 0WX9VX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+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 1900391] Re: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled

2021-01-31 Thread Евгений
EDAC sbridge: CPU SrcID # 0, Ha # 0, Channel # 1 has DIMMs, but ECC is disabled
EDAC sbridge: Couldn't find mci handler
EDAC sbridge: Failed to register device with error -19

Granted on: Ubuntu 20.04, 20.10,
I also tried installing Linux Mint the error persists.

Processor: Intel E5 2620
Chipset-based motherboard: X99

ECC RAM is not supported.

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

Title:
  EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is
  disabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4.589406] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but 
ECC is disabled
  [4.589410] EDAC sbridge: Couldn't find mci handler
  [4.589411] EDAC sbridge: Failed to register device with error -19.

  but x79 doesn't have ecc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:19:05 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900391/+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 1909840] Re: SDXC card reader not working properly

2021-01-31 Thread Kai-Heng Feng
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc5/amd64/

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

Title:
  SDXC card reader not working properly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have tried to use a 8GB flash and it works without any flaw in
  ubuntu 20.04, kernel 5.4.0-58-generic (machine: Ideapad 130s-11IGM),
  but i need to use my 128GB SDXC card and it only works in my windows
  system in the same machine. I am "able" to copy files to it  in ubuntu
  (to the 128GB SDXC card) but most of the copies appear as corrupted
  files, which does not happen in windows. The 8GB card had been tested
  by f3 in ubuntu and h2testw in windows, and the SDXC had been tested
  by h2testw in windows (testing the SDXC with f3 in ubuntu causes
  input/output error), so i assume there are no problems in the sd
  cards.


  I think that this problem is related to (or almost the same as)

  https://bugzilla.kernel.org/show_bug.cgi?id=202473


  by lspci i get

  00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03)
  00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium 
Silver Processor Dynamic Platform and Thermal Framework Processor Participant 
(rev 03)
  00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03)
  00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03)
  00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver 
Processor Trusted Execution Engine Interface (rev 03)
  00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03)
  00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev 
f3)
  00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev 
f3)
  00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev 
f3)
  00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03)
  00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03)
  00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver 
Processor SDA Standard Compliant SD Host Controller (rev 03)
  00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03)
  00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian 
Mixture Model (rev 03)
  -
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI 
Express Card Reader (rev 01)
  -
  03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus 
Bluetooth (rev 99)


  booting up and putting the SDXC card and removing it gives

  by dmesg

  [  119.612298] mmc1: cannot verify signal voltage switch
  [  119.737024] mmc1: new ultra high speed SDR104 SDXC card at address 
  [  119.737955] mmcblk1: mmc1: SB128 119 GiB 
  [  119.755488]  mmcblk1: p1
  [  208.417246] mmc1: card  removed


  The module used is rtsx_pci.

  by lspci -nnk|grep -A2 RTS5229

  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI 
Express Card Reader [10ec:5229] (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card 
Reader [10ec:5229]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci


  
  Sorry for the lack of information, i tried to use ubuntu-bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bruno  1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-12-01 (33 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5fa Chicony Electronics Co., Ltd EasyCamera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81KT
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=8afb288b-f3c1-45ee-9f28-513f989c2945 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  Tags:  focal
  Uname: Linux 5.4.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HCN22WW X64
  dmi.board.asset.tag: No Asset Tag
  dmi.

[Kernel-packages] [Bug 1852002] Re: Desktop frozen for 30 seconds after Nvidia driver crash

2021-01-31 Thread jasoncollege24
I may also have the same, or related issue.

OS: Kubuntu 20.04 LTS
CPU: Intel Core i9-9900K
GPU: GeForce RTX 2080 SUPER
Driver: Nvidia proprietary driver 460.32.03
Linux Kernel: 5.4.0-65-generic

What happened?
Was watching a movie on Plex, using the web player in the Brave browser (List 
as Version 1.19.88 Chromium: 88.0.4324.96 (Official Build) (64-bit)), when the 
system froze. I could hear sound for several seconds in the background, then it 
just stopped completely.

What was expected?
Should've continued playing the video.

Log:
NVRM: Xid (PCI::01:00): 31, pid=278, Ch 0002, intr . MMU Fault: 
ENGINE HOST0 HUBCLIENT_HOST faulted @ 0x10_. Fault is of type FAULT_PDE 
ACCESS_TYPE_VIRT_READ
NVRM: Xid (PCI::01:00): 31, pid=5096, Ch 0050, intr . MMU 
Fault: ENGINE HOST0 HUBCLIENT_HOST faulted @ 0x21_02b07000. Fault is of type 
FAULT_PDE ACCESS_TYPE_VIRT_READ

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

Title:
  Desktop frozen for 30 seconds after Nvidia driver crash

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just experienced a frozen desktop, where I could barely move the
  mouse, for maybe 30 seconds or more.

  When the desktop recovered, I looked at dmesg logs to find these
  lines:

  [  461.937702] NVRM: GPU at PCI::01:00: 
GPU-734060ac-116d-fbbb-1553-d84896b846a4
  [  461.937710] NVRM: Xid (PCI::01:00): 31, pid=275, Ch 002e, intr 
. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_0036d000. 
Fault is of type FAULT_PTE ACCESS_TYPE_VIRT_READ

  It looks like a fault from the Nvidia driver.
  I'm using the tested one "nvidia-driver-435", installed via the GUI tool.

  Could you report this to Nvidia please ?

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nvidia-driver-435 435.21-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 10 17:35:12 2019
  InstallationDate: Installed on 2019-09-26 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: nvidia-graphics-drivers-435
  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-435/+bug/1852002/+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 1902424] Re: iwlwifi missing firware for intel ax201

2021-01-31 Thread You-Sheng Yang
*** This bug is a duplicate of bug 1900883 ***
https://bugs.launchpad.net/bugs/1900883

For 5.4 kernel, iwlwifi-QuZ-a0-hr-b0-50.ucode was added for bug 1900883
in version >= 1.187.4.

For 5.8 kernel, iwlwifi-QuZ-a0-hr-b0-55.ucode was added for bug 1907158
in version >= 1.187.7.

Nothing else remains undone, so I'm marking this as duplicate of
1900883.

** This bug has been marked a duplicate of bug 1900883
   Add new iwlwifi firmware to solve AX201 hang

** Tags added: hwe-firmware

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

Title:
  iwlwifi missing firware for intel ax201

Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 20.04 does not have the correct firmware for the Intel ax201
  wifi 6 wireless card

  This affects both the 5.4 and 5.8 kernels shipped with Ubuntu 20.04

  currently ubuntu has this version of the firmware
  /lib/firmware/iwlwifi-QuZ-a0-hr-b0-48.ucode

  Kernel 5.4 is looking for iwlwifi-QuZ-a0-hr-b0-50.ucode

  Kernel 5.8 is looking for iwlwifi-QuZ-a0-hr-b0-56.ucode

  both kernels load iwlwifi-QuZ-a0-hr-b0-48.ucode as a fall back but
  having the latest firmware is desirable

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  
  $ apt-cache policy linux-firmware
  linux-firmware:
Installed: 1.187.3
Candidate: 1.187.3
Version table:
   *** 1.187.3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.187 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1902424/+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 1906452] Re: 5.4.0-56: External Display not recognized

2021-01-31 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  5.4.0-56: External Display not recognized

Status in linux package in Ubuntu:
  Expired

Bug description:
  Machine:   Type: Laptop System: Acer product: Aspire A515-44 v: V1.02 serial: 
 
 Mobo: RO model: Calla_RN v: V1.02 serial:  UEFI: INSYDE v: 
1.02 
 date: 03/23/2020 
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP 
 arch: Zen rev: 1 L2 cache: 4096 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31939 
 Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1397 
 4: 1396 5: 1863 6: 1863 7: 1863 8: 4180 
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: 5.6.0.20.20 
 bus ID: 05:00.0 chip ID: 1002:1636 
 Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa 
 compositor: marco resolution: 1920x1080~60Hz, 2560x1080~60Hz 
 OpenGL: renderer: AMD Radeon Graphics v: 4.6.14736 Core Profile 
Context 20.20 
 compat-v: 4.6.14736 direct render: Yes 

  If I use kernel linux-5.6.0.56, no external display is recognized.
  With linux-5.6.0.54 it works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906452/+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 1904895] Re: Network does not work after restart from Windows 10

2021-01-31 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Network does not work after restart from Windows 10

Status in linux package in Ubuntu:
  Expired

Bug description:
  I got a Intel I217-V integrated on the motherboard, it is an Ethernet
  NIC.

  $ lspci
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V 
(rev 04)

  Before this worked good, but yesterday it stopped working after
  restarting the computer from Windows 10. I suspect there might have
  been some Windows update maybe.

  It seems to work again after I went into the Device Manager in Windows
  and turned off power management settings.

  Under the "Advanced" tab, I selected the "Enable PME" option and
  changed it from "Enabled" to "Disabled".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-generic 5.8.0.29.34
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shockzor   1889 F pulseaudio
   /dev/snd/controlC0:  shockzor   1889 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Nov 19 17:23:08 2020
  HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9
  InstallationDate: Installed on 2013-12-26 (2519 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-29-generic N/A
   linux-backports-modules-5.8.0-29-generic  N/A
   linux-firmware1.190.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-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.:bvr2103:bd08/18/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904895/+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 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

2021-01-31 Thread Kai-Heng Feng
Thanks, apparently the root port doesn't stay at D0.
Please give this one a try:
https://people.canonical.com/~khfeng/lp1912057-bridge-d0-2/

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

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After boot the idle power consumption is around 2.3 W but after suspend it is 
4.7 W.
  The measurement is 5-10 min after boot/resume - looking at "top" to see 
system was idle.
  This is consistent - I have tried more that 10 times. 
  BIOS is updated to latest version.
  I have checked power consumption with external meter - and confirmed that it 
is higher.

  I have attached output of:
  sudo powertop -t 60 -r --html=before.html  (and after)

  I have noticed that Package C-state 6 is reached before suspend but
  not after.

  I expect that idle power consumption after suspend should be the same
  as before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-38-generic 5.8.0-38.43
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hjh1448 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 15:49:32 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-01-03 (13 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-38-generic N/A
   linux-backports-modules-5.8.0-38-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425JA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425JA
  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.ec.firmware.release: 3.4
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425JA_UX425JA
  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/1912057/+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 1913372] Re: Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot

2021-01-31 Thread Anthony Wong
** Changed in: linux-oem-5.10 (Ubuntu Hirsute)
   Status: New => Invalid

** Changed in: linux-oem-5.10 (Ubuntu Groovy)
   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/1913372

Title:
  Fix the video can't output through WD19TB connected  on TGL's Type-C
  port during cold-boot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  WD19TB would report the number of lane(2-lane) and it works well on Type-C 
port of TGL platform.
  Change the LTTPR mode to non-transparent mode, WD19TB would report the larger 
number of lane(4-lane). It's over the type-c port's bandwidth.

  [Fix]
  The patch is provided by 
Imre(https://patchwork.freedesktop.org/series/86267/).
  Calculate the PBN divider value based on the rate and lane count link 
parameters that the driver uses for all other computation.

  [Test Case]
  1. Connected the WD19TB with the TGL platform's Type-C port and
  connected the external monitor on WD19TB with HDMI/Displayport.
  2. Cold boot the TGL platform.
  3. Check the monitor can be blinked and the video can output to the monitor.

  [Where problems could occur]
  It's more reasonable to calculate the PBN divider based on the source's rate 
and lane count, not the mst's capability.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1913372/+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 1893752] Re: Get the extended DPCD according to the related field in the DPCD registers.

2021-01-31 Thread Anthony Wong
** Changed in: linux-oem-5.6 (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  Get the extended DPCD according to the related field in the DPCD
  registers.

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Incomplete
Status in linux-oem-5.6 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Connect the 4K@60Hz monitor on WD19, the monitor can't light.

  [Fix]
  As per DP spec, at first check DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT.
   
  If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 1, read the DP_DP13_DPCD_REV to 
get the faster capability. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 0, read 
DP_DPCD_REV. 

  [Test]
  With the patches, connect 4K@60Hz monitor on WD19, the machine can output the 
video to the monitor and the monitor can light.

  [Regression]
  low, Just get one more DPCD from the extended register, compare them and get 
the faster one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1893752/+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 1909840] Re: SDXC card reader not working properly

2021-01-31 Thread Kai-Heng Feng
It looks more like this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=204003

** Bug watch added: Linux Kernel Bug Tracker #204003
   https://bugzilla.kernel.org/show_bug.cgi?id=204003

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

Title:
  SDXC card reader not working properly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have tried to use a 8GB flash and it works without any flaw in
  ubuntu 20.04, kernel 5.4.0-58-generic (machine: Ideapad 130s-11IGM),
  but i need to use my 128GB SDXC card and it only works in my windows
  system in the same machine. I am "able" to copy files to it  in ubuntu
  (to the 128GB SDXC card) but most of the copies appear as corrupted
  files, which does not happen in windows. The 8GB card had been tested
  by f3 in ubuntu and h2testw in windows, and the SDXC had been tested
  by h2testw in windows (testing the SDXC with f3 in ubuntu causes
  input/output error), so i assume there are no problems in the sd
  cards.


  I think that this problem is related to (or almost the same as)

  https://bugzilla.kernel.org/show_bug.cgi?id=202473


  by lspci i get

  00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03)
  00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium 
Silver Processor Dynamic Platform and Thermal Framework Processor Participant 
(rev 03)
  00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03)
  00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03)
  00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver 
Processor Trusted Execution Engine Interface (rev 03)
  00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03)
  00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev 
f3)
  00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev 
f3)
  00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev 
f3)
  00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03)
  00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03)
  00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver 
Processor SDA Standard Compliant SD Host Controller (rev 03)
  00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03)
  00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian 
Mixture Model (rev 03)
  -
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI 
Express Card Reader (rev 01)
  -
  03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus 
Bluetooth (rev 99)


  booting up and putting the SDXC card and removing it gives

  by dmesg

  [  119.612298] mmc1: cannot verify signal voltage switch
  [  119.737024] mmc1: new ultra high speed SDR104 SDXC card at address 
  [  119.737955] mmcblk1: mmc1: SB128 119 GiB 
  [  119.755488]  mmcblk1: p1
  [  208.417246] mmc1: card  removed


  The module used is rtsx_pci.

  by lspci -nnk|grep -A2 RTS5229

  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI 
Express Card Reader [10ec:5229] (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card 
Reader [10ec:5229]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci


  
  Sorry for the lack of information, i tried to use ubuntu-bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bruno  1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-12-01 (33 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5fa Chicony Electronics Co., Ltd EasyCamera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81KT
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=8afb288b-f3c1-45ee-9f28-513f989c2945 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  Tags:  focal
  Uname: Linux 5.4.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/21/2019
  dmi.bios.ve

[Kernel-packages] [Bug 1913900] Re: Reset of USB device leads to GPF in cdc_acm kernel module

2021-01-31 Thread Kai-Heng Feng
Please attach full dmesg when the issue happens, thanks!

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

Title:
  Reset of USB device leads to GPF in cdc_acm kernel module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04 system, and a SparkFun RED-V RISC-V devboard attached via
  USB. Software used includes SEGGER J-Link (proprietary) and /opt
  /riscv-bin/riscv32-unknown-elf-gdb from the riscv github repo.

  With a 'gdb remote' connection established, via the JLink software,
  pressing the RESET button on the devboard leads to a GPF in the
  cdc_acm kernel module. The machine doesn't go dowdn instantly, but
  becomes progressively more unusable after that (e.g. ssh login hangs
  after password prompt, unlocking from screensaver leads to a black
  screen, but no desktop. Usually a reset is required because the system
  will fail to properly shut down. Although this description still lacks
  some precision, the effect is very reproducible. A USB device, and
  software without any special privileges, should not be able to
  destabilize the system.

  Jan 30 13:24:46 crunchy kernel: [ 4839.033113] cdc_acm 1-8.3:1.0: failed to 
set dtr/rts
  Jan 30 13:24:46 crunchy kernel: [ 4839.045325] xhci_hcd :00:14.0: WARN 
Cannot submit Set TR Deq Ptr
  Jan 30 13:24:46 crunchy kernel: [ 4839.045329] xhci_hcd :00:14.0: A Set 
TR Deq Ptr command is pending.
  Jan 30 13:24:46 crunchy kernel: [ 4839.046417] general protection fault:  
[#1] SMP PTI
  Jan 30 13:24:46 crunchy kernel: [ 4839.046430] CPU: 5 PID: 55103 Comm: 
kworker/5:3 Tainted: P   OE 5.4.0-65-generic #73-Ubuntu
  Jan 30 13:24:46 crunchy kernel: [ 4839.046435] Hardware name: System 
manufacturer System Product Name/PRIME Z270M-PLUS, BIOS 1205 05/14/2018
  Jan 30 13:24:46 crunchy kernel: [ 4839.046451] Workqueue: events acm_softint 
[cdc_acm]
  Jan 30 13:24:46 crunchy kernel: [ 4839.046465] RIP: 
0010:usb_clear_halt+0x1d/0xc0
  Jan 30 13:24:46 crunchy kernel: [ 4839.046474] Code: 85 f6 75 e8 c3 0f 1f 84 
00 00 00 00 00 0f 1f 44 00 00 55 89 f0 48 89 e5 41 54 49 89 fc 53 89 f3 c1 fb 
0f 83 e3 0f 48 83 ec 08 <8b> 37 c1 e6 08 81 ce 00 00 00 80 a8 80 74 44 68 88 13 
00 00 80 cb
  Jan 30 13:24:46 crunchy kernel: [ 4839.046480] RSP: 0018:b4523f1e3e18 
EFLAGS: 00010296
  Jan 30 13:24:46 crunchy kernel: [ 4839.046487] RAX: c0408780 RBX: 
0001 RCX: 92bbe148
  Jan 30 13:24:46 crunchy kernel: [ 4839.046493] RDX: 0001 RSI: 
c0408780 RDI: 9b444bbb6b70a4de
  Jan 30 13:24:46 crunchy kernel: [ 4839.046498] RBP: b4523f1e3e30 R08: 
0108 R09: 98c5b6b46068
  Jan 30 13:24:46 crunchy kernel: [ 4839.046503] R10: 8a0a R11: 
 R12: 9b444bbb6b70a4de
  Jan 30 13:24:46 crunchy kernel: [ 4839.046508] R13: 98c5b6b70700 R14: 
98c3e5537000 R15: 98c3d454be40
  Jan 30 13:24:46 crunchy kernel: [ 4839.046515] FS:  () 
GS:98c5b6b4() knlGS:
  Jan 30 13:24:46 crunchy kernel: [ 4839.046520] CS:  0010 DS:  ES:  
CR0: 80050033
  Jan 30 13:24:46 crunchy kernel: [ 4839.046526] CR2: 7efd6d25f020 CR3: 
000fa64e8005 CR4: 003606e0
  Jan 30 13:24:46 crunchy kernel: [ 4839.046531] DR0:  DR1: 
 DR2: 
  Jan 30 13:24:46 crunchy kernel: [ 4839.046537] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jan 30 13:24:46 crunchy kernel: [ 4839.046540] Call Trace:
  Jan 30 13:24:46 crunchy kernel: [ 4839.046556]  acm_softint+0x65/0xf0 
[cdc_acm]
  Jan 30 13:24:46 crunchy kernel: [ 4839.046570]  process_one_work+0x1eb/0x3b0
  Jan 30 13:24:46 crunchy kernel: [ 4839.046580]  worker_thread+0x4d/0x400
  Jan 30 13:24:46 crunchy kernel: [ 4839.046591]  kthread+0x104/0x140
  Jan 30 13:24:46 crunchy kernel: [ 4839.046600]  ? process_one_work+0x3b0/0x3b0
  Jan 30 13:24:46 crunchy kernel: [ 4839.046607]  ? kthread_park+0x90/0x90
  Jan 30 13:24:46 crunchy kernel: [ 4839.046619]  ret_from_fork+0x35/0x40
  Jan 30 13:24:46 crunchy kernel: [ 4839.046627] Modules linked in: cdc_acm 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables 
iptable_filter bpfilter bridge stp llc binfmt_misc zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) intel_rapl_msr zlua(PO) 
snd_hda_codec_hdmi mei_hdcp intel_rapl_common x86_pkg_temp_thermal 
intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
snd_seq_midi kvm snd_seq_midi_event snd_hda_intel snd_intel_dspcfg snd_rawmidi 
rapl snd_hda_codec intel_cstate snd_hda_core snd_hwdep eeepc_wmi asus_wmi 
sparse_keymap wmi_bmof mxm_wmi snd_pcm snd_seq snd_seq_device snd_time

[Kernel-packages] [Bug 1912898] Re: [i915] With kernel 5.8, video crashes, system freezes. But 5.4 works.

2021-01-31 Thread Daniel van Vugt
** Package changed: linux (Ubuntu) => linux-signed-hwe-5.8 (Ubuntu)

** Tags added: 5.8-gfx

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

Title:
  [i915] With kernel 5.8, video crashes, system freezes. But 5.4 works.

Status in linux-hwe-5.8 package in Ubuntu:
  New
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  1) Chromebox 2955U trying to run Ubuntu 20.04 with updates. Has been running 
Ubuntu for many years.
  2) Video seems to crash when ANY program, menu item or terminal is started 
after reboot. Flashing screen fields, boxes, menus. Cursor freezes or stutters. 
 
  3) 18.02 ran and runs fine in other partitions.
  4) Latest Debian runs fine in other partiton.
  5) Ubuntu 20.04 runs fine when running directly from USB flashdrive. This is 
really wierd.
  6) Occurs immediately after a fresh installation of 20.04 in any partition. 
Verified sha256sums.
  7) Can make system usable with nomodeset in grub linux line but runs very 
slow.
  8) Tried "sudo apt-get install xserver-xorg-video-intel". ... Already running 
latest.  
  9) Memtest86 ran 2 full iterations, no errors.
  10) Seems like I verified an older kernel worked fine, but an "autoremove" 
removed it/them. 
  11) I've been fighting this for a few months now. 

  Thank you for any support you can give...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 23 08:41:43 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Google, Inc. Haswell-ULT Integrated Graphics Controller 
[1ae0:c000]
  InstallationDate: Installed on 2020-10-03 (111 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3393 IMC Networks 
   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: Google Panther
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=3124be5d-3014-4ee1-ac5b-8c48babfde15 ro quiet splash nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2014
  dmi.bios.release: 4.0
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.0-7565-gc6e3a3a-dirty
  dmi.board.name: Panther
  dmi.board.vendor: Google
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Google
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.0-7565-gc6e3a3a-dirty:bd12/10/2014:br4.0:efr0.0:svnGoogle:pnPanther:pvr1.0:rvnGoogle:rnPanther:rvr1.0:cvnGoogle:ct3:cvr:
  dmi.product.name: Panther
  dmi.product.version: 1.0
  dmi.sys.vendor: Google
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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-hwe-5.8/+bug/1912898/+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 1913045] Re: [i915] System freezes with kernel 5.8, but not 5.4

2021-01-31 Thread Daniel van Vugt
** Package changed: linux (Ubuntu) => linux-signed-hwe-5.8 (Ubuntu)

** Tags added: 5.8-gfx

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

Title:
  [i915] System freezes with kernel 5.8, but not 5.4

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  My system freezes when I'm in lockscreen. This happens every few ours
  after I leave the computer running some low to mediocre computation
  tasks, no memory problems. It does not happen when I run heavy tasks.
  I can only hard reboot, nothing else is working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 25 11:26:10 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 620 [17aa:2245]
  InstallationDate: Installed on 2020-06-02 (236 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20HD0001MZ
  ProcEnviron:
   LANGUAGE=de_CH:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=df6eb87b-cd89-4867-9c7c-de8b08bbdbcf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2020
  dmi.bios.release: 1.63
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET88W (1.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HD0001MZ
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.35
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET88W(1.63):bd04/22/2020:br1.63:efr1.35:svnLENOVO:pn20HD0001MZ:pvrThinkPadT470:rvnLENOVO:rn20HD0001MZ:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470
  dmi.product.name: 20HD0001MZ
  dmi.product.sku: LENOVO_MT_20HD_BU_Think_FM_ThinkPad T470
  dmi.product.version: ThinkPad T470
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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-signed-hwe-5.8/+bug/1913045/+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 1912936] Re: [i915] Unable to launch GUI application due to Intel GPU driver bug

2021-01-31 Thread Daniel van Vugt
Please try a kernel from the 5.4 series instead like:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.94/

** Summary changed:

- Unable to launch GUI application due to Intel GPU driver bug 
+ [i915] Unable to launch GUI application due to Intel GPU driver bug

** Package changed: linux (Ubuntu) => linux-signed-hwe-5.8 (Ubuntu)

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: Confirmed => Incomplete

** Tags added: 5.8-gfx

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

Title:
  [i915] Unable to launch GUI application due to Intel GPU driver bug

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  I can confirm this problem: https://askubuntu.com/questions/1306700
  /fixing-gpu-hang-caused-by-i915-driver

  Symptom: unable to launch any application after login on to the
  system, login screen etc works fine. The system thus becomes
  completely unusable for regular users. I have tried both X and
  Wayland.

  Workaround: boot using "nomodeset" kernel parameter. The lowlatency
  kernel did not help in my case.

  Error (dmesg): "i915 :00:02.0: [drm] GPU HANG: ecode 7:1:85ddfffd,
  in Xorg [8648]"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-generic 5.4.0.64.67
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  karla  4037 F pulseaudio
   /dev/snd/controlC0:  karla  4037 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Jan 24 10:36:59 2021
  InstallationDate: Installed on 2015-04-20 (2105 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: Acer Aspire V5-473P
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: 
BOOT_IMAGE=/ZFSL/System/U1804@/boot/vmlinuz-5.8.0-40-generic 
root=ZFS=hostname-isatapool/ZFSL/System/U1804 ro ZFSSNAP=31 quiet splash 
elevator=noop vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-40-generic N/A
   linux-backports-modules-5.8.0-40-generic  N/A
   linux-firmware1.187.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-10-04 (111 days ago)
  dmi.bios.date: 01/12/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Polaris_HW
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.30:bd01/12/2015:br0.0:efr0.0:svnAcer:pnAspireV5-473P:pvrTBDbyOEM:rvnAcer:rnPolaris_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V5-473P
  dmi.product.sku: Aspire V5-473P_079C_2_30
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912936/+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 1913217] Re: [nvidia] Screen going black and not responding to input

2021-01-31 Thread Daniel van Vugt
If the problem started in a kernel update then you might be able to
solve it by going back to a 5.4 kernel like:

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

You wouldn't be the first to find graphics problems in kernel 5.8.


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

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

** Package changed: linux (Ubuntu) => linux-signed-hwe-5.8 (Ubuntu)

** Tags added: 5.8-gfx

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

Title:
  [nvidia] Screen going black and not responding to input

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expecting:
  (usually after opening a new application): window to open

  Happened instead:
  Screen going black. System not responding to inputs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 25 21:49:05 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed
   nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
   NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7]
  InstallationDate: Installed on 2021-01-24 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Apple Inc. MacBookPro6,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic 
root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 99.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22586C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22586C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro6,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  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.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
h

[Kernel-packages] [Bug 1912676] Re: Fix regression introduced by codec PM change

2021-01-31 Thread Kai-Heng Feng
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
   Fix regression introduced by codec PM change

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.10 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  After the codec PM optimization, laptops with SOF may take very long to
  suspend. In addition to that, HDA may not be able to be runtim suspended
  again after resume from hibernation.

  [Fix]
  Prevent the SOF driver touches codec during system suspend, and properly
  refcount the PM usage counter.

  [Test]
  On an affected SOF system, it takes 5 mins to suspend.
  On another affected HDA system, S4 resume causes high power consumption
  becuase HDA controller can't be runtime suspended.

  Both issues are gone by applying these patches.

  [Where problems could occur]
  If somehow any laptop depends on the old behavior to work properly, this
  can break them. It's highly unlikely though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1912676/+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 1911830] Re: alsa/sdw: support soundwire audio for TGL-H machines

2021-01-31 Thread Hui Wang
Installed the 5.10.0-1012-oem kernel on the Dell TGL-H machine with
soundwire audio, the speaker, headphone, internal mic and headset-mic
all worked well.

verified done.


** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  alsa/sdw: support soundwire audio for TGL-H machines

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  In the OEM project, we have a new TGL-H soundwire machine, with
  the current oem-5.10 kernel, the audio can't work.

  [Fix]
  Backport 6 patches from Intel thesofproject kernel.

  [Test]
  Put the testing sof-tgl-h.ri in the /lib/firmware/intel/sof,
  boot the patched kernel, we could see speakers and microphone
  from gnome-setting, and they all work well.

  
  [Where problems could occur]
  The patches changed soundwire machine driver, it is possible
  to make the audio on old soundwire machines not work anymore.
  But we tested the patches on TGL-U and cml soundwire machines,
  all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1911830/+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 1852493] Re: Freeze on suspend (Acer SF314-57)

2021-01-31 Thread Kedar Patankar
Reporting after a long time, but the s2idle=deep does not really fix anything. 
Just made it less frequent if at all. Since then I have upgraded to 20.04 and 
the issue is there.
I have essentially given up on using any kind of power management on this 
laptop under 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/1852493

Title:
  Freeze on suspend (Acer SF314-57)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I freshly installed Ubuntu Budgie 19.10 today after receiving my new
  notebook. However, when putting the system to suspend (or hibernate),
  the screen goes off and the system freezes. The fan keeps running,
  keyboard backlight and power led are on. Sometimes, when pressing a
  button, I can get the screen to turn back on, but its frozen as well
  (no mouse movement, clock stuck etc.)

  So far I tried increasing the swap file size, however this did not
  help. I also livebooted Ubuntu 19.10 and tried suspend, but I had the
  same issue.

  Could this be a problem of my fairly new chipset (Intel i7 1065G7)?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  norbert1508 F pulseaudio
   /dev/snd/pcmC0D0p:   norbert1508 F...m pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-13 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: Acer Swift SF314-57
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/vgubuntu--budgie-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

2021-01-31 Thread ch shr
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458611/+files/WifiSyslog.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/1913933

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no

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

2021-01-31 Thread ch shr
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458608/+files/ProcModules.txt

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: 

[Kernel-packages] [Bug 1913933] acpidump.txt

2021-01-31 Thread ch shr
apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458612/+files/acpidump.txt

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

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy

[Kernel-packages] [Bug 1913933] Lsusb-v.txt

2021-01-31 Thread ch shr
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458603/+files/Lsusb-v.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/1913933

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tag

[Kernel-packages] [Bug 1913933] Lsusb-t.txt

2021-01-31 Thread ch shr
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458602/+files/Lsusb-t.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/1913933

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tag

[Kernel-packages] [Bug 1913933] Lspci-vt.txt

2021-01-31 Thread ch shr
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458600/+files/Lspci-vt.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/1913933

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  T

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

2021-01-31 Thread ch shr
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458606/+files/ProcCpuinfoMinimal.txt

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes

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

2021-01-31 Thread ch shr
apport information

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

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags: 

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

2021-01-31 Thread ch shr
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458605/+files/ProcCpuinfo.txt

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: 

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

2021-01-31 Thread ch shr
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458607/+files/ProcInterrupts.txt

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blo

[Kernel-packages] [Bug 1913933] PaInfo.txt

2021-01-31 Thread ch shr
apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1913933/+attachment/5458604/+files/PaInfo.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/1913933

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags: 

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

2021-01-31 Thread ch shr
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458609/+files/PulseList.txt

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
 

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

2021-01-31 Thread ch shr
apport information

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

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  g

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

2021-01-31 Thread ch shr
apport information

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

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  g

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

2021-01-31 Thread ch shr
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458597/+files/CurrentDmesg.txt

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked

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

2021-01-31 Thread ch shr
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1913933/+attachment/5458598/+files/IwConfig.txt

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  T

[Kernel-packages] [Bug 1913933] Re: System freeze while dbus-daemon execution

2021-01-31 Thread ch shr
apport information

** Tags added: apport-collected

** Description changed:

  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last time
  it happened:
  
  These are the last 3 kernel log entries before the freeze:
  
  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  
  So I think this is related to the dbus-daemon.
  
  If you need any more information, please let me know so I can provide
  them.
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  chris  2241 F pulseaudio
+  /dev/snd/controlC0:  chris  2241 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 20.10
+ HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
+ MachineType: Micro-Star International Co., Ltd MS-7A34
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/usr/bin/bash
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
+ RelatedPackageVersions:
+  linux-restricted-modules-5.8.0-41-generic N/A
+  linux-backports-modules-5.8.0-41-generic  N/A
+  linux-firmware1.190.3
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: yes
+   Hard blocked: no
+ Tags:  groovy
+ Uname: Linux 5.8.0-41-generic x86_64
+ UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/02/2020
+ dmi.bios.release: 5.14
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: A.LR
+ dmi.board.ass

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

2021-01-31 Thread ch shr
apport information

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

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  2241 F pulseaudio
   /dev/snd/controlC0:  chris  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  gro

[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device

2021-01-31 Thread Jeremy
Yes, you obviously have a driver issue along with a Bluez version that
was installed via a snap package that is getting blocked by apparmor

You should run in terminal apport-collect 1913859

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

Title:
  RT3290 Bluetooth not finding any device

Status in Ubuntu:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.930261] audit: type=1400 audit(1611909043.623:63): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   68.194380] audit: type=1400 audit(1611909043.887:65): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [ 

[Kernel-packages] [Bug 1913950] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build

2021-01-31 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel
  module failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  guanhe@guanhe-Lenovo-G510:~/Downloads$ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.3_amd64.deb

  cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log 
  DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-41-generic 
(x86_64)
  2021年 01月 31日 星期日 23:09:12 CST
  make: Entering directory '/usr/src/linux-headers-5.8.0-41-generic'
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
AR  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: 
In function ‘wl_dev_ioctl’:
  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9:
 error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? 
[-Werror=implicit-function-declaration]
462 |  set_fs(get_ds());
| ^~
| get_fs
  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9:
 error: incompatible type for argument 1 of ‘set_fs’
462 |  set_fs(get_ds());

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-41-generic
  Date: Sun Jan 31 23:09:15 2021
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.3:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9:
 error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2020-12-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.3
  Python3Details: /usr/local/bin/python3.9, Python 3.9.1, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1913950/+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 1913950] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build

2021-01-31 Thread guanhe
Public bug reported:

guanhe@guanhe-Lenovo-G510:~/Downloads$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.3_amd64.deb

cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log 
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-41-generic (x86_64)
2021年 01月 31日 星期日 23:09:12 CST
make: Entering directory '/usr/src/linux-headers-5.8.0-41-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
  AR  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
  CC [M]  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: 
In function ‘wl_dev_ioctl’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9:
 error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? 
[-Werror=implicit-function-declaration]
  462 |  set_fs(get_ds());
  | ^~
  | get_fs
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9:
 error: incompatible type for argument 1 of ‘set_fs’
  462 |  set_fs(get_ds());

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.8.0-41-generic
Date: Sun Jan 31 23:09:15 2021
DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.3:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9:
 error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? 
[-Werror=implicit-function-declaration]
InstallationDate: Installed on 2020-12-14 (48 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.3
Python3Details: /usr/local/bin/python3.9, Python 3.9.1, unpackaged
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.2
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel
  module failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  guanhe@guanhe-Lenovo-G510:~/Downloads$ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.3_amd64.deb

  cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log 
  DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-41-generic 
(x86_64)
  2021年 01月 31日 星期日 23:09:12 CST
  make: Entering directory '/usr/src/linux-headers-5.8.0-41-generic'
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
AR  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: 
In function ‘wl_dev_ioctl’:
  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9:
 error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? 
[-Werror=implicit-function-declaration]
462 |  set_fs(get_ds());
| ^~
| get_fs
  
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9:
 error: incompatible type for argument 1 of ‘set_fs’
462 |  set_fs(get_ds());

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-41-generic
  Date: Sun Jan 31 23:09:15 2021
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0u

[Kernel-packages] [Bug 1913944] [NEW] broadcom wireless adapter disappears after reboot

2021-01-31 Thread Patrick Castillo
Public bug reported:

Used Updater to install additional drivers for my Broadcom wireless. It worked 
at first but when I booted up the next day the wifi icon was gone as if I had 
to wifi adapter at all.
my specs: 
lspci -nn -d 14e4:
04:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4322 
802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)

This Below is what happens when I tried a fix that was suggested:

sudo apt install bcmwl-kernel-source
[sudo] password for anansi: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
bcmwl-kernel-source is already the newest version (6.30.223.271+bdcom-0ubuntu5).
The following packages were automatically installed and are no longer required:
  libfprint-2-tod1 libllvm10
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ...
Removing old bcmwl-6.30.223.271+bdcom DKMS files...

--
Deleting module version: 6.30.223.271+bdcom
completely from the DKMS tree.
--
Done.
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.8.0-41-generic
Building for architecture x86_64
Building initial module for 5.8.0-41-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-so
urce.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-41-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more informati
on.
dpkg: error processing package bcmwl-kernel-source (--configure):
 installed bcmwl-kernel-source package post-installation script subprocess retur
ned error exit status 10
Errors were encountered while processing:
 bcmwl-kernel-source
E: Sub-process /usr/bin/dpkg returned an error code (1)

Heeelp!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 31 08:27:11 2021
InstallationDate: Installed on 2021-01-27 (4 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  broadcom wireless adapter disappears after reboot

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Used Updater to install additional drivers for my Broadcom wireless. It 
worked at first but when I booted up the next day the wifi icon was gone as if 
I had to wifi adapter at all.
  my specs: 
  lspci -nn -d 14e4:
  04:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4322 
802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
  
  This Below is what happens when I tried a fix that was suggested:

  sudo apt install bcmwl-kernel-source
  [sudo] password for anansi: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  bcmwl-kernel-source is already the newest version 
(6.30.223.271+bdcom-0ubuntu5).
  The following packages were automatically installed and are no longer 
required:
libfprint-2-tod1 libllvm10
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ...
  Removing old bcmwl-6.30.223.271+bdcom DKMS files...

  --
  Deleting module version: 6.30.223.271+bdcom
  completely from the DKMS tree.
  --
  Done.
  Loading new bcmwl-6.30.223.271+bdcom DKMS files...
  Building for 5.8.0-41-generic
  Building for architecture x86_64
  Building initial module for 5.8.0-41-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-so
  urce.0.crash'
  Error! Bad return status for module build on kernel: 5.8.0-41-generic (x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more 
informati
  on.
  dpkg: error processing package bcmwl-kernel-source (

[Kernel-packages] [Bug 1912676] Re: Fix regression introduced by codec PM change

2021-01-31 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
   Fix regression introduced by codec PM change

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.10 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  After the codec PM optimization, laptops with SOF may take very long to
  suspend. In addition to that, HDA may not be able to be runtim suspended
  again after resume from hibernation.

  [Fix]
  Prevent the SOF driver touches codec during system suspend, and properly
  refcount the PM usage counter.

  [Test]
  On an affected SOF system, it takes 5 mins to suspend.
  On another affected HDA system, S4 resume causes high power consumption
  becuase HDA controller can't be runtime suspended.

  Both issues are gone by applying these patches.

  [Where problems could occur]
  If somehow any laptop depends on the old behavior to work properly, this
  can break them. It's highly unlikely though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1912676/+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 1911830] Re: alsa/sdw: support soundwire audio for TGL-H machines

2021-01-31 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
  alsa/sdw: support soundwire audio for TGL-H machines

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  In the OEM project, we have a new TGL-H soundwire machine, with
  the current oem-5.10 kernel, the audio can't work.

  [Fix]
  Backport 6 patches from Intel thesofproject kernel.

  [Test]
  Put the testing sof-tgl-h.ri in the /lib/firmware/intel/sof,
  boot the patched kernel, we could see speakers and microphone
  from gnome-setting, and they all work well.

  
  [Where problems could occur]
  The patches changed soundwire machine driver, it is possible
  to make the audio on old soundwire machines not work anymore.
  But we tested the patches on TGL-U and cml soundwire machines,
  all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1911830/+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 1913372] Re: Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot

2021-01-31 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
  Fix the video can't output through WD19TB connected  on TGL's Type-C
  port during cold-boot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.10 source package in Groovy:
  New
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  [Impact]
  WD19TB would report the number of lane(2-lane) and it works well on Type-C 
port of TGL platform.
  Change the LTTPR mode to non-transparent mode, WD19TB would report the larger 
number of lane(4-lane). It's over the type-c port's bandwidth.

  [Fix]
  The patch is provided by 
Imre(https://patchwork.freedesktop.org/series/86267/).
  Calculate the PBN divider value based on the rate and lane count link 
parameters that the driver uses for all other computation.

  [Test Case]
  1. Connected the WD19TB with the TGL platform's Type-C port and
  connected the external monitor on WD19TB with HDMI/Displayport.
  2. Cold boot the TGL platform.
  3. Check the monitor can be blinked and the video can output to the monitor.

  [Where problems could occur]
  It's more reasonable to calculate the PBN divider based on the source's rate 
and lane count, not the mst's capability.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1913372/+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 1913933] Missing required logs.

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

apport-collect 1913933

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

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

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

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

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913933/+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 1913933] Re: System freeze while dbus-daemon execution

2021-01-31 Thread Kai-Heng Feng
** Package changed: dbus (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/1913933

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  New

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913933/+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 1913933] [NEW] System freeze while dbus-daemon execution

2021-01-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I regularly get my system frozen while using. It does not occur on any
user interaction I do periodically, so I checked the log files last time
it happened:

These are the last 3 kernel log entries before the freeze:

Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

So I think this is related to the dbus-daemon.

If you need any more information, please let me know so I can provide
them.


ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: dbus 1.12.20-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun Jan 31 09:22:49 2021
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/usr/bin/bash
SourcePackage: dbus
UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)

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


** Tags: amd64 apport-bug groovy
-- 
System freeze while dbus-daemon execution
https://bugs.launchpad.net/bugs/1913933
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2021-01-31 Thread Stefano
I have the same issue, I'm using an ASUS k50in with graphic card Nvidea GT220M. 
When I power off my laptop the procedure stops at the output line Reached 
target Power-Off.
This is the output of the command uname -a for my laptop

Linux stefano-K61IC 5.8.0-40-generic #45~20.04.1-Ubuntu SMP Fri Jan 15
11:35:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

I have tried in the grub configurations the 
GRUB_CMDLINE_LINUX_DEFAULT='acpi=force' then I tried using 
GRUB_CMDLINE_LINUX_DEFAULT='acpi=noirq' and then 
GRUB_CMDLINE_LINUX_DEFAULT='acpi=off' everytime without success.
Can you suggest a way to fix it? Or some debug steps that can be performed to 
better understand the issue?

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

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

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1594023/+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 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

2021-01-31 Thread Leonard Broman
@andch

Thanks for reporting this progress so us 9310 owners can solve this
eventually!

I tried this but got only minor progress. Update to 1.2.5 firmware as
you advised.

Installed kernel 5.10.12 with mainline but can only see wifi list
(better than before) but not connect. Bluetooth is not working either.

Also tried
5.6.0-1036-oem
5.6.0-1042-oem
Both locks up on the login screen and forces me to do 4 second hard power down.

I could not find the package you mentioned, which PPA did you get this
kernel so I can try it out?

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

Title:
  Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Won't Fix
Status in linux-firmware source package in Groovy:
  Won't Fix
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification: oem-5.6]

  [Impact]

  Qualcomm QCA6390 series not recognized due to the lack of ath11k and all
  its prerequisite drivers.

  $ lspci
  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  [Fix]

  Tag ath11k-qca6390-bringup-202011301608 from ath tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git) marks
  first stable milestone on the platform/device under development since
  v5.6-rc1. Most of the commits under this tag, ~350 commits, have been
  in vanilla kernel v5.10-rc4 except those starting from commit
  065c9528cc50 ("ath11k: add 64bit check before reading msi high addr").

  While ath11k depends on MHI bus, qrtr and qmi helpers, changes falling
  in these components are also pulled.

  Besides, tx encapsulation
  https://lore.kernel.org/linux-wireless/20200908123702.88454-1-...@nbd.name/
  and a couple more inclusive of 6 GHz capability, BSS Color were also
  pulled to satisfy API changes in mac80211/cfg80211.

  [Test Case]

  1. Install firmwares & boot from patched kernel,
  2. ath11k should be now up and running. Check with
 `sudo dmesg | grep ath11k`

  While this is going to bring massive changes to the kernel, as well as
  shared wireless stack that is not only used by ath11k but also many
  others, prebuilt kernel/firmware packages were deployed on platforms
  with and without ath11k for regression tests, and so far the results are
  positive.

  [Where problems could occur]

  ath11k and its relying parts have never been enabled in oem-5.6, so
  changes to them should have little effect on most platforms. For
  platforms equip QCA6390, this will be the first time they're probed and
  enabled, and as the driver is still under polishing, there can be
  regressions, performance lost, power consumption increase at this
  moment.

  Changes to wireless stack could also be an issue as this introduces
  interface changes to the API, so maybe DKMS packages in the wild will be
  affected.

  == SRU for U/OEM-5.10 ==

  [SRU Justification: U/OEM-5.10]

  [Impact]

  Qualcomm QCA6390 series not recognized due to the lack of ath11k
  driver.

  $ lspci
  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  [Fix]

  25 additional fixes in ath tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag
  ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms,
  and firmware updates from mainline are required.

  [Test Case]

  1. Install firmwares & boot from patched kernel,
  2. ath11k should be now up and running. Check with
     `sudo dmesg | grep ath11k`

  [Where problems could occur]

  There has been a lot patches landed in kernel since 5.7 devel cycle. The
  last bits here has merge base with mainline at v5.10-rc4, and since then
  only patches for ath11k itself has been committed.

  == Original Bug Description ==

  Qualcomm QCA6390 series not recognized due to the lack of ath11k
  driver.

  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  Depending on bug 1891632 to fix Wi-Fi dead after resumed from suspend.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1842 F...

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-01-31 Thread Chelsea Sidrane
Oh, I understand Nicolas' message now: maybe there is a patched 5.8
kernel I can just install?

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(cus

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-01-31 Thread Chelsea Sidrane
Thanks all for this thread!

I have the legion 5 with a MSFT0001:00 04F3:3186 Touchpad 
graphics: 0NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] (rev a1)

I got this error message when trying to do what Eamon (342) said (upgrade the 
kernel), as I too am new to kernel patching:
ERROR (dkms apport): kernel package linux-headers-5.11.0-051100rc2-generic is 
not supported
Error! Bad return status for module build on kernel: 5.11.0-051100rc2-generic 
(x86_64)

It said to consult this log:
/var/lib/dkms/nvidia/460.32.03/build/make.log

which is attached.

It seems like maybe this isn't compatible with my nvidia graphics card (1660) 
for some reason?
Has anyone else has this problem?

So instead I tried to solve my touchpad issues by upgrading to 5.9.16
like Koen said in 325, but my it did not fix things :/

If there are no other "quick fixes" I supposed I will embark on the
journey of applying #189. But just wondering -- will #189 work with the
kernel I just installed: 5.9.16 or would I have to install
5.9.0-rc7-MANJARO+ ?


** Attachment added: "error log from trying to install kernel 5.11.0 rc2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5458483/+files/make.log

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboard