[Desktop-packages] [Bug 1891132] [NEW] package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1

[William]

calibre (4.99.4+dfsg+really4.12.0-1build1) ...
Setting up imagemagick (8:6.9.10.23+dfsg-2.1ubuntu11) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for libc-bin (2.31-0ubuntu9) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for shared-mime-info (1.15-1) ...
Processing triggers for fontconfig (2.13.1-2ubuntu3) ...
Errors were encountered while processing:
 zsys
[master 4d8b0ba] committing changes in /etc made by "apt install calibre"
 Author: william 
 69 files changed, 3770 insertions(+)
 create mode 100644 ImageMagick-6/coder.xml
 create mode 100644 ImageMagick-6/colors.xml
 create mode 100644 ImageMagick-6/delegates.xml
 create mode 100644 ImageMagick-6/log.xml
 create mode 100644 ImageMagick-6/magic.xml
 create mode 100644 ImageMagick-6/mime.xml
 create mode 100644 ImageMagick-6/policy.xml
 create mode 100644 ImageMagick-6/quantization-table.xml
 create mode 100644 ImageMagick-6/thresholds.xml
 create mode 100644 ImageMagick-6/type-apple.xml
 create mode 100644 ImageMagick-6/type-dejavu.xml
 create mode 100644 ImageMagick-6/type-ghostscript.xml
 create mode 100644 ImageMagick-6/type-urw-base35.xml
 create mode 100644 ImageMagick-6/type-windows.xml
 create mode 100644 ImageMagick-6/type.xml
 create mode 12 alternatives/animate
 create mode 12 alternatives/animate-im6
 create mode 12 alternatives/animate-im6.1.gz
 create mode 12 alternatives/animate.1.gz
 create mode 12 alternatives/compare
 create mode 12 alternatives/compare-im6
 create mode 12 alternatives/compare-im6.1.gz
 create mode 12 alternatives/compare.1.gz
 create mode 12 alternatives/composite
 create mode 12 alternatives/composite-im6
 create mode 12 alternatives/composite-im6.1.gz
 create mode 12 alternatives/composite.1.gz
 create mode 12 alternatives/conjure
 create mode 12 alternatives/conjure-im6
 create mode 12 alternatives/conjure-im6.1.gz
 create mode 12 alternatives/conjure.1.gz
 create mode 12 alternatives/convert
 create mode 12 alternatives/convert-im6
 create mode 12 alternatives/convert-im6.1.gz
 create mode 12 alternatives/convert.1.gz
 create mode 12 alternatives/csscapture
 create mode 12 alternatives/csscapture.1.gz
 create mode 12 alternatives/csscombine
 create mode 12 alternatives/csscombine.1.gz
 create mode 12 alternatives/cssparse
 create mode 12 alternatives/cssparse.1.gz
 create mode 12 alternatives/display
 create mode 12 alternatives/display-im6
 create mode 12 alternatives/display-im6.1.gz
 create mode 12 alternatives/display.1.gz
 create mode 12 alternatives/html2markdown
 create mode 12 alternatives/html2markdown.1.gz
 create mode 12 alternatives/identify
 create mode 12 alternatives/identify-im6
 create mode 12 alternatives/identify-im6.1.gz
 create mode 12 alternatives/identify.1.gz
 create mode 12 alternatives/import
 create mode 12 alternatives/import-im6
 create mode 12 alternatives/import-im6.1.gz
 create mode 12 alternatives/import.1.gz
 create mode 12 alternatives/mogrify
 create mode 12 alternatives/mogrify-im6
 create mode 12 alternatives/mogrify-im6.1.gz
 create mode 12 alternatives/mogrify.1.gz
 create mode 12 alternatives/montage
 create mode 12 alternatives/montage-im6
 create mode 12 alternatives/montage-im6.1.gz
 create mode 12 alternatives/montage.1.gz
 create mode 12 alternatives/stream
 create mode 12 alternatives/stream-im6
 create mode 12 alternatives/stream-im6.1.gz
 create mode 12 alternatives/stream.1.gz
ZSys is adding automatic system snapshot to GRUB menu
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: zsys 0.4.6
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Aug 11 08:07:51 2020
ErrorMessage: installed zsys package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2020-04-25 (107 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_61wq9x@/vmlinuz-5.4.0-28-generic 
root=ZFS=rpool/ROOT/ubuntu_61wq9x ro quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 zfs-initramfs  0.8.3-1ubuntu12.2
 zfsutils-linux 0.8.3-1ubuntu12.2
SourcePackage: zsys
Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package 
post-installation script subprocess returned error exit status

[Desktop-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[William]

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

This still happens on ubuntu 18.10.
sudo kbd_mode -s does work.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in console-setup package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

[William]

This issue is also present in 22.10. After the update broke audio, I
reinstalled 22.10 from a live usb which fixed the issue until I updated
again and the issue reappeared.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

[William]

Booting with linux-image-5.19.0-35-generic appears to be the problem in
22.10. Booting with linux-image-5.19.0-21-generic lists the audio
devices again.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

[William]

You select your kernel in the grub boot menu. There is an option for
alternative boot configurations. I have a dual boot environment set up
so grub comes up every time for me. I think you hit esc to bring it up
if it normally boots straight into windows. If you have any trouble it
should come up in a search pretty quick.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 1797749] Re: Drag and drop from File Roller to Nautilus not working

[William]

I'm experiencing this on Ubuntu 19.04. Can this bug be re-opened or
should I create a new one?

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

Title:
  Drag and drop from File Roller to Nautilus not working

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  This started to appear after updating to 18.10.

  Steps to reproduce:
  * open any archive with File Roller
  * open any location in Nautilus
  * drag a file or directory from File Roller to Nautilus

  Expected:
  * selected files/directories are extracted to the drop location

  Actually happens:
  * nothing

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu6
  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: GNOME
  Date: Sun Oct 14 10:26:22 2018
  InstallationDate: Installed on 2017-12-20 (297 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-04-20T17:55:23.166649
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797749/+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 1803469] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package libnvidia

[William]

Public bug reported:

I installed nvidia-toolkit before installing nvidia-340. When I tried
installing nvidia-340, I got this error. Here are the last few lines
from terminal.

Adding 'diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.distrib by nvidia-340'
Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also 
in package libnvidia-compute-390:amd64 390.77-0ubuntu0.18.04.1
Errors were encountered while processing:
 /var/cache/apt/archives/nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Wed Nov 14 20:13:53 2018
ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', 
which is also in package libnvidia-compute-390:amd64 390.77-0ubuntu0.18.04.1
InstallationDate: Installed on 2018-11-15 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
libnvidia-compute-390:amd64 390.77-0ubuntu0.18.04.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is
  also in package libnvidia-compute-390:amd64 390.77-0ubuntu0.18.04.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  I installed nvidia-toolkit before installing nvidia-340. When I tried
  installing nvidia-340, I got this error. Here are the last few lines
  from terminal.

  Adding 'diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.distrib by nvidia-340'
  Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package libnvidia-compute-390:amd64 390.77-0ubuntu0.18.04.1
  Errors were encountered while processing:
   /var/cache/apt/archives/nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Nov 14 20:13:53 2018
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
libnvidia-compute-390:amd64 390.77-0ubuntu0.18.04.1
  InstallationDate: Installed on 2018-11-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in 
package libnvidia-compute-390:amd64 390.77-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1803469/+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 1767817] Re: Full text search does not work

[William]

I registered just to post on this bug report. 
I'm a dev trying to switch over to Linux and I chose Ubuntu assuming it would 
be the most functionable distro in 2018.
However I simply cannot make the transition until type-as-you-go search + 
indexing is not working just like on macos in 2013 and even now on windows 10.

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

Title:
  Full text search does not work

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Background: I have installed Tracker. It has finished indexing. I can
  also use Tracker's command line interface to search by content.

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

  nautilus:
