from:"E"

Oh, I DO have sound in the speakers, BT high def (A2DP) audio too...

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  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/pulseaudio/+bug/1988658/+subscriptions


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

[Desktop-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

$ lspci | grep -i audio
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller 
(rev a1)

*** Is there REALLY Realtek audio hardware in here too? 
*** or just a partly initialized driver due to the missing hardware?

Looks as that driver(?) in linux-modules-extra-(uname -r)...

$ apt-file find snd-hda-intel | grep $(uname -r)
linux-modules-extra-5.13.0-52-generic: 
/lib/modules/5.13.0-52-generic/kernel/sound/pci/hda/snd-hda-intel.ko

$ apt-file find snd-hda-intel | wc -l
576

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.

[Desktop-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

$ cat /sys/class/sound/hwC0D0/vendor_name
Realtek

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  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/pulseaudio/+bug/1988658/+subscriptions


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

[Desktop-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

Hmm...

$ cat /sys/class/sound/hwC0D0/chip_name
ALC294

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  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/pulseaudio/+bug/1988658/+subscriptions


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

[Desktop-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

--- audio in the output of lshw ---

   *-multimedia
description: Audio device
product: TU116 High Definition Audio Controller
vendor: NVIDIA Corporation
physical id: 0.1
bus info: pci@:01:00.1
version: a1
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:17 memory:a508-a5083fff
---

*-multimedia
 description: Audio device
 product: Cannon Lake PCH cAVS
 vendor: Intel Corporation
 physical id: 1f.3
 bus info: pci@:00:1f.3
 version: 10
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi bus_master cap_list
 configuration: driver=snd_hda_intel latency=32
 resources: irq:150 memory:a5418000-a541bfff 
memory:a510-a51f
---

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asse

[Desktop-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

--- seen in dmesg ---
[5.815777] Bluetooth: hci0: Firmware revision 0.1 build 26 week 11 2020
[5.881465] NET: Registered protocol family 38
[9.328954] wlo1: authenticate with 94:18:65:08:59:ae
[9.338666] wlo1: send auth to 94:18:65:08:59:ae (try 1/3)
[9.382307] wlo1: authenticated
[9.384831] wlo1: associate with 94:18:65:08:59:ae (try 1/3)
[9.389564] wlo1: RX AssocResp from 94:18:65:08:59:ae (capab=0x431 status=0 
aid=3)
[9.392938] wlo1: associated
[9.505267] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
[   64.717314] snd_hda_intel :00:1f.3: couldn't bind with audio component
[   64.772851] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[   64.772856] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   64.772858] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   64.772860] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   64.772862] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   64.772863] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
[   64.772865] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   65.227287] snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel 
HDMI/DP codec
[   65.231312] hdaudio hdaudioC0D2: Unable to configure, disabling
[   65.232125] input: HDA Intel PCH Headset Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input21
[   65.232353] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input22
[  481.066720] kauditd_printk_skb: 22 callbacks suppressed
[  481.066723] audit: type=1400 audit(1663175820.795:34): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=2107 
comm="cups-browsed" capability=23  capname="sys_nice"
[  482.476639] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit
[  482.476642] usb usb3: root hub lost power or was reset
[  482.476643] usb usb4: root hub lost power or was reset
[  482.598315] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[  482.687635] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
[  484.946351] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[  485.054903] rfkill: input handler disabled
[  491.657064] Bluetooth: RFCOMM TTY layer initialized
[  491.657070] Bluetooth: RFCOMM socket layer initialized
[  491.657073] Bluetooth: RFCOMM ver 1.11
[  491.886727] rfkill: input handler enabled
[  492.013259] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[  493.174837] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[  493.434596] rfkill: input handler disabled

--- end of dmsg ---
" autoconfig for ALC294" =>

$ sudo lshw | grep ALC294 | wc -l
0
$
---
https://www.google.com/search?q=ALC294+%2Bg731 -> notably "g731" doesn't seem 
to be present in the google-search for ALC294 

https://www.google.com/search?q=%2BALC294+%2Bg731 => no match on g731

Why is there an attempt to initialize this non-existant hardware?

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfki

[Desktop-packages] [Bug 1988658] [NEW] boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

2022-09-03 Thread Hannu E K N

Public bug reported:

$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

3 to 5 of 10 boot occasions stops prematurely.

dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
I have NOT investigated further (knowledge limit).

This very latest bootup seemed to indicate that there is something
waiting on the keyboard, as I got all the way "up" after beating
repeatedly - alternating - on ESC and ENTER

