[Touch-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

[fossfreedom]

** Changed in: ubuntu-budgie-meta (Ubuntu Noble)
   Status: Triaged => Fix Committed

** Changed in: ubuntu-budgie-meta (Ubuntu Noble)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in kubuntu-meta package in Ubuntu:
  Triaged
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in wslu package in Ubuntu:
  Invalid
Status in kubuntu-meta source package in Noble:
  Triaged
Status in lubuntu-meta source package in Noble:
  Triaged
Status in ubuntu-budgie-meta source package in Noble:
  Fix Committed
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

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


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

[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[fossfreedom]

Hi - ok - very long thread so not quite sure how best to resolve.

I note bubblewrap is marked as confirmed but no resolution.

For budgie-control-center - backgrounds - Add Picture I found that the
gnome-desktop library libgnome-desktop-3-20 is calling bwrap and that
this was failing due to permissions.

I worked around this via

```
cat /etc/apparmor.d/bwrap 
# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"

abi ,
include 

profile bwrap /usr/bin/bwrap flags=(unconfined) {
  userns,

  # Site-specific additions and overrides. See local/README for details.
  include if exists 
}
```

Can this be added to apparmor please?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2046844

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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

[Touch-packages] [Bug 2057710] [NEW] Accountsservice FTBFS on noble

[fossfreedom]

Public bug reported:

 package version 23.13.9-2ubuntu FTBFS on all architectures.

This is because of an invalid test

This has been resolved upstream - see the attached debdiff

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

** Patch added: "addtest.patch"
   
https://bugs.launchpad.net/bugs/2057710/+attachment/5755358/+files/addtest.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2057710

Title:
  Accountsservice FTBFS on noble

Status in accountsservice package in Ubuntu:
  New

Bug description:
   package version 23.13.9-2ubuntu FTBFS on all architectures.

  This is because of an invalid test

  This has been resolved upstream - see the attached debdiff

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


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

[Touch-packages] [Bug 2055088] Re: debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie

[fossfreedom]

@ahasenack ... lessons learned.  Never fill in bug reports late at
night.

Ok - clarified the reasoning in the description

** Description changed:

- d/control is used on the official gtk desktops such as budgie.
+ software-properties-gtk is used on the official gtk desktops such as
+ budgie.
  
- budgie-desktop for noble now uses budgie-session instead of gnome-
- session.
+ Currently in the debian control file it has a recommendation to install
+ the session manager for that desktop - so gnome-session-bin for GNOME
+ based desktops, mate-session for mate desktop and so on.
  
- software-properties needs an update to its dependency list
+ budgie-desktop for noble now uses budgie-session as its session manager
+ instead of gnome-session.
+ 
+ Because of the current recommendation, gnome-session-bin is installed on
+ budgie-desktop.  It no longer needs to be installed.
+ 
+ software-properties needs an update to its alternate recommendations so
+ that budgie-desktop doesnt pull in gnome-session-bin incorrectly.

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2055088

Title:
  debian/control incorrectly installs gnome-session dependencies in
  ubuntu-budgie

Status in software-properties package in Ubuntu:
  New

Bug description:
  software-properties-gtk is used on the official gtk desktops such as
  budgie.

  Currently in the debian control file it has a recommendation to
  install the session manager for that desktop - so gnome-session-bin
  for GNOME based desktops, mate-session for mate desktop and so on.

  budgie-desktop for noble now uses budgie-session as its session
  manager instead of gnome-session.

  Because of the current recommendation, gnome-session-bin is installed
  on budgie-desktop.  It no longer needs to be installed.

  software-properties needs an update to its alternate recommendations
  so that budgie-desktop doesnt pull in gnome-session-bin incorrectly.

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


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

[Touch-packages] [Bug 2055088] [NEW] debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie

[fossfreedom]

Public bug reported:

d/control is used on the official gtk desktops such as budgie.

budgie-desktop for noble now uses budgie-session instead of gnome-
session.

software-properties needs an update to its dependency list

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: noble

** Tags added: noble

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2055088

Title:
  debian/control incorrectly installs gnome-session dependencies in
  ubuntu-budgie

Status in software-properties package in Ubuntu:
  New

Bug description:
  d/control is used on the official gtk desktops such as budgie.

  budgie-desktop for noble now uses budgie-session instead of gnome-
  session.

  software-properties needs an update to its dependency list

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


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

[Touch-packages] [Bug 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live session

[fossfreedom]

** Summary changed:

- df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
+ df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live 
session

** Description changed:

  df: /sys/firmware/efi/efivars: Invalid argument appears on first display
  of the  live session - I note subsequently that at the end of the
  installation curtin fails due to an efivars error - looking at syslog I
  saw various efivars errors so I'm filing this with the kernel since this
  is the first instance.
+ 
+ Note - raised separate issue for the installation crash which has now
+ been duplicated against
+ https://bugs.launchpad.net/subiquity/+bug/2003222
  
  i.e. running grep efivars /var/log/*
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-7-generic 6.5.0-7.7
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   2077 F wireplumber
   /dev/snd/seq:ubuntu-budgie   2074 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CasperVersion: 1.486
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct  8 16:27:29 2023
  LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 
(20231008.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-7-generic N/A
   linux-backports-modules-6.5.0-7-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/2038765

Title:
  df: /sys/firmware/efi/efivars: Invalid argument causes error on
  login/live session

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

Bug description:
  df: /sys/firmware/efi/efivars: Invalid argument appears on first
  display of the  live session - I note subsequently that at the end of
  the installation curtin fails due to an efivars error - looking at
  syslog I saw various efivars errors so I'm filing this with the kernel
  since this is the first instance.

  Note - raised separate issue for the installation crash which has now
  been duplicated against
  https://bugs.launchpad.net/subiquity/+bug/2003222

  i.e. running grep efivars /var/log/*

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-7-generic 6.5.0-7.7
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   2077 F wireplumber
   /dev/snd/seq:ubuntu-budgie   2074 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CasperVersion: 1.486
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct  8 16:27:29 2023
  LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 
(20231008.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-7-generic N/A
   linux-backports-modules-6.5.0-7-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 0.1
  

[Touch-packages] [Bug 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash

[fossfreedom]

After installing via the legacy iso I saw the same message on login.

Opening a terminal and typing df I saw again the same message in the
terminal followed by the normal df output.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/2038765

Title:
  df: /sys/firmware/efi/efivars: Invalid argument causes installation
  crash

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

Bug description:
  df: /sys/firmware/efi/efivars: Invalid argument appears on first
  display of the  live session - I note subsequently that at the end of
  the installation curtin fails due to an efivars error - looking at
  syslog I saw various efivars errors so I'm filing this with the kernel
  since this is the first instance.

  i.e. running grep efivars /var/log/*

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-7-generic 6.5.0-7.7
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   2077 F wireplumber
   /dev/snd/seq:ubuntu-budgie   2074 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CasperVersion: 1.486
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct  8 16:27:29 2023
  LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 
(20231008.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-7-generic N/A
   linux-backports-modules-6.5.0-7-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Touch-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

[fossfreedom]

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-budgie-meta (Ubuntu)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in edubuntu-meta package in Ubuntu:
  New
Status in kubuntu-meta package in Ubuntu:
  New
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-unity-meta package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

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


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

[Touch-packages] [Bug 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages

[fossfreedom]

** Description changed:

  Examining the .list file for the amd64 image it contains various kernel
  5.13 .deb packages.
  
  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list
  
  e.g.
  
  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
  This is a little unexpected given that 5.15 is the default kernel.
  
  Possibly nvidia-390 doesn't have 5.15 packages?
+ 
+ This impacts all flavours as well that include nvidia stuff in their ISO
+ - so if the solution is to change the meta file for a revised regexp for
+ nvidia then all flavours that include nvidia will likewise need their
+ meta packages updated.

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

Title:
  20.04.5 (20220829.1 build) has kernel 5.13 packages

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Examining the .list file for the amd64 image it contains various
  kernel 5.13 .deb packages.

  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list

  e.g.

  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

  This is a little unexpected given that 5.15 is the default kernel.

  Possibly nvidia-390 doesn't have 5.15 packages?

  This impacts all flavours as well that include nvidia stuff in their
  ISO - so if the solution is to change the meta file for a revised
  regexp for nvidia then all flavours that include nvidia will likewise
  need their meta packages updated.

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


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

[Touch-packages] [Bug 1988143] [NEW] 20.04.5 (20220829.1 build) has kernel 5.13 packages

[fossfreedom]

Public bug reported:

Examining the .list file for the amd64 image it contains various kernel
5.13 .deb packages.

http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
amd64.list

e.g.

/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

This is a little unexpected given that 5.15 is the default kernel.

Possibly nvidia-390 doesn't have 5.15 packages?

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


** Tags: focal iso-testing

** Tags added: iso-testing

** Description changed:

  Examining the .list file for the amd64 image it contains various kernel
  5.13 .deb packages.
+ 
+ http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
+ amd64.list
+ 
+ e.g.
+ 
+ 
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
+ 
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
+ 
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
+ 
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
+ 
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
  This is a little unexpected given that 5.15 is the default kernel.
  
  Possibly nvidia-390 doesn't have 5.15 packages?

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

Title:
  20.04.5 (20220829.1 build) has kernel 5.13 packages

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Examining the .list file for the amd64 image it contains various
  kernel 5.13 .deb packages.

  http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
  amd64.list

  e.g.

  
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
  
/pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb
  
/pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb

  This is a little unexpected given that 5.15 is the default kernel.

  Possibly nvidia-390 doesn't have 5.15 packages?

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


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

[Touch-packages] [Bug 1965636] Re: libfuse2 no longer included in jammy, required for AppImages

[fossfreedom]

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  libfuse2 no longer included in jammy, required for AppImages

Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntukylin-meta package in Ubuntu:
  Confirmed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Attempting to run an AppImage in Xubuntu 22.04 displays the following
  error:

  $ ./cryptomator-1.6.5-x86_64.AppImage 
  dlopen(): error loading libfuse.so.2

  AppImages require FUSE to run. 
  You might still be able to extract the contents of this AppImage 
  if you run it with the --appimage-extract option. 
  See https://github.com/AppImage/AppImageKit/wiki/FUSE 
  for more information

  ---

  Simply installing libfuse2 resolves this issue. Some flavors seem to
  still include it. I noticed that today's Ubuntu MATE daily still does.
  Ubuntu and Xubuntu do not.

  Ubuntu: 
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.manifest
  Xubuntu: 
https://cdimage.ubuntu.com/xubuntu/daily-live/current/jammy-desktop-amd64.manifest
  Ubuntu MATE: 
https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.manifest

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


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

[Touch-packages] [Bug 1960264] Re: 503 errors for Jammy PPAs

[fossfreedom]

Julian - correct I was using apt-cacher-ng as per sbuild instructions
here https://wiki.ubuntu.com/SimpleSbuild

Sorry - I've no idea how to configure squid-deb-proxy with sbuild.  So
I've deleted my sbuild chroots  & disabled using the .mk-sbuildrc proxy.
Installing from a ppa no longer shows 503 errors.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1960264

Title:
  503 errors for Jammy PPAs

Status in apt package in Ubuntu:
  New

Bug description:
  For Jammy - all PPAs seem to fail - the main archive is ok

   503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Err:12 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-window-shuffler amd64 1.3.0+202202062047~ubuntu22.04.1
    503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Err:6 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-rotation-lock-applet all 
1.3.0+202202062047~ubuntu22.04.1
    503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Fetched 114 kB in 7s (15.8 kB/s)
  E: Failed to fetch 
http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-quicknote-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  E: Failed to fetch 
http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-recentlyused-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]

  ppa:ubuntubudgie-dev/budgie-extras-daily

  The same PPA for impish & focal work just fine

  Thoughts?

  

  Continually running repeatedly sudo apt update && sudo apt dist-
  upgrade -y eventually forces the downloads to occur ok and the
  upgrades can then be installed ok

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.3.15
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Feb  7 18:47:47 2022
  InstallationDate: Installed on 2022-01-29 (8 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220129)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1960264] [NEW] 503 errors for Jammy PPAs

[fossfreedom]

Public bug reported:

For Jammy - all PPAs seem to fail - the main archive is ok

 503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
Err:12 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-window-shuffler amd64 1.3.0+202202062047~ubuntu22.04.1
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
Err:6 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-rotation-lock-applet all 
1.3.0+202202062047~ubuntu22.04.1
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
Fetched 114 kB in 7s (15.8 kB/s)
E: Failed to fetch 
http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-quicknote-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
E: Failed to fetch 
http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-recentlyused-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]

ppa:ubuntubudgie-dev/budgie-extras-daily

The same PPA for impish & focal work just fine

Thoughts?



Continually running repeatedly sudo apt update && sudo apt dist-upgrade
-y eventually forces the downloads to occur ok and the upgrades can then
be installed ok

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apt 2.3.15
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Mon Feb  7 18:47:47 2022
InstallationDate: Installed on 2022-01-29 (8 days ago)
InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220129)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** Description changed:

  For Jammy - all PPAs seem to fail - the main archive is ok
  
-  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
+  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Err:12 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-window-shuffler amd64 1.3.0+202202062047~ubuntu22.04.1
-   503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
+   503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Err:6 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-rotation-lock-applet all 
1.3.0+202202062047~ubuntu22.04.1
-   503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
- Fetched 114 kB in 7s (15.8 kB/s)  
 
+   503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
+ Fetched 114 kB in 7s (15.8 kB/s)
  E: Failed to fetch 
http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-quicknote-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  E: Failed to fetch 
http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu/pool/main/b/budgie-extras/budgie-recentlyused-applet_1.3.0%2b202202062047%7eubuntu22.04.1_amd64.deb
  503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  
  ppa:ubuntubudgie-dev/budgie-extras-daily
  
  The same PPA for impish & focal work just fine
  
  Thoughts?
+ 
+ 
+ 
+ Continually running repeatedly sudo apt update && sudo apt dist-upgrade
+ -y eventually forces the downloads to occur ok and the upgrades can then
+ be installed ok
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.3.15
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Feb  7 18:47:47 2022
  InstallationDate: Installed on 2022-01-29 (8 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220129)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1960264

Title:
  503 errors for Jammy PPAs

Status in apt package in Ubuntu:
  New

Bug description:
  For Jammy - all PPAs seem to fail - the main archive is ok

   503  Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
  Err:12 http://ppa.launchpad.net/ubuntubudgie-dev/budgie-extras-daily/ubuntu 
jammy/main amd64 budgie-window-shuffler amd64 1.3.0+202202062047~ubuntu22.04.1
    503  Connection closed, check DlMaxRetries [IP: 

[Touch-packages] [Bug 1956473] Re: kernel 5.13.0-23 seems to cause graphics driver issues

[fossfreedom]

This issue might be the same as this issue
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956396

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1956473

Title:
  kernel 5.13.0-23 seems to cause graphics driver issues

Status in Ubuntu Budgie:
  Invalid
Status in xorg package in Ubuntu:
  New

Bug description:
  After updating to kernel 5.13.0-23 I started having issues. Startup
  and logging are extremely slow.

  When I try to run firefox a dialog box shows up saying it is not
  respondig and asking to wait or forcequit. If a wait it eventually
  opens (after over a minute) and seems to work correctly. Similar
  issues occur when trying to run mpv. In some cases the computer might
  even hang completely.

  I am running Ubuntu Budgie 21.10 (budgie-desktop 10.5.3). I also have
  Xmonad installed. Xmonad starts much quicker but has the same issues
  when running applications.

  The problems seem to be solved by booting with kernel 5.13.0-22 or
  kernel 5.13.0-23 with nomodeset.

  I am using an HP computer with an AMD Ryzen 3 cpu with Radeon Vega Mobile Gfx.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroRelease: Ubuntu 21.10
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, 5.5.2.1, 5.13.0-22-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.13.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c3) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Pavilion Laptop 15-cw1xxx [103c:8615]
  InstallationDate: Installed on 2021-11-13 (52 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 
(20211012)
  MachineType: HP HP Pavilion Laptop 15-cw1xxx
  Package: xorg 1:7.7+22ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=bb28a6f2-0184-4836-8a2b-734aa3554528 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Tags:  impish ubuntu
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2021
  dmi.bios.release: 15.47
  dmi.bios.vendor: AMI
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8615
  dmi.board.vendor: HP
  dmi.board.version: 46.30
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 46.30
  dmi.modalias: 
dmi:bvnAMI:bvrF.47:bd08/27/2021:br15.47:efr46.30:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.30:cvnHP:ct10:cvrChassisVersion:sku9UV88LA#AC8:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cw1xxx
  dmi.product.sku: 9UV88LA#AC8
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Touch-packages] [Bug 1956473] Re: kernel 5.13.0-23 seems to cause graphics driver issues

[fossfreedom]

This is filed against Ubuntu Budgie - I think it should have been filed
against xorg or one of the linux kernel packages - but I will defer to
the more experienced here.

For either it is probably missing important logs - so at the very
minimum please run in a terminal

apport-collect 1956473

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

** Changed in: ubuntubudgie
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1956473

Title:
  kernel 5.13.0-23 seems to cause graphics driver issues

Status in Ubuntu Budgie:
  Invalid
Status in xorg package in Ubuntu:
  New

Bug description:
  After updating to kernel 5.13.0-23 I started having issues. Startup
  and logging are extremely slow.

  When I try to run firefox a dialog box shows up saying it is not
  respondig and asking to wait or forcequit. If a wait it eventually
  opens (after over a minute) and seems to work correctly. Similar
  issues occur when trying to run mpv. In some cases the computer might
  even hang completely.

  I am running Ubuntu Budgie 21.10 (budgie-desktop 10.5.3). I also have
  Xmonad installed. Xmonad starts much quicker but has the same issues
  when running applications.

  The problems seem to be solved by booting with kernel 5.13.0-22 or
  kernel 5.13.0-23 with nomodeset.

  I am using an HP computer with an AMD Ryzen 3 cpu with Radeon Vega
  Mobile Gfx.

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


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

[Touch-packages] [Bug 1955434] Re: Driverless printing detection does not work

[fossfreedom]

OK,

I rebooted the printer and the printer was autodiscovered again.

Those cups apparmor denies don't appear to stop discovery ... so they
are noise on the journal log ... minor.

I will mark this as invalid.

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1955434

Title:
  Driverless printing detection does not work

Status in apparmor package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Invalid

Bug description:
  20 Dec 2021 fresh just installed ubuntu budgie jammy daily

  My network HP Photosmart printer is not detected.  In fact the only
  printer found via gnome settings is CUPS-BRF-PRINTER

  This is a regression since both 20.04.3 and 21.10 both find the same
  printer on the network automatically.

  journal -ae | grep cups shows apparmor issues

  dad@dad-MacBookPro:~$ journalctl -ae | grep cups
  Dec 20 23:42:40 dad-MacBookPro audit[711]: AVC apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" 
capability=12  capname="net_admin"
  Dec 20 23:42:40 dad-MacBookPro kernel: audit: type=1400 
audit(1640043760.707:41): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12  
capname="net_admin"
  Dec 20 23:42:48 dad-MacBookPro audit[834]: AVC apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=834 
comm="cups-browsed" capability=23  capname="sys_nice"
  Dec 20 23:42:48 dad-MacBookPro kernel: audit: type=1400 
audit(1640043768.971:42): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23  
capname="sys_nice"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.3.3op2-7ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Dec 20 23:44:41 2021
  InstallationDate: Installed on 2021-12-20 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211220)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Apple Inc. MacBookPro9,2
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=69ee9609-7759-4141-a4ce-e89f3cb9e31a ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Touch-packages] [Bug 1955434] [NEW] Driverless printing detection does not work

[fossfreedom]

Public bug reported:

20 Dec 2021 fresh just installed ubuntu budgie jammy daily

My network HP Photosmart printer is not detected.  In fact the only
printer found via gnome settings is CUPS-BRF-PRINTER

This is a regression since both 20.04.3 and 21.10 both find the same
printer on the network automatically.

journal -ae | grep cups shows apparmor issues

dad@dad-MacBookPro:~$ journalctl -ae | grep cups
Dec 20 23:42:40 dad-MacBookPro audit[711]: AVC apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" 
capability=12  capname="net_admin"
Dec 20 23:42:40 dad-MacBookPro kernel: audit: type=1400 
audit(1640043760.707:41): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12  
capname="net_admin"
Dec 20 23:42:48 dad-MacBookPro audit[834]: AVC apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=834 
comm="cups-browsed" capability=23  capname="sys_nice"
Dec 20 23:42:48 dad-MacBookPro kernel: audit: type=1400 
audit(1640043768.971:42): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23  
capname="sys_nice"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.3.3op2-7ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Mon Dec 20 23:44:41 2021
InstallationDate: Installed on 2021-12-20 (0 days ago)
InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211220)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Apple Inc. MacBookPro9,2
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=69ee9609-7759-4141-a4ce-e89f3cb9e31a ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug jammy

** Description changed:

  20 Dec 2021 fresh just installed ubuntu budgie jammy daily
  
  My network HP Photosmart printer is not detected.  In fact the only
  printer found via gnome settings is CUPS-BRF-PRINTER
+ 
+ This is a regression since both 20.04.3 and 21.10 both find the same
+ printer on the network automatically.
  
  journal -ae | grep cups shows apparmor issues
  
  dad@dad-MacBookPro:~$ journalctl -ae | grep cups
  Dec 20 23:42:40 dad-MacBookPro audit[711]: AVC apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" 
capability=12  capname="net_admin"
  Dec 20 23:42:40 dad-MacBookPro kernel: audit: type=1400 
audit(1640043760.707:41): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12  
capname="net_admin"
  Dec 20 23:42:48 dad-MacBookPro audit[834]: AVC apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=834 
comm="cups-browsed" capability=23  capname="sys_nice"
  Dec 20 23:42:48 dad-MacBookPro kernel: audit: type=1400 
audit(1640043768.971:42): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23  
capname="sys_nice"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.3.3op2-7ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Dec 20 23:44:41 2021
  InstallationDate: Installed on 2021-12-20 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211220)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Apple Inc. MacBookPro9,2
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=69ee9609-7759-4141-a4ce-e89f3cb9e31a ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Touch-packages] [Bug 1931901] Re: Revert background key patch removal breaks dependent packages

[fossfreedom]

Thanks Marco - Ubuntu Budgie packageset doesnt cover this - please can
you sponsor the upload?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1931901

Title:
  Revert background key patch removal breaks dependent packages

Status in gnome-desktop3 package in Ubuntu:
  New
Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  in the package gnome-desktop3 there is a custom ubuntu patch that
  tries to write to the draw-background key that has now been removed in
  gsettings-desktop-schemas 40.0-1ubuntu1

  All packages that depend on the gnome-desktop3 library now crash such
  as budgie-desktop

  Suggestion - either re-add the patch again ... or revert the gnome-
  desktop3 custom patch.

  The latter option changes the symbols so probably I'm guessing a so-
  name version bump is needed and any dependent packages need a rebuild?

  I'll try to locally rebuild gnome-desktop3 without the custom ubuntu
  patch to see what happens with budgie-desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gsettings-desktop-schemas 40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun 14 20:52:16 2021
  InstallationDate: Installed on 2021-06-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614)
  PackageArchitecture: all
  SourcePackage: gsettings-desktop-schemas
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1931901] Re: Revert background key patch removal breaks dependent packages

[fossfreedom]

>From the above - I've attached the alternative solution to remove the
read/write of the draw_background key without removing the patch library
functions


** Patch added: "remove_draw_background_rw.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1931901/+attachment/5505066/+files/remove_draw_background_rw.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1931901

Title:
  Revert background key patch removal breaks dependent packages

Status in gnome-desktop3 package in Ubuntu:
  New
Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  in the package gnome-desktop3 there is a custom ubuntu patch that
  tries to write to the draw-background key that has now been removed in
  gsettings-desktop-schemas 40.0-1ubuntu1

  All packages that depend on the gnome-desktop3 library now crash such
  as budgie-desktop

  Suggestion - either re-add the patch again ... or revert the gnome-
  desktop3 custom patch.

  The latter option changes the symbols so probably I'm guessing a so-
  name version bump is needed and any dependent packages need a rebuild?

  I'll try to locally rebuild gnome-desktop3 without the custom ubuntu
  patch to see what happens with budgie-desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gsettings-desktop-schemas 40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun 14 20:52:16 2021
  InstallationDate: Installed on 2021-06-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614)
  PackageArchitecture: all
  SourcePackage: gsettings-desktop-schemas
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1931901] Re: Revert background key patch removal breaks dependent packages

[fossfreedom]

** Patch removed: "remove-git-revert.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+attachment/5505056/+files/remove-git-revert.debdiff

** Patch added: "remove-git-revert.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+attachment/5505057/+files/remove-git-revert.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1931901

Title:
  Revert background key patch removal breaks dependent packages

Status in gnome-desktop3 package in Ubuntu:
  New
Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  in the package gnome-desktop3 there is a custom ubuntu patch that
  tries to write to the draw-background key that has now been removed in
  gsettings-desktop-schemas 40.0-1ubuntu1

  All packages that depend on the gnome-desktop3 library now crash such
  as budgie-desktop

  Suggestion - either re-add the patch again ... or revert the gnome-
  desktop3 custom patch.

  The latter option changes the symbols so probably I'm guessing a so-
  name version bump is needed and any dependent packages need a rebuild?

  I'll try to locally rebuild gnome-desktop3 without the custom ubuntu
  patch to see what happens with budgie-desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gsettings-desktop-schemas 40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun 14 20:52:16 2021
  InstallationDate: Installed on 2021-06-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614)
  PackageArchitecture: all
  SourcePackage: gsettings-desktop-schemas
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1931901] Re: Revert background key patch removal breaks dependent packages

[fossfreedom]

As discussed with Marco Trevisan on IRC
https://irclogs.ubuntu.com/2021/06/16/%23ubuntu-desktop.html#t14:06 Two
potential solutions here.

Attached is a simple debdiff to drop the git-revert patch without
amending the so-name

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

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: New => Invalid

** Tags removed: block-proposed

** Patch added: "remove-git-revert.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+attachment/5505056/+files/remove-git-revert.debdiff

** Changed in: gnome-desktop3 (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1931901

Title:
  Revert background key patch removal breaks dependent packages

Status in gnome-desktop3 package in Ubuntu:
  New
Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  in the package gnome-desktop3 there is a custom ubuntu patch that
  tries to write to the draw-background key that has now been removed in
  gsettings-desktop-schemas 40.0-1ubuntu1

  All packages that depend on the gnome-desktop3 library now crash such
  as budgie-desktop

  Suggestion - either re-add the patch again ... or revert the gnome-
  desktop3 custom patch.

  The latter option changes the symbols so probably I'm guessing a so-
  name version bump is needed and any dependent packages need a rebuild?

  I'll try to locally rebuild gnome-desktop3 without the custom ubuntu
  patch to see what happens with budgie-desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gsettings-desktop-schemas 40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun 14 20:52:16 2021
  InstallationDate: Installed on 2021-06-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614)
  PackageArchitecture: all
  SourcePackage: gsettings-desktop-schemas
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1931901] Re: Revert background key patch removal breaks dependent packages

[fossfreedom]

Just a follow-up - so recompiling budgie-desktop with a rebuilt gnome-
desktop3 bumped with a so-name of 20 stops budgie crashing.  There are
other issues - but highly likely because a other packages need to be
rebuilt with the bumped so-name package version.

Enclosed a debdiff ( if the soname change is deemed the way forward

** Patch added: "soname.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1931901/+attachment/5504590/+files/soname.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1931901

Title:
  Revert background key patch removal breaks dependent packages

Status in gsettings-desktop-schemas package in Ubuntu:
  New

Bug description:
  in the package gnome-desktop3 there is a custom ubuntu patch that
  tries to write to the draw-background key that has now been removed in
  gsettings-desktop-schemas 40.0-1ubuntu1

  All packages that depend on the gnome-desktop3 library now crash such
  as budgie-desktop

  Suggestion - either re-add the patch again ... or revert the gnome-
  desktop3 custom patch.

  The latter option changes the symbols so probably I'm guessing a so-
  name version bump is needed and any dependent packages need a rebuild?

  I'll try to locally rebuild gnome-desktop3 without the custom ubuntu
  patch to see what happens with budgie-desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gsettings-desktop-schemas 40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun 14 20:52:16 2021
  InstallationDate: Installed on 2021-06-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614)
  PackageArchitecture: all
  SourcePackage: gsettings-desktop-schemas
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1931901/+subscriptions

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

[Touch-packages] [Bug 1931901] [NEW] Revert background key patch removal breaks dependent packages

[fossfreedom]

Public bug reported:

in the package gnome-desktop3 there is a custom ubuntu patch that tries
to write to the draw-background key that has now been removed in
gsettings-desktop-schemas 40.0-1ubuntu1

All packages that depend on the gnome-desktop3 library now crash such as
budgie-desktop

Suggestion - either re-add the patch again ... or revert the gnome-
desktop3 custom patch.

The latter option changes the symbols so probably I'm guessing a so-name
version bump is needed and any dependent packages need a rebuild?

I'll try to locally rebuild gnome-desktop3 without the custom ubuntu
patch to see what happens with budgie-desktop

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gsettings-desktop-schemas 40.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Mon Jun 14 20:52:16 2021
InstallationDate: Installed on 2021-06-14 (0 days ago)
InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614)
PackageArchitecture: all
SourcePackage: gsettings-desktop-schemas
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish package-from-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1931901

Title:
  Revert background key patch removal breaks dependent packages

Status in gsettings-desktop-schemas package in Ubuntu:
  New

Bug description:
  in the package gnome-desktop3 there is a custom ubuntu patch that
  tries to write to the draw-background key that has now been removed in
  gsettings-desktop-schemas 40.0-1ubuntu1

  All packages that depend on the gnome-desktop3 library now crash such
  as budgie-desktop

  Suggestion - either re-add the patch again ... or revert the gnome-
  desktop3 custom patch.

  The latter option changes the symbols so probably I'm guessing a so-
  name version bump is needed and any dependent packages need a rebuild?

  I'll try to locally rebuild gnome-desktop3 without the custom ubuntu
  patch to see what happens with budgie-desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gsettings-desktop-schemas 40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun 14 20:52:16 2021
  InstallationDate: Installed on 2021-06-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614)
  PackageArchitecture: all
  SourcePackage: gsettings-desktop-schemas
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1931901/+subscriptions

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

[Touch-packages] [Bug 1911030] Re: Graphical flashes on a raspi 4 when software rendering is forced

[fossfreedom]

hmm?  No this issue is with the default fkms out of the box overlay - so
nothing is forced here.

What I was also saying that the v3d overlay overcomes the flashes issue
... but only if you copy the overlay into the overlays folder as
upstream pi maintainers say should be happening with the Ubuntu kernel
anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1911030

Title:
  Graphical flashes on a raspi 4 when software rendering is forced

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

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1911030] Re: Graphical flashes on a raspi 4

[fossfreedom]

Daniel - FYI - I raised the issue of the dtoverlay vc4-kms-v3d vs vc4
-kms-v3d-pi4.

TL;DR - the v3d overlay is not activating the accelerated driver.

Upstream confirmed this is an issue with Ubuntu's kernel - I'm hoping
this will be caught and resolved in an upcoming raspi kernel update.

https://github.com/raspberrypi/linux/issues/4080#issuecomment-762709027

Looking forward to testing the v5.10 raspi kernel whenever that is
pushed into proposed

** Bug watch added: github.com/raspberrypi/linux/issues #4080
   https://github.com/raspberrypi/linux/issues/4080

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1911030

Title:
  Graphical flashes on a raspi 4

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

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

Re: [Touch-packages] [Bug 1911030] Re: Graphical flashes on a raspi 4

[fossfreedom]

think we are going to have to wait for the raspi v5.10 kernels - even
after installing the 5.10 arm debs, the raspi ignores them and boots
with the 5.8 raspi kernel.

On Tue, 19 Jan 2021 at 03:00, Daniel van Vugt
<1911...@bugs.launchpad.net> wrote:
>
> Full KMS hardware support is available in newer kernels (5.10.x I think)
> so please try installing a newer arm64 kernel like:
>
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.8/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1911030
>
> Title:
>   Graphical flashes on a raspi 4
>
> Status in mesa package in Ubuntu:
>   New
> Status in xorg-server package in Ubuntu:
>   New
>
> Bug description:
>   Using gnome-shell - activities - see attached video
>
>   Graphics flash - more prominent with more than one app running.
>
>   If you install ubuntu-budgie-desktop and simply move through the menu
>   categories the flashing is even more prominent.
>
>   I'm guessing this is xorg related - but I do note the recent mesa
>   uplift has made things worse
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: xorg 1:7.7+19ubuntu15
>   ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
>   Uname: Linux 5.8.0-1011-raspi aarch64
>   ApportVersion: 2.20.11-0ubuntu55
>   Architecture: arm64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jan 11 16:49:14 2021
>   DistUpgraded: Fresh install
>   DistroCodename: hirsute
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>
>   ImageMediaBuild: 20201225
>   Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
> 3.0 Host Controller
>   ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
> snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
> snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
> smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
> vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
> root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
> splash
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   acpidump:
>
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.103-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911030/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1911030

Title:
  Graphical flashes on a raspi 4

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

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  

Re: [Touch-packages] [Bug 1911030] Re: graphical flashes on a raspi 4

[fossfreedom]

Further testing. Using the KMS driver results in mesa defaulting to
llvmpipe software rendering making YouTube a painful experience.

So the fkms is needed for 3d acceleration but glitchy graphics... ho-
hum.


On Thu, 14 Jan 2021, 16:34 David Mohammed,  wrote:

> Do note.
>
> If I change in /boot/firmware/config.txt the default
>
> dtoverlay=vc4-fkms-v3d
>
> To
>
> dtoverlay=vc4-kms-v3d
>
> Then the graphical issues disappear.  Maybe something to consider?
>
> On Tue, 12 Jan 2021, 02:25 Daniel van Vugt, <1911...@bugs.launchpad.net>
> wrote:
>
>> ** Tags added: raspi raspi-gfx
>>
>> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
>>
>> ** Also affects: mesa (Ubuntu)
>>Importance: Undecided
>>Status: New
>>
>> ** Summary changed:
>>
>> - graphical flashes on a raspi 4
>> + Graphical flashes on a raspi 4
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1911030
>>
>> Title:
>>   Graphical flashes on a raspi 4
>>
>> Status in mesa package in Ubuntu:
>>   New
>> Status in xorg-server package in Ubuntu:
>>   New
>>
>> Bug description:
>>   Using gnome-shell - activities - see attached video
>>
>>   Graphics flash - more prominent with more than one app running.
>>
>>   If you install ubuntu-budgie-desktop and simply move through the menu
>>   categories the flashing is even more prominent.
>>
>>   I'm guessing this is xorg related - but I do note the recent mesa
>>   uplift has made things worse
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 21.04
>>   Package: xorg 1:7.7+19ubuntu15
>>   ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
>>   Uname: Linux 5.8.0-1011-raspi aarch64
>>   ApportVersion: 2.20.11-0ubuntu55
>>   Architecture: arm64
>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>   CasperMD5CheckResult: skip
>>   CompositorRunning: None
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Mon Jan 11 16:49:14 2021
>>   DistUpgraded: Fresh install
>>   DistroCodename: hirsute
>>   DistroVariant: ubuntu
>>   ExtraDebuggingInterest: Yes
>>   GraphicsCard:
>>
>>   ImageMediaBuild: 20201225
>>   Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805
>> USB 3.0 Host Controller
>>   ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0
>> snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1
>> snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60
>> smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0
>> vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1
>> root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet
>> splash
>>   SourcePackage: xorg
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   acpidump:
>>
>>   version.compiz: compiz N/A
>>   version.libdrm2: libdrm2 2.4.103-2
>>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
>>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
>>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
>>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
>> 1:1.0.16-1
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911030/+subscriptions
>>
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1911030

Title:
  Graphical flashes on a raspi 4

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

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 

Re: [Touch-packages] [Bug 1911030] Re: graphical flashes on a raspi 4

[fossfreedom]

Do note.

If I change in /boot/firmware/config.txt the default

dtoverlay=vc4-fkms-v3d

To

dtoverlay=vc4-kms-v3d

Then the graphical issues disappear.  Maybe something to consider?

On Tue, 12 Jan 2021, 02:25 Daniel van Vugt, <1911...@bugs.launchpad.net>
wrote:

> ** Tags added: raspi raspi-gfx
>
> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
>
> ** Also affects: mesa (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Summary changed:
>
> - graphical flashes on a raspi 4
> + Graphical flashes on a raspi 4
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1911030
>
> Title:
>   Graphical flashes on a raspi 4
>
> Status in mesa package in Ubuntu:
>   New
> Status in xorg-server package in Ubuntu:
>   New
>
> Bug description:
>   Using gnome-shell - activities - see attached video
>
>   Graphics flash - more prominent with more than one app running.
>
>   If you install ubuntu-budgie-desktop and simply move through the menu
>   categories the flashing is even more prominent.
>
>   I'm guessing this is xorg related - but I do note the recent mesa
>   uplift has made things worse
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: xorg 1:7.7+19ubuntu15
>   ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
>   Uname: Linux 5.8.0-1011-raspi aarch64
>   ApportVersion: 2.20.11-0ubuntu55
>   Architecture: arm64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jan 11 16:49:14 2021
>   DistUpgraded: Fresh install
>   DistroCodename: hirsute
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>
>   ImageMediaBuild: 20201225
>   Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805
> USB 3.0 Host Controller
>   ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0
> snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1
> snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60
> smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0
> vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1
> root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet
> splash
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   acpidump:
>
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.103-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911030/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1911030

Title:
  Graphical flashes on a raspi 4

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

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  

[Touch-packages] [Bug 1911030] Re: graphical flashes on a raspi 4

[fossfreedom]

** Attachment added: "Video of the issue"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1911030/+attachment/5451810/+files/20210111_164733.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1911030

Title:
  graphical flashes on a raspi 4

Status in xorg package in Ubuntu:
  New

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1911030] [NEW] graphical flashes on a raspi 4

[fossfreedom]

Public bug reported:

Using gnome-shell - activities - see attached video

Graphics flash - more prominent with more than one app running.

If you install ubuntu-budgie-desktop and simply move through the menu
categories the flashing is even more prominent.

I'm guessing this is xorg related - but I do note the recent mesa uplift
has made things worse

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
Uname: Linux 5.8.0-1011-raspi aarch64
ApportVersion: 2.20.11-0ubuntu55
Architecture: arm64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 11 16:49:14 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 
ImageMediaBuild: 20201225
Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 3.0 
Host Controller
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
 
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.103-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: apport-bug arm64 hirsute reproducible single-occurrence ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1911030

Title:
  graphical flashes on a raspi 4

Status in xorg package in Ubuntu:
  New

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

Re: [Touch-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

[fossfreedom]

I can confirm that sound is no longer muted for the ISO and is not muted on
installation.

So thanks and congrats!

On Thu, 22 Oct 2020, 14:30 Launchpad Bug Tracker, <
1897...@bugs.launchpad.net> wrote:

> This bug was fixed in the package alsa-lib - 1.2.3.2-1ubuntu3
>
> ---
> alsa-lib (1.2.3.2-1ubuntu3) groovy; urgency=medium
>
>   * d/p/0001-ucm-add-a-check-for-the-empty-configuration.patch
>   - Fix the failure on init the HDA-Intel sound card, because there
> is no init mixer values in the ucm, the alsa-lib should return
> error and then let alsautils init this sound card in the legacy
> HDA way. (LP: #1897934)
>
>  -- Hui Wang   Thu, 22 Oct 2020 16:46:14 +0800
>
> ** Changed in: alsa-lib (Ubuntu Groovy)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1897934
>
> Title:
>   [SRU][Intel HDA] The initial sound level is set to zero (muted)
>
> Status in Release Notes for Ubuntu:
>   New
> Status in alsa-lib package in Ubuntu:
>   Fix Released
> Status in alsa-lib source package in Focal:
>   Fix Committed
> Status in alsa-lib source package in Groovy:
>   Fix Released
>
> Bug description:
>   [Impact]
>   Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
>   results in the failure on setting the init mixer values for HDA sound
>   card, and users experience the mute of audio after installing the
> 20.10.
>
>   [Fix]
>   Backport a patch from the latest alsa-lib (v1.2.3+)
>
>   [Test]
>   Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm
> /var/lib/alsa/*;
>   sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
>   muted.
>
>   Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm
> /var/lib/alsa/*;
>   sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
>   not muted.
>
>   [Regression Potential]
>   This could make the ucm audio fail to initialize, but this possibility is
>   very low, since this patch is from upstream, and I tested on a ucm based
>   machine, the audio is good.
>
>
>   On boot into the live session - or on first install the sound level is
> muted.
>
>   I have to use GNOME Control Center - Sounds to change to an
>   appropriate level.  Once changed the level chosen is correctly
>   retained between reboots.
>
>   This appears to be a regression from 20.04 where the sound level was
>   set to - I guess - 80% on the live-session/first install
>
>   ProblemType: BugDistroRelease: Ubuntu 20.10
>   Package: pulseaudio 1:13.99.1-1ubuntu11
>   ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
>   Uname: Linux 5.8.0-20-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu48
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
>   CasperMD5CheckResult: pass
>   CasperVersion: 1.452
>   CurrentDesktop: Budgie:GNOME
>   Date: Wed Sep 30 16:03:08 2020
>   LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64
> (20200930)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bashSourcePackage: pulseaudio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/15/2016
>   dmi.bios.release: 15.31
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.1F
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 80BF
>   dmi.board.vendor: HP
>   dmi.board.version: 95.16
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.ec.firmware.release: 95.22
>   dmi.modalias:
> dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV G=N L=CON B=HP
>   dmi.product.name: HP Notebook
>   dmi.product.sku: N9S73EA#ABU
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1897934

Title:
  [SRU][Intel HDA] The initial sound level is set to zero (muted)

Status in Release Notes for Ubuntu:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
  results in the failure on setting the init mixer values for HDA sound
  card, and users experience the mute of audio after installing the 20.10.  

  [Fix]
  Backport a patch from the 

Re: [Touch-packages] [Bug 1897934] Re: The initial sound level is set to zero (mute)

[fossfreedom]

Hi Lukasz,

  on 20.04.1 the sound level is correct (tested on the ISO).

So its only 20.10 where the sound level starts at zero.

On Thu, 1 Oct 2020 at 11:30, Łukasz Zemczak <1897...@bugs.launchpad.net> wrote:
>
> How was this in 20.04? Since you mentioned that it's a regression from
> 18.04 - does this mean we had it like this in focal as well?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1897934
>
> Title:
>   The initial sound level is set to zero (mute)
>
> Status in pulseaudio package in Ubuntu:
>   New
>
> Bug description:
>   On boot into the live session - or on first install the sound level is
>   muted.
>
>   I have to use GNOME Control Center - Sounds to change to an
>   appropriate level.  Once changed the level chosen is correctly
>   retained between reboots.
>
>   This appears to be a regression from 18.04 where the sound level was
>   set to - I guess - 80% on the live-session/first install
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.10
>   Package: pulseaudio 1:13.99.1-1ubuntu11
>   ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
>   Uname: Linux 5.8.0-20-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu48
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
>   CasperMD5CheckResult: pass
>   CasperVersion: 1.452
>   CurrentDesktop: Budgie:GNOME
>   Date: Wed Sep 30 16:03:08 2020
>   LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: pulseaudio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/15/2016
>   dmi.bios.release: 15.31
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.1F
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 80BF
>   dmi.board.vendor: HP
>   dmi.board.version: 95.16
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.ec.firmware.release: 95.22
>   dmi.modalias: 
> dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV G=N L=CON B=HP
>   dmi.product.name: HP Notebook
>   dmi.product.sku: N9S73EA#ABU
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897934/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1897934

Title:
  The initial sound level is set to zero (mute)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On boot into the live session - or on first install the sound level is
  muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 18.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Touch-packages] [Bug 1897934] [NEW] The initial sound level is set to zero (mute)

[fossfreedom]

Public bug reported:

On boot into the live session - or on first install the sound level is
muted.

I have to use GNOME Control Center - Sounds to change to an appropriate
level.  Once changed the level chosen is correctly retained between
reboots.

This appears to be a regression from 18.04 where the sound level was set
to - I guess - 80% on the live-session/first install

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.1-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.452
CurrentDesktop: Budgie:GNOME
Date: Wed Sep 30 16:03:08 2020
LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2016
dmi.bios.release: 15.31
dmi.bios.vendor: Insyde
dmi.bios.version: F.1F
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80BF
dmi.board.vendor: HP
dmi.board.version: 95.16
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 95.22
dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.sku: N9S73EA#ABU
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1897934

Title:
  The initial sound level is set to zero (mute)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On boot into the live session - or on first install the sound level is
  muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 18.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1870814] Re: Lists of Output and Input devices empty on sound settings

[fossfreedom]

Raised it here to note https://github.com/UbuntuBudgie/budgie-
welcome/issues/249

Using Menu - Sound is more logical to access the sound settings

** Bug watch added: github.com/UbuntuBudgie/budgie-welcome/issues #249
   https://github.com/UbuntuBudgie/budgie-welcome/issues/249

** Changed in: ubuntubudgie
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1870814

Title:
  Lists of Output and Input devices empty on sound settings

Status in Ubuntu Budgie:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  While both Sound Input and Output is working well, their respective
  lists on the Sound tab on Settings are empty, preventing from
  adjusting and testing any settings.

  Aspire-A315-55G:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  
  Aspire-A315-55G:~$ budgie-desktop --version
  budgie-desktop 10.5.1
  Copyright © 2014-2019 Budgie Desktop Developers

  
  Aspire-A315-55G:~$ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  Aspire-A315-55G:~$ arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1870814] Re: Lists of Output and Input devices empty on sound settings

[fossfreedom]

I'm guessing this is either a pulseaudio or a gnome-control-center
issue.

Assigning to pulseaudio for the moment.

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

** No longer affects: ubuntubudgie

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1870814

Title:
  Lists of Output and Input devices empty on sound settings

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  While both Sound Input and Output is working well, their respective
  lists on the Sound tab on Settings are empty, preventing from
  adjusting and testing any settings.

  Aspire-A315-55G:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  
  Aspire-A315-55G:~$ budgie-desktop --version
  budgie-desktop 10.5.1
  Copyright © 2014-2019 Budgie Desktop Developers

  
  Aspire-A315-55G:~$ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  Aspire-A315-55G:~$ arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

[fossfreedom]

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

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

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

[Touch-packages] [Bug 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

[fossfreedom]

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

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

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

[Touch-packages] [Bug 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

[fossfreedom]

** Changed in: ubuntu-budgie-meta (Ubuntu)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: New => In Progress

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

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  In Progress
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

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

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

[Touch-packages] [Bug 1847431] Re: Installing ZFS without network is failing

[fossfreedom]

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-budgie-meta (Ubuntu)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

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

Title:
  Installing ZFS without network is failing

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  We need to:
  * seed zfs-initramfs
  * remove apt install from ubiquity zfs script.

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

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

[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option

[fossfreedom]

** Also affects: ubuntu-budgie-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-budgie-meta (Ubuntu)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [FFe] Ubiquity with zfs install option

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Part of the 19.10 feature announcement is zfs experimental support in
  the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
  ubuntu-19-10-an-introduction). We modified ubiquity to present an
  “EXPERIMENTAL” (with warning) ZSYS install option. This option is only
  visible is zfsutils-linux is installed on the system. So, it won't be
  available for derivatives that use ubiquity but do not seed zfsutils-
  linux.

  Update as of 20/09/2019: the plan is to not seed zsys (security review
  will take a while), but to only seed zfsutils-linux. People can then
  opt-in to zsys which should be available by default next cycle.

  This option takes an entire disk and have a fix set of dataset
  installed. There is no support but we need this to make an official
  install option for the next LTS.

  The patch has been created to be as minimal as possible. Partman does
  a full disk partitioning, and then the script zsys-setup the first
  non-ESP partition and replaces with zfs pools.

  4 partitions are created:
  1. if GPT partitioning: ESP partition. This one is done by partman directly.
  2. bpool (for boot), pool with older zfs compatible version to be readable by 
grub)
  3. rpool (for / and userdataset)
  4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on 
moved to the ESP)

  Additionaly if a swap file has been created by ubiquity, it is
  recreated as a ZFS volume. If the script fails to execute, the final
  installation is an ext4 installation on entire disk.

  Note that the implementation is slightly different from the
  specification due to a difficult cohabitation with partman in the
  custom partitioning page.

  Please find attached the MP on ubiquity as well as the package build
  log.

  https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan-
  amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

[fossfreedom]

Can confirm slick-greeter with Ubuntu Budgie is also affected.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1841079

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1821462] Re: Ubuntu 19.04 Desktop:slow boot

[fossfreedom]

** Tags added: disco

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821462

Title:
  Ubuntu 19.04 Desktop:slow boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I have my ubuntu desktop set to boot text only mode.

  it seems a removable hard drive was pplugged into my machine some time ago.
  On every boot the boot takes a minute and a half to search to see if that 
drive is plugged in.

  I ran systemd-analyze blame

  
  Below is my output:

   37.816s apt-daily.service
2.383s dev-sda4.device
2.381s NetworkManager-wait-online.service
1.198s man-db.service
1.112s dev-loop9.device
1.108s dev-loop8.device
1.098s dev-loop4.device
1.083s dev-loop6.device
1.071s dev-loop10.device
1.057s dev-loop13.device
1.057s dev-loop11.device
1.051s dev-loop7.device
1.051s dev-loop12.device
1.046s dev-loop2.device
1.032s dev-loop14.device
1.024s apt-daily-upgrade.service
1.017s snap-core18-782.mount
 988ms snap-vice\x2djz-22.mount
 983ms snap-gnome\x2dcalculator-260.mount
 949ms dev-loop15.device
 930ms dev-loop3.device
 905ms dev-loop5.device
 901ms dev-loop1.device
 899ms dev-loop0.device
 891ms dev-loop16.device
 878ms snap-gnome\x2d3\x2d26\x2d1604-78.mount
 868ms snap-remmina-2831.mount
 855ms snap-gnome\x2dcharacters-139.mount
 845ms snap-youtube\x2ddl\x2dsnap-1.mount
 844ms dev-loop17.device
 834ms snap-gnome\x2d3\x2d26\x2d1604-74.mount
 824ms snap-gnome\x2d3\x2d28\x2d1804-15.mount
 814ms snap-remmina-2823.mount
 803ms snap-gnome\x2dclocks-85.mount
 798ms snap-gnome\x2dcharacters-206.mount
 793ms snap-core-6350.mount
 783ms snap-core-6531.mount
 776ms udisks2.service
 773ms snap-gnome\x2dlogs-45.mount
 763ms snap-vice\x2djz-20.mount
 753ms snap-gtk\x2dcommon\x2dthemes-1198.mount
 744ms snap-core-6405.mount
 734ms snap-vice\x2djz-19.mount
 733ms snap-gnome\x2dcharacters-124.mount
 725ms snap-gtk\x2dcommon\x2dthemes-1122.mount
 719ms dev-loop18.device
 715ms snap-core18-731.mount
 706ms snap-core18-719.mount
 695ms snap-gnome\x2dcalculator-238.mount
 680ms upower.service
 662ms snap-gnome\x2d3\x2d28\x2d1804-19.mount
 646ms dev-loop19.device
 643ms snap-gtk\x2dcommon\x2dthemes-818.mount
 638ms dev-loop23.device
 626ms snap-gnome\x2dlogs-57.mount
 626ms dev-loop26.device
 610ms snap-gnome\x2dsystem\x2dmonitor-70.mount
 596ms dev-loop21.device
 589ms dev-loop25.device
 587ms dev-loop20.device
 583ms dev-loop24.device
 528ms logrotate.service
 523ms systemd-journal-flush.service
 496ms dev-loop22.device
 491ms dev-loop30.device
 490ms dev-loop27.device
 487ms dev-loop28.device
 433ms networkd-dispatcher.service
 427ms snapd.service
 397ms ModemManager.service
 382ms snap-gnome\x2d3\x2d26\x2d1604-82.mount
 379ms snap-gnome\x2dcalculator-352.mount
 369ms snap-remmina-2819.mount
 362ms snap-gnome\x2d3\x2d28\x2d1804-23.mount
 359ms snap-gnome\x2dsystem\x2dmonitor-57.mount
 340ms accounts-daemon.service
 307ms systemd-logind.service
 281ms keyboard-setup.service
 280ms kmod-static-nodes.service
 261ms dev-hugepages.mount
 260ms avahi-daemon.service
 259ms sys-kernel-debug.mount
 259ms ufw.service
 255ms apport-autoreport.service
 251ms systemd-udev-trigger.service
 242ms systemd-modules-load.service
 232ms systemd-journald.service
 230ms fwupd.service
 206ms apport.service
 196ms dev-mqueue.mount
 194ms apparmor.service
 186ms rsyslog.service
 184ms dev-loop29.device
 182ms NetworkManager.service
 181ms systemd-remount-fs.service
 180ms gdm.service
 174ms nmbd.service
 164ms smbd.service
 164ms wpa_supplicant.service
 157ms dev-loop32.device
 154ms networking.service
 142ms thermald.service
 137ms virtualbox.service
 124ms systemd-sysusers.service
   

[Touch-packages] [Bug 1812867] Re: sound from bluetooth device is like vintage when quiting the hibernate

[fossfreedom]

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

** No longer affects: ubuntubudgie

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1812867

Title:
  sound from bluetooth device is like vintage when quiting the hibernate

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi
  I've just noticed this today, with my laptop and my desktop, both under 
Ubuntu Budgie 18.10, all last updates installed if it can help you. Using a USB 
Bluetooth key for both

  After using my wireless speaker (JBL GO for more precision if it's
  needed) within Bluetooth, I lock my computer when I leave my office.
  then I unlock my computer when I'm back to.

  Wanna play some music on the said device. Then I start to play
  music... with somewhat vintage effect on the sound.

  I shutdown the device, start it up and same thing.

  To get a working properly BT, I have to

  - unplug and plug the USB BT key
  - middle click two time on the Bluetooth logo at the top, likely to disable / 
enable it

  and then it work like a charm.

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

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

[Touch-packages] [Bug 1812867] Re: sound from bluetooth device is like vintage when quiting the hibernate

[fossfreedom]

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1812867

Title:
  sound from bluetooth device is like vintage when quiting the hibernate

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

Bug description:
  Hi
  I've just noticed this today, with my laptop and my desktop, both under 
Ubuntu Budgie 18.10, all last updates installed if it can help you. Using a USB 
Bluetooth key for both

  After using my wireless speaker (JBL GO for more precision if it's
  needed) within Bluetooth, I lock my computer when I leave my office.
  then I unlock my computer when I'm back to.

  Wanna play some music on the said device. Then I start to play
  music... with somewhat vintage effect on the sound.

  I shutdown the device, start it up and same thing.

  To get a working properly BT, I have to

  - unplug and plug the USB BT key
  - middle click two time on the Bluetooth logo at the top, likely to disable / 
enable it

  and then it work like a charm.

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

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

[Touch-packages] [Bug 1791378] Re: Try install option from EFI boot displays login screen not the live session

[fossfreedom]

closing - works on final beta isos for UM and UB

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1791378

Title:
  Try install option from EFI boot displays  login screen not the live
  session

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  Testing todays (7th Sept 2018) of cosmic.

  Using virtualbox.  Set to boot the ISO using EFI option.

  Select Try Ubuntu option from ISO Grub.

  Expected to see the live session.  Instead saw the login window.  I
  had to login using ubuntu-budgie / ubuntu-mate to see the live
  session.

  Tested both Ubuntu Mate and Ubuntu Budgie

  Apologies if I raised this against the wrong package!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.395
  CurrentDesktop: Budgie:GNOME
  Date: Fri Sep  7 21:02:15 2018
  LightdmConfig:
   [SeatDefaults]
   allow-guest=false
   autologin-guest=false
   autologin-user=ubuntu-budgie
   autologin-user-timeout=0
  LiveMediaBuild: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1791378] Re: Try install option from EFI boot displays login screen not the live session

[fossfreedom]

Just subscribing Mate Devs  - this still appears to be happening on the
latest ISO's for Ubuntu Mate and Ubuntu Budgie.

Any thoughts where the issue should reside?  Possible thoughts on how to
tackle?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1791378

Title:
  Try install option from EFI boot displays  login screen not the live
  session

Status in lightdm package in Ubuntu:
  New

Bug description:
  Testing todays (7th Sept 2018) of cosmic.

  Using virtualbox.  Set to boot the ISO using EFI option.

  Select Try Ubuntu option from ISO Grub.

  Expected to see the live session.  Instead saw the login window.  I
  had to login using ubuntu-budgie / ubuntu-mate to see the live
  session.

  Tested both Ubuntu Mate and Ubuntu Budgie

  Apologies if I raised this against the wrong package!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.395
  CurrentDesktop: Budgie:GNOME
  Date: Fri Sep  7 21:02:15 2018
  LightdmConfig:
   [SeatDefaults]
   allow-guest=false
   autologin-guest=false
   autologin-user=ubuntu-budgie
   autologin-user-timeout=0
  LiveMediaBuild: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1791378] Re: Try install option from EFI boot displays login screen not the live session

[fossfreedom]

** Tags added: iso-testing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1791378

Title:
  Try install option from EFI boot displays  login screen not the live
  session

Status in lightdm package in Ubuntu:
  New

Bug description:
  Testing todays (7th Sept 2018) of cosmic.

  Using virtualbox.  Set to boot the ISO using EFI option.

  Select Try Ubuntu option from ISO Grub.

  Expected to see the live session.  Instead saw the login window.  I
  had to login using ubuntu-budgie / ubuntu-mate to see the live
  session.

  Tested both Ubuntu Mate and Ubuntu Budgie

  Apologies if I raised this against the wrong package!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.395
  CurrentDesktop: Budgie:GNOME
  Date: Fri Sep  7 21:02:15 2018
  LightdmConfig:
   [SeatDefaults]
   allow-guest=false
   autologin-guest=false
   autologin-user=ubuntu-budgie
   autologin-user-timeout=0
  LiveMediaBuild: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1791378] [NEW] Try install option from EFI boot displays login screen not the live session

[fossfreedom]

Public bug reported:

Testing todays (7th Sept 2018) of cosmic.

Using virtualbox.  Set to boot the ISO using EFI option.

Select Try Ubuntu option from ISO Grub.

Expected to see the live session.  Instead saw the login window.  I had
to login using ubuntu-budgie / ubuntu-mate to see the live session.

Tested both Ubuntu Mate and Ubuntu Budgie

Apologies if I raised this against the wrong package!

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: lightdm 1.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
Uname: Linux 4.17.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
CasperVersion: 1.395
CurrentDesktop: Budgie:GNOME
Date: Fri Sep  7 21:02:15 2018
LightdmConfig:
 [SeatDefaults]
 allow-guest=false
 autologin-guest=false
 autologin-user=ubuntu-budgie
 autologin-user-timeout=0
LiveMediaBuild: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180907)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1791378

Title:
  Try install option from EFI boot displays  login screen not the live
  session

Status in lightdm package in Ubuntu:
  New

Bug description:
  Testing todays (7th Sept 2018) of cosmic.

  Using virtualbox.  Set to boot the ISO using EFI option.

  Select Try Ubuntu option from ISO Grub.

  Expected to see the live session.  Instead saw the login window.  I
  had to login using ubuntu-budgie / ubuntu-mate to see the live
  session.

  Tested both Ubuntu Mate and Ubuntu Budgie

  Apologies if I raised this against the wrong package!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.395
  CurrentDesktop: Budgie:GNOME
  Date: Fri Sep  7 21:02:15 2018
  LightdmConfig:
   [SeatDefaults]
   allow-guest=false
   autologin-guest=false
   autologin-user=ubuntu-budgie
   autologin-user-timeout=0
  LiveMediaBuild: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1790021] Re: Apport warns about perl crashes …many times a day

[fossfreedom]

Duplicate of a private bug
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1743216

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1790021

Title:
  Apport warns about perl crashes …many times a day

Status in perl package in Ubuntu:
  Triaged

Bug description:
  Hi,

  Ubuntu 18.04, I noticed this on Ubuntu-Budgie and Xubuntu ( different
  machines / or partitions ) as far I can tell I did not notice it yet
  on default-ubuntu :

  apport is triggered many times a day because of /usr/bin/perl crashes

  I can't see a pattern to trigger that myself.

  I don't use myself directly perl…

  …I hit continue and presumably sent the bug report.

  Attached an example screenshot from Budgie.

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

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

[Touch-packages] [Bug 1771733] Re: bluetooth device disappears after several minutes of use

[fossfreedom]

Ok. So not a TLP  issue. Subscribing to the bluez package. But may also
be kernel related.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1771733

Title:
  bluetooth device disappears after several minutes of use

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

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any
  important details and I will provide them as soon as possible. Thanks
  for all your hard work with Ubuntu Budgie!

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

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

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

[fossfreedom]

Testing the packaging for budgie-artwork:

I tested the plymouth update for artful by making sure I was fully up-
to-date, enabling proposed, then installing all the binaries created by
budgie-artwork:


budgie-lightdm-theme
budgie-lightdm-theme-base
plymouth-theme-ubuntu-budgie-logo
plymouth-theme-ubuntu-budgie-text
pocillo-icon-theme Tango-esque

Then I unticked proposed.

Ran update-manager -d

Completed and rebooted.  Confirmed can login and budgie plymouth theme
was still visible.

I then repeated the above but this time switched to a TTY and ran do-
release-upgrade -d

I'm setting this to verification-done.


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1750465

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Fix Committed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

[fossfreedom]

** No longer affects: budgie-artwork (Ubuntu Xenial)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1750465

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Fix Committed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago)
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  

[Touch-packages] [Bug 1755442] Re: vpn connection on network applet

[fossfreedom]

"Budgie network applet" is GNOME's network-manager.

Not sure - A fresh install should have installed this package network-
manager-openvpn-gnome.  However, as to your observation I don't know if
there is an actual bug here or if yet another package is required.

I've added "network-manager" to the affects package list.

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  vpn connection on network applet

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

Bug description:
  Ubuntu Budgie 18.04 beta x64

  i added my openVpn config (configuration works fine on other devices). 
  On Budgie network applet, i switched my VPN connection "ON" and absolutely 
nothing happened.
  Switch remains on, but there no info about connecting and my ip remains 
unchanged.

  Regards.

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

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[fossfreedom]

Budgie welcome in its current form will never be run on a Wayland
session. Marked as invalid

** Changed in: budgie-welcome (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1713313

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  New
Status in zulucrypt package in Ubuntu:
  New

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 

[Touch-packages] [Bug 1719136] Re: Ubuntu Budgie - again there is no background picture on try/install

[fossfreedom]

apport information

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

** No longer affects: xorg (Ubuntu)

** Tags added: apport-collected staging

** Description changed:

  the latest daily from which I'm reporting this again has the same
  reoccurance of the observation in \1713662 i.e. no background wallpaper.
  Worse - there is no window decoration at all
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity 17.10.7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep 23 23:06:36 2017
  InstallCmdLine: file=/cdrom/preseed/ubuntu-budgie.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu-budgie   3965 F pulseaudio
+ CasperVersion: 1.384
+ CurrentDesktop: Budgie:GNOME
+ DistroRelease: Ubuntu 17.10
+ IwConfig:
+  lono wireless extensions.
+  
+  enp0s3no wireless extensions.
+ LiveMediaBuild: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170923)
+ Lsusb:
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: innotek GmbH VirtualBox
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 vboxdrmfb
+ ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
+ ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
+ RelatedPackageVersions:
+  linux-restricted-modules-4.13.0-11-generic N/A
+  linux-backports-modules-4.13.0-11-generic  N/A
+  linux-firmware 1.168
+ RfKill:
+  
+ StagingDrivers: vboxvideo
+ Tags:  artful staging
+ Uname: Linux 4.13.0-11-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/01/2006
+ dmi.bios.vendor: innotek GmbH
+ dmi.bios.version: VirtualBox
+ dmi.board.name: VirtualBox
+ dmi.board.vendor: Oracle Corporation
+ dmi.board.version: 1.2
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Oracle Corporation
+ dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
+ dmi.product.family: Virtual Machine
+ dmi.product.name: VirtualBox
+ dmi.product.version: 1.2
+ dmi.sys.vendor: innotek GmbH

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1719136/+attachment/4955916/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1719136

Title:
  Ubuntu Budgie - again there is no background picture on try/install

Status in ubiquity package in Ubuntu:
  New

Bug description:
  the latest daily from which I'm reporting this again has the same
  reoccurance of the observation in #1713662 i.e. no background
  wallpaper.  Worse - there is no window decoration at all

  No idea what has gone wrong this time :(

  the move to kernel 4.13?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity 17.10.7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep 23 23:06:36 2017
  InstallCmdLine: file=/cdrom/preseed/ubuntu-budgie.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713984] [NEW] started raise network interfaces - times out

[fossfreedom]

Public bug reported:

Ubuntu Budgie 17.10 Beta 1 32bit virtualbox install

Test Case AutoResize

choose to encrypt home drive, install all updates and non free codecs
for the installation options

On boot (and every subsequent boot) I see in the boot sequence

started raise network interfaces
networking.service

this sits there for 1 minute 30 seconds before resuming.


On login, fired up chromium and connected to google so the networking is ok.

Question - why the 1 minute 30 seconds delay?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu9
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic i686
ApportVersion: 2.20.6-0ubuntu7
Architecture: i386
CurrentDesktop: Budgie:GNOME
Date: Wed Aug 30 12:24:23 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-30 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha i386 (20170829)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=cfd3c5b9-deb1-4d8f-8d6a-98996d260029 ro quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: apport-bug artful i386 iso-testing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1713984

Title:
  started raise network interfaces - times out

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu Budgie 17.10 Beta 1 32bit virtualbox install

  Test Case AutoResize

  choose to encrypt home drive, install all updates and non free codecs
  for the installation options

  On boot (and every subsequent boot) I see in the boot sequence

  started raise network interfaces
  networking.service

  this sits there for 1 minute 30 seconds before resuming.

  
  On login, fired up chromium and connected to google so the networking is ok.

  Question - why the 1 minute 30 seconds delay?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: Budgie:GNOME
  Date: Wed Aug 30 12:24:23 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha i386 
(20170829)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=cfd3c5b9-deb1-4d8f-8d6a-98996d260029 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1712283] Re: Ubuntu Budgie - Cannot resolve DNS in artful daily

[fossfreedom]

** Description changed:

  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session
- / installed session.
+ / installed session - running on virtualbox 5.1.26.
  
  However I cannot ping google.com - "Name or service not known"
  
  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.
  
  Happy to provide more details - please can someone guide me producing a
  much better bug-report?
+ 
+ 
+ 
+ my zesty VM is working just fine.  As of a week ago, my artful daily was
+ working just fine also.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1712283

Title:
  Ubuntu Budgie - Cannot resolve DNS in artful daily

Status in systemd package in Ubuntu:
  New

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

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

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

[Touch-packages] [Bug 1712283] [NEW] Ubuntu Budgie - Cannot resolve DNS in artful daily

[fossfreedom]

Public bug reported:

in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session
/ installed session.

However I cannot ping google.com - "Name or service not known"

Kind of difficult to run ubuntu-bug here without a fully functioning
network.

Happy to provide more details - please can someone guide me producing a
much better bug-report?

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


** Tags: artful

** Tags added: artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1712283

Title:
  Ubuntu Budgie - Cannot resolve DNS in artful daily

Status in systemd package in Ubuntu:
  New

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

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

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

[Touch-packages] [Bug 1708931] Re: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04

[fossfreedom]

Justas - yes it does have TLP preinstalled.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1708931

Title:
  Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie
  17.04

Status in bluez package in Ubuntu:
  New

Bug description:
  It happens at every reset, after using bluetooth mouse for a few
  minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1 [modified: lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Aug  6 16:42:56 2017
  InstallationDate: Installed on 2017-08-05 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80E5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic 
root=UUID=0585caf9-68a0-4a81-ba3d-c030affa951e ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN97WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.name: 80E5
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: B4:6D:83:B1:A7:87  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:301634 acl:15117 sco:0 events:1578 errors:0
TX bytes:2425 acl:31 sco:0 commands:169 errors:0

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

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

[Touch-packages] [Bug 1708931] Re: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04

[fossfreedom]

just wondering if this is a TLP / bluetooth interaction issue

Can you have a look here - http://linrunner.de/en/tlp/docs/tlp-
faq.html#btusb

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1708931

Title:
  Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie
  17.04

Status in bluez package in Ubuntu:
  New

Bug description:
  It happens at every reset, after using bluetooth mouse for a few
  minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1 [modified: lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Aug  6 16:42:56 2017
  InstallationDate: Installed on 2017-08-05 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80E5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic 
root=UUID=0585caf9-68a0-4a81-ba3d-c030affa951e ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN97WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.name: 80E5
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: B4:6D:83:B1:A7:87  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:301634 acl:15117 sco:0 events:1578 errors:0
TX bytes:2425 acl:31 sco:0 commands:169 errors:0

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

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

[Touch-packages] [Bug 1710978] Re: bluetooth stack looses connection to bluetooth devices

[fossfreedom]

just wondering if this is a TLP / bluetooth interaction issue

Can you have a look here - http://linrunner.de/en/tlp/docs/tlp-
faq.html#btusb

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1710978

Title:
  bluetooth stack looses connection to bluetooth devices

Status in bluez package in Ubuntu:
  New

Bug description:
  In Ubuntu Budgie bluetooth connection is lost in regular intervals
  (5mins).

  Thus my mouse stops working, my headset stops playing music.

  Reconnecting my mouse takes ages requiring a restart of bluez and
  reconnecting the mouse.

  This issue became worse ever since installing budgie (17.04) in May.

  (during writing this, the mouse stopped working again)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Aug 15 23:02:08 2017
  InstallationDate: Installed on 2017-05-25 (81 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:10:9F:D2:25:F8  ACL MTU: 1021:6  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0
TX bytes:14741 acl:474 sco:0 commands:583 errors:0

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

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

[Touch-packages] [Bug 1707392] Re: nm-applet not shown

[fossfreedom]

Things to check.

1. make sure that the system-tray applet is still in the panel (open
raven - budgie settings - panel)

2. look at /etc/xdg/autostart/budgie-desktop-nm-applet.desktop.  The
exec= line should read nm-applet --no-indicator

3. look at /etc/xdg/autostart - if you see the file budgie-desktop-nm-
applet2.desktop then delete that

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

Title:
  nm-applet not shown

Status in network-manager package in Ubuntu:
  New

Bug description:
  after an upgrade of shim-signed the nm-applet does not show in the
  budgie indication bar. Network connections cannot be established from
  the GUI anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jul 29 14:17:45 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-05-25 (64 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  IpRoute:
   default via 10.1.0.254 dev wlp4s0 proto static metric 600 
   10.0.0.0/8 dev wlp4s0 proto kernel scope link src 10.1.0.162 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.73.0/24 dev vmnet1 proto kernel scope link src 192.168.73.1 
   192.168.197.0/24 dev vmnet8 proto kernel scope link src 192.168.197.1
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/1  rsb  
   2e593024-0de5-4795-b3bf-6918a96a15a1  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   vmnet1  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --   
   ---- 

   vmnet8  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/3  --   
   ---- 

   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1693895] Re: ubuntu budgie suspend to ram fails on Macbook Pro Ret

[fossfreedom]

Might be TLP related - to test, enable ubuntu budgie backports via
budgie-welcome recommendations.

Do a full update.  Then uninstall tlp.  This will also uninstall the UB
meta package "ubuntu-budgie-desktop" - dont worry about that.  Before
you upgrade to 17.10 just reinstall that package.

If all works - great - although don't know why TLP/systemd/kernel is
interfering with your suspend.

If suspend is still broken - then yeah - probably either systemd or
kernel related.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1693895

Title:
  ubuntu budgie suspend to ram fails on Macbook Pro Ret

Status in systemd package in Ubuntu:
  New

Bug description:
  A default installation of Ubuntu Budgie fails to suspend to RAM.

  Workaround:
  sudo apt-get install pm-utils

  => Suspend works

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri May 26 20:13:16 2017
  InstallationDate: Installed on 2017-05-25 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1673398] Re: A workaround for making a default monitor in multi monitor environment is not working

[fossfreedom]

not sure gnome-control-center is the correct package here - either
lightdm or lightdm-gtk-greeter is probably the correct packages to
report against.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1673398

Title:
  A workaround for making a default monitor in multi monitor environment
  is not working

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

Bug description:
  In Ubuntu 16.04(and 16.10), to specify a default monitor in multi
  monitor environment is possible by this command.

  $ sudo cp ~/.config/monitors.xml /var/lib/lightdm/.config/

  I don't know it's a right way or not, but it works. But in Ubuntu
  Budgie, that does not work.

  I'm using Ubuntu Budgie 17.04 beta(up to dated) with Nvidia 1050ti graphic 
card, using Nvidia 378 drivers.
  And I have 3 monitors connected to the graphic card.
  I attached a monitors.xml, which works well in Ubuntu 16.04.

  I think Budgie did not check /var/lib/lightdm/.config/monitors.xml or
  ignore it. The log on screen is always shown on another moniotor(not
  on the default monitor I set). I changed the owner/permission of the
  file(/var/lib/lightdm/.config/monitors.xml) in several ways but
  nothing works.

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

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

[Touch-packages] [Bug 1675556] Re: Teclado e sistema

[fossfreedom]

Hi,

  you should file one bug report per issue.  Remember to file against
the correct package.

ubuntu-bug budgie-desktop   for the print-screen issue
ubuntu-bug network-manager  for the wifi issue

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1675556

Title:
  Teclado e sistema

Status in xorg package in Ubuntu:
  New

Bug description:
  A tecla print screen não funciona, e, o sistema operacional quando tem
  uma atualização e pede para eu reiniciar o sistema operacional ele
  dasativa o wifi, tendo que reiniciar o sistema novamente e entrar na
  bios e apertar a tecla esc para sair, e o sistema reiniciar novamente
  para poder entrar no sistema com wifi ativado. entendeu? Obs: Esse
  defeito de inicialização sempre vinha acontecendo nas outras versões,
  ou seja, é um problema crônico. Agora esse problema na tecla print só
  nesta versão 17,04. Tirando esses defeitos o sistema pra mim é um dos
  o melhores,e, o melhor que fizeram.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Mar 23 17:36:06 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity [Radeon HD 
7480D] [1462:7721]
  InstallationDate: Installed on 2017-03-03 (19 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170219)
  MachineType: MSI MS-7721
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=7037c3cd-8eca-49b4-8138-4b24f26ab4f4 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V11.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FM2-A55M-E33 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV11.4:bd10/12/2013:svnMSI:pnMS-7721:pvr2.0:rvnMSI:rnFM2-A55M-E33(MS-7721):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7721
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.75-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1
  xserver.bootTime: Thu Mar 23 16:12:27 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-1ubuntu9

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

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

[Touch-packages] [Bug 1659412] Re: Ubuntu Budgie live session in virtualbox not displayed correctly

[fossfreedom]

ok - changing the display ram allocation from the default 12MB to 128MB
fixes this issue.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1659412

Title:
  Ubuntu Budgie live session in virtualbox not displayed correctly

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Budgie Alpha 2 AMD64 and i386

  see screenshot

  Note - this affect virtualbox only.

  In QEMU the display of the live-session is ok

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

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

[Touch-packages] [Bug 1659412] [NEW] Ubuntu Budgie live session in virtualbox not displayed correctly

[fossfreedom]

Public bug reported:

Ubuntu Budgie Alpha 2 AMD64 and i386

see screenshot

Note - this affect virtualbox only.

In QEMU the display of the live-session is ok

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


** Tags: iso-testing zesty

** Attachment added: "ubuntu budgie [Running] - Oracle VM VirtualBox_735.png"
   
https://bugs.launchpad.net/bugs/1659412/+attachment/4809082/+files/ubuntu%20budgie%20%5BRunning%5D%20-%20Oracle%20VM%20VirtualBox_735.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1659412

Title:
  Ubuntu Budgie live session in virtualbox not displayed correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu Budgie Alpha 2 AMD64 and i386

  see screenshot

  Note - this affect virtualbox only.

  In QEMU the display of the live-session is ok

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

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

[Touch-packages] [Bug 1562415] [NEW] totem euronews (english) produces "the movie could not be read"

[fossfreedom]

Public bug reported:

Using Totem - one of the default channels - Euronews - and then choosing
"Euronews english" produces the above error message.

Please see the enclosed screenshot

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.0-1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Mar 26 22:58:13 2016
InstallationDate: Installed on 2015-12-12 (105 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

** Attachment added: "Screenshot from 2016-03-26 22-57-35.png"
   
https://bugs.launchpad.net/bugs/1562415/+attachment/4612941/+files/Screenshot%20from%202016-03-26%2022-57-35.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1562415

Title:
  totem euronews (english) produces "the movie could not be read"

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Using Totem - one of the default channels - Euronews - and then
  choosing "Euronews english" produces the above error message.

  Please see the enclosed screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar 26 22:58:13 2016
  InstallationDate: Installed on 2015-12-12 (105 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1562415/+subscriptions

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

[Touch-packages] [Bug 1553592] [NEW] 16.04 casper 15_autologin file contains obsolete lightdm configuration

[fossfreedom]

Public bug reported:

/usr/share/initramfs-tools/scripts/casper-bottom/15autologin

the lightdm section of the file contains a lightdm configuration that is
incorrect for 15.10 and later

for example it writes out /root/etc/lightdm/lightdm.conf

according to the lightdm wiki this should be
/root/etc/lightdm/lightdm.conf.d/xyz.conf

Additionally using [SeatDefaults] is wrong.  Again according the wiki
[SeatDefaults] is obsolete and should be [Seat:*]

Think this is probably why manual live CD creators and those who use
Pinguy ISO Builder cannot create a lightdm autologin live CD

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.17.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
Uname: Linux 4.4.0-9-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sat Mar  5 21:07:13 2016
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1553592

Title:
  16.04 casper 15_autologin file contains obsolete lightdm configuration

Status in lightdm package in Ubuntu:
  New

Bug description:
  /usr/share/initramfs-tools/scripts/casper-bottom/15autologin

  the lightdm section of the file contains a lightdm configuration that
  is incorrect for 15.10 and later

  for example it writes out /root/etc/lightdm/lightdm.conf

  according to the lightdm wiki this should be
  /root/etc/lightdm/lightdm.conf.d/xyz.conf

  Additionally using [SeatDefaults] is wrong.  Again according the wiki
  [SeatDefaults] is obsolete and should be [Seat:*]

  Think this is probably why manual live CD creators and those who use
  Pinguy ISO Builder cannot create a lightdm autologin live CD

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.17.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Mar  5 21:07:13 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1422036] [NEW] no support for laptop touchpad under unity8 lxc

[fossfreedom]

Public bug reported:

basic support for a standard laptop touchpad seems to be missing.

The mouse cursor is extremely sensitive - so much so that just touching
the outside areas around the touchpad can cause the mouse cursor to
nervously wander.

Single clicking on a touchpad doesnt seem to invoke click event - or at
least it appeared it didnt because I couldnt get passed the initial
phone intro asking me to swipe rightwards to show the launcher.

Why the phone intro is being displayed in desktop mode is baffling -
however - given that I dont own a mouse, with no touchpad support, it
makes testing unity8 more than a bit difficult.

Any plans to introduce such support so that I can help continue testing?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity8 (not installed)
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 14 23:47:06 2015
SourcePackage: unity8
UpgradeStatus: Upgraded to trusty on 2014-08-24 (174 days ago)

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


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1422036

Title:
  no support for laptop touchpad under unity8 lxc

Status in unity8 package in Ubuntu:
  New

Bug description:
  basic support for a standard laptop touchpad seems to be missing.

  The mouse cursor is extremely sensitive - so much so that just
  touching the outside areas around the touchpad can cause the mouse
  cursor to nervously wander.

  Single clicking on a touchpad doesnt seem to invoke click event - or
  at least it appeared it didnt because I couldnt get passed the initial
  phone intro asking me to swipe rightwards to show the launcher.

  Why the phone intro is being displayed in desktop mode is baffling -
  however - given that I dont own a mouse, with no touchpad support, it
  makes testing unity8 more than a bit difficult.

  Any plans to introduce such support so that I can help continue
  testing?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 14 23:47:06 2015
  SourcePackage: unity8
  UpgradeStatus: Upgraded to trusty on 2014-08-24 (174 days ago)

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

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

[Touch-packages] [Bug 1421875] [NEW] gnome headerbar apps show buttons with a relief border

[fossfreedom]

Public bug reported:

Pictures paint a thousand words

The first shows a gnome based app which has buttons in the headerbar.
The theme is adwaita.

The whole header bar matches the minimize/maximize and close buttons -
i.e. flat appearance.

Compare in the second attachment screenshot - the same headerbar.  The
buttons in ambiance show a relief border whereas the same
minimize/maximize and close buttons are all flat.  This is visually
annoying - all headerbar based apps should be consistent and should not
have buttons with a relief border

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: light-themes 14.04+15.04.20150212-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 13 23:31:29 2015
InstallationDate: Installed on 2014-11-27 (78 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141123)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

** Attachment added: with adwaita theme
   
https://bugs.launchpad.net/bugs/1421875/+attachment/4319087/+files/Screenshot%20from%202015-02-13%2023%3A26%3A56.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1421875

Title:
  gnome headerbar apps show buttons with a relief border

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Pictures paint a thousand words

  The first shows a gnome based app which has buttons in the headerbar.
  The theme is adwaita.

  The whole header bar matches the minimize/maximize and close buttons -
  i.e. flat appearance.

  Compare in the second attachment screenshot - the same headerbar.  The
  buttons in ambiance show a relief border whereas the same
  minimize/maximize and close buttons are all flat.  This is visually
  annoying - all headerbar based apps should be consistent and should
  not have buttons with a relief border

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: light-themes 14.04+15.04.20150212-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 13 23:31:29 2015
  InstallationDate: Installed on 2014-11-27 (78 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141123)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1421875] Re: gnome headerbar apps show buttons with a relief border

[fossfreedom]

** Attachment added: with ambiance theme
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1421875/+attachment/4319090/+files/Screenshot%20from%202015-02-13%2023%3A26%3A28.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1421875

Title:
  gnome headerbar apps show buttons with a relief border

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Pictures paint a thousand words

  The first shows a gnome based app which has buttons in the headerbar.
  The theme is adwaita.

  The whole header bar matches the minimize/maximize and close buttons -
  i.e. flat appearance.

  Compare in the second attachment screenshot - the same headerbar.  The
  buttons in ambiance show a relief border whereas the same
  minimize/maximize and close buttons are all flat.  This is visually
  annoying - all headerbar based apps should be consistent and should
  not have buttons with a relief border

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: light-themes 14.04+15.04.20150212-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 13 23:31:29 2015
  InstallationDate: Installed on 2014-11-27 (78 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141123)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1404730] [NEW] software updater icon displayed in Dash is too large compared to others

[fossfreedom]

Public bug reported:

Please see the enclosed screenshot - the software updater icon is
oversized compared to others displayed in Dash

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity 7.3.1+15.04.20141216-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion: 2.15.1-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Sun Dec 21 21:13:29 2014
InstallationDate: Installed on 2014-11-27 (24 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141123)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

** Attachment added: Screenshot from 2014-12-21 21:13:05.png
   
https://bugs.launchpad.net/bugs/1404730/+attachment/4285403/+files/Screenshot%20from%202014-12-21%2021%3A13%3A05.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1404730

Title:
  software updater icon displayed in Dash is too large compared to
  others

Status in unity package in Ubuntu:
  New

Bug description:
  Please see the enclosed screenshot - the software updater icon is
  oversized compared to others displayed in Dash

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20141216-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Dec 21 21:13:29 2014
  InstallationDate: Installed on 2014-11-27 (24 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141123)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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