Installed: 1:3.26.3-0ubuntu4
Candidate: 1:3.26.3-0ubuntu4
Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expect to be able to search files by content from Nautilus,
  because this feature worked in 17.10.

  4. I get no results from full text search unless the search matches
  file names.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+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 1903723] [NEW] Audio dropouts and general surround sound issues. Device shown as ALC887-VD Analog instead of ALC1220 as per motherboard specifications [AB350-Gaming, Realtek AL

[William]

Public bug reported:

Audio dropouts and general surround sound issues.
Incorrect ALC device shown from cat /proc/asound/card1/pcm0c/info
card: 1
device: 0
subdevice: 0
stream: CAPTURE
id: ALC887-VD Analog
name: ALC887-VD Analog
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 1

Device should be shown as ALC1220 as per Motherboard (Gigabyte AB350
Gaming 3) Specifications.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-52.57-lowlatency 5.4.65
Uname: Linux 5.4.0-52-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  billy  9531 F pulseaudio
 /dev/snd/controlC2:  billy  9531 F pulseaudio
 /dev/snd/controlC1:  billy  9531 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 10 15:05:30 2020
InstallationDate: Installed on 2020-11-10 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic
Symptom_Jack: Green Line Out, Rear
Symptom_PulseAudioLog:
 Nov 10 14:37:41 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.28' (uid=1000 pid=1083 comm="/usr/bin/pulseaudio 
--daemonize=no --log-target=jo" label="unconfined")
 Nov 10 14:37:43 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.41' 
(uid=1000 pid=1083 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
 Nov 10 14:57:06 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.341' 
(uid=1000 pid=9531 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [AB350-Gaming, Realtek ALC887-VD, Green Line Out, Rear] Underruns, 
dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F23d
dmi.board.asset.tag: Default string
dmi.board.name: AB350-Gaming-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350-Gaming
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-11-10T14:56:54.599621

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1903723

Title:
  Audio dropouts and general surround sound issues. Device shown as
  ALC887-VD Analog instead of ALC1220 as per motherboard specifications
  [AB350-Gaming, Realtek ALC887-VD, Green Line Out, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Audio dropouts and general surround sound issues.
  Incorrect ALC device shown from cat /proc/asound/card1/pcm0c/info
  card: 1
  device: 0
  subdevice: 0
  stream: CAPTURE
  id: ALC887-VD Analog
  name: ALC887-VD Analog
  subname: subdevice #0
  class: 0
  subclass: 0
  subdevices_count: 1
  subdevices_avail: 1

  Device should be shown as ALC1220 as per Motherboard (Gigabyte AB350
  Gaming 3) Specifications.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-52.57-lowlatency 5.4.65
  Uname: Linux 5.4.0-52-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  billy  9531 F pulseaudio
   /dev/snd/controlC2:  billy  9531 F pulseaudio
   /dev/snd/controlC1:  billy  9531 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 10 15:05:30 2020
  InstallationDate: Installed on 2020-11-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom:

Re: [Desktop-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[william]

Em 03/05/2016 07:47, Rick Harris escreveu:
> One last thing...ice in comment #12 said:
> "Some people say it has to do with a ASMedia USB Controller"
>
> Have found that USB enumeration failure can cause a bottleneck in
> systemd getting the upower.service unit to finally start.
>
> You'll know if the system is hit with this as it'll be much slower to boot 
> and the kernel will spew errors of the type:
> kernel: usb 2-1.1: device descriptor read/64, error -110
> kernel: usb 2-1-port1: unable to enumerate USB device
>
> Occasionally after several suspend/resumes, I have a USB device
> (wireless game controller) that must be unplugged/replugged to stop this
> error (simply rebooting does not fix).
>
> Have found on my laptop, if the USB enumeration boots through without
> any error then it's quick enough to have systemd start  upower.service
> in time before u-s-d is started, otherwise the u-s-d segfault occurs as
> above.
>
> Thanks :)

That's my problem. But I will solve. If you have or found an package to 
solve this problem to people that eran less than 15 dollars a day like 
me, I would be glad. I from Brasil, we are in terrible economic crisis. 
And many of us had kids to support to. But I thank you a lot. Thanks for 
care.

GM

>

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+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 1599353] [NEW] package mythes-en-us 1:5.1.0-1ubuntu2 failed to install/upgrade: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't exist: Read-only file system

[william]

Public bug reported:

Trying to install to an SSD with WIN 10 and could not soo I had Ubuntu
format the whole disk.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mythes-en-us 1:5.1.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.376
Date: Tue Jul  5 18:37:45 2016
ErrorMessage: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't 
exist: Read-only file system
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: libreoffice-dictionaries
Title: package mythes-en-us 1:5.1.0-1ubuntu2 failed to install/upgrade: error 
ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't exist: Read-only file 
system
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libreoffice-dictionaries (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 libreoffice-dictionaries in Ubuntu.
https://bugs.launchpad.net/bugs/1599353

Title:
  package mythes-en-us 1:5.1.0-1ubuntu2 failed to install/upgrade: error
  ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't exist: Read-
  only file system

Status in libreoffice-dictionaries package in Ubuntu:
  New

Bug description:
  Trying to install to an SSD with WIN 10 and could not soo I had Ubuntu
  format the whole disk.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: mythes-en-us 1:5.1.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  Date: Tue Jul  5 18:37:45 2016
  ErrorMessage: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't 
exist: Read-only file system
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libreoffice-dictionaries
  Title: package mythes-en-us 1:5.1.0-1ubuntu2 failed to install/upgrade: error 
ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't exist: Read-only file 
system
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1599353/+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 1599519] [NEW] package libreoffice-help-en-us 1:5.1.2-0ubuntu1 failed to install/upgrade: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't exist: Read-only file sys

[william]

Public bug reported:

Error occurred while trying to install Ubuntu.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-help-en-us 1:5.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.376
Date: Tue Jul  5 18:37:45 2016
ErrorMessage: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't 
exist: Read-only file system
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: libreoffice-l10n
Title: package libreoffice-help-en-us 1:5.1.2-0ubuntu1 failed to 
install/upgrade: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't 
exist: Read-only file system
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libreoffice-l10n (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 libreoffice-l10n in Ubuntu.
https://bugs.launchpad.net/bugs/1599519

Title:
  package libreoffice-help-en-us 1:5.1.2-0ubuntu1 failed to
  install/upgrade: error ensuring '/target/var/lib/dpkg/reassemble.deb'
  doesn't exist: Read-only file system

Status in libreoffice-l10n package in Ubuntu:
  New

Bug description:
  Error occurred while trying to install Ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-help-en-us 1:5.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  Date: Tue Jul  5 18:37:45 2016
  ErrorMessage: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't 
exist: Read-only file system
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libreoffice-l10n
  Title: package libreoffice-help-en-us 1:5.1.2-0ubuntu1 failed to 
install/upgrade: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't 
exist: Read-only file system
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-l10n/+bug/1599519/+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 1548041] Re: xorg

[william]

OK I will try. It is too much info for my Brazilian Brain. My world and
knowledge can not be compare to yours. Understand? Thank you.
Em 22/02/2016 00:15, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> escreveu:

> william, thank you for reporting this and helping make Ubuntu better.
> However, your crash report is missing.
>
> Please follow these instructions to have apport report a new bug about
> your crash that can be dealt with by the automatic retracer. First, execute
> at a terminal:
> cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y
> dist-upgrade && sudo service apport start force_start=1
>
> If you are running the Ubuntu Stable Release you might need to enable
> apport in /etc/default/apport and restart. Now reproduce the crash, then
> open a terminal, navigate to your /var/crash directory and file your report
> with:
> sudo ubuntu-bug /var/crash/_my_crash_report.crash
>
> where _my_crash_report.crash is the crash you would like to report. By
> default, this sends the crash to the Ubuntu Error Tracker
> infrastructure, which is different than Launchpad. For more on this,
> please see https://wiki.ubuntu.com/ErrorTracker .
>
> However, if after doing this you would still like to have a crash report
> posted to Launchpad, for example to ease triage and add others to your
> report, one would need to open the following file via a terminal:
> sudo nano /etc/apport/crashdb.conf
>
> and comment out the line:
> 'problem_types': ['Bug', 'Package'],
>
> by changing it to:
> # 'problem_types': ['Bug', 'Package'],
>
> Save, close, and file the crash report via:
> sudo ubuntu-bug /var/crash/FILENAME.crash
>
> Where FILENAME is the actual name of the file found in the folder.
>
> However, this report is being closed since the process outlined above
> will deal with this issue more efficiently.
>
> Also, please do not attach your crash report manually to this report and
> reopen it.
>
> Thank you for your understanding.
>
> Helpful bug reporting tips:
> https://wiki.ubuntu.com/ReportingBugs
>
> ** Changed in: xorg (Ubuntu)
>Importance: Low => Undecided
>
> ** Changed in: xorg (Ubuntu)
>Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1548041
>
> Title:
>   xorg
>
> Status in xorg package in Ubuntu:
>   Invalid
>
> Bug description:
>   crash
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu1
>   ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
>   Uname: Linux 4.4.0-7-generic x86_64
>   NonfreeKernelModules: wl
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: amd64
>   BootLog: [ [0;32m  OK   [0m] Started LSB: Set the CPU Frequency Scaling
> governor to "ondemand".
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Sun Feb 21 07:32:06 2016
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-7-generic, x86_64: installed
>   ExtraDebuggingInterest: I just need to know a workaround
>   GraphicsCard:
>Intel Corporation Broadwell-U Integrated Graphics [8086:1606] (rev 08)
> (prog-if 00 [VGA controller])
>  Subsystem: Samsung Electronics Co Ltd Broadwell-U Integrated Graphics
> [144d:c755]
>   InstallationDate: Installed on 2016-02-08 (12 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160205)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic
> root=UUID=3c02014d-5d32-41b6-8b67-b1d45dd7d695 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/06/2015
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: P03RCX.066.150706.JJ
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: NP370E4K-KWABR
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: SGL8537A09-C01-G001-S0001+10.0.10240
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrP03RCX.066.150706.JJ:bd07/06/2015:s

Re: [Desktop-packages] [Bug 1548041] Re: xorg

[william]

Friend var/crash has
102 _usr_lib_   --> unity, tracker, x86, share... etc, ...
Em 21/02/2016 14:30, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> escreveu:

> william, thank you for reporting this and helping make Ubuntu better.
>
> To clarify, after the crash, is there a crash file in /var/crash?
>
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1548041
>
> Title:
>   xorg
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   crash
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu1
>   ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
>   Uname: Linux 4.4.0-7-generic x86_64
>   NonfreeKernelModules: wl
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: amd64
>   BootLog: [ [0;32m  OK   [0m] Started LSB: Set the CPU Frequency Scaling
> governor to "ondemand".
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Sun Feb 21 07:32:06 2016
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-7-generic, x86_64: installed
>   ExtraDebuggingInterest: I just need to know a workaround
>   GraphicsCard:
>Intel Corporation Broadwell-U Integrated Graphics [8086:1606] (rev 08)
> (prog-if 00 [VGA controller])
>  Subsystem: Samsung Electronics Co Ltd Broadwell-U Integrated Graphics
> [144d:c755]
>   InstallationDate: Installed on 2016-02-08 (12 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160205)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic
> root=UUID=3c02014d-5d32-41b6-8b67-b1d45dd7d695 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/06/2015
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: P03RCX.066.150706.JJ
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: NP370E4K-KWABR
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: SGL8537A09-C01-G001-S0001+10.0.10240
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrP03RCX.066.150706.JJ:bd07/06/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP03RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KWABR:rvrSGL8537A09-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
>   dmi.product.name: 370E4K
>   dmi.product.version: P03RCX
>   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.67+git1602190630.99ede3~gd~x
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.2~git1602201930.89d25a~gd~x
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.2~git1602201930.89d25a~gd~x
>   version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.9.2-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160218-1ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
>   xserver.bootTime: Sun Feb 21 07:06:19 2016
>   xserver.configfile: default
>   xserver.errors: systemd-logind: failed to get session: PID 1069 does not
> belong to any known session
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id1534
>vendor BOE
>   xserver.version: 2:1.17.3-2ubuntu4
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1548041/+subscriptions
>

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

Title:
  xorg

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  crash

  ProblemType: Bug

Re: [Desktop-packages] [Bug 1548041] Re: xorg

[william]

Yes, I think so.
Em 21/02/2016 14:30, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> escreveu:

> william, thank you for reporting this and helping make Ubuntu better.
>
> To clarify, after the crash, is there a crash file in /var/crash?
>
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1548041
>
> Title:
>   xorg
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   crash
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu1
>   ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
>   Uname: Linux 4.4.0-7-generic x86_64
>   NonfreeKernelModules: wl
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: amd64
>   BootLog: [ [0;32m  OK   [0m] Started LSB: Set the CPU Frequency Scaling
> governor to "ondemand".
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Sun Feb 21 07:32:06 2016
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-7-generic, x86_64: installed
>   ExtraDebuggingInterest: I just need to know a workaround
>   GraphicsCard:
>Intel Corporation Broadwell-U Integrated Graphics [8086:1606] (rev 08)
> (prog-if 00 [VGA controller])
>  Subsystem: Samsung Electronics Co Ltd Broadwell-U Integrated Graphics
> [144d:c755]
>   InstallationDate: Installed on 2016-02-08 (12 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160205)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic
> root=UUID=3c02014d-5d32-41b6-8b67-b1d45dd7d695 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/06/2015
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: P03RCX.066.150706.JJ
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: NP370E4K-KWABR
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: SGL8537A09-C01-G001-S0001+10.0.10240
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrP03RCX.066.150706.JJ:bd07/06/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP03RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KWABR:rvrSGL8537A09-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
>   dmi.product.name: 370E4K
>   dmi.product.version: P03RCX
>   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.67+git1602190630.99ede3~gd~x
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.2~git1602201930.89d25a~gd~x
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.2~git1602201930.89d25a~gd~x
>   version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.9.2-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160218-1ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
>   xserver.bootTime: Sun Feb 21 07:06:19 2016
>   xserver.configfile: default
>   xserver.errors: systemd-logind: failed to get session: PID 1069 does not
> belong to any known session
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id1534
>vendor BOE
>   xserver.version: 2:1.17.3-2ubuntu4
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1548041/+subscriptions
>

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

Title:
  xorg

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  crash

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu1
 

[Desktop-packages] [Bug 1548041] [NEW] xorg

[william]

Public bug reported:

crash

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
Uname: Linux 4.4.0-7-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
BootLog: [  OK  ] Started LSB: Set the CPU Frequency Scaling 
governor to "ondemand".
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Feb 21 07:32:06 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-7-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1606] (rev 08) 
(prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Broadwell-U Integrated Graphics 
[144d:c755]
InstallationDate: Installed on 2016-02-08 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic 
root=UUID=3c02014d-5d32-41b6-8b67-b1d45dd7d695 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P03RCX.066.150706.JJ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP370E4K-KWABR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8537A09-C01-G001-S0001+10.0.10240
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03RCX.066.150706.JJ:bd07/06/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP03RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KWABR:rvrSGL8537A09-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 370E4K
dmi.product.version: P03RCX
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67+git1602190630.99ede3~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2~git1602201930.89d25a~gd~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2~git1602201930.89d25a~gd~x
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Sun Feb 21 07:06:19 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 1069 does not belong 
to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1534 
 vendor BOE
xserver.version: 2:1.17.3-2ubuntu4

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  crash

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  BootLog: [  OK  ] Started LSB: Set the CPU Frequency Scaling 
governor to "ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Feb 21 07:32:06 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-7-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1606] (rev 08) 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Broadwell-U Integrated Graphics 
[144d:c755]
  InstallationDate: Installed on 2016-02-08 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.

Re: [Desktop-packages] [Bug 1558821] Re: transmission-gtk crashed with SIGABRT in event_errx()

[william]

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

Thank you.
Em 17/03/2016 19:50, "Apport retracing service" <1558...@bugs.launchpad.net>
escreveu:

> *** This bug is a duplicate of bug 1421440 ***
> https://bugs.launchpad.net/bugs/1421440
>
> Thank you for taking the time to report this crash and helping to make
> this software better.  This particular crash has already been reported
> and is a duplicate of bug #1421440, so is being marked as such.  Please
> look at the other bug report to see if there is any missing information
> that you can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report.  Please continue to report any other bugs you may
> find.
>
> ** Attachment removed: "CoreDump.gz"
>
> https://bugs.launchpad.net/bugs/1558821/+attachment/4602604/+files/CoreDump.gz
>
> ** Attachment removed: "Disassembly.txt"
>
> https://bugs.launchpad.net/bugs/1558821/+attachment/4602606/+files/Disassembly.txt
>
> ** Attachment removed: "ProcMaps.txt"
>
> https://bugs.launchpad.net/bugs/1558821/+attachment/4602608/+files/ProcMaps.txt
>
> ** Attachment removed: "ProcStatus.txt"
>
> https://bugs.launchpad.net/bugs/1558821/+attachment/4602609/+files/ProcStatus.txt
>
> ** Attachment removed: "Registers.txt"
>
> https://bugs.launchpad.net/bugs/1558821/+attachment/4602610/+files/Registers.txt
>
> ** Attachment removed: "Stacktrace.txt"
>
> https://bugs.launchpad.net/bugs/1558821/+attachment/4602611/+files/Stacktrace.txt
>
> ** Attachment removed: "ThreadStacktrace.txt"
>
> https://bugs.launchpad.net/bugs/1558821/+attachment/4602612/+files/ThreadStacktrace.txt
>
> ** This bug has been marked a duplicate of private bug 1421440
>
> ** Information type changed from Private Security to Public Security
>
> ** Tags removed: need-amd64-retrace
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1558821
>
> Title:
>   transmission-gtk crashed with SIGABRT in event_errx()
>
> Status in transmission package in Ubuntu:
>   New
>
> Bug description:
>   The connection was completely disabled and only get back, after kill
>   transmission process.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 16.04
>   Package: transmission-gtk 2.84-3ubuntu2
>   ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
>   Uname: Linux 4.4.0-13-generic x86_64
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: MATE
>   Date: Thu Mar 17 19:13:44 2016
>   ExecutablePath: /usr/bin/transmission-gtk
>   InstallationDate: Installed on 2016-03-12 (5 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160205)
>   ProcCmdline: transmission-gtk
>   ProcEnviron:
>LANGUAGE=pt_BR:pt:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=pt_BR.UTF-8
>SHELL=/bin/bash
>   Signal: 6
>   SourcePackage: transmission
>   StacktraceTop:
>?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
>event_errx () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
>evdns_cancel_request () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
>evdns_getaddrinfo_cancel () from
> /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
>?? ()
>   Title: transmission-gtk crashed with SIGABRT in event_errx()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1558821/+subscriptions
>

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

Title:
  transmission-gtk crashed with SIGABRT in event_errx()

Status in transmission package in Ubuntu:
  New

Bug description:
  The connection was completely disabled and only get back, after kill
  transmission process.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: transmission-gtk 2.84-3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Mar 17 19:13:44 2016
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationDate: Installed on 2016-03-12 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: transmission-gtk
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: transmission
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
   event_errx () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
   evdns_cancel_request () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
   evdns_getaddrinfo_cancel () from /usr/lib/x86_64-linux-g

Re: [Desktop-packages] [Bug 1556993] Re: liferea crashed with signal 5 in g_variant_new_parsed_va()

[william]

Thank you.
Em 16/03/2016 16:25, "Steve Beattie"  escreveu:

> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. We appreciate the difficulties you are facing, but this appears
> to be a "regular" (non-security) bug.  I have unmarked it as a security
> issue since this bug does not show evidence of allowing attackers to
> cross privilege boundaries nor directly cause loss of data/privacy.
> Please feel free to report any other bugs you may find.
>
> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1556993
>
> Title:
>   liferea crashed with signal 5 in g_variant_new_parsed_va()
>
> Status in liferea package in Ubuntu:
>   New
>
> Bug description:
>   Hello guys. I'm back. Congratulations. I think you will win this war.
>   The UK guys... The best. But I want to know why the screenlets are not
>   working? You create a new store and I can find Screenlets that you do
>   not let work on your Xenial? Ok. Be good.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 16.04
>   Package: liferea 1.10.17-1ubuntu2
>   ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
>   Uname: Linux 4.4.0-12-generic x86_64
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Mon Mar 14 11:35:59 2016
>   ExecutablePath: /usr/bin/liferea
>   InstallationDate: Installed on 2016-03-12 (1 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160205)
>   ProcCmdline: liferea
>   ProcEnviron:
>LANGUAGE=pt_BR:pt:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=pt_BR.UTF-8
>SHELL=/bin/bash
>   Signal: 5
>   SourcePackage: liferea
>   StacktraceTop:
>g_variant_new_parsed_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>g_variant_new_parsed () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
>?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
>?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
>   Title: liferea crashed with signal 5 in g_variant_new_parsed_va()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1556993/+subscriptions
>

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

Title:
  liferea crashed with signal 5 in g_variant_new_parsed_va()

Status in liferea package in Ubuntu:
  New

Bug description:
  Hello guys. I'm back. Congratulations. I think you will win this war.
  The UK guys... The best. But I want to know why the screenlets are not
  working? You create a new store and I can find Screenlets that you do
  not let work on your Xenial? Ok. Be good.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: liferea 1.10.17-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 14 11:35:59 2016
  ExecutablePath: /usr/bin/liferea
  InstallationDate: Installed on 2016-03-12 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: liferea
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: liferea
  StacktraceTop:
   g_variant_new_parsed_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_parsed () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
  Title: liferea crashed with signal 5 in g_variant_new_parsed_va()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1556993/+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 1556993] Re: liferea crashed with signal 5 in g_variant_new_parsed_va()

[william]

ok thank you! :)

On Wed, 16 Mar 2016 19:18:52 -
Steve Beattie  wrote:

> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. We appreciate the difficulties you are facing, but this appears
> to be a "regular" (non-security) bug.  I have unmarked it as a security
> issue since this bug does not show evidence of allowing attackers to
> cross privilege boundaries nor directly cause loss of data/privacy.
> Please feel free to report any other bugs you may find.
> 
> ** Information type changed from Private Security to Public
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1556993
> 
> Title:
>   liferea crashed with signal 5 in g_variant_new_parsed_va()
> 
> Status in liferea package in Ubuntu:
>   New
> 
> Bug description:
>   Hello guys. I'm back. Congratulations. I think you will win this war.
>   The UK guys... The best. But I want to know why the screenlets are not
>   working? You create a new store and I can find Screenlets that you do
>   not let work on your Xenial? Ok. Be good.
> 
>   ProblemType: Crash
>   DistroRelease: Ubuntu 16.04
>   Package: liferea 1.10.17-1ubuntu2
>   ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
>   Uname: Linux 4.4.0-12-generic x86_64
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Mon Mar 14 11:35:59 2016
>   ExecutablePath: /usr/bin/liferea
>   InstallationDate: Installed on 2016-03-12 (1 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
>   ProcCmdline: liferea
>   ProcEnviron:
>LANGUAGE=pt_BR:pt:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=pt_BR.UTF-8
>SHELL=/bin/bash
>   Signal: 5
>   SourcePackage: liferea
>   StacktraceTop:
>g_variant_new_parsed_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>g_variant_new_parsed () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
>?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
>?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
>   Title: liferea crashed with signal 5 in g_variant_new_parsed_va()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1556993/+subscriptions


-- 
tree.yello...@gmail.com 

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

Title:
  liferea crashed with signal 5 in g_variant_new_parsed_va()

Status in liferea package in Ubuntu:
  New

Bug description:
  Hello guys. I'm back. Congratulations. I think you will win this war.
  The UK guys... The best. But I want to know why the screenlets are not
  working? You create a new store and I can find Screenlets that you do
  not let work on your Xenial? Ok. Be good.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: liferea 1.10.17-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 14 11:35:59 2016
  ExecutablePath: /usr/bin/liferea
  InstallationDate: Installed on 2016-03-12 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: liferea
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: liferea
  StacktraceTop:
   g_variant_new_parsed_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_parsed () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
  Title: liferea crashed with signal 5 in g_variant_new_parsed_va()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1556993/+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 1568180] [NEW] Mouse scroll wheel does not work, and thumb buttons

[William]

Public bug reported:

General information
For all bug categories the following general information should be provided:

Ensure you report the bug via ubuntu-bug xorg as outlined above.
T
What is the full manufacturer and model of your mouse.
AULA Killing the Soul Gaming Optical Mouse
How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, etc.
USB
What mechanism does your mouse use: roller ball, optical, trackball, etc.
Optical
How many physical buttons and scrollwheels does you mouse have?
2-right and left
3- scroll up/down + middle click
2 - thumb buttons

In case some mouse buttons or scrollwheels don't work (as expected)
Provide the general information.
T
Open a terminal and enter the following commands:

xmodmap -pp > ~/xmodmap-pp
xev | grep -i button 
T
Put the mouse cursor into the rectangle and push your mouse buttons. Mention in 
the bug report which button number is reported, e.g. left = 1, scrollwheel up = 
4, horizontal scrollwheel left = 6, thumb button = 8, pinkie button = 9, ...
1 and 3 are the only buttons this utility detects.
Attach as separate attachments to your bug report /var/log/Xorg.0.log and 
~/xmodmap-pp.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
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
Date: Fri Apr  8 17:25:56 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: fglrx-core, 15.201, 4.2.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] 
(prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Device [1682:3112]
InstallationDate: Installed on 2016-04-07 (1 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7376
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.B0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: K9A2 Platinum (MS-7376)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.B0:bd06/21/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7376:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9A2Platinum(MS-7376):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7376
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Apr  8 16:56:57 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 fglrx(0): Cannot read int vect
 fglrx(0): Cannot read int vect
 AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
 AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
 AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
xserver.video_driver: fglrx

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

** Attachment added: "xmodmap-pp"
   https://bugs.launchpad.net/bugs/1568180/+attachment/4629749/+files/xmodmap-pp

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

[Desktop-packages] [Bug 358825] Re: rhythmbox stops playing after some time

[William]

Same for me on Ubuntu 15.10

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

Title:
  rhythmbox stops playing after some time

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  When I play an album with rhythmbox, it stops playing after 1 or 2 tracks 
without reason and if I try to select another track after that it doesn't 
respond anymore. I have to terminate the application and restart it.
  For information, all my music is in wavpack and crossfading is enabled.
  Also I'm using rhythmbox 0.12.0-0ubuntu4 on Jaunty.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Package: rhythmbox 0.12.0-0ubuntu4
  ProcEnviron:
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/358825/+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 245716] Re: file-roller puts temporary files in the home dir instead of /tmp

[William]

I tracked down this bug.  The source of the problem is in src/file-
utils.c.  It looks like File Roller calls _g_path_get_temp_work_dir,
which searches the user's cache dir, user's home dir, and tmp, for a
place to put the temporary folder.  It searches in that order.  The
criteria for the search is available free space.  The location with the
most free space will be used.  If two locations have the same amount of
free space, the one searched first will be used.

The bug is that, at least on my system, /tmp and ~/.cache both have the
same amount of free space.  So ~/.cache gets used, since it's searched
first.

This searching algorithm is reasonable, as opposed to just always using
/tmp.  What if File Roller is run on a system where /tmp is limited, and
now the user can't extract an archive because /tmp keeps blowing up.  So
it makes sense to use whatever has the most available disk space.

I suggest fixing this by changing the search order.  The search order is
defined by:

static const char *try_folder[] = { "cache", "~", "tmp", NULL };

Let's change that to:

static const char *try_folder[] = { "tmp", "cache", "~", NULL };

It's a simple change, and for systems like mine, where /tmp is part of
the root filesystem, File Roller will use tmp since it should have the
same free space as cache.

A better solution may be a compile time option to force a particular
folder, or a run-time preference.  In both cases it will be up to the
distro to configure the appropriate compile option or default
preference, according to how their distro installs.

If someone lets me know: where to pull the latest File Roller source
code, and how to submit a patch, I can at least submit a patch tweaking
try_folder.

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

Title:
  file-roller puts temporary files in the home dir instead of /tmp

Status in File Roller:
  Confirmed
Status in file-roller package in Ubuntu:
  Triaged

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy file-roller
  file-roller:
Installed: 3.12.2-0ubuntu1
Candidate: 3.12.2-0ubuntu1
Version table:
   *** 3.12.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one opens a tarball with file-
  roller, and without extracting the file, open it (ex. open PDF file
  with evince) the file-roller utilizes /tmp for this.

  4) What happens instead is file-roller utilizes a directory ~/.cache/.fr-* , 
where * is a changing folder name. If one logs out, or kills the file-roller 
process via:
  kill PID

  the temp files are left behind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/245716/+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 1676326] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1

[william]

Public bug reported:

after cleanning kernel

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CupsErrorLog:
 
Date: Mon Mar 27 06:12:20 2017
ErrorMessage: sub-processo novo script pre-removal retornou estado de saída de 
erro 1
InstallationDate: Installed on 2017-03-17 (9 days ago)
InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=UUID=fb0afc59-47a0-4c6d-8d0c-08e38348217c ro quiet splash 
intel_pstate=enable
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=UUID=fb0afc59-47a0-4c6d-8d0c-08e38348217c ro quiet splash 
intel_pstate=enable
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo 
script pre-removal retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P03RCX.066.150706.JJ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP370E4K-KWABR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8537A09-C01-G001-S0001+10.0.10240
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03RCX.066.150706.JJ:bd07/06/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP03RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KWABR:rvrSGL8537A09-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 370E4K
dmi.product.version: P03RCX
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apparmor apport-package third-party-packages xenial

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo
  novo script pre-removal retornou estado de saída de erro 1

Status in cups package in Ubuntu:
  New

Bug description:
  after cleanning kernel

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Mar 27 06:12:20 2017
  ErrorMessage: sub-processo novo script pre-removal retornou estado de saída 
de erro 1
  InstallationDate: Installed on 2017-03-17 (9 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=UUID=fb0afc59-47a0-4c6d-8d0c-08e38348217c ro quiet splash 
intel_pstate=enable
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=UUID=fb0afc59-47a0-4c6d-8d0c-08e38348217c ro quiet splash 
intel_pstate=enable
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo 
novo script pre-removal retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P03RCX.066.150706.JJ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370E4K-KWABR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8537A09-C01-G001-S0001+10.0.10240
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03RCX.066.150706.JJ:bd07/06/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP03RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KWABR:rvrSGL8537A09-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 370E4K
  dmi.product.version: P03RCX
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676326/+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 1064962] Re: Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running

[William]

The problem also occurs if I do "open recent" when a document is already
open. The second doc opens with no menu displayed.

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

Title:
  Global menubar items do not work when opening a document directly from
  nautilus with no LibreOffice instance running

Status in BAMF Application Matching Framework:
  Confirmed
Status in The Application Menu:
  Confirmed
Status in “bamf” package in Ubuntu:
  Confirmed
Status in “indicator-appmenu” package in Ubuntu:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Invalid
Status in “bamf” source package in Quantal:
  Confirmed
Status in “indicator-appmenu” source package in Quantal:
  Confirmed
Status in “libreoffice” source package in Quantal:
  Invalid

Bug description:
  1) Have no instance of LibreOffice running
  2) open a document by double-clicking it in nautilus
  3) new window has no menu
  4) unfocusing/refocusing (e.g. by pressing F7 to bring up the spelling 
dialog) makes the menu appear

  WORKAROUND: minimize and restore the LibreOffice window

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-gtk 1:3.6.2~rc2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 10 11:48:20 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2012-09-30 (9 days ago)

  original description:
  In writer, none of the menubar items appear to work.  Example:

  * Open new document in Writer
  * Type some text and highlight it
  * Try Edit->Cut
  >> Nothing happens
  * Try Format->Change chase->UPPERCASE
  >> Nothing happens!
  workaround: restart your session after update

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1064962/+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 1135038] Re: friends-dispatcher crashed with friends.errors.AuthorizationError in _login_cb(): GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: userA