--- dmesg tail on this boot ---
4 sec pause from previous line (at 9 secs)
[   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit
[   13.444031] usb usb3: root hub lost power or was reset
[   13.444032] usb usb4: root hub lost power or was reset
[   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
[   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[   17.105681] rfkill: input handler disabled
[   28.694324] Bluetooth: RFCOMM TTY layer initialized
[   28.694328] Bluetooth: RFCOMM socket layer initialized
[   28.694331] Bluetooth: RFCOMM ver 1.11
[   28.922797] rfkill: input handler enabled
[   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[   31.907300] rfkill: input handler disabled
[   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit
[   78.940840] usb usb3: root hub lost power or was reset
[   78.940841] usb usb4: root hub lost power or was reset
[  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit
[  929.174669] usb usb3: root hub lost power or was reset
[  929.174671] usb usb4: root hub lost power or was reset
-- end ---

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.13
ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CasperMD5CheckResult: skip
Date: Sun Sep  4 08:19:01 2022
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2021
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G731GU.312
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G731GU
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: 0.6
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G731GU_G731GU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focal

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=foc

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-29 Thread Douglas E Engert

Thanks for the ldd output.
libpcsclite.so.1 is the lib to used the pcscd socket, and is used by modules 
libstpkcs11.so, libeToken.so.10.7.77 and libopensc.so.8 (see below)   It is not 
used in libbit4xpki.so which may be a software pkcs11 or does not use pcscd.  

libcrypto.so.1.1 is OpenSSL-1.1 and also used by modules libstpkcs11.so
and opensc-pkcs11.so

So libstpkcs11.so, libeToken.so.10.7.77 and libstpkcs11.so,
libeToken.so.10.7.77 all appear to work as all the libs are available.

The difference is opensc-pkcs11.so needs to load libopensc.so.8 and a
few others that I have not looked at


On a 22.04.1 system running the command  `sudo snap run --shell 
firefox.firefox` will run snap as root to have snap start up a shell with the 
environment that firefox would run under. 

The `df` command shows:
 
/dev/sda3   122388080  11202960  104921928  10% /var/lib/snapd/hostfs
tmpfs  814036  1272 812764   1% /run
tmpfs5120 4   5116   1% /run/lock
tmpfs  814036   100 813936   1% /run/user/1000
/dev/loop0128   128  0 100% /snap/bare/5
/dev/loop1  63488 63488  0 100% /snap/core20/1587
/dev/loop2  63488 63488  0 100% /
/dev/loop3 167296167296  0 100% /snap/firefox/1635
/dev/loop4 181248181248  0 100% /snap/firefox/1749
/dev/loop5 410496410496  0 100% /snap/gnome-3-38-2004/112
/dev/loop7  48128 48128  0 100% /snap/snapd/16292
/dev/loop6  93952 93952  0 100% /snap/gtk-common-themes/1535
/dev/sda2  524252  5364 51   2% 
/var/lib/snapd/hostfs/boot/efi
Argonne1952871748 479641924 1473229824  25% /media/sf_Argonne
VM-Shared  1952871748 479641924 1473229824  25% /media/sf_VM-Shared
/dev/loop8 354688354688  0 100% /snap/gnome-3-38-2004/115
udev  4034884 04034884   0% /dev
tmpfs 4070180 04070180   0% /dev/shm
tmpfs 4070180 04070180   0% 
/snap/firefox/1749/data-dir/icons
tmpfs 4070180 04070180   0% 
/snap/firefox/1749/data-dir/sounds
tmpfs 4070180 04070180   0% 
/snap/firefox/1749/data-dir/themes
tmpfs 4070180  19964068184   1% /usr/lib/x86_64-linux-gnu
tmpfs 4070180 04070180   0% /usr/share

and /var/lib/snapd/hostfs is the host's filesystem. I was able to copy
libopensc.so.8.0.0 and symlink libopensc.so.8.0.0 to
/usr/lib/x86_64-linux-gnu FF will still not load opensc-pkcs11.so and it
will be gone on a reboot.

snap does set sone environemt variables that could help:
LD_PRELOAD=:/snap/firefox/1749/gnome-platform/$LIB/bindtextdomain.so
LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/firefox/1749/usr/lib:/snap/firefox/1749/usr/lib/x86_64-linux-gnu:/snap/firefox/1749/gnome-platform/lib/x86_64-linux-gnu:/snap/firefox/1749/gnome-platform/usr/lib/x86_64-linux-gnu:/snap/firefox/1749/gnome-platform/usr/lib:/snap/firefox/1749/gnome-platform/lib:/snap/firefox/1749/gnome-platform/usr/lib/x86_64-linux-gnu/dri:/var/lib/snapd/lib/gl:/snap/firefox/1749/gnome-platform/usr/lib/x86_64-linux-gnu/libunity:/snap/firefox/1749/gnome-platform/usr/lib/x86_64-linux-gnu/pulseaudio


So this is where I am at. Firefox-esr from debiaen works with opensc. Forefox 
from snap does not. It appears the some effort when it to geting p11-kit to 
start, but all p11-kit does is load other pkcs11 modules, that may have been 
installed using normal apt-get. It the initial comments of this bug report 
there were suggestions to copy the single file if a pkcs11 module to a "doc" 
directory, but no attempt was made to copy dependent libraries that the module 
needs. 

These will only work if missing libraries are in the snap base or of
firefox snap packages.

OpenSC also has a notify capability to tell the user when a card was
inserted or removed. This may add additional complications to getting it
to work under snap.

Not much else I can do.

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firef

[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-28 Thread Alexander E. Patrakov

Also note that there is no requirement to have Secure Boot enabled in
Cyber Essentials.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1987162

Title:
43: New Device Security feature is confusing and unhelpful currently

Status in gnome-control-center package in Ubuntu:
Fix Released

Bug description:
GNOME 43 added a new Device Security feature in the Settings app.

You can access it in gnome-control-center 1:43~beta-1ubuntu1
1. Open the Settings app
2. Click Privacy then Device Security

The Security Events aren't clickable.

A default Ubuntu install only gets us "Security Level 1". The highest
level is "Security Level 3".

There isn't anything an Ubuntu user can do to get to a higher security
level from the Device Security screen.

If a user attempts to get their system to a higher security level, I
think they could break their system since this isn't something we
currently support.

Therefore, I think we ought to hide/disable the screen for Ubuntu
22.10. We can work towards better integrating this screen for Ubuntu
in future releases.

I'm attaching several screenshots although it's worth trying out the
feature for yourself too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions

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

[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-28 Thread Alexander E. Patrakov

@billdietrich444

Note: my comment is a trolling attempt, and hopefully an obvious one due
to the choice of an obviously unimplementable-in-a-useful-way standard.
Please take only 10% seriously.

It may be a good idea to stop talking about pure security according to
our own set of criteria (because it's up to discussion what's good
enough) and start talking about compliance to recognized standards. We
can start with the UK standard named Cyber Essentials, which is required
for all organizations that need to deal with the UK government. The
standard itself is available at https://www.ncsc.gov.uk/files/Cyber-
Essentials-Requirements-for-Infrastructure-v3-0-January-2022.pdf

It has the following testable requirements related to technical
controls:

* Firewalls - we can check that the firewall is installed and configured
to "block unauthenticated inbound connections by default".

* Secure configuration - this also includes removing unneeded or unused
services (and this means that it is forbidden to run the SSH server
unless there is a documented business need) and uninstalling unused
software. So we might want to display when each piece of software was
last used so that to ease the audit. Another testable requirement is
that any auto-run feature is disabled or configured to "ask". And also
there are some checkable requirements related to device unlocking.

* User access control - we could list administrative accounts. Also, if
a fingerprint reader is detected, or another form of 2FA is available,
we can list all all non-enrolled accounts as non-compliant. We can also
check if the password quality requirements are implemented and the
mandatory unsuccessful login throttling (or lock-out) policy is enforced
by PAM.

* Malware protection - with specific requirements, related to on-access
scanning of all files (including those on network shares, so sorry,
ClamAV is not compliant) and web pages. This was the reason I had to
tell one of my clients that they have to stop using Linux or stop
dealing with the UK government.

* Security update management - we can check Ubuntu-specific settings
related to the freshness of the database, whether a reboot is needed for
something to apply (e.g. are there running copies of deleted and
replaced binaries, or do they use deleted libraries), and whether the
updates are configured to install automatically.

* Backups - we can test whether they configured through known backup
applications.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1987162

Title:
43: New Device Security feature is confusing and unhelpful currently

Status in gnome-control-center package in Ubuntu:
Fix Released

Bug description:
GNOME 43 added a new Device Security feature in the Settings app.

You can access it in gnome-control-center 1:43~beta-1ubuntu1
1. Open the Settings app
2. Click Privacy then Device Security

The Security Events aren't clickable.

A default Ubuntu install only gets us "Security Level 1". The highest
level is "Security Level 3".

There isn't anything an Ubuntu user can do to get to a higher security
level from the Device Security screen.

If a user attempts to get their system to a higher security level, I
think they could break their system since this isn't something we
currently support.

Therefore, I think we ought to hide/disable the screen for Ubuntu
22.10. We can work towards better integrating this screen for Ubuntu
in future releases.

I'm attaching several screenshots although it's worth trying out the
feature for yourself too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-28 Thread Douglas E Engert

So it appears that to load a PKCS11 module in snap packaged FireFox requires:
 1)  "/run/user/[0-9]*/** mr,"
 2)  "/run/pcscd/pcscd.comm rw," (if module uses pcscd)
 3)  absolute path (i.e. no symlinks) to the module
 4)  all libs the module may need to be in the snap base

To test if (4) is correct:

 https://launchpad.net/~ascaneo can you run "ldd
/usr/lib/libeToken.so.10.7.77"

 https://launchpad.net/~liuck can you run "ldd
/usr/lib/bit4id/libbit4xpki.so"

I posted the output of "ldd opensc-pkcs11.so" in
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/comments/18

It requires "libopensc.so.8 => /lib/x86_64-linux-gnu/libopensc.so.8"
which is most likely not in the snap package base as per
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/comments/17

So how should a snap package handle arbitrary pkcs11 packages that
require libs that would have been installed in a traditional install,
but are not by snap packaging?

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-26 Thread Douglas E Engert

This maybe the biggest problem:
"- /usr inside the snap is a bind-mount from /usr in the base snap, not on the 
host system, which explains why your addition of `/usr/lib/x86_64-linux-gnu/** 
rm,` to the apparmor profile doesn't work as you'd expect (see 
https://github.com/snapcore/snapd/pull/11025#issuecomment-1225787194 for 
details)"

Are both of you saying that the location of the PKCS11 module makes a 
difference?
And if the normal location is in /usr/lib/x86_64-linux-gnu is part of the FF 
snap package and 
their is no way to include files from the local system's 
/usr/lib/x86_64-linux-gnu.
So is that what the copying to the /usr/run//doc is trying to overcome? 

There are many PKCS11 modules out there, some provided by smartcard vendors and 
not part of a distro.
OpenSC is distributed Ubuntu and most other distros. How will you handle these 
other modules?


What package has the /usr/lib/bit4id/libbit4xpki.so? 

can you run "ldd /usr/lib/bit4id/libbit4xpki.so" to see what other libs are 
required?
Does it use a socket to pcscd?

Is it possible some other libs must also be included?

Can you try to install opensc-pkcs11 (which also installs opensc) to
your system and see you can get FF to load it?

opensc-pkcs11-0.22.0-1ubuntu2 installs opensc-pkcs11.so in two places: 
/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so and 
/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so (which is were p11-kit would 
load it)
and depends on libopensc.so.8  and /usr/lib/x86_64-linux-gnu/libcrypto.so.3 
from libssl3-3.0.2-0ubuntu1.6


 $ ls -l /usr/lib/x86_64-linux-gnu/*opensc*
lrwxrwxrwx 1 root root  18 Mar 10 11:00 
/usr/lib/x86_64-linux-gnu/libopensc.so.8 -> libopensc.so.8.0.0
-rw-r--r-- 1 root root 2040208 Mar 10 11:00 
/usr/lib/x86_64-linux-gnu/libopensc.so.8.0.0
-rw-r--r-- 1 root root  234704 Mar 10 11:00 
/usr/lib/x86_64-linux-gnu/onepin-opensc-pkcs11.so
-rw-r--r-- 1 root root  234704 Mar 10 11:00 
/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
$ ldd /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
linux-vdso.so.1 (0x7ffcbbdfe000)
libopensc.so.8 => /lib/x86_64-linux-gnu/libopensc.so.8 
(0x7efd3cd14000)
libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 
(0x7efd3c8d2000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7efd3c6aa000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7efd3c68e000)
libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7efd3c4b6000)
libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7efd3c456000)
/lib64/ld-linux-x86-64.so.2 (0x7efd3cf58000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7efd3c31a000)
libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7efd3c313000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 
(0x7efd3c2cf000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7efd3c2a3000)
libffi.so.8 => /lib/x86_64-linux-gnu/libffi.so.8 (0x7efd3c296000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7efd3c21e000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7efd3c137000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 
(0x7efd3c10)
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 
(0x7efd3c069000)

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-25 Thread Douglas E Engert

https://launchpad.net/~liuck
You can test your reader/card with OpenSC  without firefox.

see: "man pkcs11-tool" or "pkcs11-tool --help".  "pkcs11-tool --test
--login" will try and read certificates and do sign/verify using
private keys. It may prompt for pin several times.

If you can also add --module  to use test a different
PKCS11 module.

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-25 Thread Douglas E Engert

This problem is an Ubuntu/snap packaging issue. FF and Thunderbird both
allow the loading of PKCS11 modules as do other programs. But the snap
has not packaged these.

Access to smartcards is usually handled by PC/SC i.e. the pcscd daemon.
It provides locking access to the smartcards from multiple running
applications. So this is another issue for snap, how to provide access
to this system daemon.

Snap does provide the ability to load the p11-kit but then p11-kit tries
to load other PKCS11 modules which may need to load additional
libraries. /usr/lib/x86_64-linux-gnu/pkcs11/* and run "p11-kit list-
modules".

p11-kit has a client/remote capability that I have never looked at. It
might be possible to use this from snap to a "remote" server running on
the the local host.

Are there FF extensions that may similar problems?

Until Ubuntu can packaged up other pkcs11 modules and handle pcscd, the
way to: "test from CLI if my smart card reader is working" is to use the
debian firefox-esr  which does not have any problems.

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-08-24 Thread Douglas E Engert

https://launchpad.net/~liuck can you give some more information:

 What PKCS11 module are you using?

 What version of Ubuntu?

From my testing with a fresh copy install of XUbuntu-22.04.1 as guest of
VirtualBox, the "/run/user/[0-9]*/** mr," appears to allow access to any
file in my /usr/run/1000 directory.

When I use firefox's "Security Devices... Load" and browse for a module,
I give the path to the system version of the module(s) I have tried:
both /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-client.so and
/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so. Both get a "Unable to
add module" and the location shown in
/run/user/1000/doc/48e09223/p11-kit-client.so
/run/user/1000/doc/e3261d9/opensc-pkcs11.so

So it looks like it find the files and copies to /run/user/1000/doc/*.

But both of these modules need access to other libs and also need to use
pcscd to access the smartcard readers.

https://launchpad.net/~tnetter 
Can you give some more information about "/usr/local/lib/libcvP11.so"
It is not clear why this works with:  
https://forums.epo.org/new-version-of-the-cryptovision-software-12191#p40162

It may be that this is a simple library and does not use pcscd.

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-05-21 Thread Douglas E Engert

After spending a week on this, I think I see the problem.

(1) pkcs11 modules are dynamically load by mozilla nss and need the
/etc/apparmor.d/abstractions/p11-kit   as stated in previous comment.

(2) dynamically loaded modules may also load additional shared
libraries. So apparmor profiles are need for each possible pkcs11
module. Ubuntu-22.04 has a /etc/apparmor.d/abstractions/p11-kit but
needs the "m" file_mmap as stated in previous comment.

(3) /var/lib/snapd/apparmor/profiles/snap.firefox.firefox included these system 
based profiles:
  #include 
  #include 
  #include 
But it does not include 
  #include  
So it can not load the p11-kit or any pkcs11 module p11-kit might try and load.
(/etc/apparmor.d/abstractions/p11-kit will also include any profiles in 
abstractions/p11-kit.d) 

(4) Smartcard pkcs11 modules use the pcscd system service. On most linux
system this is the pcscd-lite package:
https://github.com/LudovicRousseau/PCSC the ClientSetupSession
https://github.com/LudovicRousseau/PCSC/blob/master/src/winscard_msg.c#L107-L167
sets client access to the socket. (I have not looked at what it would
take to add the dbus apparmor code needed to do this.)

Observations:

With a modified p11-kit /etc/apparmor.d/abstractions/p11-kit with the "m" 
file_mmap and adding the #include  to 
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox I can add p11-kit as a 
"security Device", but it does not load any additional pkcs11 modules.
 
 ~/snap/firefox/common/.mozilla/firefox/0i8u9awg.default/pkcs11.txt has: 
   library=/lib/x86_64-linux-gnu/libp11-kit.so.0.3.0
name=p11-kit
   (using symlinks to libs appears to be a problem, so I avoided using them.)

I can not add a "security device" for OpenSC even with adding a
/etc/apparmor.d/abstractions/opensc profile.

(Others on the internet have reported problems with other smart card
pkcs11 modules not just opensc.)

Using audit on all possible files, does not show a file loading problem or does 
running
sudo apparmor_parser -v -C -r snap.firefox.firefox to reload with complain only 
show any problems. So the problme must be somehing else.

P11-kit does not directly need access to pcscd, so (4) is not an issue
with p11 kit itself but (4) is an issued with any (or most) pkcs11
modules loaded by p11-kit.

Solutions:

For a snap installed firefox if (1), (2), (3) and (4) where addressed, snap 
firefox should work.
Adding profiles for each pkcs11 module to /etc/apparmor.d/abstractions and 
adding an include in /etc/apparmor.d/abstractions/p11-kit.d would require only 
only adding an include for p11-kit to snap.firefox.firefox. I hope that there 
is enough info above so someone else can add the dbus code.


Personally:

I find snap to be nightmare and Ubuntu should not have made it the
default firefox. Ubuntu should at least continue to give the user a
choice. All my testing has been on a virtual test 22.04 system. I was in
the process of converting from 20.04 to 22.04, both virtual, when I ran
into this problem. I have removed the snap firefox and am working on
using the Debian firefox-esr which works great with smartcards and
pkcs11, and is much faster. I just have to convert my .mozilla profiles
because the name changed from firefox to firefox-esr.

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probabl

[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

2022-05-16 Thread Douglas E Engert

Initial problem of:

Initial problem of "[sáb abr 2 17:32:27 2022] audit: type=1400
audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap"
profile="snap.firefox.firefox"
name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0"

can be solved by adding to  
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox something like:
-- DEE.snap.firefox.firefox 2022-05-15 00:51:38.010651530 -0500
+++ snap.firefox.firefox2022-05-15 21:18:39.445523027 -0500
@@ -312,6 +312,9 @@
   /tmp/   r,
   /tmp/** mrwlkix,
 
+  #DEE
+  /run/user/[0-9]*/** mrwlkix,
+
   # App-specific access to files and directories in /dev/shm. We allow file
   # access in /dev/shm for shm_open() and files in subdirectories for open()
   # bind mount *not* used here (see 'parallel installs', above)

This adds the "m" mask to the  "/run/user/1000/doc/e0bac853/" directory
but does allow the module to be loaded. This is overkill, for the
directory. For a PKCS11 module "mr" maybe all that is needed.

It is not clear why the choice was made to copy the pkcs11 modules to the doc 
directory in the first place.
Ubuntu appears to install PKCS11 modules (at least some in) in  
/usr/lib/x86_64-linux-gnu/pkcs11 so why can't this be used without copying?

The above only show how to get around the first of many possible
problems.

Not all Ubuntu installed PKCS11 modules are installed in the above
directory. p11-kit-client.so is but opensc-pkcs11.so and onepin-opensc-
pkcs11.so are not, just symlinks.

Trying to use the apparmor aa-complain to get more info does not work
with the way the snap apparmor profiles are named. It appears the
profile uses "." inplace of "/" and there is no "snap/firefox/firefox"


Pkcs11 modules may load other PKCS11 modules, i.e. that is what p11-kit does. 
Each of these modules may have config files with system and user versions. 
apparmor needs to address how these config files can be read.

 
Until it can be shown that PKCS11 modules can be easily be used, I would 
suggest that firefox not be installed by snap. 

Also see:
https://github.com/OpenSC/OpenSC/issues/2552






** Bug watch added: OpenSC Issues #2552
   https://github.com/OpenSC/OpenSC/issues/2552

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1973403] Re: gnome-shell is using over 13GB of ram after 5 days

2022-05-16 Thread Richard e Collins

I have looked in ~/.local/share/gnome-shell/ There is no extensions
folder. This is a new install of Ubuntu 22.04 with no modifications yet.
Here is the ls output of the folder ~/.local/share/gnome-shell/

drwx--  2 richard richard 4.0K May 16 07:24 .
drwx-- 23 richard richard 4.0K May 15 16:21 ..
-rw-rw-r--  1 richard richard 2.0K May 16 07:24 application_state
-rw-rw-r--  1 richard richard0 May  7 15:13 gnome-overrides-migrated
-rw-rw-r--  1 richard richard  592 May 14 23:56 notifications

I will apply a updates again, if there are any, reboot and create the
file you need. It'll take a day or so.

Many thanks for your feedback. :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1973403

Title:
  gnome-shell is using over 13GB of ram after  5 days

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is on Ubuntu 22.04
  All updates
  After 5 days gnome-shell is using 13GB or ram.

  System is a Asus PN50
  512 GB m.2 drive
  64 GIG Ram.
  AMD 4800U

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 11:27:20 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-07 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973403/+subscriptions


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

[Desktop-packages] [Bug 1973403] [NEW] gnome-shell is using over 13GB of ram after 5 days

2022-05-14 Thread Richard e Collins

Public bug reported:

This is on Ubuntu 22.04
All updates
After 5 days gnome-shell is using 13GB or ram.

System is a Asus PN50
512 GB m.2 drive
64 GIG Ram.
AMD 4800U

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat May 14 11:27:20 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-05-07 (6 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screen shot of resource viewer"
   
https://bugs.launchpad.net/bugs/1973403/+attachment/5589711/+files/Screenshot%20from%202022-05-14%2011-34-11.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1973403

Title:
  gnome-shell is using over 13GB of ram after  5 days

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is on Ubuntu 22.04
  All updates
  After 5 days gnome-shell is using 13GB or ram.

  System is a Asus PN50
  512 GB m.2 drive
  64 GIG Ram.
  AMD 4800U

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 11:27:20 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-07 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973403/+subscriptions


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

[Desktop-packages] [Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04

2022-04-21 Thread Elias E. del Real

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

I just did a fresh install of the official release 22.04 LTS image
today, and hit this problem. No gear, and it defaults to X11, whether I
have just the NVIDIA GPU enabled, or both the Intel integrated GPU and
the NVIDIA discrete GPU enabled in hybrid mode.

I had previously installed a nightly build of 22.04 LTS (beta) last
week, and had the gear as an option, and was able to use Wayland.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1969254

Title:
  wayland session not longer an option after recent update on Ubuntu
  22.04

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  After some recent update to Ubuntu 22.04 dev, X11 is selected by
  default and there is no longer the option to select the display
  protocol at login.

  It seems I am not the only affected:
  https://askubuntu.com/questions/1402671/ubuntu-no-gear-for-
  waylaland-x11

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-session 42.0-1ubuntu2
  Uname: Linux 5.17.3-051703-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 15 22:20:35 2022
  InstallationDate: Installed on 2022-02-02 (72 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+subscriptions


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

Re: [Desktop-packages] [Bug 1949618] Re: system locks up when selection one of top 2 items in dock

2022-01-23 Thread Robert E. Novak

This behavior disappeared in 21.10

Robert E. Novak
sailnf...@gmail.com
Cell: +1 (209) 620-3130
FAX: +1 (866) 889-1639
Skype: sailnfool.ren
https://www.linkedin.com/in/sailnfool


On Sat, Jan 22, 2022 at 8:25 PM Launchpad Bug Tracker
<1949...@bugs.launchpad.net> wrote:
>
> [Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
> has been no activity for 60 days.]
>
> ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
>Status: Incomplete => Expired
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1949618
>
> Title:
>   system locks up when selection one of top 2 items in dock
>
> Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
>   Expired
>
> Bug description:
>   This bug occurs when using the cursor to select one of the top two icons on 
> the dock area of the Ubuntu desktop.  When the system is under load and I 
> click the cursor on one of the two icons, the cursor freezes and the system 
> is unresponsive, requiring a power down reboot to recover.
>   Description:  Ubuntu 21.04
>   Release:  21.04
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: dash 
> 0.5.11+git20200708+dd9ef66+really0.5.11+git20200708+dd9ef66-5ubuntu1
>   ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22
>   Uname: Linux 5.11.0-38-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu65.4
>   Architecture: amd64
>   CasperMD5CheckResult: unknown
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Nov  3 09:56:31 2021
>   InstallationDate: Installed on 2021-03-06 (241 days ago)
>   InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: dash
>   UpgradeStatus: Upgraded to hirsute on 2021-06-10 (145 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1949618/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1949618

Title:
  system locks up when selection one of top 2 items in dock

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Expired

Bug description:
  This bug occurs when using the cursor to select one of the top two icons on 
the dock area of the Ubuntu desktop.  When the system is under load and I click 
the cursor on one of the two icons, the cursor freezes and the system is 
unresponsive, requiring a power down reboot to recover.
  Description:  Ubuntu 21.04
  Release:  21.04

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: dash 
0.5.11+git20200708+dd9ef66+really0.5.11+git20200708+dd9ef66-5ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  3 09:56:31 2021
  InstallationDate: Installed on 2021-03-06 (241 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dash
  UpgradeStatus: Upgraded to hirsute on 2021-06-10 (145 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1949618/+subscriptions


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

Re: [Desktop-packages] [Bug 1949618] Re: system locks up when selection one of top 2 items in dock

2021-11-23 Thread Robert E. Novak

Either left or right

On Tue, Nov 23, 2021, 2:20 AM Daniel van Vugt <1949...@bugs.launchpad.net>
wrote:

> Also do you mean regular left click, or right click?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1949618
>
> Title:
>   system locks up when selection one of top 2 items in dock
>
> Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
>   Incomplete
>
> Bug description:
>   This bug occurs when using the cursor to select one of the top two icons
> on the dock area of the Ubuntu desktop.  When the system is under load and
> I click the cursor on one of the two icons, the cursor freezes and the
> system is unresponsive, requiring a power down reboot to recover.
>   Description:  Ubuntu 21.04
>   Release:  21.04
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: dash
> 0.5.11+git20200708+dd9ef66+really0.5.11+git20200708+dd9ef66-5ubuntu1
>   ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22
>   Uname: Linux 5.11.0-38-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu65.4
>   Architecture: amd64
>   CasperMD5CheckResult: unknown
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Nov  3 09:56:31 2021
>   InstallationDate: Installed on 2021-03-06 (241 days ago)
>   InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64
> (20201022)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: dash
>   UpgradeStatus: Upgraded to hirsute on 2021-06-10 (145 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1949618/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1949618

Title:
  system locks up when selection one of top 2 items in dock

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  This bug occurs when using the cursor to select one of the top two icons on 
the dock area of the Ubuntu desktop.  When the system is under load and I click 
the cursor on one of the two icons, the cursor freezes and the system is 
unresponsive, requiring a power down reboot to recover.
  Description:  Ubuntu 21.04
  Release:  21.04

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: dash 
0.5.11+git20200708+dd9ef66+really0.5.11+git20200708+dd9ef66-5ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  3 09:56:31 2021
  InstallationDate: Installed on 2021-03-06 (241 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dash
  UpgradeStatus: Upgraded to hirsute on 2021-06-10 (145 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1949618/+subscriptions


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

Re: [Desktop-packages] [Bug 1949618] Re: system locks up when selection one of top 2 items in dash

2021-11-15 Thread Robert E. Novak

Sorry I missed the name change.  I was having trouble finding references 
that described the changes in names for screen elements.  I am referring 
to the top icons in the left hand toolbar/launcher, not the top task 
bar.  The attached picture should help.

On 11/13/21 12:43 PM, Paul White wrote:
> Robert, you raised this issue agaist "dash" which is a shell similar to
> bash, zsh etc. 'Dash' was a term used when the default Ubuntu desktop
> was Unity which has of course now been superceded by GNOME Shell.
>
> Please advise on which "top two icons" you are referring to. Icons in
> the top bar (which might vary depnding on the hardware being used) or
> icons which are displayed when clicking on the nine dots in the botton
> left hand corner of the screen (Show Applications).
>
> I'm moving this bug report to the gnome-shell package.
>
>
> ** Package changed: dash (Ubuntu) => gnome-shell (Ubuntu)
>
> ** Changed in: gnome-shell (Ubuntu)
> Status: New => Incomplete
>


** Attachment added: "Modified Screenshot from 2021-11-15 11-14-55.png"
   
https://bugs.launchpad.net/bugs/1949618/+attachment/5541057/+files/Modified%20Screenshot%20from%202021-11-15%2011-14-55.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1949618

Title:
  system locks up when selection one of top 2 items in dash

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This bug occurs when using the cursor to select one of the top two icons on 
the DASH area of the Ubuntu desktop.  When the system is under load and I click 
the cursor on one of the two icons, the cursor freezes and the system is 
unresponsive, requiring a power down reboot to recover.
  Description:  Ubuntu 21.04
  Release:  21.04

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: dash 
0.5.11+git20200708+dd9ef66+really0.5.11+git20200708+dd9ef66-5ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  3 09:56:31 2021
  InstallationDate: Installed on 2021-03-06 (241 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dash
  UpgradeStatus: Upgraded to hirsute on 2021-06-10 (145 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949618/+subscriptions


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

[Desktop-packages] [Bug 1932328]

2021-09-08 Thread U-adam-e

Hi everyone, 
I have the same issue on my computer : Ubuntu 21.04+Wayland, TB 78.13.0. 
I would like to add that the bug impacts the whole system. On top of having 
phantom windows I also loose the ability of switching through open-windows with 
ALT+TAB, which is quite annoying… not saying totally irritating! 
The same behavior has been described on Ubuntu French Forum : 
https://forum.ubuntu-fr.org/viewtopic.php?pid=22484498#p22484498

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1932328

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

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


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

[Desktop-packages] [Bug 1912859] [NEW] package libsane 1.0.29-0ubuntu5 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2021-01-22 Thread M E

Public bug reported:

tried to get rhythmbox to access music on NAS via Firefly media server
and crashed. probably too much music to load in one file as i have more
than 100gb of music. Cant access it thru Itunes server either.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libsane 1.0.29-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jan 21 14:07:22 2021
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
InstallationDate: Installed on 2021-01-21 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: sane-backends
Title: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: dpkg-deb 
--fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1912859

Title:
  package libsane 1.0.29-0ubuntu5 failed to install/upgrade: dpkg-deb
  --fsys-tarfile subprocess returned error exit status 2

Status in sane-backends package in Ubuntu:
  New

Bug description:
  tried to get rhythmbox to access music on NAS via Firefly media server
  and crashed. probably too much music to load in one file as i have
  more than 100gb of music. Cant access it thru Itunes server either.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libsane 1.0.29-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 21 14:07:22 2021
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2021-01-21 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: sane-backends
  Title: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: dpkg-deb 
--fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1912859/+subscriptions

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

[Desktop-packages] [Bug 1825071] Re: Super + p does not work as expected, it's defective

2021-01-19 Thread E-Korn

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

It is 2021, I'm using 20.04 and still have the very same behavior
described by Jeremy almost 2 years ago.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1825071

Title:
  Super + p does not work as expected, it's defective

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have 3 monitors (2 landscape and 1 portrait), I normally need to
  change between my monitors due to my setup. If I want to play a game,
  I typically switch to a single monitor (Built-in) then I can switch
  back to Join and everything goes back to normal. That is what I would
  expect but that is NOT what happens.

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

  The first two options work correctly, but the 3rd and 4th options do
  not.

  
  External and Built-in do the exact same thing: they simply shift my monitors 
around, lose all settings (reset everything). So all 3 monitors are still in 
use but settings are cleared (orientation, resolution, and frequency are 
reset). I have to then open up the settings to change it all back. When I go 
back to Join, I would expect the settings to return to normal. They do not. 
Super + P simply wipes out monitor settings in my case.

  
  I am using:
  - Ubuntu 4.15.0-47.50-generic 4.15.18
  - GeForce GTX 1080/PCIe/SSE2
  - I have attached: lspci-vnvn.log

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  
  With nvidia-driver-418 from: ppa:graphics-drivers/ppa

  $ apt-cache policy nvidia-driver-418
  nvidia-driver-418:
Installed: 418.56-0ubuntu0~gpu18.04.1
Candidate: 418.56-0ubuntu0~gpu18.04.1
Version table:
   *** 418.56-0ubuntu0~gpu18.04.1 500
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status


  I am not sure if this is actually necessary because I don't think this
  has to do with the graphics card.

  I am not sure what other information you will need for this report. I can 
provide more data upon request.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC1:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC0:  jpsimkins   3108 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (298 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97X-UD5H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825071/+subscriptions

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

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

2020-11-18 Thread E

Mentioned in #15 there is a question about whether using the trackpad
increases the amount of interrupts. For me it does do so! Placing my
finger on the trackpad does generate mouse events, but it only rapidly
generates click events non-stop. It cannot be used to move the pointer
but just spams clicks. Would anybody know of a solution?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput 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:
  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=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB16

[Desktop-packages] [Bug 1901542] Re: [Skylake] Wallpaper corrupted after upgrading to 20.04

2020-10-27 Thread E Eee

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

Hi,

I followed the suggested solution to remove the outdated 'Intel's driver
as per bug 1867668

sudo apt remove xserver-xorg-video-intel

And this resolved the reported issues :  corrupted background and the
issue with video players (mplayer).

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

Title:
  [Skylake] Wallpaper corrupted after upgrading to 20.04

Status in mutter package in Ubuntu:
  New

Bug description:
  Displays are corrupted after upgrading to 20.04. No video players
  appear to work (VLC, mplayer), crashing with "Segmentation fault".

  If I boot up in recovery mode and then continue to normal bootup, the
  screen appears fine and the video players work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 26 13:03:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06f7]
  InstallationDate: Installed on 2016-11-05 (1450 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3650
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e9f748e2-864c-425c-8218-4007afd40ebb ro quiet splash 
i915.alpha_support=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.3.6
  dmi.board.name: 0C2XKD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.3.6:bd09/30/2016:svnDellInc.:pnInspiron3650:pvrX00:rvnDellInc.:rn0C2XKD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3650
  dmi.product.sku: Inspiron 3650
  dmi.product.version: X00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Mon Oct 26 11:38:32 2020
  xserver.configfile: default
  xserver.errors:
   No devices detected.
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2.4

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

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

[Desktop-packages] [Bug 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.

2020-07-31 Thread e X t 7 3

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

Unfortunately, Ubuntu developers forgot something. I have been building
my optimized kernel with lz4 for 5 years ... and here it is necessary to
compile or upload lz4 and only then e.g. sudo update-initramfs -u -k
5.7.11-ext73-77.11-kabylake-8th and after restarting the message you
will not see

https://github.com/lz4/lz4

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1870260

Title:
  initramfs unpacking failed: Decoding failed", message appears on boot
  up.

Status in linux package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  OS : Ubuntu 20.04(20200401)

  Problem: "initramfs unpacking failed: Decoding failed", message
  appears on boot up

  solution: 
If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to 
COMPRESS=gzip 
  then the error is fixing .

  Expected solution:
  This but in there from a long time I have seen this from 
Ubuntu 18.04,19.04,19.10
  now in 20.04 So please fix it or change it from lz4 to gzip.
  an early reply is highly appreciated 
  Thank you .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tamal  1451 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD 
Camera
   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: HP HP Laptop 15-da0xxx
  Package: ubuntu-meta
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-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: 11/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84A6
  dmi.board.vendor: HP
  dmi.board.version: 80.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-da0xxx
  dmi.product.sku: 5AY34PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1879742]

2020-07-18 Thread Duncan-e-chung

Hi Saeed.

Just letting you know the fix seems to work for me.

I've tried both on Firefox Developer (version 79.0b6) and Firefox
(version 78.0.2).

Thanks for your effort here.

Duncan.

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

Title:
  When using Google Meet on Firefox, delay sending sound from microphone

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  New

Bug description:
  When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
  the first 5-10 seconds of the meeting, nobody can hear anything that I
  am saying. After that, I have no issues. I also have no issues joining
  with Chromium.

  The sound indicator on my end (the little green bars that flash when
  you are talking) start immediately, but nobody on the call hears
  anything from me.

  The only info I could find from Googling was somebody else talking about a 
similar problem:
  
https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   1813 F pulseaudio
  BuildID: 20200507114007
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 17:05:20 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-05-03 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices

2020-07-15 Thread e-fernbach

on Jul 16 2020 I still have the same problem. The pad is perfectly recognized
when using terminal commands but not detected in the device dialog under
settings>devices>Wacom Tablet. When I hit Test your settings I can input but
have to use high pressure. I did install the most recent drivers from source
following this link https://linuxwacom.github.io/ , installing input wacom from
source and building the Xdriver. Installing input wacom went without error
messages and installing the Xdriver gave the message that the installed driver
is already the newest one. When I try to use the tablet with Xournal it
sometimes works and sometime doesn't rebooting usually fixes the "not working".
"Not working" symptoms are: when drawing a line it gets interrupted, the
pressure has to be extremely high, the cursor jumps around wildly, switching
between eraser and pen is not controllable, the cursor can not be mapped to a
specific monitor. I am on Ubuntu 18.04.3 The tablet is a Wacom Intuos BT S The
output from xsetwacom --get "Wacom Co.,Ltd. Intuos BT S stylus" all is:
Option "Area" "0 0 15200 9500"
Button: Actions are not supported by xorg.conf. Try shell format (-s) instead.
Button: Actions are not supported by xorg.conf. Try shell format (-s) instead.
Button: Actions are not supported by xorg.conf. Try shell format (-s) instead.
Button: Actions are not supported by xorg.conf. Try shell format (-s) instead.
Option "DebugLevel" "0"
Option "CommonDBG" "0"
Option "Suppress" "2"
Option "RawSample" "4"
Option "PressCurve" "0 0 100 100"
Option "Mode" "Absolute"
Option "TPCButton" "off"
Option "Touch" "off"
Property 'Wacom Hardware Touch Switch' does not exist on device.
Option "Gesture" "off"
Option "ZoomDistance" "0"
Option "ScrollDistance" "0"
Option "TapTime" "250"
Property 'Wacom Proximity Threshold' does not exist on device.
Option "Rotate" "none"
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Wheel Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Property 'Wacom Strip Buttons' does not exist on device.
Option "Threshold" "26"
Option "Serial" "0"
Option "PressureRecalibration" "on"
Option "PanScrollThreshold" "1300"

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1753525

Title:
Wacom tablet not recognized in Settings > Devices

Status in gnome-control-center package in Ubuntu:
Confirmed

Bug description:
I have the same problem with Ubuntu 18.04 developing branch as described for
Ubuntu 16.04 in
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1575887
I can draw, e.g., with tuxpaint, I can use stylus and graphic tablet "Wacom
Intuos Art Black Pen + Touch S" like a touchpad with mouse (left, muddle, right
button), but I cannot access the pad via Settings > Devices > Wacom Tablet:
"Stylus not recognized". So, no reprogramming of stylus buttons and tablet
buttons :(

Hopefully this will be resolved till the final version of 18.04 in
April?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.26.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 5 16:48:48 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-03-05 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/+subscriptions

[Desktop-packages] [Bug 1882085] [NEW] Missing perl dependencies for latexindent

2020-06-04 Thread Émile E

Public bug reported:

I'm using Linux Mint 19.3 which is based on Ubuntu 18.04.

Installing texlive-extra-utils (version 2017.20180305-2) makes a
latexindent command available, but it does not run because dependencies
are missing. This the output upon launching latexindent in the shell:

Can't locate Log/Dispatch/File.pm in @INC (you may need to install the
Log::Dispatch::File module)

Installing libfile-homedir-perl and liblog-dispatch-perl solves the
issue.

What I expected: Either latexindent is installed by texlive-extra-utils,
or it is not. If it is, it should come with all its dependencies. I
notice on packages.ubuntu.com that they have been made "recommended" in
20.04, but it looks like they should be regular dependencies.

** Affects: texlive-extra (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  I'm using Linux Mint 19.3 which is based on Ubuntu 18.04.
  
  Installing texlive-extra-utils (version 2017.20180305-2) makes a
  latexindent command available, but it does not run because dependencies
  are missing. This the output upon launching latexindent in the shell:
  
  Can't locate Log/Dispatch/File.pm in @INC (you may need to install the
  Log::Dispatch::File module)
  
  Installing libfile-homedir-perl and liblog-dispatch-perl solves the
  issue.
  
- What I expected: Either latexindent is installed by texlive-latex-utils,
+ What I expected: Either latexindent is installed by texlive-extra-utils,
  or it is not. If it is, it should come with all its dependencies. I
  notice on packages.ubuntu.com that they have been made "recommended" in
  20.04, but it looks like they should be regular dependencies.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1882085

Title:
  Missing perl dependencies for latexindent

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  I'm using Linux Mint 19.3 which is based on Ubuntu 18.04.

  Installing texlive-extra-utils (version 2017.20180305-2) makes a
  latexindent command available, but it does not run because
  dependencies are missing. This the output upon launching latexindent
  in the shell:

  Can't locate Log/Dispatch/File.pm in @INC (you may need to install the
  Log::Dispatch::File module)

  Installing libfile-homedir-perl and liblog-dispatch-perl solves the
  issue.

  What I expected: Either latexindent is installed by texlive-extra-
  utils, or it is not. If it is, it should come with all its
  dependencies. I notice on packages.ubuntu.com that they have been made
  "recommended" in 20.04, but it looks like they should be regular
  dependencies.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1882085/+subscriptions

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

[Desktop-packages] [Bug 1866999] Re: gnome-calendar does not sync with Google Calendar

2020-05-07 Thread Timothy E. Hall

Same issue here. What is the best way o can help get this resolved?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1866999

Title:
  gnome-calendar does not sync with Google Calendar

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my 
Google Calendar.
  Online accounts is activated and, for example, gnome-contacts does show the 
contacts I have in Google.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 09:47:25 2020
  InstallationDate: Installed on 2018-02-23 (746 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+subscriptions

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

[Desktop-packages] [Bug 1846505] [NEW] package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: problemas com dependências - a deixar triggers por processar

2019-10-03 Thread Pedro Ivo Marques e Silva Brito

Public bug reported:

Erro ao instalar o pacote.
O que fazer?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: desktop-file-utils 0.22-1ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux 4.4.0-128-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu Oct  3 11:18:46 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: problemas com dependências - a deixar triggers por processar
InstallationDate: Installed on 2019-06-21 (103 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.26
SourcePackage: desktop-file-utils
Title: package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: 
problemas com dependências - a deixar triggers por processar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: desktop-file-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1846505

Title:
  package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade:
  problemas com dependências - a deixar triggers por processar

Status in desktop-file-utils package in Ubuntu:
  New

Bug description:
  Erro ao instalar o pacote.
  O que fazer?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: desktop-file-utils 0.22-1ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Oct  3 11:18:46 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: problemas com dependências - a deixar triggers por processar
  InstallationDate: Installed on 2019-06-21 (103 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.26
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.22-1ubuntu5 failed to install/upgrade: 
problemas com dependências - a deixar triggers por processar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc

2019-07-22 Thread Alexander E. Patrakov

Ping - did I follow the instructions correctly?

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1837081

Title:
  xorg crashes on virgl with 3d enabled (Haswell on the host),
  ms_dri2_schedule_wait_msc

Status in xorg-server package in Ubuntu:
  New
Status in xorg package in Fedora:
  Unknown

Bug description:
  I have recently files this bug:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and
  decided to test if it affects Ubuntu 19.04.

  Just to remind you, this was about xorg crashing in a virtual machine
  that uses virtio VGA with virgl enabled. The host is Arch Linux, the
  CPU is Intel Core i7 4770S (Haswell).

  Well, xorg crashes on 19.04, too, but with a different backtrace, and
  adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a
  separate bug.

  Disabling virgl on qemu command line helps, but I would rather have it
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Thu Jul 18 21:09:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc

I have tried to follow the instructions, but not sure if I did it
correctly. Does this link help? https://errors.ubuntu.com/oops/d2e06dde-
a9d9-11e9-a2e9-fa163e6cac46

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1837081

Title:
  xorg crashes on virgl with 3d enabled (Haswell on the host),
  ms_dri2_schedule_wait_msc

Status in xorg-server package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  I have recently files this bug:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and
  decided to test if it affects Ubuntu 19.04.

  Just to remind you, this was about xorg crashing in a virtual machine
  that uses virtio VGA with virgl enabled. The host is Arch Linux, the
  CPU is Intel Core i7 4770S (Haswell).

  Well, xorg crashes on 19.04, too, but with a different backtrace, and
  adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a
  separate bug.

  Disabling virgl on qemu command line helps, but I would rather have it
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Thu Jul 18 21:09:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc

https://bugzilla.redhat.com/show_bug.cgi?id=1652274 is a duplicate

** Bug watch added: Red Hat Bugzilla #1652274
   https://bugzilla.redhat.com/show_bug.cgi?id=1652274

** Also affects: xorg (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1652274
   Importance: Unknown
   Status: Unknown

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

Title:
  xorg crashes on virgl with 3d enabled (Haswell on the host),
  ms_dri2_schedule_wait_msc

Status in xorg package in Ubuntu:
  New
Status in xorg package in Fedora:
  Unknown

Bug description:
  I have recently files this bug:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and
  decided to test if it affects Ubuntu 19.04.

  Just to remind you, this was about xorg crashing in a virtual machine
  that uses virtio VGA with virgl enabled. The host is Arch Linux, the
  CPU is Intel Core i7 4770S (Haswell).

  Well, xorg crashes on 19.04, too, but with a different backtrace, and
  adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a
  separate bug.

  Disabling virgl on qemu command line helps, but I would rather have it
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Thu Jul 18 21:09:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1837081] [NEW] xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc

Public bug reported:

I have recently files this bug:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided
to test if it affects Ubuntu 19.04.

Just to remind you, this was about xorg crashing in a virtual machine
that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU
is Intel Core i7 4770S (Haswell).

Well, xorg crashes on 19.04, too, but with a different backtrace, and
adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a
separate bug.

Disabling virgl on qemu command line helps, but I would rather have it
enabled.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
Date: Thu Jul 18 21:09:46 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.12.0-20181126_142135-anatol
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.0
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-4.0
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco third-party-packages ubuntu

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

Title:
  xorg crashes on virgl with 3d enabled (Haswell on the host),
  ms_dri2_schedule_wait_msc

Status in xorg package in Ubuntu:
  New

Bug description:
  I have recently files this bug:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and
  decided to test if it affects Ubuntu 19.04.

  Just to remind you, this was about xorg crashing in a virtual machine
  that uses virtio VGA with virgl enabled. The host is Arch Linux, the
  CPU is Intel Core i7 4770S (Haswell).

  Well, xorg crashes on 19.04, too, but with a different backtrace, and
  adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a
  separate bug.

  Disabling virgl on qemu command line helps, but I would rather have it
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Thu Jul 18 21:09:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU
  version.compiz: c

[Desktop-packages] [Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)

It works.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1836772

Title:
  Xorg crash on 3d-enabled virgl (Haswell host)

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I am running a KVM virtual machine with 3D acceleration (virgl). The
  host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
  session started crashing just after the login. In xorg logs, I see
  this:

  [15.338] (WW) modeset(0): Page flip failed: Invalid argument
  [15.338] (EE) modeset(0): present flip failed
  [15.397] (WW) modeset(0): Page flip failed: Invalid argument
  [15.397] (EE) modeset(0): present flip failed
  [15.418] (WW) modeset(0): Page flip failed: Invalid argument
  [15.419] (EE) modeset(0): present flip failed
  [15.440] (WW) modeset(0): Page flip failed: Invalid argument
  [15.440] (EE) modeset(0): present flip failed
  [15.460] (WW) modeset(0): Page flip failed: Invalid argument
  [15.460] (EE) modeset(0): present flip failed
  [15.975] (WW) modeset(0): Page flip failed: Invalid argument
  [15.976] (EE) modeset(0): present flip failed
  [16.039] (WW) modeset(0): Page flip failed: Invalid argument
  [16.040] (EE) modeset(0): present flip failed
  [16.064] (WW) modeset(0): Page flip failed: Invalid argument
  [16.064] (EE) modeset(0): present flip failed
  [16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
  0:11(2): error: value of type vec4 cannot be assigned to variable of type 
error
  0:12(2): error: `color1' undeclared
  0:12(2): error: value of type vec4 cannot be assigned to variable of type 
error

  [16.096] Program source:
  #ifdef GL_ES
  precision mediump float;
  #endif
  #define ATLAS_DIM_INV 0.0009765625
  varying vec2 glyph_pos;
  uniform vec4 fg;
  uniform sampler2D atlas;
  void main() {
 vec4 mask = texture2D(atlas, glyph_pos);
 vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
  }
  [16.096] (EE)
  Fatal server error:
  [16.096] (EE) GLSL compile failure

  Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
  18.0.0~rc5-1ubuntu1 helps.

  Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.

  On the host, the GPU is Intel Haswell:

  00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
  E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  [8086:0412] (rev 06)

  The CPU is Intel(R) Core(TM) i7-4770S CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 20:52:03 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

[Desktop-packages] [Bug 1836772] [NEW] Xorg crash on 3d-enabled virgl (Haswell host)

2019-07-16 Thread Alexander E. Patrakov

Public bug reported:

I am running a KVM virtual machine with 3D acceleration (virgl). The
host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
session started crashing just after the login. In xorg logs, I see this:

[15.338] (WW) modeset(0): Page flip failed: Invalid argument
[15.338] (EE) modeset(0): present flip failed
[15.397] (WW) modeset(0): Page flip failed: Invalid argument
[15.397] (EE) modeset(0): present flip failed
[15.418] (WW) modeset(0): Page flip failed: Invalid argument
[15.419] (EE) modeset(0): present flip failed
[15.440] (WW) modeset(0): Page flip failed: Invalid argument
[15.440] (EE) modeset(0): present flip failed
[15.460] (WW) modeset(0): Page flip failed: Invalid argument
[15.460] (EE) modeset(0): present flip failed
[15.975] (WW) modeset(0): Page flip failed: Invalid argument
[15.976] (EE) modeset(0): present flip failed
[16.039] (WW) modeset(0): Page flip failed: Invalid argument
[16.040] (EE) modeset(0): present flip failed
[16.064] (WW) modeset(0): Page flip failed: Invalid argument
[16.064] (EE) modeset(0): present flip failed
[16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
0:11(2): error: value of type vec4 cannot be assigned to variable of type error
0:12(2): error: `color1' undeclared
0:12(2): error: value of type vec4 cannot be assigned to variable of type error

[16.096] Program source:
#ifdef GL_ES
precision mediump float;
#endif
#define ATLAS_DIM_INV 0.0009765625
varying vec2 glyph_pos;
uniform vec4 fg;
uniform sampler2D atlas;
void main() {
   vec4 mask = texture2D(atlas, glyph_pos);
   vec4 source = fg;
  color0 = source * mask;
  color1 = source.a * mask;
}
[16.096] (EE)
Fatal server error:
[16.096] (EE) GLSL compile failure

Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
18.0.0~rc5-1ubuntu1 helps.

Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.

On the host, the GPU is Intel Haswell:

00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200
v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412]
(rev 06)

The CPU is Intel(R) Core(TM) i7-4770S CPU.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 16 20:52:03 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.12.0-20181126_142135-anatol
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-4.0
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-4.0
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic crash ubuntu

** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/bugs/1836772/+attachment/5277429/+files/Xorg.0.log.old

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

Title:
  Xorg crash on 3d-enabled virgl (Haswell host)

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running a KVM virtual machine with 3D acceleration (virgl). The
  host is Arch Linux, the guest

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-06-21 Thread Teresa e Junior

@karl-piccket try booting with ahci.mobile_lpm_policy=0, and then try
comment #42 if it doesn't work.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1798961

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1831375] Re: Pride Month themed Wallpaper for Ubuntu

2019-06-03 Thread Jeb E.

I made an edit to the Grey Disco Dingo wallpaper using the Pride color
spectrum. Please see the attached image for the full resolution copy. I
will be adding the GIMP .xcf file in a following comment.

** Attachment added: "Edited Pride-Themed Disco Dingo Wallpaper"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1831375/+attachment/5268558/+files/Dingo_Wallpaper_Grey_Pride_4096x2304.png

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1831375

Title:
Pride Month themed Wallpaper for Ubuntu

Status in ubuntu-wallpapers package in Ubuntu:
Confirmed

Bug description:
I have a small idea for the Ubuntu community and brand image: Why not
put out a "Pride Month" themed default Ubuntu wallpaper? This could be
pushed to users as part of an update to the Ubuntu Wallpapers package
as an additional wallpaper and feature a light addition of the 🌈
rainbow color spectrum easily added in GIMP or Inkscape.

Why not, I mean? Everyone is doing it, from Microsoft to Apple. This
will show a little support to the LGBT community and the world.

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

[Desktop-packages] [Bug 1831375] Re: Pride Month themed Wallpaper for Ubuntu

2019-06-03 Thread Jeb E.

Please see the attached .xcf document for a working copy of the Pride-
themed Ubuntu Disco Dingo (Grey) wallpaper I put together.

** Attachment added: "Working Copy (.xcf for Gimp 2.10 and higher) of the 
wallpaper edit."
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1831375/+attachment/5268559/+files/Dingo_Wallpaper_Grey_Pride_4096x2304.xcf

** Tags added: branding community-art

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1831375

Title:
  Pride Month themed Wallpaper for Ubuntu

Status in ubuntu-wallpapers package in Ubuntu:
  Confirmed

Bug description:
  I have a small idea for the Ubuntu community and brand image: Why not
  put out a "Pride Month" themed default Ubuntu wallpaper? This could be
  pushed to users as part of an update to the Ubuntu Wallpapers package
  as an additional wallpaper and feature a light addition of the 🌈
  rainbow color spectrum easily added in GIMP or Inkscape.

  Why not, I mean? Everyone is doing it, from Microsoft to Apple. This
  will show a little support to the LGBT community and the world.

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

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

[Desktop-packages] [Bug 1831375] Re: Pride Month themed Wallpaper for Ubuntu

2019-06-02 Thread Jeb E.

Related theme from Microsoft:
https://www.microsoft.com/en-us/p/pride-2019/9n6sk33v4vgb

** Tags added: aesthetic artwork brand equality humanity

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1831375

Title:
  Pride Month themed Wallpaper for Ubuntu

Status in ubuntu-wallpapers package in Ubuntu:
  Confirmed

Bug description:
  I have a small idea for the Ubuntu community and brand image: Why not
  put out a "Pride Month" themed default Ubuntu wallpaper? This could be
  pushed to users as part of an update to the Ubuntu Wallpapers package
  as an additional wallpaper and feature a light addition of the 🌈
  rainbow color spectrum easily added in GIMP or Inkscape.

  Why not, I mean? Everyone is doing it, from Microsoft to Apple. This
  will show a little support to the LGBT community and the world.

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

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

[Desktop-packages] [Bug 1831375] [NEW] Pride Month themed Wallpaper for Ubuntu

2019-06-02 Thread Jeb E.

Public bug reported:

I have a small idea for the Ubuntu community and brand image: Why not
put out a "Pride Month" themed default Ubuntu wallpaper? This could be
pushed to users as part of an update to the Ubuntu Wallpapers package as
an additional wallpaper and feature a light addition of the 🌈 rainbow
color spectrum easily added in GIMP or Inkscape.

Why not, I mean? Everyone is doing it, from Microsoft to Apple. This
will show a little support to the LGBT community and the world.

** Affects: ubuntu-wallpapers (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: aesthetic artwork brand equality gtk humanity pride theme wallpaper

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-wallpapers in Ubuntu.
https://bugs.launchpad.net/bugs/1831375

Title:
  Pride Month themed Wallpaper for Ubuntu

Status in ubuntu-wallpapers package in Ubuntu:
  Confirmed

Bug description:
  I have a small idea for the Ubuntu community and brand image: Why not
  put out a "Pride Month" themed default Ubuntu wallpaper? This could be
  pushed to users as part of an update to the Ubuntu Wallpapers package
  as an additional wallpaper and feature a light addition of the 🌈
  rainbow color spectrum easily added in GIMP or Inkscape.

  Why not, I mean? Everyone is doing it, from Microsoft to Apple. This
  will show a little support to the LGBT community and the world.

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

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

[Desktop-packages] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)

2019-05-22 Thread Teresa e Junior

I would refrain from messing with the video drivers just to workaround a
bug in the screen locker. Solution #27 doesn't work for me either.

What works for me is killing light-locker and replacing it with
xfce4-screensaver or gnome-screensaver. I haven't tested mate-
screensaver and xscreensaver.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1801609

Title:
  Fails to deactivate dpms off mode after user initiated wake-up
  events(not system-suspended, just locked and dpms active)

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 18.10 with Xubuntu.desktop session running. System will lock
  and turn-off monitors(automatically or manually), but--will not wake-
  up monitors upon keyboard or mouse activity. I can type unlock
  password, blindly and then the monitors will wake and show unlocked
  session.

  WORKAROUND:  I uninstalled light-locker, then, I installed gnome-
  screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver
  if light-locker is not found or installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: light-locker (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  4 13:01:36 2018
  InstallationDate: Installed on 2018-11-03 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714178]

2019-05-21 Thread Ville-syrjala-e

Took a while but we got there in the end.

commit 5c000fb33b767c3fa10d29a1021edbf4f92b76a2
Author: Ville Syrjälä 
Date:   Thu May 9 15:21:59 2019 +0300

drm/i915: Bump gen7+ fb size limits to 16kx16k

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Fix Released
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-05-20 Thread Teresa e Junior

The correct solution to the problem I've been facing was finally solved
on comment #58, thanks @prasanth-s-cmi. I've contacted the kernel
developer responsible for these patches introduced around Linux 4.16.1
on https://bugzilla.redhat.com/show_bug.cgi?id=1571330 , and he will
blacklist my laptop model (Lenovo G40-80) for newer versions of Linux.
Meanwhile, `ahci.mobile_lpm_policy=0` can workaround this problem.

** Bug watch added: Red Hat Bugzilla #1571330
   https://bugzilla.redhat.com/show_bug.cgi?id=1571330

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1798961

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Desktop-packages] [Bug 1823363] Re: Running "Junk Mail Controls" does not appear in Activity Manager

2019-04-25 Thread Jeb E.

Thank you for thanking me and letting me know! It's greatly appreciated.

On Thu, Apr 25, 2019, 9:20 AM Olivier Tilloy 
wrote:

> Thanks Paul for the upstream report!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1823363
>
> Title:
>   Running "Junk Mail Controls" does not appear in Activity Manager
>
> Status in Mozilla Thunderbird:
>   Confirmed
> Status in thunderbird package in Ubuntu:
>   Confirmed
>
> Bug description:
>   "Running Junk Mail Controls" does not appear in Activity Manager
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.10
>   Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1
>   ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
>   Uname: Linux 4.18.0-17-generic x86_64
>   AddonCompatCheckDisabled: False
>   ApportVersion: 2.20.10-0ubuntu13.2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC2:  jeb3837 F pulseaudio
>/dev/snd/controlC1:  jeb3837 F pulseaudio
>/dev/snd/controlC0:  jeb3837 F pulseaudio
>   BuildID: 20190325141154
>   Channel: Unavailable
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Apr  5 11:09:14 2019
>   Extensions: extensions.sqlite corrupt or missing
>   ForcedLayersAccel: False
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   IncompatibleExtensions: Unavailable (corrupt or non-existant
> compatibility.ini or extensions.sqlite)
>   InstallationDate: Installed on 2018-08-17 (231 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   IpRoute:
>default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600
>169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000
>192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src
> 192.168.86.25 metric 600
>192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
> linkdown
>   Locales: extensions.sqlite corrupt or missing
>   MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
>   PrefSources: prefs.js
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use)
>   RunningIncompatibleAddons: False
>   SourcePackage: thunderbird
>   SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
>   Themes: extensions.sqlite corrupt or missing
>   UpgradeStatus: Upgraded to cosmic on 2018-10-19 (168 days ago)
>   dmi.bios.date: 09/21/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 080016
>   dmi.board.asset.tag: To Be Filled By O.E.M.
>   dmi.board.name: A880G+
>   dmi.board.vendor: BIOSTAR Group
>   dmi.chassis.asset.tag: None
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: BIOSTAR Group
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
>   dmi.product.family: To Be Filled By O.E.M.
>   dmi.product.name: A880G+
>   dmi.product.sku: To Be Filled By O.E.M.
>   dmi.sys.vendor: BIOSTAR Group
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/thunderbird/+bug/1823363/+subscriptions
>

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

Title:
  Running "Junk Mail Controls" does not appear in Activity Manager

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  "Running Junk Mail Controls" does not appear in Activity Manager

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeb3837 F pulseaudio
   /dev/snd/controlC1:  jeb3837 F pulseaudio
   /dev/snd/controlC0:  jeb3837 F pulseaudio
  BuildID: 20190325141154
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 11:09:14 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-08-17 (231 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 
   169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 
   192.168

[Desktop-packages] [Bug 1826056] [NEW] Desktop context: Keep aligned, Organize desktop by name missing in 19.04

2019-04-23 Thread JOSEPH E CONNER

Public bug reported:

After upgrading from 18.10 to 19.04 the desktop context menu no longer
contains the choices:

Keep aligned
Organize desktop by name

These were very useful to me. I would like them to be restored.

Ubuntu 19.04, 64bit
Gnome 3.32.1

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

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

Title:
  Desktop context: Keep aligned, Organize desktop by name missing in
  19.04

Status in tracker package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 to 19.04 the desktop context menu no longer
  contains the choices:

  Keep aligned
  Organize desktop by name

  These were very useful to me. I would like them to be restored.

  Ubuntu 19.04, 64bit
  Gnome 3.32.1

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

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

[Desktop-packages] [Bug 1334329] Re: Sound input settings not saved

2019-04-22 Thread Chris E.

It's also in Ubuntu 19.04. Tested minutes ago with two different
laptops.

Steps to reproduce:

1. Mute mic
2. Restart laptop
3. Check mic state/volume level
-> Mic ins't muted. Volume level wasn't saved. Really annoying bug, if want to 
use Ubuntu in production/telcos

** Tags added: disco

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1334329

Title:
  Sound input settings not saved

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When attempting to set my preferred sound input device, simply leaving
  sound preferences and going back to sound preferences, and selecting
  input, causes the default SPDIF to be selected again, and not the
  internal microphone I preferred.  I made a video to demonstrate what I
  mean by this here:  http://youtu.be/9Q9EQvLl_rA

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  I really don't know.  It's just the sound preferences.

  3) What you expected to happen
  For my selected sound input to be saved.

  4) What happened instead
  Keeps defaulting to the top sound input

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brandon   23953 F pulseaudio
   /dev/snd/controlC0:  brandon   23953 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 25 11:20:14 2014
  InstallationDate: Installed on 2014-04-26 (60 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B27.1201241646
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245A3940C91C80
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245A3940C91C80
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80:
  dmi.product.name: MacBookPro8,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1823363] [NEW] "Running Junk Mail Controls" does not appear in Activity Manager

2019-04-05 Thread Jeb E.

Public bug reported:

"Running Junk Mail Controls" does not appear in Activity Manager

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  jeb3837 F pulseaudio
 /dev/snd/controlC1:  jeb3837 F pulseaudio
 /dev/snd/controlC0:  jeb3837 F pulseaudio
BuildID: 20190325141154
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  5 11:09:14 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-08-17 (231 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 
 169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 
 192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src 192.168.86.25 
metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
PrefSources: prefs.js
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to cosmic on 2018-10-19 (168 days ago)
dmi.bios.date: 09/21/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: A880G+
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: A880G+
dmi.product.sku: To Be Filled By O.E.M.
dmi.sys.vendor: BIOSTAR Group

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


** Tags: amd64 apport-bug cosmic

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

Title:
  "Running Junk Mail Controls" does not appear in Activity Manager

Status in thunderbird package in Ubuntu:
  New

Bug description:
  "Running Junk Mail Controls" does not appear in Activity Manager

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeb3837 F pulseaudio
   /dev/snd/controlC1:  jeb3837 F pulseaudio
   /dev/snd/controlC0:  jeb3837 F pulseaudio
  BuildID: 20190325141154
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 11:09:14 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-08-17 (231 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 
   169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 
   192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src 
192.168.86.25 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (168 days ago)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends Inc.

[Desktop-packages] [Bug 1822900] [NEW] A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script

2019-04-02 Thread Jeb E.

Public bug reported:

A script on this page may be busy, or it may have stopped responding.
You can stop the script now, or you can continue to see if the script
will complete.

Script: chrome://messenger/content/folderPane.js:2199

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  jeb3837 F pulseaudio
 /dev/snd/controlC1:  jeb3837 F pulseaudio
 /dev/snd/controlC0:  jeb3837 F pulseaudio
BuildID: 20190325141154
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  2 18:51:12 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-08-17 (228 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 
 169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 
 192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src 192.168.86.25 
metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
PrefSources: prefs.js
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to cosmic on 2018-10-19 (165 days ago)
dmi.bios.date: 09/21/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: A880G+
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: A880G+
dmi.product.sku: To Be Filled By O.E.M.
dmi.sys.vendor: BIOSTAR Group

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


** Tags: amd64 apport-bug cosmic imap server

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

Title:
  A script on this page may be busy, or it may have stopped responding.
  You can stop the script now, or you can continue to see if the script
  will complete.  Script: chrome://messenger/content/folderPane.js:2199

Status in thunderbird package in Ubuntu:
  New

Bug description:
  A script on this page may be busy, or it may have stopped responding.
  You can stop the script now, or you can continue to see if the script
  will complete.

  Script: chrome://messenger/content/folderPane.js:2199

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeb3837 F pulseaudio
   /dev/snd/controlC1:  jeb3837 F pulseaudio
   /dev/snd/controlC0:  jeb3837 F pulseaudio
  BuildID: 20190325141154
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 18:51:12 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-08-17 (228 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 
   169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 
   192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src 
192.168.86.25 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(cus

[Desktop-packages] [Bug 1819023] Re: [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen

2019-04-02 Thread Jeb E.

Apologies, I forgot to get back.
Please see the attachment included in this response. Note the effect is very 
minimal when recorded or shot as a moving GIF.

** Attachment added: "Note the effect appeats very minimal when recorded with a 
camera."
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1819023/+attachment/5252101/+files/20190402_113806-ANIMATION.gif

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1819023

Title:
  [nouveau] Scrolling screen flicker, especially on default Ubuntu lock
  screen

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  My screen is experiencing a weird "scrolling" flicker, especially
  while displaying blue, indigo, and violet hues/colors, such as on the
  default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker
  scrolls up and down, with the brightest part of the flicker being
  towards the top, with a gradient that fades back to the original color
  near the bottom.

  Problem occurs on any one monitor on any one video output protocol
  (DVI-D, HDMI, and VGA).

  
  I will upload an illustration or render as soon as possible for better 
explanation.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 10:39:50 2019
  DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828]
  InstallationDate: Installed on 2018-08-17 (202 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: BIOSTAR Group A880G+
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (139 days ago)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A880G+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A880G+
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.sys.vendor: BIOSTAR Group
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1087582]

2019-03-28 Thread Ville-syrjala-e

I got fed up with my 945gm not being capabile of 60fps glxgears.

commit d938da6b132a2d6addeba4c57a67ec3c07824843
Author: Ville Syrjälä 
Date:   Fri Mar 22 20:08:03 2019 +0200

drm/i915: Disable C3 when enabling vblank interrupts on i945gm

The main difference compared to the older pm_qos attempts is that I
found a way to dig out the exact c3 disable latency, so we should have a
reasonable guarantee that we do disable c3 but not c2. The power cost of
not using c3 seems to be about 0.7W on my machine (with the display on),
so this isn't exactly cheap :(

I did spend quite a bit of time at some point digging through the
chipset docs (such as they are). It's been a while since I did that but
I'll try to summarize what I recall; Gen3 introduced some kind of new
mechanism by which the gmch can wake up the CPU. The old AGPBUSY/PM_BUSY
involved the ICH as well IIRC, whereas the new mechanism supposedly does
not. IIRC the new mechanism already appears in the i915gm docs, but my
theory is that i945gm is where it actually got into use and either it is
broken or we're missing some magic undocumented bit somewhere. I did try
(blindly if necessary) poking at various registers that seemed relevant.
Alas, I was unable to find a magic bit to make C3+vblank interrupts
cooperate.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1087582

Title:
  [gen3] Bad GPU performance whilst CPU is in deep sleep

Status in xf86-video-intel:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I have an Acer AOD250(KAV60) netbook.
  On Ubuntu 12.10 with glxgears I get 50-60 fps, while on Lubuntu I get half 
that and sometimes worse.
  The odd thing about this is that when I start moving my mouse around it 
straightens up and goes back to roughly 55-60 fps, and once I stop moving the 
mouse, the performance drops again.
  I know the chipset and GPU isn't the best out there, but it shouldn't be 
acting like this(before, I was able to use Celestia with ease but now I get 
below 5 fps).

  Latest available BIOS(v1.29)
  Intel Atom N270 1.6GHz(1 core, 2 threads)
  1024RAM
  Intel 945GMA(8MB VRAM from BIOS)

  Tested glxgears from mesa-utils "8.0.1+git20110129+d8f7d6b-0ubuntu2"

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Fri Dec  7 02:37:04 2012
  InstallationDate: Installed on 2012-12-07 (0 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  MarkForUpload: True
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1087582/+subscriptions

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

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

2019-03-23 Thread e-fernbach

Ubuntu 18.04.2 Gnome 
had the problem described above, followed #23 and now my Xserver doesn't work 
anymore. I am stuck at a terminal.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1774957

Title:
  Network icons in status menu disappearing

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Disco:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/140

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774957/+subscriptions

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

[Desktop-packages] [Bug 1819023] [NEW] Scrolling screen flicker, especially on default Ubuntu lock screen

2019-03-07 Thread Jeb E.

Public bug reported:

My screen is experiencing a weird "scrolling" flicker, especially while
displaying blue, indigo, and violet hues/colors, such as on the default
Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker scrolls up
and down, with the brightest part of the flicker being towards the top,
with a gradient that fades back to the original color near the bottom.

Problem occurs on any one monitor on any one video output protocol
(DVI-D, HDMI, and VGA).


I will upload an illustration or render as soon as possible for better 
explanation.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  7 10:39:50 2019
DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828]
InstallationDate: Installed on 2018-08-17 (202 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: BIOSTAR Group A880G+
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to cosmic on 2018-10-19 (139 days ago)
dmi.bios.date: 09/21/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: A880G+
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: A880G+
dmi.product.sku: To Be Filled By O.E.M.
dmi.sys.vendor: BIOSTAR Group
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

** Affects: nouveau
 Importance: Undecided
 Status: New

** Affects: xorg-server
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug cosmic driver flicker gpu gradient graphic manager 
ubuntu window

** Also affects: xorg-server
   Importance: Undecided
   Status: New

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

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

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

Title:
  Scrolling screen flicker, especially on default Ubuntu lock screen

Status in Nouveau Xorg driver:
  New
Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My screen is experiencing a weird "scrolling" flicker, especially
  while displaying blue, indigo, and violet hues/colors, such as on the
  default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker
  scrolls up and down, with the brightest part of the flicker being
  towards the top, with a gradient that fades back to the original color
  near the bottom.

  Problem occurs on any one monitor on any one video output protocol
  (DVI-D, HDMI, and VGA).

  
  I will upload an illustration or render as soon as possible for better 
explanation.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 10:39:50 2019
  DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to ex

Re: [Desktop-packages] [Bug 1455857] Re: Program crashes before a window appears. Having Xlib: extension GLX missing problems

2019-03-06 Thread Pablo E. Adames

Paul,Thanks.I am on 18.04 LTS and ever since I updated from 16.04 LTS the 
laptop integrated webcam stopped working.
pablo@pablo-P170EM:~$ lsusb
Bus 002 Device 003: ID 147e:1002 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
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 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
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 005: ID 047d:1012 Kensington PocketMouse
Bus 003 Device 004: ID 045e:0780 Microsoft Corp. Comfort Curve Keyboard 3000
Bus 003 Device 003: ID 1058:10b8 Western Digital Technologies, Inc. Elements 
Portable (WDBU6Y, WDBUZG)
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


pablo@pablo-P170EM:~$ lsmod
Module  Size  Used by
btrfs    1122304  0
zstd_compress 163840  1 btrfs
xor    24576  1 btrfs
raid6_pq  114688  1 btrfs
ufs    77824  0
qnx4   16384  0
hfsplus   106496  0
hfs    57344  0
minix  32768  0
ntfs  102400  0
msdos  20480  0
jfs   188416  0
xfs  1200128  0
libcrc32c  16384  1 xfs
cpuid  16384  0
nls_iso8859_1  16384  1
pci_stub   16384  1
vboxpci    24576  0
vboxnetadp 28672  0
vboxnetflt 28672  0
vboxdrv   471040  3 vboxpci,vboxnetadp,vboxnetflt
ipheth 16384  0
binfmt_misc    20480  1
intel_rapl 20480  0
x86_pkg_temp_thermal    16384  0
intel_powerclamp   16384  0
coretemp   16384  0
kvm_intel 212992  0
kvm   598016  1 kvm_intel
irqbypass  16384  1 kvm
crct10dif_pclmul   16384  0
snd_hda_codec_hdmi 49152  1
crc32_pclmul   16384  0
ghash_clmulni_intel    16384  0
arc4   16384  2
pcbc   16384  0
ath9k 151552  0
aesni_intel   188416  0
snd_hda_codec_realtek   106496  1
snd_hda_codec_generic    73728  1 snd_hda_codec_realtek
aes_x86_64 20480  1 aesni_intel
snd_hda_intel  40960  6
snd_hda_codec 126976  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core   81920  5 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_hwdep  20480  1 snd_hda_codec
crypto_simd    16384  1 aesni_intel
snd_pcm    98304  4 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd_seq_midi   16384  0
snd_seq_midi_event 16384  1 snd_seq_midi
snd_rawmidi    32768  1 snd_seq_midi
ath9k_common   36864  1 ath9k
ath9k_hw  471040  2 ath9k_common,ath9k
snd_seq    65536  2 snd_seq_midi,snd_seq_midi_event
snd_seq_device 16384  3 snd_seq,snd_seq_midi,snd_rawmidi
ath    28672  3 ath9k_common,ath9k,ath9k_hw
snd_timer  32768  2 snd_seq,snd_pcm
glue_helper    16384  1 aesni_intel
cryptd 24576  3 crypto_simd,ghash_clmulni_intel,aesni_intel
intel_cstate   20480  0
intel_rapl_perf    16384  0
rtsx_pci_ms    20480  0
snd    81920  23 
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi
mac80211  778240  1 ath9k
memstick   16384  1 rtsx_pci_ms
joydev 24576  0
input_leds 16384  0
wmi_bmof   16384  0
serio_raw  16384  0
cfg80211  622592  4 ath9k_common,ath9k,ath,mac80211
mei_me 40960  0
shpchp 36864  0
lpc_ich    24576  0
soundcore  16384  1 snd
mei    90112  1 mei_me
mac_hid    16384  0
sch_fq_codel   20480  3
parport_pc 36864  0
ppdev  20480  0
lp 20480  0
parport    49152  3 parport_pc,lp,ppdev
ip_tables  28672  0
x_tables   40960  1 ip_tables
autofs4    40960  2
hid_generic    16384  0
usbhid 49152  0
hid   118784  2 usbhid,hid_generic
mmc_block  36864  2
uas    24576  0
usb_storage    69632  2 uas
nouveau  1716224  2
i915 1617920  24
rtsx_pci_sdmmc 24576  0
ttm   106496  1 nouveau
i2c_algo_bit   16384  2 i915,nouveau
drm_kms_helper    172032  2 i915,nouveau
syscopyarea

[Desktop-packages] [Bug 1735202] Re: "Continue on PC" feature with signed in Microsoft accounts

This feature should work with Microsoft's new open source Graph API, as
long as it's implemented and integrated into the OS (or software).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1735202

Title:
  "Continue on PC" feature with signed in Microsoft accounts

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Please bring compatibility with the Windows 10 and Cortana feature
  "Continue on PC" for users signed into Microsoft Accounts in gnome-
  control-center.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8
  Uname: Linux 4.13.0-17-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 29 10:43:08 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1735202/+subscriptions

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

[Desktop-packages] [Bug 1750146] Re: Xbox (One) Wireless Controller won't connect

No fix yet?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1750146

Title:
  Xbox (One) Wireless Controller won't connect

Status in gnome-control-center:
  Confirmed
Status in Linux:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth 
with Ubuntu 17.10 in the gnome-control-center.
  Placing the controller into pairing mode makes it visible on the Bluetooth 
Devices list and the device pairs, but does not make the full connection needed 
to pull the controller out of pairing mode.

  This renders my controller unusable with my Ubuntu PC unless I want to
  resort to using the wire (microUSB).

  Please fix. See the attached system information below.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 09:26:14 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+subscriptions

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

[Desktop-packages] [Bug 1750151] Re: Full Microsoft OneDrive support for gnome-control-center and nautilus

Thank you.
Sorry for the delayed response, but does anyone know the status?

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

Title:
  Full Microsoft OneDrive support for gnome-control-center and nautilus

Status in gvfs:
  Expired
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Please add full OneDrive support for gnome-control-center, Nautilus,
  and Ubuntu in general. The 'Online Accounts' section within Control
  Center already has some support for OneDrive, regarding general
  Documents and Mail, so adding full cloud storage capabilities should
  be quite easy to implement.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 09:44:30 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1809975] Re: Please implement Microsoft "Your Phone" support for Chat Accounts