[William]

I have the same problem with Evolution too: 
GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: 
userActionFinished error: 10
What can we do ?

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

Title:
  friends-dispatcher crashed with friends.errors.AuthorizationError in
  _login_cb():
  GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction:
  userActionFinished error: 10 (account: 1)

Status in Online Accounts: Sign-on UI:
  Fix Released
Status in “friends” package in Ubuntu:
  Fix Released

Bug description:
  This crash came up right after booting up my laptop.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: friends-dispatcher 0.1.1bzr13.02.25-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
  Uname: Linux 3.8.0-8-generic i686
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Wed Feb 27 20:09:36 2013
  ExecutablePath: /usr/bin/friends-dispatcher
  InstallationDate: Installed on 2012-10-25 (125 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/friends-dispatcher -o
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  PythonArgs: ['/usr/bin/friends-dispatcher', '-o']
  SourcePackage: friends
  Title: friends-dispatcher crashed with friends.errors.AuthorizationError in 
_login_cb(): 
GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: 
userActionFinished error: 10 (account: 1)
  Traceback:
   Traceback (most recent call last):
 File "/usr/lib/python3/dist-packages/friends/utils/authentication.py", 
line 69, in _login_cb
   raise AuthorizationError(self.account.id, error.message)
   friends.errors.AuthorizationError: 
GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: 
userActionFinished error: 10 (account: 1)
  UpgradeStatus: Upgraded to raring on 2013-02-22 (5 days ago)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/signon-ui/+bug/1135038/+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 1080211] Re: Update to 17.0

[william]

updating not working tells me check internet while im on line. what
should i do ?

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

Title:
  Update to 17.0

Status in “firefox” package in Ubuntu:
  Invalid
Status in “ubufox” package in Ubuntu:
  Fix Released
Status in “firefox” source package in Lucid:
  Fix Released
Status in “ubufox” source package in Lucid:
  Fix Released
Status in “firefox” source package in Oneiric:
  Fix Released
Status in “ubufox” source package in Oneiric:
  Fix Released
Status in “firefox” source package in Precise:
  Fix Released
Status in “ubufox” source package in Precise:
  Fix Released
Status in “firefox” source package in Quantal:
  Fix Released
Status in “ubufox” source package in Quantal:
  Fix Released

Bug description:
http://www.ubuntu.com/usn/usn-1638-2
http://www.ubuntu.com/usn/usn-1638-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1080211/+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 951585] Re: gvfsd-afp consumes 100% of processor cycles

[William]

I run Ubuntu 14.04 on an X202E combined with CloudBox NAS after just
having unmounted the NAS, gvsd-afpg-browse loads one CPU 100%. After
killing the process the CPU runs down to idle load and fans slow down.

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

Title:
  gvfsd-afp consumes 100% of processor cycles

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Happens on an irregular basis on 12.04 and I think I've experienced it
  on 11.10.

  For no reason gvfsd-afp starts up. Cooling fan kicks in, system
  becomes laggy. Easily cured using system monitor and killing the
  process. Someone on the Ubuntu Forum asked if I have a Mac on the
  network and the answer is yes, an iMac and there are shares on that
  machine I can access.

  Have experienced this issue on my Acer Aspire 5742 and Compaq Mini 110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+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 1385292] Re: can't rename files in nautilus

[William]

Affects me too.
Use two keyboard layouts International one in English and one in Portuguese 
Brazilian.
After using the Nautilus for a few moments only the special keys work, the 
letter keyboard and numbers for work.

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

Title:
  can't rename files in nautilus

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  sometimes can't rename files with F2 button. It is higlight changing,
  but nothing gonna happen, it is not responding

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 17:48:33 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-10-24 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1385292/+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 1311257] Re: Wifi cannot connect or unstable after suspend 14.04

[william]

I did the Sudo gedit /etc/pm/config.d/config and added the line:
SUSPEND_MODULES="iwilwifi" but used my wireless driver card instead of
the "iwilwifi" to fix this issue. I am running Cinnamon in ubuntu 14.04
though. Hope you resolved your issue by now.

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

Title:
  Wifi cannot connect or unstable after suspend 14.04

Status in gnome-nettool package in Ubuntu:
  Confirmed

Bug description:
  I've tried every solution, such as
  1. editing /etc/pm/config.d to add
   SUSPEND_MODULES="iwlwifi"
  2. editing /etc/modprobe/d/wilwifi.conf to add:
  options iwlwifi bt_coex_active=0
  options iwlwifi 11n_disable=1
  3. running: sudo rmmod iwlwifi && sudo modprobe iwlwifi
  4. stopping, starting, or restarting Network Manager

  Nothing seems to work.  When I had 13.10, my wifi worked without a
  problem, but once I erased it and installed 14.04, wifi will not
  connect after suspend.  Ethernet works fine.  The only way I've found
  to resolve this is to restart my computer.  I have a Lenovo T420.  If
  I try to connect after suspend, it shows the Wifi Networks, tries to
  connect, and  says "Disconnected..." every time.

  ~$ sudo apt-get update; sudo apt-get install hwinfo grep rfkill; sudo lshw -C 
network; rfkill list; sudo iwlist scan | egrep -i 'chan|ssid'; cat 
/etc/network/interfaces; cat /etc/lsb-release; lspci -nnk | grep -iA2 net; 
lsusb; nmcli nm status; sudo lshw -short; uname -a; dmesg | egrep 
'02:00|80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|ireless|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|ound|p54|prism|rror|rtl|rt2|rt3|rt5|rt6|rt7|usb|witch|wl';sudo
 dmidecode|egrep 'anufact|roduct|erial|elease'; iwconfig; cat /etc/modprobe.d/* 
| egrep 
'80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|p54|prism|rtl|rt2|rt3|rt6|rt7|wmi|witch|wl';
 cat /var/lib/NetworkManager/NetworkManager.state; sudo hwinfo --netcard ; ps 
-aux|egrep 'wpa|icd|etwork'; netstat -rn ; cat /etc/resolv.conf; ls -lia /boot; 
sudo lsmod
  Ign http://dl.google.com stable InRelease
  Hit http://dl.google.com stable Release.gpg
  Hit http://dl.google.com stable Release
  Hit http://repository.spotify.com stable InRelease
  Ign http://us.archive.ubuntu.com trusty InRelease
  Hit http://dl.google.com stable/main amd64 Packages
  Hit http://dl.google.com stable/main i386 Packages
  Ign http://extras.ubuntu.com trusty InRelease
  Hit http://repository.spotify.com stable/non-free amd64 Packages
  Ign http://security.ubuntu.com trusty-security InRelease
  Ign http://us.archive.ubuntu.com trusty-updates InRelease
  Hit http://repository.spotify.com stable/non-free i386 Packages
  Hit http://extras.ubuntu.com trusty Release.gpg
  Hit http://security.ubuntu.com trusty-security Release.gpg
  Ign http://us.archive.ubuntu.com trusty-backports InRelease
  Hit http://extras.ubuntu.com trusty Release
  Ign http://us.archive.ubuntu.com trusty-proposed InRelease
  Hit http://security.ubuntu.com trusty-security Release
  Hit http://extras.ubuntu.com trusty/main Sources
  Ign http://dl.google.com stable/main Translation-en_US
  Hit http://us.archive.ubuntu.com trusty Release.gpg
  Ign http://dl.google.com stable/main Translation-en
  Hit http://security.ubuntu.com trusty-security/main Sources
  Hit http://extras.ubuntu.com trusty/main amd64 Packages
  Hit http://us.archive.ubuntu.com trusty-updates Release.gpg
  Hit http://security.ubuntu.com trusty-security/restricted Sources
  Hit http://extras.ubuntu.com trusty/main i386 Packages
  Hit http://us.archive.ubuntu.com trusty-backports Release.gpg
  Hit http://security.ubuntu.com trusty-security/universe Sources
  Hit http://us.archive.ubuntu.com trusty-proposed Release.gpg
  Hit http://security.ubuntu.com trusty-security/multiverse Sources
  Hit http://us.archive.ubuntu.com trusty Release
  Ign http://ppa.launchpad.net trusty InRelease
  Hit http://security.ubuntu.com trusty-security/main amd64 Packages
  Hit http://us.archive.ubuntu.com trusty-updates Release
  Ign http://ppa.launchpad.net trusty InRelease
  Hit http://security.ubuntu.com trusty-security/restricted amd64 Packages
  Ign http://repository.spotify.com stable/non-free Translation-en_US
  Hit http://us.archive.ubuntu.com trusty-backports Release
  Ign http://ppa.launchpad.net trusty InRelease
  Ign http://repository.spotify.com stable/non-free Translation-en
  Hit http://security.ubuntu.com trusty-security/universe amd64 Packages
  Hit http://us.archive.ubuntu.com trusty-proposed Release
  Ign http://ppa.launchpad.net trusty InRelease
  Hit http://security.ubuntu.com trusty-security/multiverse amd64 Packages
  Hit http://us.archive.ubuntu.com trusty/main Sources
  Ign http://ppa.launchpad.net trusty InRelease
  Hit http://security.ubuntu.com trusty-security/main i386 Packages
  Hit http://us.archive.ubuntu.com trusty/restricted Sourc

[Desktop-packages] [Bug 816570] Re: NetworkManager crashed with SIGABRT in raise()

[William]

For  my case network manager crashed shortly after logging in to lightdm
but appeared to recover as I am connected ok via wifi.

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

Title:
  NetworkManager crashed with SIGABRT in raise()

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Crashed at boot

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: network-manager 0.8.9997+git.20110721t045648.36db194-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-7.8-server 3.0.0
  Uname: Linux 3.0.0-7-server x86_64
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  CrashCounter: 1
  Date: Tue Jul 26 20:06:26 2011
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: NetworkManager
  ProcEnviron: PATH=(custom, no user)
  RfKill:

  Signal: 6
  SourcePackage: network-manager
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   nm_manager_get ()
  Title: NetworkManager crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to oneiric on 2011-07-26 (0 days ago)
  UserGroups:

  modified.conffile..etc.NetworkManager.NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=true
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2011-07-12T21:36:27.879352

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/816570/+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 943801] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_a()

[William]

Hasn't occurred again and the other bug mentioned (943800) appears to
have been fixed by subsequent updates.

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

Title:
  nautilus crashed with SIGSEGV in g_type_check_instance_is_a()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Happenned at the same time as bug 943800. (Not sure which one occurred
  first).

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.3.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.93-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Mar  1 18:06:21 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: org.gnome.nautilus.window-state geometry '1275x761+242+109'
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f2e7c8f0740 :   
testb  $0x4,0x16(%rdi)
   PC (0x7f2e7c8f0740) ok
   source "$0x4" ok
   destination "0x16(%rdi)" (0x756e656d2d6b747a) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gdk_window_get_screen () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_device_get_position () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_menu_popup_for_device () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to precise on 2012-02-21 (8 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/943801/+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 976751] Re: Graphical bug, Nautilus right click menu, rename option greyed out

[William]

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

I get this too. Cosmetic only as the greyed out menu entires still
appear to work. I see the issue on rename, paste, paste into folder on
the context menus

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

Title:
  Graphical bug, Nautilus right click menu, rename option greyed out

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Graphical bug, Nautilus right click menu, rename option greyed out and
  when passing over it becomes normal again when trying to rename a jpg
  file or Download folder rename option is greyed out too for no reason.

  In Home folder it doesn't do this.

  See attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sun Apr  8 14:31:33 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+189'
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to precise on 2012-04-01 (6 days ago)

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

[William]

(In reply to V Stuart Foote from comment #40)
> (In reply to gulpen from comment #39)
> 
> > Please give this issue some love!
> 
> We have.
> 
> Two options for working with wide columns or tall rows. Or with undersized
> displays.
> 
> One would be to adjust the sheet scroll from default spreadsheet centric
> "scroll by cell edge" to a "scroll by screen pixel" and requiring new
> implementation.
> 
> The other option was implemented to expose the content of oversize cells to
> edit engine and UI control via an expandable input window on the FormulaBar
> (View ->  Formula Bar) where you will find a "Expand Formula Bar" and
> "Collapse Formula Bar" toggle triangle.
> 
> The collapsed formula bar is one character row in height. The expanded
> formula bar input window can be dragged as tall as 25 lines. Default is 6
> lines, but the UI value is recorded into the spreadsheet on save, so it
> keeps it handy.  For really large cell content (an actual sc formula or text
> strings), the input window has a vertical scroll to work with the entire
> cell (up to 64,000 characters IANM).
> 
> Pixel level scrolling a sheet would be nice to implement, but you already
> are able to work with cells larger than the display or the app window using
> the Formula Bar's input window, without having to zoom the sheet out.

Where do I go in the github to assist with creating a scroll by pixel
implementation?

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+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 1606238] Re: gnome-software won't open

[william]

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => william (teoh04)

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

Title:
  gnome-software won't open

Status in GNOME Software:
  New
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I upgrade the system from Ubuntu 14.04 to 16.04 some time ago.
  At beginning, gnome-software refused to open and I had to remove old ubuntu 
software and "--reinstall" the gnome-software.
  Everything was fine, except for many sorts of packages it can't install so I 
installed synaptic.

  Some days ago, gnome software went on a strike but claimed nothing !
  I can open a terminal and call gnome-software : nothing 
  The launcher turns around in the dock.

  Any Idea ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 25 15:28:05 2016
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1606238/+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 12608] Re: 'keep aligned' does not work right

[William]

still not working

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

Title:
  'keep aligned' does not work right

Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  How it does work:
  If I add some icons they are not realigned automaticly, instead I have to
  deselect 'keep aligned' in the context menu (of the desktop) and then 
reselect it.
  how it should work:
  If anything happens with the icons on the desktop realign them to fit into 
the grid.

  Seems to me like there's just the part missing where the desktop calls the
  realign function if an icon is moved/created.

  http://bugzilla.gnome.org/show_bug.cgi?id=129937

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/12608/+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 1885130] [NEW] Please add a way to show only open-source apps

[William Dietrich]

Public bug reported:

Please add a setting in the store app to show only open-source apps,
hiding proprietary apps.  Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-software 3.36.0-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 25 15:07:51 2020
InstallationDate: Installed on 2020-04-29 (57 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.36.0-0ubuntu3
 gnome-software-plugin-snap3.36.0-0ubuntu3
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-software (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 gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1885130

Title:
  Please add a way to show only open-source apps

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Please add a setting in the store app to show only open-source apps,
  hiding proprietary apps.  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 25 15:07:51 2020
  InstallationDate: Installed on 2020-04-29 (57 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.36.0-0ubuntu3
   gnome-software-plugin-snap3.36.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1885130/+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 1885130] Re: Please add a way to show only open-source apps

[William Dietrich]

Okay, filed https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1021

Would be nice if ubuntu-bug sent me there directly.  I'm getting tired
of having to file a lot of bug reports twice.  Sometimes downstream says
go to upstream, sometimes upstream says go to downstream.  The app
displays as Ubuntu Software, but its CLI / package name is gnome-
software.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1021
   https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1021

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

Title:
  Please add a way to show only open-source apps

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Please add a setting in the store app to show only open-source apps,
  hiding proprietary apps.  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 25 15:07:51 2020
  InstallationDate: Installed on 2020-04-29 (57 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.36.0-0ubuntu3
   gnome-software-plugin-snap3.36.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1885130/+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 1889447] [NEW] Progress dialog looks frozen for multi-file 7z archives

[William Dietrich]

Public bug reported:

Suppose you have a four-file archive with files a.7z.001 a.7z.002
a.7z.003 a.7z.004 containing 500 files.  While extracting from it, the
progress dialog will show filename "a.7z.001" and "500 files remaining"
and the progress-bar will stay near the left end, for the whole time,
until extracting finishes.

If it's not possible to display progress (maybe file-roller is launching
7zip in the background and there's no feedback mechanism ?), the dialog
should say so.  Give what information it has (total number of files that
will be extracted, maybe), say progress can not be monitored, and don't
give the appearance of a frozen extraction process.

I don't know if the same happens for other file types.  Same should
apply to them.

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: file-roller 3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 29 18:49:48 2020
InstallationDate: Installed on 2020-04-29 (91 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: file-roller
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: file-roller (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 file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1889447

Title:
  Progress dialog looks frozen for multi-file 7z archives

Status in file-roller package in Ubuntu:
  New

Bug description:
  Suppose you have a four-file archive with files a.7z.001 a.7z.002
  a.7z.003 a.7z.004 containing 500 files.  While extracting from it, the
  progress dialog will show filename "a.7z.001" and "500 files
  remaining" and the progress-bar will stay near the left end, for the
  whole time, until extracting finishes.

  If it's not possible to display progress (maybe file-roller is
  launching 7zip in the background and there's no feedback mechanism ?),
  the dialog should say so.  Give what information it has (total number
  of files that will be extracted, maybe), say progress can not be
  monitored, and don't give the appearance of a frozen extraction
  process.

  I don't know if the same happens for other file types.  Same should
  apply to them.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: file-roller 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 18:49:48 2020
  InstallationDate: Installed on 2020-04-29 (91 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1889447/+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 1889447] Re: Progress dialog looks frozen for multi-file 7z archives

[William Dietrich]

Maybe use these steps to create the archives, then double-click on the
first resulting archive file (tmp1.7z.001) and do an extract.

mkdir tmp1
cd tmp1

for f in a b c d e f g h i j
do
for g in a b c d e f g h i j
do
for h in a b c d e f g h i j
do
dd if=/bin/ls of="$f$g$h" count=200
done
done
done

cd ..

7za a -v10m -mx=0 tmp1.7z tmp1/*

mv tmp1 tmp2

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

Title:
  Progress dialog looks frozen for multi-file 7z archives

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Suppose you have a four-file archive with files a.7z.001 a.7z.002
  a.7z.003 a.7z.004 containing 500 files.  While extracting from it, the
  progress dialog will show filename "a.7z.001" and "500 files
  remaining" and the progress-bar will stay near the left end, for the
  whole time, until extracting finishes.

  If it's not possible to display progress (maybe file-roller is
  launching 7zip in the background and there's no feedback mechanism ?),
  the dialog should say so.  Give what information it has (total number
  of files that will be extracted, maybe), say progress can not be
  monitored, and don't give the appearance of a frozen extraction
  process.

  I don't know if the same happens for other file types.  Same should
  apply to them.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: file-roller 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 18:49:48 2020
  InstallationDate: Installed on 2020-04-29 (91 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1889447/+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 1761216] Re: Backup fails if backup destination is not mounted

[William Ritchie]

Yes, it is listed in fstab and yes, I entered the path as a local 
storage device.

All drives are SSD's connected to the computer's internal SSD ports and 
seen as local. The server is running XIGMANAS with SMB shares for each 
of the SSD's. I am not running SAMBA server.

The local OS is Unbuntu 20.04 where the backup app is running and will 
not work if the backup drive partition is not mounted first. I can get 
to it by using a combination of IP address and share name, i.e. 
"smb:192.168.15.1/Backup Drive".

Hope this helps.

On 8/1/20 10:57 AM, Michael Terry wrote:
> How is this other drive configured? Is it an entry in fstab? And you
> were entering its path as a Local Folder storage location?
>
> If so, we didn't previously do anything special about mounting fstab
> entries for you. But I just added some code to try that.
>
> Could you give a beta build a try and see if it works for you?
> `snap install deja-dup --classic --edge`
>
> ** Changed in: deja-dup
> Status: Triaged => Incomplete
>

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

Title:
  Backup fails if backup destination is not mounted

Status in Déjà Dup:
  Incomplete
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I have set my backup destination to a separate drive in the machine,
  but not at the default location.

  When the backup runs, it fails stating permission denied, as the
  destination drive is not mounted.

  When I enter the proper destination in the backup at the "storage
  location", the drive then mounts and is present on the desktop. Then
  the backup will run successfully.

  I then "unmount" the drive using the menu on the drive icon, and the
  mounted drive disappears from the desktop. I don't need a bunch of
  drives listed or shown on my desktop, as it detracts from the beauty
  of the screen.

  If I mount the drive before running the backup, it will succeed.

  My point with this is that I am not going to mount the drive every
  time I run backup, and when mounted, I don't need it listed or shown
  on my desktop.

  In unity, the drives appeared in the launcher or dock, and there was
  an option to "remove from launcher", which still left the drive
  mounted, but off the desktop and launcher. This was a nice way to fix
  this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1761216/+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 1761216] Re: Backup fails if backup destination is not mounted

[William Ritchie]

Yes, since 20.04, I have not had the problem, but I thought it was due 
to using a linux server and smb  which solved the problem.

The original problem was localized to my desktop machine and a local 
drive, which would fail after bootup because the dedicated backup 
drrive/partition was not mounted at bootup. Only after mounting the 
drive/partition would the backup run. This prevented the automated 
backup that should run shortly after the system booted up. To be clear, 
the backup partition and deja-dup were being run locally on a client 
machine. Since 20.04, I built a xigmanas server and moved the backup 
destination off the local machine to the server and started using smb to 
access the backup partition. This saved space on the local machine and 
further protected the backups as they are now stored on a remote server.

Thanks for the reply, response and fix.

On 8/2/20 4:13 PM, Michael Terry wrote:
> OK, then yah, I suspect the change I recently made should fix this:
> deja-dup now checks fstab and mounts the target location before a backup
> starts.
>
> You should be able to test it by installing the latest edge snap:
> snap install deja-dup --classic --edge
>

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

Title:
  Backup fails if backup destination is not mounted

Status in Déjà Dup:
  Incomplete
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I have set my backup destination to a separate drive in the machine,
  but not at the default location.

  When the backup runs, it fails stating permission denied, as the
  destination drive is not mounted.

  When I enter the proper destination in the backup at the "storage
  location", the drive then mounts and is present on the desktop. Then
  the backup will run successfully.

  I then "unmount" the drive using the menu on the drive icon, and the
  mounted drive disappears from the desktop. I don't need a bunch of
  drives listed or shown on my desktop, as it detracts from the beauty
  of the screen.

  If I mount the drive before running the backup, it will succeed.

  My point with this is that I am not going to mount the drive every
  time I run backup, and when mounted, I don't need it listed or shown
  on my desktop.

  In unity, the drives appeared in the launcher or dock, and there was
  an option to "remove from launcher", which still left the drive
  mounted, but off the desktop and launcher. This was a nice way to fix
  this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1761216/+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 1893119] [NEW] Restart-required dialog gives no feedback

[William Dietrich]

Public bug reported:

I uninstall something that affects Nautilus, such as the MEGA sync
package.  I get a dialog that says "Nautilus Restart Required" (see
attached screenshot).  I click the "Restart Nautilus" button.  I get no
feedback that anything happened.  I sit there wondering if it worked.  I
click the button a few more times.  Eventually I go looking at other
windows and find that yes, clicking that button makes any open Nautilus
windows close, so I think a restart actually does happen.  But the
dialog gives me no feedback, no "restarted" message or anything.  It
should do so.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55
Uname: Linux 5.4.0-44-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 26 20:17:34 2020
InstallationDate: Installed on 2020-04-29 (119 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

** Attachment added: "screenshot of dialog"
   
https://bugs.launchpad.net/bugs/1893119/+attachment/5404892/+files/Screenshot%20from%202020-08-26%2020-16-17.png

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

Title:
  Restart-required dialog gives no feedback

Status in nautilus package in Ubuntu:
  New

Bug description:
  I uninstall something that affects Nautilus, such as the MEGA sync
  package.  I get a dialog that says "Nautilus Restart Required" (see
  attached screenshot).  I click the "Restart Nautilus" button.  I get
  no feedback that anything happened.  I sit there wondering if it
  worked.  I click the button a few more times.  Eventually I go looking
  at other windows and find that yes, clicking that button makes any
  open Nautilus windows close, so I think a restart actually does
  happen.  But the dialog gives me no feedback, no "restarted" message
  or anything.  It should do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55
  Uname: Linux 5.4.0-44-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 26 20:17:34 2020
  InstallationDate: Installed on 2020-04-29 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1893119/+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 1893311] [NEW] Add libcurl4-openssl-dev build-dep for lumix camlib

[William Wilhelm]

Public bug reported:

The lumix camlib is in a somewhat usable state 
(https://github.com/gphoto/libgphoto2/issues/409) and I have been successfully 
using it for a few months.
It would be good to add the libcurl4-openssl-dev to Build-Depends to enable 
building the lumix camlib.

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

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

Title:
  Add libcurl4-openssl-dev build-dep for lumix camlib

Status in libgphoto2 package in Ubuntu:
  New

Bug description:
  The lumix camlib is in a somewhat usable state 
(https://github.com/gphoto/libgphoto2/issues/409) and I have been successfully 
using it for a few months.
  It would be good to add the libcurl4-openssl-dev to Build-Depends to enable 
building the lumix camlib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1893311/+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 1895421] [NEW] package libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1 failed to install/upgrade: unable to stat './usr/share/libreoffice/help/es' (which I was about to install):

[William Plummer]

Public bug reported:

Hello, trying to install over outdated w7

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.445.1
Date: Sat Sep 12 22:21:20 2020
ErrorMessage: unable to stat './usr/share/libreoffice/help/es' (which I was 
about to install): Input/output error
LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: libreoffice
Title: package libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1 failed to 
install/upgrade: unable to stat './usr/share/libreoffice/help/es' (which I was 
about to install): Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libreoffice (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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1895421

Title:
  package libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1 failed to
  install/upgrade: unable to stat './usr/share/libreoffice/help/es'
  (which I was about to install): Input/output error

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hello, trying to install over outdated w7

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.445.1
  Date: Sat Sep 12 22:21:20 2020
  ErrorMessage: unable to stat './usr/share/libreoffice/help/es' (which I was 
about to install): Input/output error
  LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libreoffice
  Title: package libreoffice-help-es 1:6.4.4-0ubuntu0.20.04.1 failed to 
install/upgrade: unable to stat './usr/share/libreoffice/help/es' (which I was 
about to install): Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1895421/+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 1819005] Re: Want To Pass JN0-220 Juniper Exam Immediately?

[William Grant]

** Package changed: gvfs (Ubuntu) => null-and-void

** Information type changed from Public to Private

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

Title:
  Want To Pass JN0-220 Juniper Exam Immediately?

Status in NULL Project:
  Invalid

Bug description:
  Buy Our Effective Juniper JN0-220 Exam Dumps

  Dumpsprovider.com provides Juniper JN0-220 dumps which are prepared
  beautifully in detail and whole course is included in it. The
  presentation is great. All technical details are explained in easy way
  with the help of demos. Clients feel like it’s a one to one session
  and not an online distant class because of high quality and well
  explained content. Juniper Networks Automation and DevOps Associate
  JN0-220 Braindumps are full of relevant information and guidance which
  is enough for success in first attempt. It is a very important factor,
  that one must pass the exam in first try. Juniper JN0-220 Exam Dumps
  will save your time and money and help you succeed in your career.

  Quick Tips To Pass - Juniper JN0-220 Exam Questions

  Juniper JN0-220 Question Answers are prepared by a very skillful and
  competent IT team at Dumpsprovider.com. A large no. of practice tests
  is provided for the sake of rehearsal and improvement. The right
  solution is also provided along with the tests so that clients can
  check their results and improve their skills before actual exam.
  Juniper JN0-220 Dumps PDF is an easily manageable document. It is a
  very user-friendly guide. The best thing is extra software
  installation is not needed in order to run this. It is compatible to
  mobiles, tablets and laptops. It can be used in printed form also.

  Download Full Exam In PDF

  https://www.dumpsprovider.com/Juniper/JN0-220-exam-dumps

  Pass Juniper JN0-220 Exam Easily With 100% Success Guaranteed
  The price of our product is also very reasonable. It is not at all heavy on 
pocket. Furthermore, we also provide money back guarantee. If due to any 
misfortune, a client fails in the Juniper Automation and DevOps Certification 
exam, he or she can claim money back from us. Please read our refund policy in 
detail before purchasing the study material in order to avoid any ambiguity or 
complexity. Free demo is also another perk by us. Have an overview of our 
product before buying the product. Once you purchase the product, updates will 
be provided absolutely free of cost up till three months.

  Try Our Best Juniper JN0-220 Exam Actual Questions

  Our customer support team is very courteous, proficient and well
  qualified. They never hesitate to help the customers. Feel free to
  contact them whenever you have any query related to content or any
  system related issue, you will be entertained immediately. Our team is
  available 24/7 and gives a prompt response.

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1819005/+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 1809685] Re: The evince application often freezes

[William Smith]

I also see this happen quite often. 
The User Manual link posted here will trigger it when you open the link with 
Document Viewer.
https://www.star-cooperation.com/de/kompetenzen/elektronik/produkte/vernetzungstechnik/hardware/vernetzungszubehoer/flexmedia-100base-t1/

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

Title:
  The evince application often freezes

Status in evince package in Ubuntu:
  Expired

Bug description:
  Hi!
  The evince application (pdf document viewer) often freezes. 
  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 25 07:12:13 2018
  InstallationDate: Installed on 2018-05-06 (232 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1809685/+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 1723117] Re: Desktop icons goes under the Dock, if the Dock is set to auto-hide.

[William Ranvaud]

Still happening on 20.04 LTS.

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

Title:
  Desktop icons goes under the Dock, if the Dock is set to auto-hide.

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  This bug is found in Artful.

  Desktop icons goes under the Dock, if the Dock is set to auto-hide.

  Either the Dock should auto-hide on the Desktop as well, or the
  Desktop Icons should leave a margin with the same size of the Dock.

  This happen both horizontal and vertical Dock positions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1723117/+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 1879144] [NEW] Volume output settings reset on analog surround 4.0

[William CHan]

Public bug reported:

It seems to be a pulseaudio issue but unsure if it is a settings error.

Version: Ubuntu 20.04 LTS / 20.04
Computer Model: HP Envy x360 13 with AMD Ryzen 3500U
PulseAudio version: 1:13.99.1-1ubuntu3.2

Problem Description:
When manually reduce volume, Balance and Fade level resets when such reduction 
reaches 0 audio output.

This is not the case when I manually mute the audio output (or with a
mute switch)

Intended Outcome:
There should not be any reset at all.

Other information:
It seems to be a problem with pulseaudio. However, I cannot confirm if it is a 
bug from the pulseaudio side or the Ubuntu settings side.

Intended outcome: It should work the same: turning the volume to 0
should not reset the fade settings nor the balance settings.

Check the screencast below for what is going on (youtube link)
(0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08

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

** Summary changed:

- Volume output reset settings reset on surround 4.0 
+ Volume output reset settings reset on pulseaudio surround 4.0

** Summary changed:

- Volume output reset settings reset on pulseaudio surround 4.0
+ Volume output settings reset on pulseaudio surround 4.0

** Summary changed:

- Volume output settings reset on pulseaudio surround 4.0
+ Volume output settings reset on analog surround 4.0

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

Title:
  Volume output settings reset on analog surround 4.0

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  It seems to be a pulseaudio issue but unsure if it is a settings
  error.

  Version: Ubuntu 20.04 LTS / 20.04
  Computer Model: HP Envy x360 13 with AMD Ryzen 3500U
  PulseAudio version: 1:13.99.1-1ubuntu3.2

  Problem Description:
  When manually reduce volume, Balance and Fade level resets when such 
reduction reaches 0 audio output.

  This is not the case when I manually mute the audio output (or with a
  mute switch)

  Intended Outcome:
  There should not be any reset at all.

  Other information:
  It seems to be a problem with pulseaudio. However, I cannot confirm if it is 
a bug from the pulseaudio side or the Ubuntu settings side.

  Intended outcome: It should work the same: turning the volume to 0
  should not reset the fade settings nor the balance settings.

  Check the screencast below for what is going on (youtube link)
  (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+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 1879144] Re: Volume output settings reset on analog surround 4.0

[William Chan]

There is one thing I am not sure: it is an issue of pulseaudio or an
issue of the ubuntu settings. But I will upstream it though.

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

Title:
  Volume output settings reset on analog surround 4.0

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  It seems to be a pulseaudio issue but unsure if it is a settings
  error.

  Version: Ubuntu 20.04 LTS / 20.04
  Computer Model: HP Envy x360 13 with AMD Ryzen 3500U
  PulseAudio version: 1:13.99.1-1ubuntu3.2

  Problem Description:
  When manually reduce volume, Balance and Fade level resets when such 
reduction reaches 0 audio output.

  This is not the case when I manually mute the audio output (or with a
  mute switch)

  Intended Outcome:
  There should not be any reset at all.

  Other information:
  It seems to be a problem with pulseaudio. However, I cannot confirm if it is 
a bug from the pulseaudio side or the Ubuntu settings side.

  Intended outcome: It should work the same: turning the volume to 0
  should not reset the fade settings nor the balance settings.

  Check the screencast below for what is going on (youtube link)
  (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+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 1879144] Re: Custom volume output configuration reset

[William Chan]

It seems that it is not a single problem that happens on analog surround
4.0

I tried using Bluetooth audio, then set custom balance. The same thing
resets when the volume gradually turns down and reached 0 volume. Didn't
reset when I manually mute it with a switch or through a button.

** Summary changed:

- Volume output settings reset on analog surround 4.0
+ Custom volume output configuration reset

** Summary changed:

- Custom volume output configuration reset
+ Audio custom output settings reset

** Summary changed:

- Audio custom output settings reset
+ Audio custom output settings unintendly reset

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

Title:
  Audio custom output settings unintendly reset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  It seems to be a pulseaudio issue but unsure if it is a settings
  error.

  Version: Ubuntu 20.04 LTS / 20.04
  Computer Model: HP Envy x360 13 with AMD Ryzen 3500U
  PulseAudio version: 1:13.99.1-1ubuntu3.2

  Problem Description:
  When manually reduce volume, Balance and Fade level resets when such 
reduction reaches 0 audio output.

  This is not the case when I manually mute the audio output (or with a
  mute switch)

  Intended Outcome:
  There should not be any reset at all.

  Other information:
  It seems to be a problem with pulseaudio. However, I cannot confirm if it is 
a bug from the pulseaudio side or the Ubuntu settings side.

  Intended outcome: It should work the same: turning the volume to 0
  should not reset the fade settings nor the balance settings.

  Check the screencast below for what is going on (youtube link)
  (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+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 1879144] Re: Balance reset when sound reachs 0

[William Chan]

** Summary changed:

- Balance resetted when sound reachs 0
+ Balance reset when sound reachs 0

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

Title:
  Balance reset when sound reachs 0

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  It seems to be a pulseaudio issue but unsure if it is a settings
  error.

  Version: Ubuntu 20.04 LTS / 20.04
  Computer Model: HP Envy x360 13 with AMD Ryzen 3500U
  PulseAudio version: 1:13.99.1-1ubuntu3.2

  Problem Description:
  When manually reduce volume, Balance and Fade level resets when such 
reduction reaches 0 audio output.

  This is not the case when I manually mute the audio output (or with a
  mute switch)

  Intended Outcome:
  There should not be any reset at all.

  Other information:
  It seems to be a problem with pulseaudio. However, I cannot confirm if it is 
a bug from the pulseaudio side or the Ubuntu settings side.

  Intended outcome: It should work the same: turning the volume to 0
  should not reset the fade settings nor the balance settings.

  Check the screencast below for what is going on (youtube link)
  (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+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 1857941] [NEW] [HDA-Intel - HDA Intel PCH, playback] Audio playback is choppy when connected to wifi (sounds like turntable skipping), problem goes away when wifi disabled

[William Myers]

Public bug reported:

Turning off PulseAudio timer scheduling does not fix the problem.
Shouldn't be a hardware issue because it was not present in Ubuntu
18.04. I am currently on the latest Ubuntu Studio release.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pulseaudio 1:13.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10
Uname: Linux 5.3.0-24-lowlatency x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  william2221 F jackdbus
 /dev/snd/pcmC2D0c:   william2221 F...m jackdbus
 /dev/snd/pcmC2D0p:   william2221 F...m jackdbus
CurrentDesktop: MATE
Date: Mon Dec 30 18:22:30 2019
InstallationDate: Installed on 2019-11-27 (33 days ago)
InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: USB-Audio - USB Audio CODEC
Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 0TRW8H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd12/24/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TRW8H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.sku: 0665
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2019-12-30T18:20:31.085005

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


** Tags: amd64 apport-bug eoan

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Audio playback is choppy when
  connected to wifi (sounds like turntable skipping), problem goes away
  when wifi disabled

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Turning off PulseAudio timer scheduling does not fix the problem.
  Shouldn't be a hardware issue because it was not present in Ubuntu
  18.04. I am currently on the latest Ubuntu Studio release.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10
  Uname: Linux 5.3.0-24-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  william2221 F jackdbus
   /dev/snd/pcmC2D0c:   william2221 F...m jackdbus
   /dev/snd/pcmC2D0p:   william2221 F...m jackdbus
  CurrentDesktop: MATE
  Date: Mon Dec 30 18:22:30 2019
  InstallationDate: Installed on 2019-11-27 (33 days ago)
  InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: USB-Audio - USB Audio CODEC
  Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0TRW8H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd12/24/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TRW8H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.sku: 0665
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2019-12-30T18:20:31.085005

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857941/+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 1857941] Re: Ubuntu Studio audio playback is choppy when connected to wifi (sounds like turntable skipping), problem goes away when wifi disabled

[William Myers]

I think you're right that it's probably the kernel. I'm having trouble
changing that, but when I get it done I'll update.

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

Title:
  Ubuntu Studio audio playback is choppy when connected to wifi (sounds
  like turntable skipping), problem goes away when wifi disabled

Status in jackd2 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Turning off PulseAudio timer scheduling does not fix the problem.
  Shouldn't be a hardware issue because it was not present in Ubuntu
  18.04. I am currently on the latest Ubuntu Studio release.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10
  Uname: Linux 5.3.0-24-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  william2221 F jackdbus
   /dev/snd/pcmC2D0c:   william2221 F...m jackdbus
   /dev/snd/pcmC2D0p:   william2221 F...m jackdbus
  CurrentDesktop: MATE
  Date: Mon Dec 30 18:22:30 2019
  InstallationDate: Installed on 2019-11-27 (33 days ago)
  InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: USB-Audio - USB Audio CODEC
  Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0TRW8H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd12/24/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TRW8H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.sku: 0665
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2019-12-30T18:20:31.085005

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1857941/+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 1857941] Re: Ubuntu Studio audio playback is choppy when connected to wifi (sounds like turntable skipping), problem goes away when wifi disabled

[William Myers]

Also, no I'm not using bluetooth. The sound issues happen whether I'm
using an audio interface or the onboard sound.

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

Title:
  Ubuntu Studio audio playback is choppy when connected to wifi (sounds
  like turntable skipping), problem goes away when wifi disabled

Status in jackd2 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Turning off PulseAudio timer scheduling does not fix the problem.
  Shouldn't be a hardware issue because it was not present in Ubuntu
  18.04. I am currently on the latest Ubuntu Studio release.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10
  Uname: Linux 5.3.0-24-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  william2221 F jackdbus
   /dev/snd/pcmC2D0c:   william2221 F...m jackdbus
   /dev/snd/pcmC2D0p:   william2221 F...m jackdbus
  CurrentDesktop: MATE
  Date: Mon Dec 30 18:22:30 2019
  InstallationDate: Installed on 2019-11-27 (33 days ago)
  InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: USB-Audio - USB Audio CODEC
  Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0TRW8H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd12/24/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TRW8H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.sku: 0665
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2019-12-30T18:20:31.085005

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1857941/+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 1584402] Re: TEch&Help norton phone number 1-800-769-2805 norton technical support p.h.o.n.e n.u.m.b.e.r

[William Grant]

** Package changed: ibus (Ubuntu) => null-and-void

** Information type changed from Public to Private

** Changed in: null-and-void
   Status: Confirmed => Invalid

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

Title:
  TEch&Help norton phone number 1-800-769-2805 norton technical support
  p.h.o.n.e n.u.m.b.e.r

Status in NULL Project:
  Invalid

Bug description:
  Norton phone number 1855-977-4636
  Norton antivirus phone number1855-977-4636
  Norton security phone number1855-977-4636
  Norton 36O phone number1855-977-4636
  Norton support phone number1855-977-4636
  Norton symantec phone number1855-977-4636
  Norton customer service phone number
  Norton technical support phone number
  Norton tech support phone number
  Norton help phone number
  Norton phone number customer service
  Norton antivirus support phone number
  Norton internet security phone number
  Norton antivirus customer service phone number
  Norton 36O support phone number
  phone number for Norton
  Norton contact phone number
  Norton customer support phone number
  Norton 8OO phone number
  Norton phone number usa
  phone number for Norton antivirus
  Norton by symantec phone number
  phone number for Norton security
  Norton security phone number customer service
  Norton number
  Norton phone number get human
  Norton contact number
  Norton support number
  Norton phone number for support
  Norton phone number billing
  Norton virus phone number
  Norton phone number toll free
  Norton antivirus contact phone number
  Norton antivirus tech support phone number
  Norton antivirus technical support phone number
  Norton sales phone number
  Norton renewal phone number
  Norton phone support number
  Norton antivirus customer support phone number
  Norton telephone number
  Norton billing phone number
  Norton phone number customer support
  Norton antivirus phone support number
  Norton 36O customer service phone number
  contact Norton phone number
  Norton antivirus phone number support
  Norton antivirus phone number customer service
  Norton customer service number
  Norton 36O number
  phone number for Norton support
  ww Norton phone number
  Norton antivirus phone number tech support
  Norton customer service phone number usa
  Norton internet security customer service phone number
  phone number for Norton antivirus customer service
  Norton 36O technical support phone number
  Norton phone number support
  Norton anti virus phone number
  Norton customer phone number
  Norton 8OO number
  Norton security support phone number
  phone number for Norton internet security
  Norton help desk phone number
  Norton security customer service phone number
  Norton tech support number
  Norton 36O contact phone number
  phone number for Norton antivirus support
  Norton cancellation phone number
  Norton antivirus contact number
  Norton service phone number
  Norton com support phone number
  Norton toll free number
  Norton 18OO phone number
  Norton antivirus phone number customer service us
  phone number for Norton 36O
  Norton 36O phone support number
  Norton internet security support phone number
  Norton antivirus number
  Norton security help phone number
  Norton 36O tech support phone number
  Norton customer service number us
  Norton customer care phone number
  Norton.com phone number
  Norton security phone contact number
  Norton 36O phone number customer service
  phone number for Norton customer support
  contact Norton antivirus customer service phone number
  Norton security contact number
  customer service phone number for Norton security
  Norton antivirus help phone number
  phone number for Norton customer service
  Norton 18OO number
  Norton 36O customer support phone number
  Norton technical support number
  phone number Norton antivirus
  Norton customer support number
  Norton help number
  Norton help support phone number
  Norton antivirus support number
  Norton antivirus customer service number
  Norton helpline phone number
  Norton symantec customer service phone number
  Norton 36O help phone number
  Norton 36O contact number
  Norton customer service telephone number
  phone number Norton security
  phone number Norton internet security
  Norton security contact phone number
  Norton antivirus telephone number
  Norton customer service toll free number
  what is the phone number for Norton customer service
  Norton internet security tech support phone number
  Norton antivirus help desk phone number
  phone number Norton antivirus customer service
  Norton security number
  Norton internet security contact phone number
  Norton security telephone number
  Norton securities phone number
  Norton security technical support phone number
  Norton internet security help phone number
  Norton internet security technical support phone number
  Norton 36O help and support pho

[Desktop-packages] [Bug 1797744] [NEW] Mouse scrolling no longer moves between tabs in gnome-terminal 2.30

[William Grant]

Public bug reported:

In gnome-terminal 2.28 and earlier, scrolling with the mouse cursor over
the tab bar switched between tabs. This seems to be broken in cosmic's
2.30.

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

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

Title:
  Mouse scrolling no longer moves between tabs in gnome-terminal 2.30

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  In gnome-terminal 2.28 and earlier, scrolling with the mouse cursor
  over the tab bar switched between tabs. This seems to be broken in
  cosmic's 2.30.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1797744/+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 1685035] Re: GDM login doesn't scale on Hi-DPI display

[William Maddler]

I think this is still happening on 17.10 with 3.26.1-3ubuntu1.
I'm on a Lenovo Thinkpad T470p laptop with Intel video card.

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

Title:
  GDM login doesn't scale on Hi-DPI display

Status in GNOME Settings Daemon:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  GDM's login screen was being start with no gnome-settings-daemons plugins. In 
particular, this broke Hi-DPI support in the login screen

  Test Case
  -
  - Install the update on a computer running Ubuntu GNOME 17.04 with a Hi-DPI 
display (ideally one that worked well with Ubuntu GNOME 16.10).
  - Restart your computer.
  - The login screen should automatically show at the right scale.

  Regression Potential
  
  See the other 3.24.2 bugs but this commit is a simple typo fix.

  Original Bug Report
  ---
  Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800, login 
screen is too tiny to read. GDM login screen doesn't reflect changes to 
org.gnome.desktop.interface scaling-factor or text-scaling-factor.

  Eg:
  xhost +SI:localuser:gdm
  sudo su gdm -s /bin/bash
  gsettings set org.gnome.desktop.interface scaling-factor 2
  gsettings set org.gnome.desktop.interface text-scaling-factor 2.0

  no effect.

  Creating a gdm user under /etc/dconf and running dconf update has no
  effect either. Scaling-factor seems to scale the mouse cursor, but
  nothing else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1685035/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[William Richards]

I wonder how many people's DNS leaked over the year this bug hasn't been
addressed. Oh well..it's just your users' security. Canonical is a joke.
Please stop endangering your users with your incompetence.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 2036373] [NEW] package cups-bsd 2.3.1-9ubuntu1.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

[William Ryan]

Public bug reported:

I am attempting to install Zoom onto my laptop. Any assistance would be
greatly appreciated. Thank you!

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups-bsd 2.3.1-9ubuntu1.5
ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116
Uname: Linux 5.15.0-83-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CupsErrorLog:
 
Date: Sun Sep 17 20:37:58 2023
DpkgHistoryLog:
 Start-Date: 2023-09-17  20:37:00
 Requested-By: ned_land (1000)
 Install: libgcc1:amd64 (1:10.5.0-1ubuntu1~20.04)
 Upgrade: libwebp6:amd64 (0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), 
libcups2:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), cups-server-common:amd64 
(2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), libwebpdemux2:amd64 
(0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), cups-ppdc:amd64 
(2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), firefox-locale-en:amd64 
(117.0+build2-0ubuntu0.20.04.1, 117.0.1+build2-0ubuntu0.20.04.1), 
libflac8:amd64 (1.3.3-1ubuntu0.1, 1.3.3-1ubuntu0.2), cups-daemon:amd64 
(2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), cups:amd64 (2.3.1-9ubuntu1.4, 
2.3.1-9ubuntu1.5), cups-client:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5)
DuplicateSignature:
 package:cups-bsd:2.3.1-9ubuntu1.5
 Setting up cups (2.3.1-9ubuntu1.5) ...
 Updating PPD files for cups ...
 dpkg: error processing package cups-bsd (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2020-09-07 (1105 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lpstat: device for HP_OfficeJet_Pro_6970_BE52B8_: 
implicitclass://HP_OfficeJet_Pro_6970_BE52B8_/
MachineType: LENOVO 80XS
Papersize: letter
PpdFiles: HP_OfficeJet_Pro_6970_BE52B8_: HP OfficeJet Pro 6970, driverless, 
cups-filters 1.27.4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=7dbb25c2-5410-4536-83ab-b1e2505c1318 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=7dbb25c2-5410-4536-83ab-b1e2505c1318 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: cups
Title: package cups-bsd 2.3.1-9ubuntu1.5 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2017
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: 5QCN18WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 320-15ABR
dmi.ec.firmware.release: 1.18
dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN18WW:bd07/13/2017:br1.18:efr1.18:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:skuLENOVO_MT_80XS_BU_idea_FM_ideapad320-15ABR:
dmi.product.family: ideapad 320-15ABR
dmi.product.name: 80XS
dmi.product.sku: LENOVO_MT_80XS_BU_idea_FM_ideapad 320-15ABR
dmi.product.version: Lenovo ideapad 320-15ABR
dmi.sys.vendor: LENOVO

** Affects: cups (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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/2036373

Title:
  package cups-bsd 2.3.1-9ubuntu1.5 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in cups package in Ubuntu:
  New

Bug description:
  I am attempting to install Zoom onto my laptop. Any assistance would
  be greatly appreciated. Thank you!

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: cups-bsd 2.3.1-9ubuntu1.5
  ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116
  Uname: Linux 5.15.0-83-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
   
  Date: Sun Sep 17 20:37:58 2023
  DpkgHistoryLog:
   Start-Date: 2023-09-17  20:37:00
   Requested-By: ned_land (1000)
   Install: libgcc1:amd64 (1:10.5.0-1ubuntu1~20.04)
   Upgrade: libwebp6:amd64 (0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), 
libcups2:amd64 (2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), cups-server-common:amd64 
(2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), libwebpdemux2:amd64 
(0.6.1-2ubuntu0.20.04.2, 0.6.1-2ubuntu0.20.04.3), cups-ppdc:amd64 
(2.3.1-9ubuntu1.4, 2.3.1-9ubuntu1.5), firefox-locale-en:amd64 
(117.0+build2-0ubuntu0.20.04.1, 117.0.1+build2-0ubuntu0.20.04.1), 
libflac8:amd64 (1.3.3-1ubuntu0.1, 1.3.3-1ubunt

[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[William Grant]

** Attachment added: "journal from a single-display hang with 
gnome-shell/(lib)mutter 45.0-1ubuntu1, Alder Lake-P, two external displays 
through an MST hub"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702587/+files/journal-redacted.txt

** Attachment removed: "journal from a single-display hang with 
gnome-shell/(lib)mutter 45.0-1ubuntu1, Alder Lake-P, two external displays 
through an MST hub, with MUTTER_DEBUG=kms MUTTER_DEBUG_KMS_THREAD_TYPE=user"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702587/+files/journal-redacted.txt

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
reso

[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[William Grant]

** Attachment added: "journal from a single-display hang with 
gnome-shell/(lib)mutter 45.0-1ubuntu1, Alder Lake-P, two external displays  
through an MST hub, with MUTTER_DEBUG=kms MUTTER_DEBUG_KMS_THREAD_TYPE=user"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702590/+files/journal-redacted.txt.zst

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789da70 i   
reso

[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[William Grant]

Here's another journal from the boot after the one before, with the same
settings as before (I've set MUTTER_DEBUG_TRIPLE_BUFFERING=never but not
yet rebooted).

My primary display should have multiple hangs in the last couple of
minutes here. I unwisely fullscreened a YouTube video in Firefox, and
recovered by replugging my docking station. This repeated a few times,
with a LUKS unlock prompt sometimes stopping it from hanging until I
dismissed the dialog, until I hit Esc to de-fullscreen the video and
replugged one last time. I think my secondary display might also have
hung at some point during this boot, but I forget.

** Attachment added: "a journal from several single-display hangs in one 
session"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702630/+files/journal-redacted.txt.zst

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420

[Desktop-packages] [Bug 2038892] Re: How To Contact +1(202-960-2084) McAfee Customer Service Number?

[William Grant]

** Package changed: cups (Ubuntu) => null-and-void

** Information type changed from Public to Private

** Changed in: null-and-void
   Status: New => Invalid

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

Title:
  How To Contact +1(202-960-2084) McAfee Customer Service Number?

Status in NULL Project:
  Invalid

Bug description:
  o contact McAfee Customer Service Phone Number, you can follow these
  steps:

  Visit the McAfee Website: Start by going to the official McAfee
  website.

  Navigate to Support: Look for a “Support” or “Contact Us” link on the
  website. This is typically found at the top or bottom of the homepage.

  Choose Your Product: Select the McAfee product you need assistance
  with. They offer various security solutions, so make sure to pick the
  right one.

  Access the Help Center: Many common issues can be resolved by
  searching the McAfee Help Center. Try entering your problem or
  question in the search bar.

  Contact Options: If you can’t find a solution in the Help Center, look
  for contact options. This may include phone numbers, live chat, or
  email support. Click on the option that suits you best.

  Provide Information: When contacting McAfee, be prepared to provide
  information like your product key, account details, and a clear
  description of your issue.

  Follow Instructions: Follow the instructions provided by McAfee’s
  customer support team. They may guide you through troubleshooting
  steps or offer a solution tailored to your problem.

  Record Reference Numbers: If you speak to a customer service
  representative or open a support ticket, make sure to record any
  reference numbers or case IDs for future reference.

  Remember that McAfee’s contact options may vary depending on your
  location and the specific product you’re using. Always verify the
  contact details on their official website to ensure you’re reaching
  out to legitimate customer support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/2038892/+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 1960458] [NEW] patch git_socket_dir.patch causing FTBFS in gspell

[William Wilson]

Public bug reported:

With this patch applied gspell is FTBFS with the following errors:

Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus:
Failed to connect to socket debian/home/.cache/at-spi/bus: No such file
or directory

I removed the patch and rebuilt this package in a PPA. When built
against this PPA, gpsell is able to build again.

** Affects: at-spi2-core (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  patch git_socket_dir.patch causing FTBFS in gspell

Status in at-spi2-core package in Ubuntu:
  New

Bug description:
  With this patch applied gspell is FTBFS with the following errors:

  Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus:
  Failed to connect to socket debian/home/.cache/at-spi/bus: No such
  file or directory

  I removed the patch and rebuilt this package in a PPA. When built
  against this PPA, gpsell is able to build again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

[William Maddox]

Inspired by BloodyIron's comments above, I investigated this issue and
was able to develop a patch that solves this problem for my use case:
browsing NAS devices running TrueNAS and OpenMediaVault.  It appears
that the gvfsd-smb-browse process is left in a bad state after
attempting to mount a workgroup, which occurs either when attempting to
open an URL like smb://WORKGROUP/ or during network discovery in gvfsd-
network.  My patch simply disables workgroup discovery/browsing
functionality, leaving *browsing* functionality intact for servers that
are *discovered* via DNS-SD (mDNS). This does not address the issue of
discovering Windows 10 servers that advertise themselves only via WS-
Discovery, but appears to work fine for devices that advertise
themselves using mDNS, allowing those devices to be successfully
browsed.

I note that workgroups are an obsolete concept in a post-NT1 (post-SMB1)
world, so the offending code should eventually just be yanked out, along
with the addition of support for WS-Discovery in Linux.  My patch does
not address the root cause, as whatever is going wrong while attempting
to mount a workgroup should result in a recoverable error.  I traced
gvfsbackendsmbbrowse.c:do_mount() up to the point at which
smbc_opendir() is called without any surprises, whereupon things went
south.  I did not investigate any further, but if I were to do so, I'd
be inclined to take a look for an unreleased lock.

** Patch added: "Disable broken workgroup discovery/browsing"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828107/+attachment/5639041/+files/smb-browse-patch.diff

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828107/+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 2007052] [NEW] package chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned erro

[William Anderson]

Public bug reported:

crash occurred during 18.04 -> 20.04 do-release-upgrade, transition from
dpkg/deb to snap install

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser 109.0.5414.74-0ubuntu0.18.04.14
ProcVersionSignature: Ubuntu 5.4.0-137.154~18.04.1-generic 5.4.218
Uname: Linux 5.4.0-137-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: amd64
DRM.card0-Virtual-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
 modes: preferred 1152x864 1024x768 800x600 640x480
DRM.card0-Virtual-2:
 enabled: disabled
 dpms: On
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-Virtual-3:
 enabled: disabled
 dpms: On
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-Virtual-4:
 enabled: disabled
 dpms: On
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-Virtual-5:
 enabled: disabled
 dpms: On
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-Virtual-6:
 enabled: disabled
 dpms: On
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-Virtual-7:
 enabled: disabled
 dpms: On
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-Virtual-8:
 enabled: disabled
 dpms: On
 status: disconnected
 edid-base64: 
 modes:
Date: Mon Feb 13 01:03:59 2023
Desktop-Session:
 'None'
 'None'
 'None'
Env:
 'None'
 'None'
ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2015-11-04 (2657 days ago)
InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140806.1)
InstalledPlugins:
 
Load-Avg-1min: 0.71
Load-Processes-Running-Percent:   0.3%
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
 
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: VMware, Inc. VMware7,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-137-generic 
root=UUID=152d5d4a-70ca-4be1-a626-b450c2b7965b ro
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
SourcePackage: chromium-browser
Title: package chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2023-02-13 (0 days ago)
dmi.bios.date: 06/25/2021
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW71.00V.18227214.B64.2106252220
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.18227214.B64.2106252220:bd06/25/2021:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware7,1
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
modified.conffile..etc.default.chromium-browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal third-party-packages

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

Title:
  package chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  crash occurred during 18.04 -> 20.04 do-release-upgrade, transition
  from dpkg/deb to snap install

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 109.0.5414.74-0ubuntu0.18.04.14
  ProcVersionSignature: Ubuntu 5.4.0-137.154~18.04.1-generic 5.4.218
  Uname: Linux 5.4.0-137-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  DRM.card0-Virtual-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
   modes: preferred 1152x864 1024x768 800x600 640x480
  DRM.card0-Virtual-2:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-Virtual-3:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-Virtual-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-Virtual-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-Virtual-6:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-Virtual-7:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-Virtual-8:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  Date: Mon Feb 13 01:03:59 2023
  Desktop-Session:
   'None'
   'None'
   'None'
  Env:
   'None'
   'None'
  Erro

[Desktop-packages] [Bug 2008999] Re: User-Agent change breaks sniffing on e.g. meet.google.com

[William Grant]

This is because of https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?h=stable&id=42ed9c6a14ae9631d0a200dff1674e60560a3d28,
which inserted "Ubuntu; " inside the "X11; Linux" part of the User-Agent
that lots of services sniff.

** Package changed: ubuntu => chromium-browser (Ubuntu)

** Tags added: snap

** Tags added: regression-update

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

Title:
  User-Agent change breaks sniffing on e.g. meet.google.com

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Not sure whether this has been already reported:
  ---
  Google Drive is rendered in a weird way, see attached file.
  Google Meet is telling me "Meet doesn't work on your browser"

  What steps will reproduce the problem?
  * Update chromium with `snap refresh chromium` from 110.0.5481.100 to 
110.0.5481.177
  * Open Google Drive/Google Meet

  What happens instead?
  * No proposals for files during search in Google Drive
  * Old-fashioned look & feel (See screenshot)
  * Google Meet is telling me: "Meet doesn't work on your browser"

  uname -a
  Linux frn-xps-15 5.19.0-31-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 20 
15:20:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -rd
  Description:  Ubuntu 22.10
  Release:  22.10

  snap list chromium --all
  Name  Version Rev   Tracking   Publisher   Notes
  chromium  110.0.5481.100  2333  latest/stable  canonical✓  disabled
  chromium  110.0.5481.177  2356  latest/stable  canonical✓  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008999/+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 2009005] Re: snap version 110.0.5481.177 cant open meets and calendar seems broken

[William Grant]

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

** This bug has been marked a duplicate of bug 2008999
   User-Agent change breaks sniffing on e.g. meet.google.com

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

Title:
  snap version 110.0.5481.177 cant open meets and calendar seems broken

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With the latest version of chromium snap 110.0.5481.177 installed
  yesterday I am no longer able to use google meet or view my google
  calendar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2009005/+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 2008999] Re: User-Agent change breaks sniffing on e.g. meet.google.com

[William Grant]

As a workaround, install a User-Agent switcher extension (e.g.
https://chrome.google.com/webstore/detail/user-agent-switcher-
for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg) and set a value closer to the
old one, e.g. "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36"

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

Title:
  User-Agent change breaks sniffing on e.g. meet.google.com

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Not sure whether this has been already reported:
  ---
  Google Drive is rendered in a weird way, see attached file.
  Google Meet is telling me "Meet doesn't work on your browser"

  What steps will reproduce the problem?
  * Update chromium with `snap refresh chromium` from 110.0.5481.100 to 
110.0.5481.177
  * Open Google Drive/Google Meet

  What happens instead?
  * No proposals for files during search in Google Drive
  * Old-fashioned look & feel (See screenshot)
  * Google Meet is telling me: "Meet doesn't work on your browser"

  uname -a
  Linux frn-xps-15 5.19.0-31-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 20 
15:20:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -rd
  Description:  Ubuntu 22.10
  Release:  22.10

  snap list chromium --all
  Name  Version Rev   Tracking   Publisher   Notes
  chromium  110.0.5481.100  2333  latest/stable  canonical✓  disabled
  chromium  110.0.5481.177  2356  latest/stable  canonical✓  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008999/+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 2011722] [NEW] Move oem-config-setup steps into ubuntu-raspi-settings-desktop

[William Wilson]

Public bug reported:

When building images with livecd-rootfs, there is a hook to set up oem-
config for preinstalled raspi desktop images. As we move away from
livecd-rootfs (and the use of hooks in general), this step should be
moved into a package.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Move oem-config-setup steps into ubuntu-raspi-settings-desktop

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  When building images with livecd-rootfs, there is a hook to set up
  oem-config for preinstalled raspi desktop images. As we move away from
  livecd-rootfs (and the use of hooks in general), this step should be
  moved into a package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2011722/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

[William Maddox]

@ BloodyIron It looks like the problem you are experiencing is the same
issue as I have had.  I think the reason that it works after you kill
gvfsd-smb-browse is that your FreeNAS server is advertising itself via
mDNS, and gvfsd will see that.  You don't need SMB1 or WSDD for gvfsd to
discover your NAS.  But it is also looking for a "Windows Network" (i.e.
the Windows "network neighborhood" or workgroup that shows up as a
separate subfolder) using SMB1, and that fails if the server does not
provide SMB1.  Crucially, however, it fails in a way that leaves the
gvfsd-smb-browse process in a bad state where it fails to allow browsing
of the server even though it has been discovered via mDNS.  I encourage
you to take a look at my patch, or to use the PPA at
https://launchpad.net/~wmaddox3rd/+archive/ubuntu/gvfs-smb-sharelist-
patch. It does indeed look like there is a bug here in that attempting
discovery via SMB1 somehow breaks browsing of the server discovered via
mDNS.

See also my remarks here:
https://gitlab.gnome.org/GNOME/gvfs/-/issues/307#note_1632096

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828107/+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 2012738] Re: language support crashes on install missing translations or writing aids

[William Wilson]

** Tags removed: rls-ll-incoming

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

Title:
  language support crashes on install missing translations or writing
  aids

Status in devscripts package in Ubuntu:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Installing missing "translations or writing aids" crashes the gnome-
  language-selector app.

  I have attached a recording (sorry should have had capture cursor on)
  and relevant stack trace from journalctl.

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

[William Dietrich]

I think the whole concept of numeric security "levels" is wrong.
Instead there should be a list of threats:

- physical (address by using LUKS, disabling USB ports, locking screen
after N minutes inactivity, etc)

- bad apps (address by enabling AppArmor or SELinux etc, using Snaps or
Flatpaks, using fewer PPAs, doing updates, etc)

- OS vulns (address by doing updates)

- network attacks (address by enabling firewall on computer, enabling
firewall in router, turning off unused services, blockers in browser,
etc)

- user mistakes (address by not running as root, using immutable OS,
etc)

And I would lump in some partially-security things too:

- data loss due to hardware failure or user error (backups: suggest
TimeShift etc)

- network security/privacy attacks (suggest VPN)

-- 
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 1833010] [NEW] PCI/internal sound card not detected

[William Silverthorne]

Public bug reported:

Linx 1010b Tablet converted from Windows 10 to Ubuntu 18.10.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  william1931 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 16 22:29:12 2019
InstallationDate: Installed on 2019-06-14 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: LINX1010B.R22.03.010
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name
dmi.board.vendor: Type2 - Board Manufacturer
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvrLINX1010B.R22.03.010:bd07/24/2015:svnLINX:pnLINX1010B:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Type1 - Family
dmi.product.name: LINX1010B
dmi.product.sku: Type1 - SKU0
dmi.product.version: Type1 - TBD by OEM
dmi.sys.vendor: LINX

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1833010

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Linx 1010b Tablet converted from Windows 10 to Ubuntu 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  william1931 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 16 22:29:12 2019
  InstallationDate: Installed on 2019-06-14 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: LINX1010B.R22.03.010
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name
  dmi.board.vendor: Type2 - Board Manufacturer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrLINX1010B.R22.03.010:bd07/24/2015:svnLINX:pnLINX1010B:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1 - Family
  dmi.product.name: LINX1010B
  dmi.product.sku: Type1 - SKU0
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: LINX

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833010/+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 1582845] [NEW] User Accounts: cannot change user picture.

[William Ritchie]

Public bug reported:

In "user accounts", click on the picture icon, browse for a picture
(stock) or (user) and size it. Accept it and no change appears in the
"login/logout/shutdown" menu. I did this with "unlock" and "lock".

Reproducible in 16.04 LTS.

I think this is the wrong place for this bug. Sorry, this is my first
time filing one.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-terminal 3.18.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 17 11:24:21 2016
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2016-05-14 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  User Accounts: cannot change user picture.

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  In "user accounts", click on the picture icon, browse for a picture
  (stock) or (user) and size it. Accept it and no change appears in the
  "login/logout/shutdown" menu. I did this with "unlock" and "lock".

  Reproducible in 16.04 LTS.

  I think this is the wrong place for this bug. Sorry, this is my first
  time filing one.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 17 11:24:21 2016
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-05-14 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1582845/+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 1588266] Re: Almost no info about Krita snap in Ubuntu Software

[William Hua]

snapd doesn't seem to be providing an endpoint to get the icon:

{
"result": [
{
"description": "Krita is the free and open source digital painting 
application. Digital painting, creative freedom!",
"developer": "krita",
"download-size": 102592512,
"icon": "",
"id": "r8Shy9i0XE50a3tUlChg3tvjSeLGJ4Za",
"name": "krita",
"resource": "/v2/snaps/krita",
"revision": 1,
"status": "available",
"summary": "Krita: the free digital painting studio",
"type": "app",
"version": "3.0-snap10"
}
],
"sources": [
"store"
],
"status": "OK",
"status-code": 200,
"suggested-currency": "USD",
"type": "sync"
}

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

Title:
  Almost no info about Krita snap in Ubuntu Software

Status in gnome-software package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  Krita 3.0 was released [1] and it was packaged as a snap which is
  available in Ubuntu Software.

  However, when a user looks for "krita" in Ubuntu Software, (s)he will
  find one package without an icon, without screenshots, without user
  reviews... and with a scary "non-free" warning box. See attached
  screenshot.

  Krita has been around for a while and the previous versions were
  available in the repo, so I'm sure there used to be an icon, some user
  reviews and probably some screenshots as well :)

  
  [1] https://krita.org/item/krita-3-0-released/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-software 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_4_0_22_40_generic_7
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun  2 18:00:34 2016
  InstallationDate: Installed on 2016-04-25 (38 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1588266/+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 1768794] Re: Snap branches all show with same name

[William Grant]

The bug has been fixed and the server no longer advertises branches.

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

Title:
  Snap branches all show with same name

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Snaps with multiple branches (e.g. communitheme) all show in GNOME Software 
with the branches having the same name.

  Steps to reproduce:
  1. Search for ”communitheme”
  2. Select ”communitheme” result
  3. Click on the channel selection button
  4. You will see a popup with loong list of channels

  Expected result:
  All branches/channels are shown.

  Observed result:
  All branches have the same name.

  [Regression Potential]
  Fix was an invalid iterator, unlikely to cause further issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768794/+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 1683445] Re: E6430 brightness control not working

[William Kao]

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  E6430 brightness control not working

Status in GNOME Settings Daemon:
  Fix Released
Status in Nouveau Xorg driver:
  Won't Fix
Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon source package in Xenial:
  New
Status in unity-settings-daemon source package in Xenial:
  New
Status in gnome-settings-daemon source package in Zesty:
  Fix Released
Status in unity-settings-daemon source package in Zesty:
  Triaged

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+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 1813893] Re: OpenVPN LZ4 compression not working in Networkmanager

[William Grant]

** Package changed: ubuntu => network-manager-openvpn (Ubuntu)

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

Title:
  OpenVPN LZ4 compression not working in Networkmanager

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  Hi there,

  when importing an ovpn profile (from a PFsense in this case) where 
compression is set to LZ4 it won't work.
  Network manager won't save the config properly, as it does not seem to 
support lz4?

  When I manually use

  sudo openvpn --config myconfig.ovpn

  it works just fine.

  OpenVPN 2.4.6 x86_64-pc-linux-gnu

  is being used right now.

  Best regards
  David

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1813893/+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 1817308] Re: GhostScript Update causes Blue Background

[William Seward]

Having the same blue background problem with an HP Deskjet 1510, on
Linux Mint 17.3. Could not get Ghostscript to downgrade, but the
grayscale works for now. Most of my printing is b/w, but hope things get
resolved soon.

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

Title:
  GhostScript Update causes Blue Background

Status in ghostscript package in Ubuntu:
  Incomplete

Bug description:
  I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with
  kernel 4.15.0-45-generic.

  Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and
  was applied to two of my machines (One is an Intel and one is an AMD,
  but both are kept fully updated) that share a networked HP OfficeJet
  6700 Printer.

  At some point following the update, I happened to print a document,
  and ended up with a blue background on every page, even otherwise
  blank second sides. This occured regardless of a variety of
  originating applications I used, such as LibreOffice, various text
  editors, and even the CUPS "print test page" option.

  It took me a while to troubleshoot this on that first machine (trying
  different apps, reinstalling CUPS and so forth) until I realized the
  new ghostscript update was the issue and that (after trying to print
  from the second machine) it was affecting both machines.

  I should note that, using the "non-CUPS" appearance of the same
  printer, no blue background is present, but of course this provides no
  features like ink-level reporting, dual-sided printing, etc.

  I "restored" the ghostscript stuff from the last Timeshift backup and
  that cured the issue but I think this is a serious matter that should
  be addressed immediately (not the least because it's hard to read
  black text on a blue background and it wastes a lot of ink).

  I first posted this at
  
  and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was
  on the update information) who advised me to post this bug here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+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 1817381] Re: After the most recent software updates to xubuntu, my printer prints normal pages (from a word processor for instance) with a blue background.

[William Seward]

Same issue on Linux Mint 17.3. printing from any program.

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

Title:
  After the most recent software updates to xubuntu, my printer prints
  normal pages (from a word processor for instance) with a blue
  background.

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This has happened to both of my computers running xubuntu.  My first
  computer, I updated yesterday.  The second computer did not exhibit
  the problem this morning.  Once I updated the software with Software
  Updater, it acquired the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.3
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CupsErrorLog:
   W [22/Feb/2019:16:38:45 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Deskjet-3050-J610-series-Gray..\' already exists
   W [22/Feb/2019:16:38:45 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Deskjet-3050-J610-series-RGB..\' already exists
  CurrentDesktop: XFCE
  Date: Fri Feb 22 17:00:53 2019
  InstallationDate: Installed on 2018-02-05 (382 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lpstat:
   device for HP-Deskjet-3050-J610-series: 
hp:/net/Deskjet_3050_J610_series?hostname=HPFDBBD9.local
   device for HP-Officejet-6600: hp:/net/Officejet_6600?hostname=HP2D4AAF.local
   device for Officejet_6600_2D4AAF_: ipp://HP2D4AAF.local:631/ipp/printer
   device for Roger-Router-Fax: roger-cups:/
  MachineType: Hewlett-Packard HP 15 TS Notebook PC
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Officejet_6600_2D4AAF_.ppd', 
'/etc/cups/ppd/HP-Deskjet-3050-J610-series.ppd', 
'/etc/cups/ppd/HP-Officejet-6600.ppd', '/etc/cups/ppd/Roger-Router-Fax.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/Officejet_6600_2D4AAF_.ppd: 
Permission denied
   grep: /etc/cups/ppd/HP-Deskjet-3050-J610-series.ppd: Permission denied
   grep: /etc/cups/ppd/HP-Officejet-6600.ppd: Permission denied
   grep: /etc/cups/ppd/Roger-Router-Fax.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (294 days ago)
  dmi.bios.date: 11/14/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.46
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/14/2014:svnHewlett-Packard:pnHP15TSNotebookPC:pvr0972110021405F0620180:rvnHewlett-Packard:rn2211:rvr86.46:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 TS Notebook PC
  dmi.product.version: 0972110021405F0620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1817381/+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 577038] Re: [Upstream] Hard lock in opening files from a remote NFS volume

[William Grant]

** Description changed:

  Binary package hint: openoffice.org
  
  I recently updated to Lucid, and noticed that Openoffice would lock with
  opening certain files. First I thought the problem was a corrupt file,
  now I can reproducibly hard lock OO.org when trying to open ANY file
  (.xls, .doc, .odt) that is present in a remote NFS volume (locally
  mounted).
  
  Any file on the local hard disk can be opened without problems.
  Any file on the mounted NFS directory causes a hard lock, requiring a 
force-quit.
  
  Other applications don't show this behaviour (e.g. gedit, command line
  programs).
  
  FilesystemSize  Used Avail Use% Mounted on
  /dev/md0   70G   17G   50G  26% /
  192.168.10.72:/home/fernan243G  182G   42G  82% /home/fernan/gama-remote
- http://yourrxstore.com/product-category/buy-soma-online/
- http://yourrxstore.com/blog/order-tramadol-online-severe-and-acute-pain/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: openoffice.org 1:3.2.0-7ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri May  7 11:48:21 2010
  EcryptfsInUse: Yes
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: openoffice.org

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

Title:
  [Upstream] Hard lock in opening files from a remote NFS volume

Status in LibreOffice:
  Invalid
Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  I recently updated to Lucid, and noticed that Openoffice would lock
  with opening certain files. First I thought the problem was a corrupt
  file, now I can reproducibly hard lock OO.org when trying to open ANY
  file (.xls, .doc, .odt) that is present in a remote NFS volume
  (locally mounted).

  Any file on the local hard disk can be opened without problems.
  Any file on the mounted NFS directory causes a hard lock, requiring a 
force-quit.

  Other applications don't show this behaviour (e.g. gedit, command line
  programs).

  FilesystemSize  Used Avail Use% Mounted on
  /dev/md0   70G   17G   50G  26% /
  192.168.10.72:/home/fernan243G  182G   42G  82% /home/fernan/gama-remote

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: openoffice.org 1:3.2.0-7ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri May  7 11:48:21 2010
  EcryptfsInUse: Yes
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: openoffice.org

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/577038/+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 1897455] [NEW] Notifications don't say which VPN and network interface

[William Dietrich]

Public bug reported:

In Ubuntu MATE 20.04:  If I connect to or disconnect from a VPN, I get a
notification that says something like "disconnected from Network".  This
is too generic.  Every notification involving a VPN change should
specify the VPN connection name, and the underlying network interface
name too.  Every notification involving a network interface change (such
as enabling/disabling Wi-Fi or Ethernet) should specify the network
interface name.  Every notification involving Wi-Fi should specify the
Wi-Fi network name.  Always give as much information as possible and
reasonable.  Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Sun Sep 27 15:04:15 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 # Include files from /etc/network/interfaces.d:
 source-directory /etc/network/interfaces.d
InstallationDate: Installed on 2020-09-26 (1 days ago)
InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
disabled  enabled  enabled

** Affects: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1897455

Title:
  Notifications don't say which VPN and network interface

Status in network-manager package in Ubuntu:
  New

Bug description:
  In Ubuntu MATE 20.04:  If I connect to or disconnect from a VPN, I get
  a notification that says something like "disconnected from Network".
  This is too generic.  Every notification involving a VPN change should
  specify the VPN connection name, and the underlying network interface
  name too.  Every notification involving a network interface change
  (such as enabling/disabling Wi-Fi or Ethernet) should specify the
  network interface name.  Every notification involving Wi-Fi should
  specify the Wi-Fi network name.  Always give as much information as
  possible and reasonable.  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Sep 27 15:04:15 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2020-09-26 (1 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1897455/+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 1896349] Re: PCI/internal sound card not detected

[william backus]

new install ubuntu 20.04.01

same audio issue, settings and pavucontrol only see hdmi audio out and not 
intel hda audio
older dell desktop with 4 years previous use ubuntu. audio worked on morning of 
my fresh install ubuntu 20.04.01. oddly virtualbox install ubuntu 20.04 and 
other dist same linux, but broke my base machine. base machine restart and 
messing with pavucontrol allowed my to select appropriate settings to restore 
audio after exit virutalbox session. all else works and i do not want to risk 
all my transfer/setup trying to fix this one issue, as important as it may be 
to me. 

just politely adding my experience to thread in case future update may
address this issue.

william@william-Studio-XPS-7100:~$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge 
(ext gfx port 0)
00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge 
(PCIE port 2)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 
Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 
Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 3c)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
IDE Controller
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar 
[Radeon HD 5000/6000/7350/8350 Series]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio 
[Radeon HD 5400/6300/7300 Series]
02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57788 
Gigabit Ethernet PCIe (rev 01)
03:05.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  I can select my default audio hardware

  When I test it, doesn't work.

  When watching a Youtube video, for example, audio doesn't work as
  well.

  Thru the command lspci, this shows up:

  00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
  00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 
(rev 07)
  00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03)
  00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB 
Controller (rev 03)
  00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host 
Controller (rev 30)
  00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
  00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz 
Wireless Network Adapter (201NGW) (rev 30)
  00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO 
I2C Controller #0 (rev 30)
  00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO 
I2C Controller #1 (rev 30)
  00:16.0 Communication controller: Intel Corporation Management Engine 
Interface (rev 30)
  00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 30)
  00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #5 
(rev 30)
  00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 
(rev 30)
  00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
  00:1d.6 PCI bridge: Intel Corporation Device 34

[Desktop-packages] [Bug 1896349] Re: PCI/internal sound card not detected

[william backus]

add to previous comment: devices found but not intialized. discovered my
webcam not initialized in clean install ubuntu 20.04.01

thanks in advance for any attention and possible response or future
fixes.

so far, no sound from my Azalia (Intel HDA)
webcam not found in cheese from my generic usb anivia webcam

william@william-Studio-XPS-7100:~$ dmesg | grep -i "Camera"
[43532.227381] usb 1-6: Product: USB 2.0 Camera
[43532.643588] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366)
[43532.670887] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not 
initialized!
[43532.671103] input: USB 2.0 Camera: USB Camera as 
/devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input27
[43931.982272] usb 1-6: Product: USB 2.0 Camera
[43931.985021] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366)
[43932.011454] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not 
initialized!
[43932.011667] input: USB 2.0 Camera: USB Camera as 
/devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input28
william@william-Studio-XPS-7100:~$ ls -ltrh /dev/video*
crw-rw+ 1 root video 81, 1 Sep 27 19:39 /dev/video1
crw-rw+ 1 root video 81, 0 Sep 27 19:39 /dev/video0
william@william-Studio-XPS-7100:~$ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 005: ID 18e3:9106 Fitipower Integrated Technology Inc Mass 
Storage Device
Bus 002 Device 006: ID 04f9:0283 Brother Industries, Ltd MFC-J825DW
Bus 002 Device 007: ID 413c:2001 Dell Computer Corp. Keyboard HID Support
Bus 002 Device 004: ID 413c:1001 Dell Computer Corp. Keyboard Hub
Bus 002 Device 002: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  I can select my default audio hardware

  When I test it, doesn't work.

  When watching a Youtube video, for example, audio doesn't work as
  well.

  Thru the command lspci, this shows up:

  00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
  00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 
(rev 07)
  00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03)
  00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB 
Controller (rev 03)
  00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host 
Controller (rev 30)
  00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
  00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz 
Wireless Network Adapter (201NGW) (rev 30)
  00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO 
I2C Controller #0 (rev 30)
  00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO 
I2C Controller #1 (rev 30)
  00:16.0 Communication controller: Intel Corporation Management Engine 
Interface (rev 30)
  00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 30)
  00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #5 
(rev 30)
  00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 
(rev 30)
  00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
  00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30)
  00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30)
  00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound Technology 
Audio Controller (rev 30)
  00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI 
Controller (rev 30)
  01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI 
Express Card Reader (rev 01)
  03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 (rev 03)
  04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x8

[Desktop-packages] [Bug 1897455] Re: Notifications don't say which VPN and network interface

[William Dietrich]

Okay, filed
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/543


** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #543
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/543

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

Title:
  Notifications don't say which VPN and network interface

Status in network-manager package in Ubuntu:
  New

Bug description:
  In Ubuntu MATE 20.04:  If I connect to or disconnect from a VPN, I get
  a notification that says something like "disconnected from Network".
  This is too generic.  Every notification involving a VPN change should
  specify the VPN connection name, and the underlying network interface
  name too.  Every notification involving a network interface change
  (such as enabling/disabling Wi-Fi or Ethernet) should specify the
  network interface name.  Every notification involving Wi-Fi should
  specify the Wi-Fi network name.  Always give as much information as
  possible and reasonable.  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Sep 27 15:04:15 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2020-09-26 (1 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1897455/+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 1897570] [NEW] PCI/internal sound card not detected

[william backus]

Public bug reported:

ubuntu 20.04.01 clean install.
thanks in advance for your attention. polite comment, no yelling here. going 
thru transfer and setup machine previous install ubuntu 16.04 when sound was 
working.

lspci lists all sources. internal intel ada card not intialized. only option in 
sound is hdmi. all worked before clean install. 
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio 
[Radeon HD 5400/6300/7300 Series]


same audio issue, settings and pavucontrol only see hdmi audio out and not 
intel hda audio
older dell desktop with 4 years previous use ubuntu. audio worked on morning of 
my fresh install ubuntu 20.04.01. oddly virtualbox install ubuntu 20.04 and 
other dist same linux, but broke my base machine. base machine restart and 
messing with pavucontrol allowed my to select appropriate settings to restore 
audio after exit virutalbox session. all else works and i do not want to risk 
all my transfer/setup trying to fix this one issue, as important as it may be 
to me.

just politely adding my experience to thread in case future update may
address this issue.

william@william-Studio-XPS-7100:~$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge 
(ext gfx port 0)
00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge 
(PCIE port 2)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 
Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 
Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 3c)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
IDE Controller
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar 
[Radeon HD 5000/6000/7350/8350 Series]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio 
[Radeon HD 5400/6300/7300 Series]
02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57788 
Gigabit Ethernet PCIe (rev 01)
03:05.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  william1432 F pulseaudio
 /dev/snd/pcmC0D1p:   william1432 F...m pulseaudio
 /dev/snd/controlC1:  william1432 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 28 09:17:53 2020
InstallationDate: Installed on 2020-09-26 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0NWWY0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Studio XPS 7100
dmi.

[Desktop-packages] [Bug 1897600] [NEW] PCI/internal sound card not detected

[william backus]

Public bug reported:

ubuntu 20.04.01 clean install.
thanks in advance for your attention. polite comment, no yelling here. going 
thru transfer and setup machine previous install ubuntu 16.04 when sound was 
working.

lspci lists all sources. internal intel ada card not intialized. only
option in sound is hdmi. all worked before clean install.

00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio 
[Radeon HD 5400/6300/7300 Series]

william@william-Studio-XPS-7100:~$ cat /proc/asound/cards
 0 [SB ]: HDA-Intel - HDA ATI SB
  HDA ATI SB at 0xfe8f4000 irq 16
 1 [HDMI   ]: HDA-Intel - HDA ATI HDMI
  HDA ATI HDMI at 0xfe9bc000 irq 26
  
william@william-Studio-XPS-7100:~$ cat /proc/asound/card0/codec* | grep Codec
Codec: Realtek ALC887

same audio issue, settings and pavucontrol only see hdmi audio out and not 
intel hda audio
older dell desktop with 4 years previous use ubuntu. audio worked on morning of 
my fresh install ubuntu 20.04.01. oddly virtualbox install ubuntu 20.04 and 
other dist same linux, but broke my base machine. base machine restart and 
messing with pavucontrol allowed my to select appropriate settings to restore 
audio after exit virutalbox session. all else works and i do not want to risk 
all my transfer/setup trying to fix this one issue, as important as it may be 
to me.

just politely adding my experience to thread in case future update may
address this issue.

william@william-Studio-XPS-7100:~$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge 
(ext gfx port 0)
00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge 
(PCIE port 2)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 
Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 
Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 3c)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
IDE Controller
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar 
[Radeon HD 5000/6000/7350/8350 Series]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio 
[Radeon HD 5400/6300/7300 Series]
02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57788 
Gigabit Ethernet PCIe (rev 01)
03:05.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  william1432 F pulseaudio
 /dev/snd/controlC0:  william1432 F pulseaudio
 /dev/snd/pcmC0D1p:   william1432 F...m pulseaudio
 /dev/snd/controlC1:  william1432 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 28 09:16:19 2020
InstallationDate: Installed on 2020-09-26 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card no

Re: [Desktop-packages] [Bug 1897567] Re: webcam not initialized

[william backus]

issue fixed...i think.
cheese: had to select a matching resolution to enable camera. webcam 
resolution was higher than default.
still have to resolve my no sound issue...so common, there are very many 
possible alsa and alsa-pulseaudio related options.

On 9/28/20 12:04 PM, Kai-Heng Feng wrote:
> Nothing special from dmesg. Probably a bug in Cheese.
>
> ** Also affects: cheese (Ubuntu)
> Importance: Undecided
> Status: New
>

-- 
W.C. Backus, Architect
Lexington, Ky

backus.will...@gmail.com

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

Title:
  webcam not initialized

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

Bug description:
  ubuntu 20.04.01 clean install.
  thanks in advance for your attention. polite comment, no yelling here. going 
thru transfer and setup machine previous install ubuntu 16.04 when usb camera 
was working.

  webcam not initialized in cheese from my generic usb anivia webcam
  webcam device found: Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera

  william@william-Studio-XPS-7100:~$ dmesg | grep -i "Camera"
  [43532.227381] usb 1-6: Product: USB 2.0 Camera
  [43532.643588] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366)
  [43532.670887] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not 
initialized!
  [43532.671103] input: USB 2.0 Camera: USB Camera as 
/devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input27
  [43931.982272] usb 1-6: Product: USB 2.0 Camera
  [43931.985021] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6366)
  [43932.011454] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was not 
initialized!
  [43932.011667] input: USB 2.0 Camera: USB Camera as 
/devices/pci:00/:00:12.2/usb1/1-6/1-6:1.0/input/input28
  william@william-Studio-XPS-7100:~$ ls -ltrh /dev/video*
  crw-rw+ 1 root video 81, 1 Sep 27 19:39 /dev/video1
  crw-rw+ 1 root video 81, 0 Sep 27 19:39 /dev/video0
  william@william-Studio-XPS-7100:~$ lsusb
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 005: ID 18e3:9106 Fitipower Integrated Technology Inc Mass 
Storage Device
  Bus 002 Device 006: ID 04f9:0283 Brother Industries, Ltd MFC-J825DW
  Bus 002 Device 007: ID 413c:2001 Dell Computer Corp. Keyboard HID Support
  Bus 002 Device 004: ID 413c:1001 Dell Computer Corp. Keyboard Hub
  Bus 002 Device 002: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC)
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 002: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 006: ID 0c45:6366 Microdia USB 2.0 Camera
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  william1432 F pulseaudio
   /dev/snd/controlC0:  william1432 F pulseaudio
   /dev/snd/pcmC0D1p:   william1432 F...m pulseaudio
   /dev/snd/controlC1:  william1432 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 28 09:03:27 2020
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2020-09-26 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: Dell Inc. Studio XPS 7100
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=ffa0aa05-8d32-4088-b80c-8afd25831dbc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  RfKill:
   
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   09:03:37.505: The udisks-daemon is running (name-owner

[Desktop-packages] [Bug 1897856] [NEW] snap launch fails: symbol lookup error

[William Dietrich]

Public bug reported:

Using snap 3.38.0+git1.ffa3fd98 on Ubuntu MATE 20.04:

/snap/evince/532/usr/bin/evince: symbol lookup error:
/snap/evince/532/usr/lib/x86_64-linux-gnu/libevdocument3.so.4: undefined
symbol: gdk_pixbuf_init_modules

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

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

Title:
  snap launch fails: symbol lookup error

Status in evince package in Ubuntu:
  New

Bug description:
  Using snap 3.38.0+git1.ffa3fd98 on Ubuntu MATE 20.04:

  /snap/evince/532/usr/bin/evince: symbol lookup error:
  /snap/evince/532/usr/lib/x86_64-linux-gnu/libevdocument3.so.4:
  undefined symbol: gdk_pixbuf_init_modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897856/+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 1898072] [NEW] no sound

[william backus]

Public bug reported:

no sound issue

4 years using ubuntu 16.04.  weekend 9.26.20 clean install ubuntu
20.04.01. planned 3 days install. day one clone and full ext hd backup
all files. day two clean install, paste files and use clean system. all
mostly works but no sound from prior working setup. day 3 troubleshoot
sound, install new versions of apps from prior working system.

seems no sound is a very common issue. ubuntu/settings/sound not showing
my outup options, being locked to an hdmi ouput was baffling and i
considered restoring my clone except for the 2 days of sucessfully
transferring my files. i am satisfied the system is functional for my
core uses so i will continue to try to work this sound issue.

politely asking for advice from community. no shouting here and i do
appreciate help.

the following is my no sound experience on day 3 of clean install:

ubuntu/settings/audio. only showed hdmi output device, everything else
blank.

online advice to search devices

lspci: found my sound card
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)

tried online advice:
search pci devices
kill alsa, reinstall
kill pulseaudio, reinstall

alsamixer: turned up/on everything, finally speaker feeback for
alsamixer loopback setting so i knew sound was capable of something.

pulseaudio, tried every random setting. finally the setting "analog
surround 4.1 ouput + analog stereo input (unplugged) (unavailable)"
setting worked normally thru my audio jacks.

now pulseaudio does not save these settings thru shutdown.
whaaa? relief! baffled. reluctant to touch anything else because it works...so 
far.

went thru pulseaudio settings files, seems almost all options are
commented out. i pasted these files at end this message.

alsa mixer keeps settings. ubuntu/settings/audio still only shows hdmi
output device, everything else blank.

now i am considering online advice to kill and reset all pulseaudio.

Reset PulseAudio If the system is not playing audio, first try reseting the 
pulseaudio daemon: systemctl --user restart pulseaudio Applications may need to 
be restarted. If this fails then try removing the user configuration files for 
PulseAudio: rm -r ~/.config/pulse Then, kill all instances of PulseAudio: 
pulseaudio -k When PulseAudio starts again (which it should do automatically), 
it will create new configuration files. 
https://support.system76.com/articles/audio/

sound output works if i manually reset pulseaudio after start. i am not
confident to blast away or edit conf or daemon files. i would like
working pulseaudio settings to survive restart and i would prefer
ubuntu/settings/audio reflect actual settings. thanks in advance for
suggestions/comments.

following are existing pulseaudio files:
********
william@william-Studio-XPS-7100:/etc/pulse$ tree
.
├── client.conf
├── client.conf.d
│   └── 01-enable-autospawn.conf -> /run/pulseaudio-enable-autospawn
├── daemon.conf
├── default.pa
└── system.pa


This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see <http://www.gnu.org/licenses/>.

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; avoid-resampling = false
; enable-remixing = yes
; remixing-use-all-sink-channels = yes
; remixing-produce-lfe = no
; remixing-consume-lfe = no
; lfe-crossover-freq = 0

; flat-volumes = no

; rescue-streams = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-me

[Desktop-packages] [Bug 1898072] Re: no sound

[william backus]

continue to ponder pavucontrol and now udev. my clean install ubuntu 20
lts did not find my built-in audio so i have posted to the bug site
hoping you will have previously sorted this. i am guessing udev is not
finding sound setup, did not correctly populate alsa and is currently
not correctly populating pavucontrol setttings.

i do not want to start editing conf files using pacmd. really wanted a
strategy that would automatically repopulate the settings. i am just
experienced enough to brick this install...a bad thing.

i realize you are sorting out issues for the greater population. ubuntu
20 lts is almost completely functional. i can manually configure gui
pavucontrol on each start and go on with life. i have a week's worth of
data and config under my belt and do not intend to restore my clone or
investigate other flavors linux.

the previous 4 years of ubuntu 16 lts was not without its quirks...and
the decades of windoze, mac and even in late 80's an ibm pc.  i no
longer have to deal with vertical market software for the architctural
industry and have fully converted all my office apps to libreoffice.

i don't want to be a weiner...i am a greyhair, retired and just tired of
messing with confusers. hope my comments are useful as you continue to
develop ubuntu 20lts.

now for something completely different: national lampoon magazine from
1971 subscription ads "you may already be a weiner" and "buy this
magazine or we will shoot the dog"

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

Title:
  no sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  no sound issue

  4 years using ubuntu 16.04.  weekend 9.26.20 clean install ubuntu
  20.04.01. planned 3 days install. day one clone and full ext hd backup
  all files. day two clean install, paste files and use clean system.
  all mostly works but no sound from prior working setup. day 3
  troubleshoot sound, install new versions of apps from prior working
  system.

  seems no sound is a very common issue. ubuntu/settings/sound not
  showing my outup options, being locked to an hdmi ouput was baffling
  and i considered restoring my clone except for the 2 days of
  sucessfully transferring my files. i am satisfied the system is
  functional for my core uses so i will continue to try to work this
  sound issue.

  politely asking for advice from community. no shouting here and i do
  appreciate help.

  the following is my no sound experience on day 3 of clean install:

  ubuntu/settings/audio. only showed hdmi output device, everything else
  blank.

  online advice to search devices

  lspci: found my sound card
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)

  tried online advice:
  search pci devices
  kill alsa, reinstall
  kill pulseaudio, reinstall

  alsamixer: turned up/on everything, finally speaker feeback for
  alsamixer loopback setting so i knew sound was capable of something.

  pulseaudio, tried every random setting. finally the setting "analog
  surround 4.1 ouput + analog stereo input (unplugged) (unavailable)"
  setting worked normally thru my audio jacks.

  now pulseaudio does not save these settings thru shutdown.
  whaaa? relief! baffled. reluctant to touch anything else because it 
works...so far.

  went thru pulseaudio settings files, seems almost all options are
  commented out. i pasted these files at end this message.

  alsa mixer keeps settings. ubuntu/settings/audio still only shows hdmi
  output device, everything else blank.

  now i am considering online advice to kill and reset all pulseaudio.

  Reset PulseAudio If the system is not playing audio, first try reseting the 
pulseaudio daemon: systemctl --user restart pulseaudio Applications may need to 
be restarted. If this fails then try removing the user configuration files for 
PulseAudio: rm -r ~/.config/pulse Then, kill all instances of PulseAudio: 
pulseaudio -k When PulseAudio starts again (which it should do automatically), 
it will create new configuration files. 
  https://support.system76.com/articles/audio/

  sound output works if i manually reset pulseaudio after start. i am
  not confident to blast away or edit conf or daemon files. i would like
  working pulseaudio settings to survive restart and i would prefer
  ubuntu/settings/audio reflect actual settings. thanks in advance for
  suggestions/comments.

  following are existing pulseaudio files:
  ****
  william@william-Studio-XPS-7100:/etc/pulse$ tree
  .
  ├── client.conf
  ├── client.conf.d
  │   └── 01-enable-autospawn.conf -> /run/pulseaudio-enable-autospawn
  ├── daemon.conf
  ├── default.pa
  └── system.pa

  
  This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it

[Desktop-packages] [Bug 1898416] [NEW] Wine failed to install

[William Ezard]

Public bug reported:

ubuntu 20.04
Tried to download wine from store, download failed.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libvdpau1 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sun Oct  4 18:32:08 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DuplicateSignature:
 package:libvdpau1:(not installed)
 Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-rmJMEd/144-libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack):
  trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from 
other instances of package libvdpau1:amd64
ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is 
different from other instances of package libvdpau1:amd64
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1462:7a40]
MachineType: Micro-Star International Co., Ltd. MS-7A40
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=c257c1a8-59c6-4967-add4-929a999d1246 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: libvdpau
Title: package libvdpau1 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other 
instances of package libvdpau1:amd64
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.70
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450I GAMING PLUS AC (MS-7A40)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.70:bd07/10/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A40
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
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 N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-package focal package-conflict ubuntu

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

Title:
  Wine failed to install

Status in libvdpau package in Ubuntu:
  New

Bug description:
  ubuntu 20.04
  Tried to download wine from store, download failed.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libvdpau1 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Oct  4 18:32:08 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libvdpau1:(not installed)
   Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-rmJMEd/144-libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack):
trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different 
from other instances of package libvdpau1:amd64
  ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is 
different from other instances of package libvdpau1:amd64
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Raven Ridge [Radeon 
Vega Series / Radeon Vega Mobile Series] [1462:7a40]
  MachineType: Micro-Star International Co., Ltd. MS-7A40
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vml

[Desktop-packages] [Bug 1893311] Re: Add libcurl4-openssl-dev build-dep for lumix camlib

[William Wilhelm]

This is now fixed in Debian as of 2.5.26-1 https://salsa.debian.org
/debian-phototools-team/libgphoto2/-/merge_requests/3

** Changed in: libgphoto2 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Add libcurl4-openssl-dev build-dep for lumix camlib

Status in libgphoto2 package in Ubuntu:
  Fix Released

Bug description:
  The lumix camlib is in a somewhat usable state 
(https://github.com/gphoto/libgphoto2/issues/409) and I have been successfully 
using it for a few months.
  It would be good to add the libcurl4-openssl-dev to Build-Depends to enable 
building the lumix camlib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1893311/+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 1901213] [NEW] I'm a novice

[William Wexler]

Public bug reported:

Just following the popup pages
Updates will not install hence why I am here on my journey
Also trying to find out how to back up Thunderbird externally as want to 
reinstall Ubuntu after using for 6 years and cannot update because of This 
report: Software updater : The package is broken window.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Oct 23 11:22:12 2020
DistUpgraded: 2018-06-30 14:29:00,147 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: bionic
DistroVariant: ubuntu
DpkgLog:
 
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
   Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
InstallationDate: Installed on 2014-09-23 ( days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: Dell Inc. OptiPlex 760
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=0eaecf29-797f-4744-9015-4ef391a04f60 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-06-30 (845 days ago)
dmi.bios.date: 02/24/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0M858N
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.asset.tag: 502420
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd02/24/2011:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 760
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Oct 28 08:24:17 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: modeset

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


** Tags: apport-bug bionic i386 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/1901213

Title:
  I'm a novice

Status in xorg package in Ubuntu:
  New

Bug description:
  Just following the popup pages
  Updates will not install hence why I am here on my journey
  Also trying to find out how to back up Thunderbird externally as want to 
reinstall Ubuntu after using for 6 years and cannot update because of This 
report: Software updater : The package is broken window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Oct 23 11:22:12 2020
  DistUpgraded: 2018-06-30 14:29:00,147 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: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
 Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
  InstallationDate: Installed on 2014-09-23 ( days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: Dell Inc. OptiPlex 760
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=0eaecf29-797f-

[Desktop-packages] [Bug 1909352] [NEW] (1) video hangs or (2) screen goes blank and case fan turns on

[William Murray]

Public bug reported:

Recover system by press and release reset switch.  Log in again.

Had these issues with Ubuntu 18.04.  Updated to Nvidia drivers and issues 
resolved.  Updated to 20.04.1 and issues have returned.  Checked and see that 
Nvidia drivers newer than those packaged for use.  Available at Nvidia / Newest 
package and in use:
  GeForce Game Ready Driver
  LINUX X64 (AMD64/EM64T) DISPLAY DRIVER
  Driver Version: 455.45 - Release Date: Tue Nov 17, 2020
  
  GeForce Game Ready Driver
  LINUX X64 (AMD64/EM64T) DISPLAY DRIVER
  Driver Version: 455.38 - Release Date: Thu Oct 29, 2020

Hopefully the command
ubuntu-bug xorg
attached all the information you may need.

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

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 26 09:54:40 2020
DistUpgraded: 2020-10-02 13:11:28,665 DEBUG icon theme changed, re-reading
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 455.38, 5.4.0-56-generic, x86_64: installed
 nvidia, 455.38, 5.4.0-58-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150]
InstallationDate: Installed on 2018-03-03 (1029 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=fc7c6eeb-fbb0-4f6c-8815-349d9ff6efd6 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-10-02 (84 days ago)
dmi.bios.date: 08/18/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F8
dmi.board.asset.tag: Default string
dmi.board.name: AB350-Gaming 3-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd08/18/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350-Gaming 3
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
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: Sat Dec 26 08:48:35 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.8-2ubuntu2.6

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


** Tags: amd64 apport-bug focal 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/1909352

Title:
  (1) video hangs or (2) screen goes blank and case fan turns on

Status in xorg package in Ubuntu:
  New

Bug description:
  Recover system by press and release reset switch.  Log in again.

  Had these issues with Ubuntu 18.04.  Updated to Nvidia drivers and issues 
resolved.  Updated to 20.04.1 and iss

[Desktop-packages] [Bug 1909352] Re: (1) video hangs or (2) screen goes blank and case fan turns on

[William Murray]

Another error state is  monitors stay black with cooling fan(s) at
normal slow speed.  This has happened after the screens go dark from
inactivity.  Such as monitors in power saving mode.  Press enter key,
monitors stay dark.  Again use reset switch on case to restart system.
Do not recall this behavior before update to Ubuntu 20.04.1 LTS. Good
thing Chrome is good at recovering open tabs and windows. :).

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

Title:
  (1) video hangs or (2) screen goes blank and case fan turns on

Status in xorg package in Ubuntu:
  New

Bug description:
  Recover system by press and release reset switch.  Log in again.

  Had these issues with Ubuntu 18.04.  Updated to Nvidia drivers and issues 
resolved.  Updated to 20.04.1 and issues have returned.  Checked and see that 
Nvidia drivers newer than those packaged for use.  Available at Nvidia / Newest 
package and in use:
GeForce Game Ready Driver
LINUX X64 (AMD64/EM64T) DISPLAY DRIVER
Driver Version: 455.45 - Release Date: Tue Nov 17, 2020

GeForce Game Ready Driver
LINUX X64 (AMD64/EM64T) DISPLAY DRIVER
Driver Version: 455.38 - Release Date: Thu Oct 29, 2020

  Hopefully the command
  ubuntu-bug xorg
  attached all the information you may need.

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 26 09:54:40 2020
  DistUpgraded: 2020-10-02 13:11:28,665 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 455.38, 5.4.0-56-generic, x86_64: installed
   nvidia, 455.38, 5.4.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150]
  InstallationDate: Installed on 2018-03-03 (1029 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=fc7c6eeb-fbb0-4f6c-8815-349d9ff6efd6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-02 (84 days ago)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350-Gaming 3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd08/18/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350-Gaming 3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  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
  versio

[Desktop-packages] [Bug 1915565] [NEW] screen fades for about 10 seconds glslideshowthen returns to normal

[WILLIAM HARRIS]

Public bug reported:

The fading happens online at . But it also happens offline in games.
Using Ubuntu 20.04
Unable to locate package pkgname

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Feb 12 13:14:56 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 5.4.0-64-generic, x86_64: installed
 bbswitch, 0.8, 5.4.0-65-generic, x86_64: installed
 nvidia, 390.141, 5.4.0-64-generic, x86_64: installed
 nvidia, 390.141, 5.4.0-65-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:820c]
   Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:820c]
InstallationDate: Installed on 2017-04-14 (1400 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0eef:c04d D-WAV Scientific Co., Ltd eGalaxTouch 
EXC3000-0367-44.01.00
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0408:5090 Quanta Computer, Inc. HP Wide version HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=07e929a4-0ebf-4ecc-bedd-3f5fbf79e6d8 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 820C
dmi.board.vendor: HP
dmi.board.version: 82.29
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/21/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820C:rvr82.29:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: X0S49UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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: Sat Oct 17 14:45:19 2020
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.8-2ubuntu2.4

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


** Tags: amd64 apport-bug focal 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/1915565

Title:
  screen fades for about 10 seconds glslideshowthen returns to normal

Status in xorg package in Ubuntu:
  New

Bug description:
  The fading happens online at . But it also happens offline in 
games.
  Using Ubuntu 20.04
  Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb 12 13:14:56 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 5.4.0-64-generic, x86_64: installed
   bbswitch, 0.8, 5.4.0-65-generic, x86_64: installed
   nvidia, 390.141, 5.4.0-64-generic, x86_64: installed
   nvidia, 390.141, 5.4.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])

[Desktop-packages] [Bug 1922792] [NEW] Bluez should notify users when they need to reboot to apply changes

[William Wilson]

Public bug reported:

In the case of upgrading bluez on certain raspberry pi devices, a reboot
may be required to apply the changes. We should add a check for this
scenario in the postinst script.

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

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

Title:
  Bluez should notify users when they need to reboot to apply changes

Status in bluez package in Ubuntu:
  New

Bug description:
  In the case of upgrading bluez on certain raspberry pi devices, a
  reboot may be required to apply the changes. We should add a check for
  this scenario in the postinst script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+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 1922712] Re: add metric for new glibc hwcaps

[William Wilson]

** Changed in: ubuntu-report (Ubuntu)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

Title:
  add metric for new glibc hwcaps

Status in ubuntu-report package in Ubuntu:
  New

Bug description:
  we want to collect information which most recent hwcap is supported by
  a machine.  The result should be a string like "x86-64-v2",
  "x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
  linux --help" output.  The string should be empty for architectures
  without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
  string should be empty if no specific hwcaps is supported (e.g. on a
  power8 machine). The string should be "N/A" (not available), when
  trying to run ld-linux on a release with glibc (<< 2.33).

  Note that lexical sorting won't work for "p9", "p10".

  if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
  elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
  elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
  fi

  supported=
  if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk 
'/supported/ {print $1}')
  fi

  Here, $supported has listed all supported hwcaps, not just the best
  supported one.

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