Re: [Desktop-packages] [Bug 2060659] Re: X11 fractional scaling support is missing in 46.0

[fossfreedom]

Marco,

  this is a temporary issue for 24.04 only.  In 24.10 (hopefully) we
will drop this current version of magpie and X11 support- so there
shouldn't be any dependency links.

On Thu, 18 Apr 2024 at 15:05, Marco Trevisan (Treviño)
<2060...@bugs.launchpad.net> wrote:
>
> fossfreedom, probably magpie should use a different schema name though
> and *always* conflict with mutter, no?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2060659
>
> Title:
>   X11 fractional scaling support is missing in 46.0
>
> Status in magpie package in Ubuntu:
>   New
> Status in mutter package in Ubuntu:
>   In Progress
>
> Bug description:
>   X11 fractional scaling support is missing in mutter/gnome-shell 46.0
>
>   https://salsa.debian.org/gnome-
>   team/mutter/-/commit/414010ddef06757000175c30238371739199d29a
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/magpie/+bug/2060659/+subscriptions
>

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

Title:
  X11 fractional scaling support is missing in 46.0

Status in magpie package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  X11 fractional scaling support is missing in mutter/gnome-shell 46.0

  https://salsa.debian.org/gnome-
  team/mutter/-/commit/414010ddef06757000175c30238371739199d29a

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


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

[Desktop-packages] [Bug 2060659] Re: X11 fractional scaling support is missing in 46.0

[fossfreedom]

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

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

Title:
  X11 fractional scaling support is missing in 46.0

Status in magpie package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  X11 fractional scaling support is missing in mutter/gnome-shell 46.0

  https://salsa.debian.org/gnome-
  team/mutter/-/commit/414010ddef06757000175c30238371739199d29a

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


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

[Desktop-packages] [Bug 2060659] Re: X11 fractional scaling support is missing in 46.0

[fossfreedom]

> I did however had to use --force-overwrite on mutter-common since
there was a conflict with the file
./usr/share/glib-2.0/schemas/org.gnome.mutter.gschema.xml that is also
provided by magpie-common. This could also have been a side effect from
my testing. What I can tell there's still that conflict.

Have discussed this with jbicha on matrix - magpie needs to revert the
schema changes here to accommodate - and the release needs to be
coordinated.

https://launchpad.net/ubuntu/+source/magpie/0.9.3-0ubuntu6

** Tags added: block-proposed

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

Title:
  X11 fractional scaling support is missing in 46.0

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  X11 fractional scaling support is missing in mutter/gnome-shell 46.0

  https://salsa.debian.org/gnome-
  team/mutter/-/commit/414010ddef06757000175c30238371739199d29a

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


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

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2059335] Re: FFe: Sync file-roller 44-2 (main) from Debian unstable (main)

[fossfreedom]

I can confirm the revised file-roller works nicely with nemo + nemo-
fileroller.

Tested compress options, extract here and open in file-roller.

Happy to support this proposal moving forward.

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

Title:
  FFe: Sync file-roller 44-2 (main) from Debian unstable (main)

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Freeze Exception Request
  
  I request to sync file-roller 44 from Debian. The largest change is that 
file-roller was ported from GTK3 to GTK4. However, this is also the strongest 
argument to doing the update: it will be significantly easier to backport 
bugfixes if Ubuntu 24.04 LTS is using the GTK4 version rather than by trying to 
port those fixes to GTK3.

  Although switching apps to GTK4 was problematic for Ubuntu 22.04 LTS,
  a significant number of apps these days are GTK4 and at least all the
  Ubuntu desktop flavors that ship file-roller do have appropriate basic
  themeing for GTK4 apps.

  Potential Problems
  --
  The new release drops the AppMenu option. In other words, showing a 
traditional File/Edit/View menu instead of a hamburger ☰ menu.

  Out of the desktop flavors that ship file-roller, it looks like this
  feature was only used in Ubuntu Unity. Notably Ubuntu Unity ships many
  MATE apps because of Unity's unique "global menu" feature. MATE does
  offer an older GTK3 file-roller fork named engrampa. If this feature
  is important to Ubuntu Unity, I recommend they switch to engrampa.

  However, Ubuntu Unity ships nemo as the default file browser. nemo
  recommends nemo-fileroller which Depends: file-roller. (Instead of
  engrampa). There is another nautilus fork named caja which Ubuntu MATE
  ships.

  Why This Didn't Happen Sooner
  
  file-roller 44 Beta was released March 10 but Feature Freeze was February 29 
so this already missed the Feature Freeze deadline.

  file-roller 44.0 was released last week

  Affected Desktop Flavors
  -
  - Ubuntu Desktop (although only in the "full" install option, but minimal is 
the default for new installs now)
  - Ubuntu Cinnamon
  - Ubuntu Unity

  Upstream changes
  -

  https://gitlab.gnome.org/GNOME/file-roller/-/blob/44/NEWS

  https://gitlab.gnome.org/GNOME/file-roller/-/compare/43.1...44

  Changelog entries since current noble version 43.1-1build2:
  -

  file-roller (44-2) unstable; urgency=medium

* Cherry-pick 5 patches to fix various issues

   -- Jeremy Bícha   Tue, 02 Apr 2024 14:45:40 -0400

  file-roller (44-1) unstable; urgency=medium

    * New upstream release (LP: #2059335)
    * Drop patch applied in new release
    * Depend on 7zip instead of p7zip on Debian (Closes: #1042447)

   -- Jeremy Bícha   Wed, 27 Mar 2024 17:38:22 -0400

  file-roller (44~beta-1) unstable; urgency=medium

    * New upstream release
    * debian/control: Bump minimum required libglib2.0-dev to 2.38.0
    * debian/control: Update to build with GTK 4, following upstream
    * debian/patches/ftbfs-gdkscreen.patch: Add patch to drop call to
  deprecated and removed GdkScreen-related method causing FTBFS
  with -Werror=implicit-function-declaration
    * debian/copyright: Drop superfluous 'Files: src/egg*' pattern (and
  accompanying license text) for unused files that were previously
  dropped upstream

   -- Amin Bandali   Thu, 21 Mar 2024 15:49:58 -0400

  Build log
  --
  
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ubuntu-desktop-gnome/+packages

  Testing Done
  
  I have verified that file-roller 44 does work on Ubuntu Desktop, Ubuntu 
Budgie, Ubuntu Cinnamon, and Ubuntu Unity

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


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to firefox 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2059335] Re: FFe: Sync file-roller 44-1 (main) from Debian unstable (main)

[fossfreedom]

I have done a quick test with ubuntu budgie and nemo.

For some unknown reason, the right-click compress option no longer
compresses the chosen folder.  This worked with the gtk3 version.

Extracting an archive does work and correctly uncompresses the tar.gz

Potentially there is a compatibility issue between nemo-fileroller and
the new fileroller.

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

Title:
  FFe: Sync file-roller 44-1 (main) from Debian unstable (main)

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Freeze Exception Request
  
  I request to sync file-roller 44 from Debian. The largest change is that 
file-roller was ported from GTK3 to GTK4. However, this is also the strongest 
argument to doing the update: it will be significantly easier to backport 
bugfixes if Ubuntu 24.04 LTS is using the GTK4 version rather than by trying to 
port those fixes to GTK3.

  Although switching apps to GTK4 was problematic for Ubuntu 22.04 LTS,
  a significant number of apps these days are GTK4 and at least all the
  Ubuntu desktop flavors that ship file-roller do have appropriate basic
  themeing for GTK4 apps.

  Potential Problems
  --
  The new release drops the AppMenu option. In other words, showing a 
traditional File/Edit/View menu instead of a hamburger ☰ menu.

  Out of the desktop flavors that ship file-roller, it looks like this
  feature was only used in Ubuntu Unity. Notably Ubuntu Unity ships many
  MATE apps because of Unity's unique "global menu" feature. MATE does
  offer an older GTK3 file-roller fork named engrampa. If this feature
  is important to Ubuntu Unity, I recommend they switch to engrampa.

  However, Ubuntu Unity ships nemo as the default file browser. nemo
  recommends nemo-fileroller which Depends: file-roller. (Instead of
  engrampa). There is another nautilus fork named caja which Ubuntu MATE
  ships.

  Why This Didn't Happen Sooner
  
  file-roller 44 Beta was released March 10 but Feature Freeze was February 29 
so this already missed the Feature Freeze deadline.

  file-roller 44.0 was released last week

  Affected Desktop Flavors
  -
  - Ubuntu Desktop (although only in the "full" install option, but minimal is 
the default for new installs now)
  - Ubuntu Cinnamon
  - Ubuntu Unity

  Upstream changes
  -

  https://gitlab.gnome.org/GNOME/file-roller/-/blob/44/NEWS

  https://gitlab.gnome.org/GNOME/file-roller/-/compare/43.1...44

  Changelog entries since current noble version 43.1-1build2:
  -

  file-roller (44-1) unstable; urgency=medium

    * New upstream release (LP: #2059335)
    * Drop patch applied in new release
    * Depend on 7zip instead of p7zip on Debian (Closes: #1042447)

   -- Jeremy Bícha   Wed, 27 Mar 2024 17:38:22 -0400

  file-roller (44~beta-1) unstable; urgency=medium

    * New upstream release
    * debian/control: Bump minimum required libglib2.0-dev to 2.38.0
    * debian/control: Update to build with GTK 4, following upstream
    * debian/patches/ftbfs-gdkscreen.patch: Add patch to drop call to
  deprecated and removed GdkScreen-related method causing FTBFS
  with -Werror=implicit-function-declaration
    * debian/copyright: Drop superfluous 'Files: src/egg*' pattern (and
  accompanying license text) for unused files that were previously
  dropped upstream

   -- Amin Bandali   Thu, 21 Mar 2024 15:49:58 -0400

  Build log
  --
  
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ubuntu-desktop-gnome/+packages

  Testing Done
  
  I have verified that file-roller 44 does work on Ubuntu Desktop, Ubuntu 
Budgie, Ubuntu Cinnamon, and Ubuntu Unity

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


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

[Desktop-packages] [Bug 2058847] Re: budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0

[fossfreedom]

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

** No longer affects: budgie-desktop (Ubuntu)

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

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

Title:
  budgie-wm crashes immediately when mutter-common has been upgraded to
  version 46.0

Status in magpie package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  New

Bug description:
  mutter-common 46.0 packages remove the org.gnome.mutter.x11 gconf
  schema.  This causes budgie-wm to crash immediately on login.

  Downgrading to 45.3 fixes everything.

  $ apt policy mutter-common
  mutter-common:
Installed: 45.3-1ubuntu1
Candidate: 46.0-1ubuntu1
Version table:
   46.0-1ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 
Packages
  500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main i386 
Packages
   *** 45.3-1ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  500 http://ch.archive.ubuntu.com/ubuntu noble/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: budgie-core 10.9.1-3ubuntu1
  Uname: Linux 6.8.1-060801-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Sun Mar 24 16:00:24 2024
  InstallationDate: Installed on 2022-03-19 (736 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 
(20211012)
  SourcePackage: budgie-desktop
  UpgradeStatus: Upgraded to noble on 2023-11-03 (142 days ago)

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


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

[Desktop-packages] [Bug 2058847] Re: budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0

[fossfreedom]

This is because magpie has a dependency on mutter-common.

The schema comes from the mutter ubuntu x11 patch which has been
temporarily disabled

https://launchpad.net/ubuntu/+source/mutter/+changelog

Once it has been readded then things will work correctly

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

** Changed in: budgie-desktop (Ubuntu)
   Status: New => Triaged

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

Title:
  budgie-wm crashes immediately when mutter-common has been upgraded to
  version 46.0

Status in budgie-desktop package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  New

Bug description:
  mutter-common 46.0 packages remove the org.gnome.mutter.x11 gconf
  schema.  This causes budgie-wm to crash immediately on login.

  Downgrading to 45.3 fixes everything.

  $ apt policy mutter-common
  mutter-common:
Installed: 45.3-1ubuntu1
Candidate: 46.0-1ubuntu1
Version table:
   46.0-1ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 
Packages
  500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main i386 
Packages
   *** 45.3-1ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  500 http://ch.archive.ubuntu.com/ubuntu noble/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: budgie-core 10.9.1-3ubuntu1
  Uname: Linux 6.8.1-060801-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Sun Mar 24 16:00:24 2024
  InstallationDate: Installed on 2022-03-19 (736 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 
(20211012)
  SourcePackage: budgie-desktop
  UpgradeStatus: Upgraded to noble on 2023-11-03 (142 days ago)

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


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

[Desktop-packages] [Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers

[fossfreedom]

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

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

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in budgie-artwork package in Ubuntu:
  Fix Committed
Status in budgie-desktop-environment package in Ubuntu:
  Fix Committed
Status in budgie-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in ubuntu-unity-backgrounds package in Ubuntu:
  Confirmed
Status in ubuntu-wallpapers package in Ubuntu:
  Triaged
Status in ubuntucinnamon-environment package in Ubuntu:
  Fix Committed
Status in ubuntucinnamon-wallpapers package in Ubuntu:
  Fix Released
Status in ubuntukylin-wallpapers package in Ubuntu:
  In Progress
Status in ubuntustudio-default-settings package in Ubuntu:
  Fix Released
Status in ubuntustudio-look package in Ubuntu:
  Fix Released

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

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


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

[Desktop-packages] [Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers

[fossfreedom]

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

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

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

** Changed in: budgie-wallpapers (Ubuntu)
   Status: Triaged => In Progress

** Changed in: budgie-desktop-environment (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in budgie-artwork package in Ubuntu:
  In Progress
Status in budgie-desktop-environment package in Ubuntu:
  In Progress
Status in budgie-wallpapers package in Ubuntu:
  In Progress
Status in ubuntu-unity-backgrounds package in Ubuntu:
  Confirmed
Status in ubuntu-wallpapers package in Ubuntu:
  Triaged
Status in ubuntucinnamon-environment package in Ubuntu:
  Confirmed
Status in ubuntucinnamon-wallpapers package in Ubuntu:
  Fix Committed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in ubuntustudio-look package in Ubuntu:
  Fix Committed

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

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


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

[Desktop-packages] [Bug 2058136] Re: Sync udisks2 2.10.1-6 (main) from Debian unstable (main)

[fossfreedom]

Hi Robie

ok - I'm asking for a sync and merge.

enc is the debdiff from what I tested via a grab-merge

I also created a test PPA building against noble-proposed for all
architectures to check the build status.

https://launchpad.net/~ubuntubudgie-
dev/+archive/ubuntu/udisks2/+packages

** Patch added: "udisks.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2058136/+attachment/5756865/+files/udisks.debdiff

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

Title:
  Sync udisks2 2.10.1-6 (main) from Debian unstable (main)

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Please sync udisks2 2.10.1-6 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Don't build with -Wl,-Bsymbolic-functions. It breaks module loading, as
  it confuses GObject's type loading cache: "cannot register existing type
  'UDisksDaemon'". (Patch also applied to Debian packaging git, can be
  synced next time). (LP: #2040488)
* Fix an event loop that can occur when ID_PART_TABLE_TYPE is not set for a
  device and that device has partitions.  (LP: #2037569)
* Fix an event loop that can occur when ID_PART_TABLE_TYPE is not set for a
  device and that device has partitions.  (LP: #2037569)

  The existing ubuntu noble-proposed FTBFS

  The -Wl, -Bsymbolic-functions is part of debian as per the -6
  changelog entry

  I did a grab-merge of udisks then built with both the debian
  tests-Fix-targetcli_config.json.patch and the ubuntu 
  lp-2037569-skip-bd_part_get_disk_spec.patch - using sbuild this successfully
  builds in noble-proposed.

  Can I suggest ubuntu adds the debian delta as well as the ubuntu delta patch
  as part of this sync & merge

  Changelog entries since current noble version 2.10.1-1ubuntu3:

  udisks2 (2.10.1-6) unstable; urgency=medium

[ Martin Pitt ]
* Don't build with -Wl,-Bsymbolic-functions.
  It breaks module loading, as it confuses GObject's type loading cache:
  "cannot register existing type 'UDisksDaemon'".
  Ubuntu enables this linker flag by default, no-op for Debian.
  (LP: #2040488)

[ Michael Biebl ]
* Drop python3-distutils Depends from debian/tests/control.
  No longer needed since 2.10.0. (Closes: #1065991)
* Build-depend on pkgconf instead of pkg-config

   -- Michael Biebl   Mon, 11 Mar 2024 23:19:45 +0100

  udisks2 (2.10.1-5) unstable; urgency=medium

* tests: Fix targetcli_config.json.
  Not all attributes are available anymore in newer kernel versions.

   -- Michael Biebl   Wed, 10 Jan 2024 12:28:58 +0100

  udisks2 (2.10.1-4) unstable; urgency=medium

* Stop moving files from /usr/sbin to /sbin.
  With merged-/usr being mandatory, this is no longer necessary.

   -- Michael Biebl   Mon, 27 Nov 2023 05:40:54 +0100

  udisks2 (2.10.1-3) unstable; urgency=medium

* Replace udev Build-Depends with systemd-dev.
  The new systemd-dev package ships udev.pc and systemd.pc which provides
  the paths for udevdir/systemdsystemunitdir/tmpfilesdir.

   -- Michael Biebl   Mon, 20 Nov 2023 23:51:36 +0100

  udisks2 (2.10.1-2) unstable; urgency=medium

* Move systemd services files and udev rules to /usr.
  Add a corresponding versioned Build-Depends on debhelper (>= 13.11.6) to
  ensure we have a recent enough dh_installsystemd.

   -- Michael Biebl   Sat, 21 Oct 2023 14:39:24 +0200

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


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

[Desktop-packages] [Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers

[fossfreedom]

Add budgie-desktop-environment since there are branding aspects that
need updating to reflect the noble mascot

** Also affects: budgie-desktop-environment (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: budgie-desktop-environment (Ubuntu)
   Status: New => Triaged

** Changed in: budgie-desktop-environment (Ubuntu)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

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

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in budgie-desktop-environment package in Ubuntu:
  Triaged
Status in budgie-wallpapers package in Ubuntu:
  Triaged
Status in ubuntu-wallpapers package in Ubuntu:
  Triaged
Status in ubuntucinnamon-environment package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Triaged
Status in ubuntustudio-look package in Ubuntu:
  Triaged

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop-environment/+bug/2056591/+subscriptions


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

[Desktop-packages] [Bug 2058136] [NEW] Sync udisks2 2.10.1-6 (main) from Debian unstable (main)

[fossfreedom]

Public bug reported:

Please sync udisks2 2.10.1-6 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Don't build with -Wl,-Bsymbolic-functions. It breaks module loading, as
it confuses GObject's type loading cache: "cannot register existing type
'UDisksDaemon'". (Patch also applied to Debian packaging git, can be
synced next time). (LP: #2040488)
  * Fix an event loop that can occur when ID_PART_TABLE_TYPE is not set for a
device and that device has partitions.  (LP: #2037569)
  * Fix an event loop that can occur when ID_PART_TABLE_TYPE is not set for a
device and that device has partitions.  (LP: #2037569)

The existing ubuntu noble-proposed FTBFS

The -Wl, -Bsymbolic-functions is part of debian as per the -6 changelog
entry

I did a grab-merge of udisks then built with both the debian
tests-Fix-targetcli_config.json.patch and the ubuntu 
lp-2037569-skip-bd_part_get_disk_spec.patch - using sbuild this successfully
builds in noble-proposed.

Can I suggest ubuntu adds the debian delta as well as the ubuntu delta patch
as part of this sync & merge

Changelog entries since current noble version 2.10.1-1ubuntu3:

udisks2 (2.10.1-6) unstable; urgency=medium

  [ Martin Pitt ]
  * Don't build with -Wl,-Bsymbolic-functions.
It breaks module loading, as it confuses GObject's type loading cache:
"cannot register existing type 'UDisksDaemon'".
Ubuntu enables this linker flag by default, no-op for Debian.
(LP: #2040488)

  [ Michael Biebl ]
  * Drop python3-distutils Depends from debian/tests/control.
No longer needed since 2.10.0. (Closes: #1065991)
  * Build-depend on pkgconf instead of pkg-config

 -- Michael Biebl   Mon, 11 Mar 2024 23:19:45 +0100

udisks2 (2.10.1-5) unstable; urgency=medium

  * tests: Fix targetcli_config.json.
Not all attributes are available anymore in newer kernel versions.

 -- Michael Biebl   Wed, 10 Jan 2024 12:28:58 +0100

udisks2 (2.10.1-4) unstable; urgency=medium

  * Stop moving files from /usr/sbin to /sbin.
With merged-/usr being mandatory, this is no longer necessary.

 -- Michael Biebl   Mon, 27 Nov 2023 05:40:54 +0100

udisks2 (2.10.1-3) unstable; urgency=medium

  * Replace udev Build-Depends with systemd-dev.
The new systemd-dev package ships udev.pc and systemd.pc which provides
the paths for udevdir/systemdsystemunitdir/tmpfilesdir.

 -- Michael Biebl   Mon, 20 Nov 2023 23:51:36 +0100

udisks2 (2.10.1-2) unstable; urgency=medium

  * Move systemd services files and udev rules to /usr.
Add a corresponding versioned Build-Depends on debhelper (>= 13.11.6) to
ensure we have a recent enough dh_installsystemd.

 -- Michael Biebl   Sat, 21 Oct 2023 14:39:24 +0200

** Affects: udisks2 (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: udisks2 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync udisks2 2.10.1-6 (main) from Debian unstable (main)

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Please sync udisks2 2.10.1-6 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Don't build with -Wl,-Bsymbolic-functions. It breaks module loading, as
  it confuses GObject's type loading cache: "cannot register existing type
  'UDisksDaemon'". (Patch also applied to Debian packaging git, can be
  synced next time). (LP: #2040488)
* Fix an event loop that can occur when ID_PART_TABLE_TYPE is not set for a
  device and that device has partitions.  (LP: #2037569)
* Fix an event loop that can occur when ID_PART_TABLE_TYPE is not set for a
  device and that device has partitions.  (LP: #2037569)

  The existing ubuntu noble-proposed FTBFS

  The -Wl, -Bsymbolic-functions is part of debian as per the -6
  changelog entry

  I did a grab-merge of udisks then built with both the debian
  tests-Fix-targetcli_config.json.patch and the ubuntu 
  lp-2037569-skip-bd_part_get_disk_spec.patch - using sbuild this successfully
  builds in noble-proposed.

  Can I suggest ubuntu adds the debian delta as well as the ubuntu delta patch
  as part of this sync & merge

  Changelog entries since current noble version 2.10.1-1ubuntu3:

  udisks2 (2.10.1-6) unstable; urgency=medium

[ Martin Pitt ]
* Don't build with -Wl,-Bsymbolic-functions.
  It breaks module loading, as it confuses GObject's type loading cache:
  "cannot register existing type 'UDisksDaemon'".
  Ubuntu enables this linker flag by default, no-op for Debian.
  (LP: #2040488)

[ Michael Biebl ]
* Drop python3-distutils Depends from debian/tests/control.
  No longer needed since 2.10.0. (Closes: #1065991)
* Build-depend on pkgconf instead of pkg-config

   -- Michael Biebl   Mon, 11 Mar 2024 23:19:45 +0100

  

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers

[fossfreedom]

** Changed in: budgie-wallpapers (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in budgie-wallpapers package in Ubuntu:
  Triaged
Status in ubuntu-wallpapers package in Ubuntu:
  Triaged
Status in ubuntustudio-look package in Ubuntu:
  Triaged

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

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


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

[Desktop-packages] [Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers

[fossfreedom]

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

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in budgie-wallpapers package in Ubuntu:
  Triaged
Status in ubuntu-wallpapers package in Ubuntu:
  Triaged
Status in ubuntustudio-look package in Ubuntu:
  Triaged

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

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


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

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems

[fossfreedom]

Reassigning to xorg-server initially.

Ubuntu doesn't have gldriver-test to enable xorg desktops to work on a
raspi5.

So is there an equivalent package for Ubuntu or should gldriver-test be
added to the ubuntu repo?

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

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

Title:
  mantic on raspberry5: x and/or lightdm problems

Status in linux-raspi package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  New

Bug description:
  running mantic on raspberry5, graphical sessions doesn't start unless on 
gdm3; while performing installation, Ubuntu Budgie graphical session goes on 
without problems but at reboot DE doesn't start.
  Tried installing "classical" ubuntu and DE came on w/o problems; installed 
budgie-desktop and lightdm side by side and budgie didn't start; installed sddm 
with same results. Only gdm3 works
  See attached logs collection

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


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

[Desktop-packages] [Bug 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 Desktop
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
  dmi.bios.vendor: Apple 

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2026544] Re: Update mutter to 44.3

[fossfreedom]

Tested version 44.3-0ubuntu1 of libmutter-12-0 on ubuntu budgie.

Test case I substituted settings for budgie-control-center. No
regressions noted.

Checked general window management - max, min, tiling as well as side-by-side 
tiling. No regressions. No reported /var/crash type stuff.
Checked fractional scaling 125% - logout, login and repeat of the above. Works 
just fine

All tested on physical laptop with amd ryzen 7 graphics.

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

Title:
  Update mutter to 44.3

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 44 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/44.3/NEWS

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  This also includes a minor update of the triple buffering patch so that it 
still applies cleanly and to try to fix a crash on resume from sleep (LP: 
#2020049)

  It is believed that new upstream release also fixes LP: #2023766 and
  LP: #2016990 but those bugs have been left out of debian/changelog to
  not slow down the SRU process with verifying those bug fixes.

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


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

[Desktop-packages] [Bug 2023766] Re: Mouse cursor stutters over GUI elements that are animated

[fossfreedom]

Tested version 44.3-0ubuntu1 of libmutter-12-0 on ubuntu budgie.

Test case I substituted settings for budgie-control-center.  No
regressions noted.


Checked general window management - max, min, tiling as well as side-by-side 
tiling.  No regressions.  No reported /var/crash type stuff.
Checked fractional scaling 125% - logout, login and repeat of the above.  Works 
just fine

All tested on  physical laptop with amd ryzen 7 graphics.

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

Title:
  Mouse cursor stutters over GUI elements that are animated

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  In Progress
Status in mutter source package in Lunar:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  Mouse cursor stutters over GUI elements that are animated, such as GTK
  apps, web pages and shell elements.

  [ Test Plan ]

  1. Open Settings.
  2. Move the cursor up/down over an empty area of the desktop.
  3. Move the cursor up/down over the list pane on the left side of the 
Settings window.

  Expect: No difference in cursor smoothness whether the window below is
  animating in response to movement or not.

  [ Where problems could occur ]

  In frame scheduling, so the risk is more stuttering or screen freezes.

  [ Workaround ]

  Add this to /etc/environment:
  CLUTTER_PAINT=disable-dynamic-max-render-time

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


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

[Desktop-packages] [Bug 1998286] Re: Release mutter 42.9 to jammy

[fossfreedom]

Installed libmutter-10-0 from jammy-proposed v42.9-0ubuntu1 in Ubuntu
Budgie

Logout and login.  Tested standard window manipulation
(maximise/minimise) as well as side-by-side tiling with center resizing
- no issues

Examined /var/crash - no issues

shortcut keys to scroll left/right in workspace works ok

Note - extra test case 1 no system prompt is visible - but that appears
to be a gnome-shell specific thing since it wasnt visible in v10.5

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

Title:
  Release mutter 42.9 to jammy

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/42.9/NEWS

  The overall GNOME project considers GNOME 42 to be end of life now and
  there are no more scheduled releases for mutter 42 after 42.9

  This is basically a prerequisite for GNOME Shell 42.9 LP: #2023913

  The current version of Mutter in Jammy is 42.5.

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  Extra Test Case 1
  -
  This release also cherry-picks a patch to fix the prompt to enable 
accessibility features using keyboard shortcuts.

  0. Install the updated mutter packages. Then log out and log back in.
  1. Open the Settings app (gnome-control-center)
  2. In the left sidebar, click Accessibility
  3. In the typing section, lick Typing Assist
  4. Turn on the first switch to enable turning accessibility features on and 
off using the keyboard
  5. Close the Settings app
  6. Press the Shift key 5 or 6 times in a row
  7. You should see a system prompt about turning on Sticky Keys

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  Upstream assumes that people will be using matching versions of mutter and 
gnome-shell. To be cautious, I therefore bumped the dependency version in GNOME 
Shell 42.9 to require mutter >= 42.9 (even though GNOME Shell 42.9 appears to 
run ok with Mutter 42.5). I believe the only way to make the dependency 
relationship work the other way (not allow Mutter 42.9 with GNOME Shell 42.5) 
requires bumping the Breaks version but I don't think it's worth using Breaks 
unless necessary.

  This release will also enable AMD Xilinx/Mali support on Wayland. See
  https://ubuntu.com/download/amd-xilinx or private bug 1961563 or the
  42.6 release notes.

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


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

[Desktop-packages] [Bug 2020225] Re: Update mutter to 44.1

[fossfreedom]

Confirmed that after install of  libmutter-12-0 v44.1-0ubuntu1 from
lunar-proposed on ubuntu budgie no additional regressions were noted.
Tested standard stuff like window switching/max/min, tiling etc.

Independently team member Jacob has also confirmed that the same version
does not additionally impacted his setup

Note - I tried to reproduce the artefact issue Andreas noted above with
google chrome on ubuntu budgie + this new version but was unable to.

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

Title:
  Update mutter to 44.1

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 44 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/44.1/NEWS

  This is also a prerequisite to update gnome-shell to 44.1 (LP:
  #2020277)

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


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

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2018234] Re: Window not focusing when title bar is clicked.

[fossfreedom]

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

I note this has a gnome-shell equivalent so marking as a duplicate

** This bug has been marked a duplicate of bug 2011251
   gnome-shell gets into state where clicking on window title bars doesn't 
raise them

** No longer affects: ubuntubudgie

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

Title:
  Window not focusing when title bar is clicked.

Status in mutter package in Ubuntu:
  New

Bug description:
  When a window is partially behind another and I click on the title
  bar, the window I clicked on does not come forward to get focus. I
  have to click in the body of the window for this to happen. This only
  started happening when I upgraded to Ubuntu Budgie 23.04.

  I am running Ubuntu Budgie 23.04, Budgie desktop version 10.7.1

  Running an Nvidia GP108 [GeForce GT 1030] using the nvidia-driver-525.

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


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

[Desktop-packages] [Bug 2018234] Re: Window not focusing when title bar is clicked.

[fossfreedom]

This has been resolved upstream
https://gitlab.gnome.org/GNOME/mutter/-/issues/2660

If ubuntu devs release mutter v44.1 point release this issue will also
be resolved

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2660
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2660

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

Title:
  Window not focusing when title bar is clicked.

Status in Ubuntu Budgie:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  When a window is partially behind another and I click on the title
  bar, the window I clicked on does not come forward to get focus. I
  have to click in the body of the window for this to happen. This only
  started happening when I upgraded to Ubuntu Budgie 23.04.

  I am running Ubuntu Budgie 23.04, Budgie desktop version 10.7.1

  Running an Nvidia GP108 [GeForce GT 1030] using the nvidia-driver-525.

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


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

[Desktop-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install

[fossfreedom]

Re secureboot

In my case my macbook air was not secure boot enabled but with the same
no wireless observation

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

Title:
  Failed to install bcmwl wireless driver during the install

Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

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


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

[Desktop-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install

[fossfreedom]

ubuntu-drivers install just returns "All the available drivers are
already installed"

Looking at Additional Drivers it does however offer "Using dkms source
for the Broadcom STA Wireless driver from broadcom-sta-dkms

I can enable that successfully from the live session but wireless
networks are not available in network manager

No errors displayed when enabling from software-properties-gtk via the
terminal

Note - in 20.04.6 enabling via the software properties dialog does
enable correctly with wireless networks in network manager

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

Title:
  Failed to install bcmwl wireless driver during the install

Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

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


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

[Desktop-packages] [Bug 1985856] Re: Update Mutter to 42.5

[fossfreedom]

libmutter10-0/42.5-0ubuntu1 installed on ubuntu-budgie

No regressions noted.  Dual monitor - maximise, minimise, workspace
movement etc etc.

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

Title:
  Update Mutter to 42.5

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


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

[Desktop-packages] [Bug 1988648] [NEW] gnome-software crashed with SIGABRT when clicking on the firefox snap

[fossfreedom]

Public bug reported:

Clicking on the Install tab followed by the Firefox snap to display more
info, gnome-software immediately crashes without displaying more info.

Clicking on an installed deb package like gnome-calculator sometimes the
more info is displayed - sometimes it is briefly displayed before
crashing again.

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-software 43~rc-2
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Sat Sep  3 21:04:41 2022
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2022-07-27 (38 days ago)
InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap43~rc-2
JournalErrors: -- No entries --
ProcCmdline: gnome-software
Signal: 6
SourcePackage: gnome-software
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gs_utils_format_size ()
 ()
Title: gnome-software crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
separator:

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


** Tags: amd64 apport-crash kinetic third-party-packages

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

Title:
  gnome-software crashed with SIGABRT when clicking on the firefox snap

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Clicking on the Install tab followed by the Firefox snap to display
  more info, gnome-software immediately crashes without displaying more
  info.

  Clicking on an installed deb package like gnome-calculator sometimes
  the more info is displayed - sometimes it is briefly displayed before
  crashing again.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-software 43~rc-2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep  3 21:04:41 2022
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2022-07-27 (38 days ago)
  InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap43~rc-2
  JournalErrors: -- No entries --
  ProcCmdline: gnome-software
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gs_utils_format_size ()
   ()
  Title: gnome-software crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  separator:

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


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

[Desktop-packages] [Bug 1988433] Re: gnome-software crashed with SIGABRT when clicking on any application to see its details and install

[fossfreedom]

This issue occurs on any tab - it basically stops any application from
being installed, kind of a critical issue for a software center!

** Summary changed:

- gnome-software crashed with SIGABRT when clicking on the firefox snap
+ gnome-software crashed with SIGABRT when clicking on any application to see 
its details and install

** Description changed:

  Clicking on the Install tab followed by the Firefox snap to display more
  info, gnome-software immediately crashes without displaying more info.
  
  Clicking on a deb package like gnome-calculator sometimes the more info
  is displayed - sometimes it is briefly displayed before crashing again.
+ 
+ In-fact this issue occurs on any tab including the front page - it
+ basically stops any application from being installed.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-software 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Thu Sep  1 14:07:02 2022
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2022-07-27 (36 days ago)
  InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  InstalledPlugins:
-  gnome-software-plugin-flatpak N/A
-  gnome-software-plugin-snap43~beta-1ubuntu2
+  gnome-software-plugin-flatpak N/A
+  gnome-software-plugin-snap43~beta-1ubuntu2
  JournalErrors: -- No entries --
  ProcCmdline: gnome-software
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
-  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  gs_utils_format_size ()
-  ()
+  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  gs_utils_format_size ()
+  ()
  Title: gnome-software crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  separator:

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

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

Title:
  gnome-software crashed with SIGABRT when clicking on any application
  to see its details and install

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Clicking on the Install tab followed by the Firefox snap to display
  more info, gnome-software immediately crashes without displaying more
  info.

  Clicking on a deb package like gnome-calculator sometimes the more
  info is displayed - sometimes it is briefly displayed before crashing
  again.

  In-fact this issue occurs on any tab including the front page - it
  basically stops any application from being installed.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-software 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Thu Sep  1 14:07:02 2022
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2022-07-27 (36 days ago)
  InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap43~beta-1ubuntu2
  JournalErrors: -- No entries --
  ProcCmdline: gnome-software
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gs_utils_format_size ()
   ()
  Title: gnome-software crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  separator:

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


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

[Desktop-packages] [Bug 1988433] [NEW] gnome-software crashed with SIGABRT when clicking on the firefox snap

[fossfreedom]

Public bug reported:

Clicking on the Install tab followed by the Firefox snap to display more
info, gnome-software immediately crashes without displaying more info.

Clicking on a deb package like gnome-calculator sometimes the more info
is displayed - sometimes it is briefly displayed before crashing again.

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-software 43~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Thu Sep  1 14:07:02 2022
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2022-07-27 (36 days ago)
InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap43~beta-1ubuntu2
JournalErrors: -- No entries --
ProcCmdline: gnome-software
RebootRequiredPkgs: Error: path contained symlinks.
Signal: 6
SourcePackage: gnome-software
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gs_utils_format_size ()
 ()
Title: gnome-software crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
separator:

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


** Tags: amd64 apport-crash kinetic need-amd64-retrace third-party-packages

** Information type changed from Private to Public

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

Title:
  gnome-software crashed with SIGABRT when clicking on the firefox snap

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Clicking on the Install tab followed by the Firefox snap to display
  more info, gnome-software immediately crashes without displaying more
  info.

  Clicking on a deb package like gnome-calculator sometimes the more
  info is displayed - sometimes it is briefly displayed before crashing
  again.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-software 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Thu Sep  1 14:07:02 2022
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2022-07-27 (36 days ago)
  InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap43~beta-1ubuntu2
  JournalErrors: -- No entries --
  ProcCmdline: gnome-software
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gs_utils_format_size ()
   ()
  Title: gnome-software crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  separator:

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


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

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1969303] Re: "No package to remove" error when attempting to uninstall

[fossfreedom]

Further to Roberts observations:

I've done a clean Ubuntu Budgie install and fully up-to-date.

Confirmed I saw the error reported here when uninstalling a .deb.

Confirmed that snap installation and snap removal works as expected
without any error reported.

Upgraded from the proposed repo version 41.5-2ubuntu2

sudo apt install gnome-software gnome-software-common gnome-software-
plugin-snap

logged out and logged in.

Retested snap installation and snap removal - as before works expected
without any error reported.

Retested .deb install and deb removal - no error reported when
uninstalling and the app was successfully removed.

Thus I'm happy to verify this bug report.

Robert - I would raise a separate issue for your snap removal issue -
please though do test on a clean install and verify as I have above

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

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Fix Released
Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * The Ubuntu repository version of gnome-software in 22.04 does not
 allow a user to uninstall an application.
 For new users this could be be construed as disconcerting
 allowing only installing apps without the ability to
 remove those apps later if required.
 
 This SRU is applicable only to the gnome-software application
 installed from the repository and not the branded 
 ubuntu-store snap that is the default in Ubuntu (but not in 
 flavours such as Ubuntu Budgie)
 
 This fix for gnome-software has been backported from the
 v41 version of ubuntu's snap-store.
 
 The fixed software now checks for the status of a deb package
 installed - either manually installed or automatically as
 part of a distro install.  Previously this check was not done
 and gnome-software defaulted to not allowing the package to
 be uninstalled.
 The new status check allows gnome-software to evaluate that
 the package can be uninstalled.

  [Test Plan]

   * Choose a package from the installed list in gnome-software.
 Click the trash icon.  Note the error message that the package
 cannot be removed.
   * install gnome-software from the proposed repository. Logout and
 login.
 Repeat the trash icon click step above.  This time the package
 can be removed.  Confirm via either your distro menu or searching in
 GNOME Overview (if you are using gnome-software from the repository) that 
the
 application has been successfully removed.

   * Perform additional testing such as installing applications from the 
repository
 (change the source to "Ubuntu (deb)") and then deleting the application.
 
   * Perform additional testing such as installing applications from the snap
 repository (change the source to "Snap") and then deleting the application.

  [Where problems could occur]

   * The code changed is specific to 'packagekit' repos i.e. debian based repos.
 Thus it is sensitive to possible regressions when installing & removing 
apps.
 
   * The patch itself is well tested since it was backported to the ubuntu 
snap-store
 several weeks ago and has been rolled out.  No adverse issues has been 
reported.
 
   * The risk would be that there could be additional changes to the snap-store
 that was not incorporated in gnome-software possibly producing different
 results.
 
   * The additional regression tests in the Test Plan will reveal this.

  
  [Other Info]
   
   * There is no need to backport this to Kinetic since a revised version
 of the patch has been upstreamed (GNOME Team) and is in the kinetic 
version.


  

  
  On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any 
application

  If you want to uninstall a software, there is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions


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

[Desktop-packages] [Bug 1981717] Re: Ubuntu MATE & Budgie metapackages need to be updated for pipewire 0.3.54-2

[fossfreedom]

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

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

Title:
  Ubuntu MATE & Budgie metapackages need to be updated for pipewire
  0.3.54-2

Status in pipewire package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in pipewire package in Debian:
  Unknown

Bug description:
  On Kinetic the latest pipewire 0.3.54-2 upgrade wants to remove:

  ubuntu-mate-core 1.284
  ubuntu-mate-desktop 1.284

  Please remove the conflict

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


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

[Desktop-packages] [Bug 1969303] Re: "No package to remove" error when attempting to uninstall

[fossfreedom]

** Changed in: gnome-software (Ubuntu Jammy)
   Status: Triaged => In Progress

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Fix Released
Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Jammy:
  In Progress

Bug description:
  [Impact]

   * The Ubuntu repository version of gnome-software in 22.04 does not
 allow a user to uninstall an application.
 For new users this could be be construed as disconcerting
 allowing only installing apps without the ability to
 remove those apps later if required.
 
 This SRU is applicable only to the gnome-software application
 installed from the repository and not the branded 
 ubuntu-store snap that is the default in Ubuntu (but not in 
 flavours such as Ubuntu Budgie)
 
 This fix for gnome-software has been backported from the
 v41 version of ubuntu's snap-store.
 
 The fixed software now checks for the status of a deb package
 installed - either manually installed or automatically as
 part of a distro install.  Previously this check was not done
 and gnome-software defaulted to not allowing the package to
 be uninstalled.
 The new status check allows gnome-software to evaluate that
 the package can be uninstalled.

  [Test Plan]

   * Choose a package from the installed list in gnome-software.
 Click the trash icon.  Note the error message that the package
 cannot be removed.
   * install gnome-software from the proposed repository. Logout and
 login.
 Repeat the trash icon click step above.  This time the package
 can be removed.  Confirm via either your distro menu or searching in
 GNOME Overview (if you are using gnome-software from the repository) that 
the
 application has been successfully removed.

   * Perform additional testing such as installing applications from the 
repository
 (change the source to "Ubuntu (deb)") and then deleting the application.
 
   * Perform additional testing such as installing applications from the snap
 repository (change the source to "Snap") and then deleting the application.

  [Where problems could occur]

   * The code changed is specific to 'packagekit' repos i.e. debian based repos.
 Thus it is sensitive to possible regressions when installing & removing 
apps.
 
   * The patch itself is well tested since it was backported to the ubuntu 
snap-store
 several weeks ago and has been rolled out.  No adverse issues has been 
reported.
 
   * The risk would be that there could be additional changes to the snap-store
 that was not incorporated in gnome-software possibly producing different
 results.
 
   * The additional regression tests in the Test Plan will reveal this.

  
  [Other Info]
   
   * There is no need to backport this to Kinetic since a revised version
 of the patch has been upstreamed (GNOME Team) and is in the kinetic 
version.


  

  
  On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any 
application

  If you want to uninstall a software, there is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions


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

[Desktop-packages] [Bug 1969303] Re: "No package to remove" error when attempting to uninstall

[fossfreedom]

** Description changed:

- On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any
- application
+ [Impact]
+ 
+  * The Ubuntu repository version of gnome-software in 22.04 does not
+allow a user to uninstall an application.
+For new users this could be be construed as disconcerting
+allowing only installing apps without the ability to
+remove those apps later if required.
+
+This SRU is applicable only to the gnome-software application
+installed from the repository and not the branded 
+ubuntu-store snap that is the default in Ubuntu (but not in 
+flavours such as Ubuntu Budgie)
+
+This fix for gnome-software has been backported from the
+v41 version of ubuntu's snap-store.
+
+The fixed software now checks for the status of a deb package
+installed - either manually installed or automatically as
+part of a distro install.  Previously this check was not done
+and gnome-software defaulted to not allowing the package to
+be uninstalled.
+The new status check allows gnome-software to evaluate that
+the package can be uninstalled.
+ 
+ [Test Plan]
+ 
+  * Choose a package from the installed list in gnome-software.
+Click the trash icon.  Note the error message that the package
+cannot be removed.
+  * install gnome-software from the proposed repository. Logout and
+login.
+Repeat the trash icon click step above.  This time the package
+can be removed.  Confirm via either your distro menu or searching in
+GNOME Overview (if you are using gnome-software from the repository) that 
the
+application has been successfully removed.
+ 
+  * Perform additional testing such as installing applications from the 
repository
+(change the source to "Ubuntu (deb)") and then deleting the application.
+
+  * Perform additional testing such as installing applications from the snap
+repository (change the source to "Snap") and then deleting the application.
+ 
+ [Where problems could occur]
+ 
+  * The code changed is specific to 'packagekit' repos i.e. debian based repos.
+Thus it is sensitive to possible regressions when installing & removing 
apps.
+
+  * The patch itself is well tested since it was backported to the ubuntu 
snap-store
+several weeks ago and has been rolled out.  No adverse issues has been 
reported.
+
+  * The risk would be that there could be additional changes to the snap-store
+that was not incorporated in gnome-software possibly producing different
+results.
+
+  * The additional regression tests in the Test Plan will reveal this.
+ 
+ 
+ [Other Info]
+  
+  * There is no need to backport this to Kinetic since a revised version
+of the patch has been upstreamed (GNOME Team) and is in the kinetic 
version.
+   
+ 
+ 
+ 
+ 
+ On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any 
application
  
  If you want to uninstall a software, there is an error message : "no
  package to remove"
  
  No problem to uninstall this same software with synaptic for example

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Fix Released
Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Jammy:
  In Progress

Bug description:
  [Impact]

   * The Ubuntu repository version of gnome-software in 22.04 does not
 allow a user to uninstall an application.
 For new users this could be be construed as disconcerting
 allowing only installing apps without the ability to
 remove those apps later if required.
 
 This SRU is applicable only to the gnome-software application
 installed from the repository and not the branded 
 ubuntu-store snap that is the default in Ubuntu (but not in 
 flavours such as Ubuntu Budgie)
 
 This fix for gnome-software has been backported from the
 v41 version of ubuntu's snap-store.
 
 The fixed software now checks for the status of a deb package
 installed - either manually installed or automatically as
 part of a distro install.  Previously this check was not done
 and gnome-software defaulted to not allowing the package to
 be uninstalled.
 The new status check allows gnome-software to evaluate that
 the package can be uninstalled.

  [Test Plan]

   * Choose a package from the installed list in gnome-software.
 Click the trash icon.  Note the error message that the package
 cannot be removed.
   * install gnome-software from the proposed repository. Logout and
 login.
 Repeat the trash icon click step above.  This time the package
 can be removed.  Confirm via either your distro menu or searching in
 GNOME 

[Desktop-packages] [Bug 1969303] Re: "No package to remove" error when attempting to uninstall

[fossfreedom]

ok - I have taken the commit from the snap-store-41 branch and applied
it - it works locally here.

I've pinged on IRC ubuntu-desktop how best to proceed with the SRU for
jammy

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Fix Released
Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Jammy:
  Triaged

Bug description:
  On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a software, there is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions


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

[Desktop-packages] [Bug 1969303] Re: "No package to remove" error when attempting to uninstall

[fossfreedom]

** Changed in: gnome-software (Ubuntu Jammy)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Fix Released
Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Jammy:
  Triaged

Bug description:
  On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a software, there is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions


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

[Desktop-packages] [Bug 1972726] Re: Update mutter to 42.1

[fossfreedom]

Confirmed Mauro's observations for Ubuntu Budgie on a Ryzen 4700 setup

libmutter-10-0 42.1-0ubuntu1

This pulled in gtk3 and other packages as well

Similar tests as Mauro - no adverse observations to report

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

Title:
  Update mutter to 42.1

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series. This is a bigger 
update with lots of bugfixes as the first bugfix release in the 42 series.

  https://gitlab.gnome.org/GNOME/mutter/-/blob/42.1/NEWS

  Test Case
  -
  sudo apt install budgie-desktop gnome-session gnome-shell-extensions
  Install the update.
  Log out.
  Select your name on the login screen.
  Click the gear button to choose a session to log in to.
  Finish logging in.

  Verify that things continue to work well for all these sessions:
  Budgie
  GNOME
  GNOME Classic
  Ubuntu
  Ubuntu on Xorg

  (There are more specific test cases for some of the other bugs fixed
  with this update.)

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  This update should not reach jammy-updates until these updates are fully 
phased in jammy-updates to avoid a known testview scrolling bug in apps like 
gedit and gnome-text-editor
  https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.33-1ubuntu2
  https://launchpad.net/ubuntu/+source/gtk4/4.6.3+ds1-0ubuntu1

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


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

[Desktop-packages] [Bug 1968081] Re: [FFe] [UIFe] gnome-characters 42

[fossfreedom]

** Changed in: gnome-characters (Ubuntu)
   Status: Confirmed => New

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

Title:
  [FFe] [UIFe] gnome-characters 42

Status in gnome-characters package in Ubuntu:
  New

Bug description:
  Benefit
  ---
  The new GNOME Characters app significantly improves the usability of the app, 
upgrading the Unicode support from something like Unicode 9 all the way to 
Unicode 14.

  The new version also removes the horizontal lines that the emoji are
  resting on. I think the UI is better without those lines.

  Comment
  ---
  GNOME Characters 42 still doesn't support emoji modifiers and sequences which 
is a really big omission for an emoji app. There is a merge proposal for 
version 43 and it may be worth a major SRU for 22.04 LTS later.

  Other UI comments
  -
  The sidebar has switched to monochrome symbolic icons instead of fullcolor.

  It looks like the selection highlight color is gray instead of the
  Ubuntu color scheme. (I'm referring to Smileys & Emotion in the
  sidebar.)

  Why This Wasn't Done Sooner
  ---
  GNOME Characters 42 switches from GTK3 to GTK4 and libadwaita. libadwaita did 
not support Ubuntu 22.04's color schemes until a patch was uploaded to 22.04 
today.

  Risks and Mitigation
  
  This version is already present in Debian Testing without new reported bugs.

  Both Ubuntu and Ubuntu Budgie includes this app by default.

  The app is standalone and does not impact other apps. We could revert
  if there were a major bug discovered.

  Changes
  ---
  https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/main/NEWS

  gnome-characters (42.0-1) unstable; urgency=medium

    * New upstream release
  - Supports Unicode 14
  - Support for Emoji Sequences and Modifiers is planned
    for the 43 release
    * Drop all patches: applied in new release
    * Switch to gtk4 and libadwaita instead of gtk3 and libhandy
    * debian/control.in: Switch from gnome-desktop 3 to gnome-desktop 4
    * debian/control.in: Drop obsolete Build-Depends on libunistring

   -- Jeremy Bicha   Sat, 19 Mar 2022 13:36:05 -0400

  Logs
  
  Build:
  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gtk4/+sourcepub/13415399/+listing-archive-extra

  Install:
  $ sudo apt install ./gnome-characters_42.0-1_amd64.deb
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Note, selecting 'gnome-characters' instead of 
'./gnome-characters_42.0-1_amd64.deb'
  The following additional packages will be installed:
    gir1.2-gnomedesktop-4.0
  The following NEW packages will be installed:
    gir1.2-gnomedesktop-4.0
  The following packages will be upgraded:
    gnome-characters
  1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 5,660 B/385 kB of archives.
  After this operation, 2,655 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 /home/jeremy/devel/temp/gnome-characters_42.0-1_amd64.deb 
gnome-characters amd64 42.0-1 [379 kB]
  Get:2 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 
gir1.2-gnomedesktop-4.0 amd64 42.0-1ubuntu1 [5,660 B]
  Fetched 5,660 B in 1s (9,886 B/s)
  Selecting previously unselected package gir1.2-gnomedesktop-4.0:amd64.
  (Reading database ... 209429 files and directories currently installed.)
  Preparing to unpack .../gir1.2-gnomedesktop-4.0_42.0-1ubuntu1_amd64.deb ...
  Unpacking gir1.2-gnomedesktop-4.0:amd64 (42.0-1ubuntu1) ...
  Preparing to unpack .../gnome-characters_42.0-1_amd64.deb ...
  Unpacking gnome-characters (42.0-1) over (41.0-4) ...
  Setting up gir1.2-gnomedesktop-4.0:amd64 (42.0-1ubuntu1) ...
  Setting up gnome-characters (42.0-1) ...
  Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
  Processing triggers for libglib2.0-0:amd64 (2.72.0-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...

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


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

[Desktop-packages] [Bug 1968081] Re: [FFe] [UIFe] gnome-characters 42

[fossfreedom]

From a Ubuntu Budgie point of view, the new libadwaita app looks out of
place in our distro with adwaita's ghastly dark brown colouration.  With
a GTK_THEME based override the headerbar looks broken with our default
theme (i.e. we would have used this to suggest this type of workaround
for folk that wants to use a non libadwaita theme).

However - we will not die in a ditch on this.  If Ubuntu really wants
this then we would request that "ubuntu-budgie-meta" be added as
affected and we will need to use this UIFe as a way to remove gnome-
characters from our seeds - i.e. we will not ship with the app.

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

Title:
  [FFe] [UIFe] gnome-characters 42

Status in gnome-characters package in Ubuntu:
  New

Bug description:
  Benefit
  ---
  The new GNOME Characters app significantly improves the usability of the app, 
upgrading the Unicode support from something like Unicode 9 all the way to 
Unicode 14.

  The new version also removes the horizontal lines that the emoji are
  resting on. I think the UI is better without those lines.

  Comment
  ---
  GNOME Characters 42 still doesn't support emoji modifiers and sequences which 
is a really big omission for an emoji app. There is a merge proposal for 
version 43 and it may be worth a major SRU for 22.04 LTS later.

  Other UI comments
  -
  The sidebar has switched to monochrome symbolic icons instead of fullcolor.

  It looks like the selection highlight color is gray instead of the
  Ubuntu color scheme. (I'm referring to Smileys & Emotion in the
  sidebar.)

  Why This Wasn't Done Sooner
  ---
  GNOME Characters 42 switches from GTK3 to GTK4 and libadwaita. libadwaita did 
not support Ubuntu 22.04's color schemes until a patch was uploaded to 22.04 
today.

  Risks and Mitigation
  
  This version is already present in Debian Testing without new reported bugs.

  Both Ubuntu and Ubuntu Budgie includes this app by default.

  The app is standalone and does not impact other apps. We could revert
  if there were a major bug discovered.

  Changes
  ---
  https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/main/NEWS

  gnome-characters (42.0-1) unstable; urgency=medium

    * New upstream release
  - Supports Unicode 14
  - Support for Emoji Sequences and Modifiers is planned
    for the 43 release
    * Drop all patches: applied in new release
    * Switch to gtk4 and libadwaita instead of gtk3 and libhandy
    * debian/control.in: Switch from gnome-desktop 3 to gnome-desktop 4
    * debian/control.in: Drop obsolete Build-Depends on libunistring

   -- Jeremy Bicha   Sat, 19 Mar 2022 13:36:05 -0400

  Logs
  
  Build:
  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gtk4/+sourcepub/13415399/+listing-archive-extra

  Install:
  $ sudo apt install ./gnome-characters_42.0-1_amd64.deb
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Note, selecting 'gnome-characters' instead of 
'./gnome-characters_42.0-1_amd64.deb'
  The following additional packages will be installed:
    gir1.2-gnomedesktop-4.0
  The following NEW packages will be installed:
    gir1.2-gnomedesktop-4.0
  The following packages will be upgraded:
    gnome-characters
  1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 5,660 B/385 kB of archives.
  After this operation, 2,655 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 /home/jeremy/devel/temp/gnome-characters_42.0-1_amd64.deb 
gnome-characters amd64 42.0-1 [379 kB]
  Get:2 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 
gir1.2-gnomedesktop-4.0 amd64 42.0-1ubuntu1 [5,660 B]
  Fetched 5,660 B in 1s (9,886 B/s)
  Selecting previously unselected package gir1.2-gnomedesktop-4.0:amd64.
  (Reading database ... 209429 files and directories currently installed.)
  Preparing to unpack .../gir1.2-gnomedesktop-4.0_42.0-1ubuntu1_amd64.deb ...
  Unpacking gir1.2-gnomedesktop-4.0:amd64 (42.0-1ubuntu1) ...
  Preparing to unpack .../gnome-characters_42.0-1_amd64.deb ...
  Unpacking gnome-characters (42.0-1) over (41.0-4) ...
  Setting up gir1.2-gnomedesktop-4.0:amd64 (42.0-1ubuntu1) ...
  Setting up gnome-characters (42.0-1) ...
  Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
  Processing triggers for libglib2.0-0:amd64 (2.72.0-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...

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


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

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1962021] Re: Make the deb package install the firefox snap

[fossfreedom]

For Ubuntu Budgie we need the auto theming to work for the transition.

In addition we will need to seed two further snap theme packages in
addition to the firefox theme since our themes are not in the general
theme snap ubuntu uses.

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

Title:
  Make the deb package install the firefox snap

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Canonical and Mozilla are working together to make the firefox snap
  the only supported package in Ubuntu, thus deprecating the deb package
  in the archive.

  This bug tracks the transformation of the firefox package in the
  archive into a transitional package that installs the snap, much like
  was done for chromium-browser in Ubuntu 19.10.

  There are a number of known problems and regressions with the snap
  compared to the deb (see
  https://bugzilla.mozilla.org/show_bug.cgi?id=snap and
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap),
  those are actively being worked on and will be addressed in due time,
  please refrain from using this bug to point them out. Instead, file
  separate bugs in the upstream bug tracker
  (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify
  this is about the snap package.

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


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

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1955475] [NEW] Sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main)

[fossfreedom]

Public bug reported:

Please sync libayatana-indicator 0.9.0-1 (main) from Debian unstable
(main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Correctly restore +x permissions on the .install for dh_exec

I've done a test build of the debian package and installed the resulting .deb 
installs just fine.
Upstream has dropped the need for lomiri-app-launch as a dependency in ubuntu

In addition the v0.9.0 of the package ensures alignment with the v0.9.0 series 
of the
other ayatana packages that have already migrated to ubuntu.

Changelog entries since current jammy version 0.8.4-4ubuntu2:

libayatana-indicator (0.9.0-1) unstable; urgency=medium

  * New upstream release.
  * debian/patches:
+ Drop all previous patches. All shipped upstream.
+ Add 0001_src-CMakeLists.txt-indicator.symbols-Don-t-export-pr.patch. Don't
  export private symbols.
  * debian/:
+ Adjust to upstream build system switch (autotools -> CMake).
  * debian/control:
+ Bump Standards-Version: to 4.6.0. No changes needed.
+ Add missing dev:pkg dependency to libayatana-indicator3-dev:
  libayatana-ido3-dev (>= 0.8.0).
+ Enforce usage of version 0.9.0 of the Ayatana IDO library.
  * debian/copyright:
+ Update auto-generated copyright.in reference file.
+ Update copyright attributions.
  * debian/watch:
+ Use format version 4.
  * debian/rules:
+ Install NEWS file as upstream ChangeLog.
  * debian/upstream/metadata:
+ Update points of contact, put UBports Foundation in Donation: field.

 -- Mike Gabriel   Thu, 18 Nov 2021 13:35:28 +0100

** Affects: libayatana-indicator (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: libayatana-indicator (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main)

Status in libayatana-indicator package in Ubuntu:
  New

Bug description:
  Please sync libayatana-indicator 0.9.0-1 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Correctly restore +x permissions on the .install for dh_exec

  I've done a test build of the debian package and installed the resulting .deb 
installs just fine.
  Upstream has dropped the need for lomiri-app-launch as a dependency in ubuntu

  In addition the v0.9.0 of the package ensures alignment with the v0.9.0 
series of the
  other ayatana packages that have already migrated to ubuntu.

  Changelog entries since current jammy version 0.8.4-4ubuntu2:

  libayatana-indicator (0.9.0-1) unstable; urgency=medium

* New upstream release.
* debian/patches:
  + Drop all previous patches. All shipped upstream.
  + Add 0001_src-CMakeLists.txt-indicator.symbols-Don-t-export-pr.patch. 
Don't
export private symbols.
* debian/:
  + Adjust to upstream build system switch (autotools -> CMake).
* debian/control:
  + Bump Standards-Version: to 4.6.0. No changes needed.
  + Add missing dev:pkg dependency to libayatana-indicator3-dev:
libayatana-ido3-dev (>= 0.8.0).
  + Enforce usage of version 0.9.0 of the Ayatana IDO library.
* debian/copyright:
  + Update auto-generated copyright.in reference file.
  + Update copyright attributions.
* debian/watch:
  + Use format version 4.
* debian/rules:
  + Install NEWS file as upstream ChangeLog.
* debian/upstream/metadata:
  + Update points of contact, put UBports Foundation in Donation: field.

   -- Mike Gabriel   Thu, 18 Nov 2021 13:35:28
  +0100

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


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

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 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)
  

[Desktop-packages] [Bug 1950809] Re: Installer crashed within virtualbox VM

[fossfreedom]

I think the issue here lookinh at the GSD errors in the trace is that
gnome-settings-daemon is mismatched with mutter

I.e. GSD is v41 and this should have been uploaded with mutter v41.
budgie desktop is crashing because it needs a matched GSD and mutter

Mutter v41 needs to be uploaded and at the same time the budgie desktop
version from debian sid should then be sync'd

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

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

Title:
  Installer crashed within virtualbox VM

Status in mutter package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Installer crashed within virtualbox VM:

  I've run an installation of Ubuntu Budgie 22.04 nightly (2022)
  within a virtualbox VM (Ubuntu Budgie 21.10 host), left the
  installation unattended for a while and after coming back found the
  installer has crashed. Then the bug report page opened automatically
  (I am writing this from within the live system).

  Not sure if this is relevant to the crash, but I've set up hard drive
  encryption within the storage configuration section.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity 21.10.10
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  Date: Fri Nov 12 19:38:41 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-budgie.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(2022)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1948544] [NEW] snap libportal error on launch

[fossfreedom]

Public bug reported:

dad@dad-TUXEDO-Pulse-15-Gen1:~$ snap install eog
eog 40.2 from Canonical✓ installed
dad@dad-TUXEDO-Pulse-15-Gen1:~$ snap run eog
/snap/eog/602/usr/bin/eog: error while loading shared libraries: 
libportal.so.0: cannot open shared object file: No such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 21.10
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Sat Oct 23 20:06:08 2021
InstallationDate: Installed on 2021-07-24 (90 days ago)
InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210724)
Snap: eog 40.2 (stable)
SnapSource: ubuntu/+source/eog
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug impish snap

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

Title:
  snap libportal error on launch

Status in eog package in Ubuntu:
  New

Bug description:
  dad@dad-TUXEDO-Pulse-15-Gen1:~$ snap install eog
  eog 40.2 from Canonical✓ installed
  dad@dad-TUXEDO-Pulse-15-Gen1:~$ snap run eog
  /snap/eog/602/usr/bin/eog: error while loading shared libraries: 
libportal.so.0: cannot open shared object file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Sat Oct 23 20:06:08 2021
  InstallationDate: Installed on 2021-07-24 (90 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210724)
  Snap: eog 40.2 (stable)
  SnapSource: ubuntu/+source/eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1948482] [NEW] Firefox is wrongly being transitioned from deb to snap

[fossfreedom]

Public bug reported:

Reported here - 6 minutes in https://www.youtube.com/watch?v=NBTws4KoPtg

In update manager the transition to snap is being made as an update

i.e. this is a fresh 21.10 ubuntu budgie install where firefox is seeded
as a deb not a snap

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: firefox 93.0+build1-0ubuntu3
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dad 828 F pulseaudio
BuildID: 20210927210923
CasperMD5CheckResult: pass
Channel: Unavailable
CurrentDesktop: Budgie:GNOME
Date: Fri Oct 22 17:46:11 2021
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:360
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2021-10-22 (0 days ago)
InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 (20211011)
IpRoute:
 default via 10.0.2.2 dev enp0s3 proto dhcp metric 100
 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100
 169.254.0.0/16 dev enp0s3 scope link metric 1000
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:360
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=93.0/20210927210923
RunningIncompatibleAddons: False
SourcePackage: firefox
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:sku: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: firefox (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: firefox (Ubuntu Impish)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

** Description changed:

- Reported here - 6 minutes in
+ Reported here - 6 minutes in https://www.youtube.com/watch?v=NBTws4KoPtg
  
  In update manager the transition to snap is being made as an update
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 93.0+build1-0ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  dad 828 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dad 828 F pulseaudio
  BuildID: 20210927210923
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: Budgie:GNOME
  Date: Fri Oct 22 17:46:11 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:360
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-10-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 
(20211011)
  IpRoute:
-  default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
-  10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
-  169.254.0.0/16 dev enp0s3 scope link metric 1000
+  default via 10.0.2.2 dev enp0s3 proto dhcp metric 100
+  10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100
+  169.254.0.0/16 dev enp0s3 scope link metric 1000
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close 

[Desktop-packages] [Bug 1939938] Re: dialog asking for restart appears on close of rhythmbox

[fossfreedom]

** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  dialog asking for restart appears on close of rhythmbox

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Fix Committed

Bug description:
  following last update to rhythmbox dialog box now appears at every
  closure of rhythmbox from top bar

  Ubuntu 21.10 image from 13/08

  lenovo thinkpad T430

  250gb ssd  16gb ram

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1939938/+subscriptions


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

[Desktop-packages] [Bug 1939938] Re: dialog asking for restart appears on close of rhythmbox

[fossfreedom]

** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
   Importance: Undecided => High

** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  dialog asking for restart appears on close of rhythmbox

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  In Progress

Bug description:
  following last update to rhythmbox dialog box now appears at every
  closure of rhythmbox from top bar

  Ubuntu 21.10 image from 13/08

  lenovo thinkpad T430

  250gb ssd  16gb ram

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1939938/+subscriptions


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

Re: [Desktop-packages] [Bug 1939938] Re: dialog asking for restart appears on close of rhythmbox

[fossfreedom]

Grrr... agreed.

I will get a new release out today

On Tue, 14 Sep 2021, 06:30 crvi, <1939...@bugs.launchpad.net> wrote:

> @fossfreedom: I think it's better to revert
>
> https://github.com/fossfreedom/alternative-
> toolbar/commit/9e50cb17a99cd2cff6f6c1b71d2ad219cac6ac5d
>
> ** Package changed: rhythmbox (Ubuntu) => rhythmbox-plugin-alternative-
> toolbar (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to
> rhythmbox-plugin-alternative-toolbar in Ubuntu.
> https://bugs.launchpad.net/bugs/1939938
>
> Title:
>   dialog asking for restart appears on close of rhythmbox
>
> Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
>   Confirmed
>
> Bug description:
>   following last update to rhythmbox dialog box now appears at every
>   closure of rhythmbox from top bar
>
>   Ubuntu 21.10 image from 13/08
>
>   lenovo thinkpad T430
>
>   250gb ssd  16gb ram
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1939938/+subscriptions
>
>

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

Title:
  dialog asking for restart appears on close of rhythmbox

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Confirmed

Bug description:
  following last update to rhythmbox dialog box now appears at every
  closure of rhythmbox from top bar

  Ubuntu 21.10 image from 13/08

  lenovo thinkpad T430

  250gb ssd  16gb ram

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1939938/+subscriptions


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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-desktop3 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-desktop3 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-desktop3 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to gnome-desktop3 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1930104] Re: GNOME 40 (GDM) prevents GNOME Screensaver from locking

[fossfreedom]

** Description changed:

+ WORK IN PROGRESS - GIT PR to be done
+ 
  Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
  screen.
  
  GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME
  Screensaver previously utilised.
  
  This prevents GNOME Screensaver from working i.e. provide its locking
  capability.
  
  To resolve this requires a patch to kill the GDM spawned process
  releasing the dbus grab.
  
  All of this is explained in the dep3 headers of the debdiff patch
  attached

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

Title:
  GNOME 40 (GDM) prevents GNOME Screensaver from locking

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  WORK IN PROGRESS - GIT PR to be done

  Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
  screen.

  GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME
  Screensaver previously utilised.

  This prevents GNOME Screensaver from working i.e. provide its locking
  capability.

  To resolve this requires a patch to kill the GDM spawned process
  releasing the dbus grab.

  All of this is explained in the dep3 headers of the debdiff patch
  attached

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

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

[Desktop-packages] [Bug 1930104] Re: GNOME 40 (GDM) prevents GNOME Screensaver from locking

[fossfreedom]

** Patch added: "gnome40gdm.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1930104/+attachment/5500946/+files/gnome40gdm.debdiff

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

Title:
  GNOME 40 (GDM) prevents GNOME Screensaver from locking

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
  screen.

  GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME
  Screensaver previously utilised.

  This prevents GNOME Screensaver from working i.e. provide its locking
  capability.

  To resolve this requires a patch to kill the GDM spawned process
  releasing the dbus grab.

  All of this is explained in the dep3 headers of the debdiff patch
  attached

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

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

[Desktop-packages] [Bug 1930104] [NEW] GNOME 40 (GDM) prevents GNOME Screensaver from locking

[fossfreedom]

Public bug reported:

Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
screen.

GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME
Screensaver previously utilised.

This prevents GNOME Screensaver from working i.e. provide its locking
capability.

To resolve this requires a patch to kill the GDM spawned process
releasing the dbus grab.

All of this is explained in the dep3 headers of the debdiff patch
attached

** Affects: gnome-screensaver (Ubuntu)
 Importance: Undecided
 Assignee: fossfreedom (fossfreedom)
 Status: New

** Changed in: gnome-screensaver (Ubuntu)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

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

Title:
  GNOME 40 (GDM) prevents GNOME Screensaver from locking

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
  screen.

  GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME
  Screensaver previously utilised.

  This prevents GNOME Screensaver from working i.e. provide its locking
  capability.

  To resolve this requires a patch to kill the GDM spawned process
  releasing the dbus grab.

  All of this is explained in the dep3 headers of the debdiff patch
  attached

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

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

[Desktop-packages] [Bug 1916711] Re: 'Restart & Update' in 'Software' application does nothing in Xubuntu

[fossfreedom]

FYI - works as expected under UB

ok - under UB - I saw the restart button after installing.  Clicking on
it restarted UB - then I saw updates installing via plymouth on a reboot
... it rebooted again and there are no more updates.

Note - for UB our default is not to have updates via gnome-software (we
hide by overriding the org.gnome.software updates key - we use Ubuntu's
software updater

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

Title:
  'Restart & Update' in 'Software' application does nothing in Xubuntu

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Release: Xubuntu dailybuilds ISO (currently 20210224 ISO)

  SW and Version: gnome-software, 3.38.0-3

  How to reproduce: 
- Launch 'Software'. If available, it shows updates under 'Updates'. 
- Click on 'Download' it changes to 'Restart & Update' after a while (I did 
not see any progress bar, may be update was very small or it is normal)
- Click on 'Restart & Update' button.

  Expected: System should reboot and during reboot the updates should be
  installed.

  Actual: Nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-software 3.38.0-3
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Feb 24 13:10:53 2021
  InstallationDate: Installed on 2021-02-24 (0 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210224)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.38.0-3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1919313] Re: Login screen has Ubuntu and not Budgiedesktop as default

[fossfreedom]

Should be fixed in todays ISO

** Also affects: budgie-desktop-environment (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: budgie-desktop-environment (Ubuntu)
   Status: New => Fix Released

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

Title:
  Login screen has Ubuntu and not Budgie desktop as default

Status in budgie-desktop-environment package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  This occurred after installing Ubuntu Budgie Hirsute (21.04) from the
  daily ISO 20210315.1

  The gdm package is 3.38.21-2 ubuntu 1

  After installing the system  and rebooting when the login screen
  appears the default desktop is Ubuntu.

  I expected the default to Budgie desktop

  See attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gdm3 3.38.2.1-2ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 16 10:56:53 2021
  InstallationDate: Installed on 2021-03-16 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210315.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop-environment/+bug/1919313/+subscriptions

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1915752] Re: Why does the package have a dependency on gnome-shell

[fossfreedom]

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

** This bug has been marked a duplicate of bug 1918336
   Sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main)

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

Title:
  Why  does the package have a dependency on gnome-shell

Status in gnome-remote-desktop package in Ubuntu:
  New

Bug description:
  Quick question - why does the binary package have a dependency on
  gnome-shell?

  This turns the package into a GNOME Shell specific package.  I was
  hoping the gnome-remote-desktop could be used on Ubuntu Budgie - but
  this dependency prevents this.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-remote-desktop 0.1.9-4
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Mon Feb 15 19:26:54 2021
  InstallationDate: Installed on 2021-02-08 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210208)
  RebootRequiredPkgs: gnome-shell
  SourcePackage: gnome-remote-desktop
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1918336] [NEW] Sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main)

[fossfreedom]

Public bug reported:

Please sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable
(main)

Changelog entries since current hirsute version 0.1.9-4build1:

gnome-remote-desktop (0.1.9-5) unstable; urgency=medium

  * Team upload

  [ David Mohammed ]
  * debian/control: add budgie-desktop as an alternate for gnome-shell
(Closes: #982937)

 -- Simon McVittie   Tue, 09 Mar 2021 10:31:04 +

** Affects: gnome-remote-desktop (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: gnome-remote-desktop (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main)

Status in gnome-remote-desktop package in Ubuntu:
  New

Bug description:
  Please sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable
  (main)

  Changelog entries since current hirsute version 0.1.9-4build1:

  gnome-remote-desktop (0.1.9-5) unstable; urgency=medium

* Team upload

[ David Mohammed ]
* debian/control: add budgie-desktop as an alternate for gnome-shell
  (Closes: #982937)

   -- Simon McVittie   Tue, 09 Mar 2021 10:31:04 +

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

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

[Desktop-packages] [Bug 1761367] Re: found solution rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

[fossfreedom]

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

** This bug is no longer a duplicate of bug 1725480
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
** This bug has been marked a duplicate of bug 1725457
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

Title:
  found solution rhythmbox crashed with SIGSEGV in
  gtk_tree_view_get_column()

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 18.04 Beta. I de-installed the alternative toolbar. Now
  everything works for me.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Thu Apr  5 05:48:37 2018
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2018-03-18 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  ProcCmdline: rhythmbox
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f7992d49724 :  mov
(%rax),%rax
   PC (0x7f7992d49724) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_view_set_model () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  Title: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1788749] Re: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

[fossfreedom]

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

** This bug is no longer a duplicate of bug 1725826
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
** This bug has been marked a duplicate of bug 1725457
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

Title:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Ubuntu 18.10

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: rhythmbox 3.4.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 23 22:45:07 2018
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2018-08-22 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723)
  ProcCmdline: rhythmbox
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fef9983ea42 :  mov
(%rax),%rdi
   PC (0x7fef9983ea42) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1726177] Re: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

[fossfreedom]

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

** This bug is no longer a duplicate of bug 1725826
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
** This bug has been marked a duplicate of bug 1725457
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

Title:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: rhythmbox 3.4.1-2ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 01:45:08 2017
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2017-10-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: rhythmbox
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f2a738e2424 :  mov
(%rax),%rax
   PC (0x7f2a738e2424) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1725826] Re: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

[fossfreedom]

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

** This bug has been marked a duplicate of bug 1725457
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

Title:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Incomplete

Bug description:
  Rhythmbox freezes after double klick on a song

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: rhythmbox 3.4.1-2ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 22:03:23 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2017-01-29 (265 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: rhythmbox
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f699c881424 :  mov
(%rax),%rax
   PC (0x7f699c881424) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
  UpgradeStatus: Upgraded to artful on 2017-10-19 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1725826/+subscriptions

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

[Desktop-packages] [Bug 1760345] Re: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

[fossfreedom]

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

** This bug is no longer a duplicate of bug 1725480
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
** This bug has been marked a duplicate of bug 1725457
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

Title:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Rhythmbox worked after I first used it. Somme 5xx songs were added and
  everything went fine. Then I added one more song to my music folder
  ans started rhythmbox again in order to add this new song to my music.
  From then on rhythmbox keeps on crashing. That meens, it stars, but
  closes some seconds later.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Sat Mar 31 21:41:10 2018
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2018-03-31 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha i386 
(20180307.1)
  ProcCmdline: rhythmbox
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb77b1b90 :  mov
(%eax),%eax
   PC (0xb77b1b90) ok
   source "(%eax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   gtk_tree_view_get_column () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   gtk_tree_view_set_model () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/librhythmbox-core.so.10
  Title: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1725480] Re: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

[fossfreedom]

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

** This bug has been marked a duplicate of bug 1725457
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

Title:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Confirmed

Bug description:
  Just had it open.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: rhythmbox 3.4.1-2ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 22:42:17 2017
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: rhythmbox /home/username/Musik/Sabine\ Alef/02\ Entspannung\ 
mit\ Yoga.mp3
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7ff6a1f0e424 :  mov
(%rax),%rax
   PC (0x7ff6a1f0e424) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_view_remove_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1725480/+subscriptions

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

[Desktop-packages] [Bug 1890632] Re: Can't open preferences

[fossfreedom]

Reset rhythmbox gsettings via https://askubuntu.com/questions/7979/how-
can-i-reset-all-rhythmbox-preferences-and-library-
information/271950#271950

Preferences menu is located via the headerbar as shown in the attached
picture

** Attachment added: "Preferences location"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1890632/+attachment/5474581/+files/Screenshot%20from%202021-03-08%2018%3A40%3A21.png

** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
   Status: New => Invalid

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

Title:
  Can't open preferences

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Invalid

Bug description:
  I can't seem to access the rhymbox preferences.
  'Preferences' does not appear in the application menu (see attachment) since 
ubuntu 17.10.
  I was still able to edit the preferences from the menu under the song slider, 
but I have now accidentally removed the whole top bar (with the current song, 
the previous, next, pause buttons, and that menu button).

  So now I can't open the preferences, nor see the current song anymore,
  or have it display again.

  Note that the option in the view menu might have been from the
  Alternative-Toolbar plugin

  A temporary fix to get the view menu again would be appreciated too.

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

  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Mirror of the attachment (screenshot of the application menu):
  https://i.imgur.com/CJUVoRZ.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1890632/+subscriptions

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

[Desktop-packages] [Bug 1917926] Re: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1

[fossfreedom]

Confirmed affecting Ubuntu Budgie - no direct workaround possible since
Wayland isn't an option.

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

Title:
  Window focus issues for Xorg sessions in 3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

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

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

[Desktop-packages] [Bug 1915751] Re: Sharing is enabled out of the box

[fossfreedom]

Ok - closing - I've tried to reproduce in today's daily build
with/without gnome-remote-desktop from proposed and can not see the
issue.  Sorry for the noise.

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Invalid

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

Title:
  Sharing is enabled out of the box

Status in gnome-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Apologies if this is the wrong package.

  Using Ubuntu Budgie

  I note that GNOME Settings - Sharing is enabled by default and that
  "Remote Login" is ticked to be on.  This could be construed as a
  security issue.

  I would have expected a user to enable if sharing should be possible -
  certainly "Remote Login" shouldnt be enabled by default out-of-the-
  box.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-settings-daemon 3.38.1-3ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Mon Feb 15 19:01:17 2021
  InstallationDate: Installed on 2021-02-08 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210208)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1915751] Re: Sharing is enabled out of the box

[fossfreedom]

Hi Seb,

  I was actually using Ubuntu Budgie when I noticed this.  At the time
gnome-remote-desktop wasn't installed and it was the older mutter [in
the release pocket] (not the pipewire enabled version in proposed).

gnome-remote-desktop has a serious issue for us (separate bug report
on that package) due to a runtime dependency on gnome-shell.

I'll double check tonight on a clean install what happens with a newer
mutter (initially) and then check what happens when installing
gnome-remote-desktop.

David

On Tue, 16 Feb 2021 at 09:00, Sebastien Bacher
<1915...@bugs.launchpad.net> wrote:
>
> Thank you for your bug report, what shell version do you use? The newer
> one with pipewire enabled? is gnome-remote-desktop installed?
>
> ** Changed in: gnome-settings-daemon (Ubuntu)
>Importance: Undecided => High
>
> ** Tags added: rls-hh-incoming
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1915751
>
> Title:
>   Sharing is enabled out of the box
>
> Status in gnome-settings-daemon package in Ubuntu:
>   New
>
> Bug description:
>   Apologies if this is the wrong package.
>
>   Using Ubuntu Budgie
>
>   I note that GNOME Settings - Sharing is enabled by default and that
>   "Remote Login" is ticked to be on.  This could be construed as a
>   security issue.
>
>   I would have expected a user to enable if sharing should be possible -
>   certainly "Remote Login" shouldnt be enabled by default out-of-the-
>   box.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: gnome-settings-daemon 3.38.1-3ubuntu2
>   ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
>   Uname: Linux 5.8.0-36-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu57
>   Architecture: amd64
>   CasperMD5CheckResult: unknown
>   CurrentDesktop: Budgie:GNOME
>   Date: Mon Feb 15 19:01:17 2021
>   InstallationDate: Installed on 2021-02-08 (6 days ago)
>   InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
> (20210208)
>   SourcePackage: gnome-settings-daemon
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1915751/+subscriptions

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

Title:
  Sharing is enabled out of the box

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  Apologies if this is the wrong package.

  Using Ubuntu Budgie

  I note that GNOME Settings - Sharing is enabled by default and that
  "Remote Login" is ticked to be on.  This could be construed as a
  security issue.

  I would have expected a user to enable if sharing should be possible -
  certainly "Remote Login" shouldnt be enabled by default out-of-the-
  box.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-settings-daemon 3.38.1-3ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Mon Feb 15 19:01:17 2021
  InstallationDate: Installed on 2021-02-08 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210208)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1915751] [NEW] Sharing is enabled out of the box

[fossfreedom]

Public bug reported:

Apologies if this is the wrong package.

Using Ubuntu Budgie

I note that GNOME Settings - Sharing is enabled by default and that
"Remote Login" is ticked to be on.  This could be construed as a
security issue.

I would have expected a user to enable if sharing should be possible -
certainly "Remote Login" shouldnt be enabled by default out-of-the-box.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-settings-daemon 3.38.1-3ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu57
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Budgie:GNOME
Date: Mon Feb 15 19:01:17 2021
InstallationDate: Installed on 2021-02-08 (6 days ago)
InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210208)
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Sharing is enabled out of the box

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  Apologies if this is the wrong package.

  Using Ubuntu Budgie

  I note that GNOME Settings - Sharing is enabled by default and that
  "Remote Login" is ticked to be on.  This could be construed as a
  security issue.

  I would have expected a user to enable if sharing should be possible -
  certainly "Remote Login" shouldnt be enabled by default out-of-the-
  box.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-settings-daemon 3.38.1-3ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Mon Feb 15 19:01:17 2021
  InstallationDate: Installed on 2021-02-08 (6 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210208)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 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 Desktop
Packages, which is subscribed to xorg-server 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: [Desktop-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 Desktop
Packages, which is subscribed to xorg-server 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: [Desktop-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 Desktop
Packages, which is subscribed to xorg-server 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
  

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1901460] Re: Back off also if IBus on Budgie

[fossfreedom]

Hi!

Yes - the support for Ibus non-xkb layouts via the applet is broken in
focal - fixed as you have seen in groovy.

Thus I have backported the patch and SRU'd here
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1902317

Hopefully the SRU team will be kind enough to review soonish.  Thanks.
Regards

On Fri, 30 Oct 2020 at 21:15, Gunnar Hjalmarsson
<1901...@bugs.launchpad.net> wrote:
>
> I verified the test case for groovy using im-config 0.45-1ubuntu1.1 from
> groovy-proposed.
>
> As regards focal I couldn't reproduce the test case successfully. IBus
> input methods are simply not recognized by the Keyboard Layout applet,
> also when budgie-desktop 10.5.1-6ubuntu0.1 is present.
>
> @David: Is there more into it to make IBus work smoothly on Budgie
> 20.04?
>
> ** Tags removed: verification-needed-groovy
> ** Tags added: verification-done-groovy
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1901460
>
> Title:
>   Back off also if IBus on Budgie
>
> Status in im-config package in Ubuntu:
>   Fix Released
> Status in im-config source package in Focal:
>   Fix Committed
> Status in im-config source package in Groovy:
>   Fix Committed
> Status in im-config package in Debian:
>   Unknown
>
> Bug description:
>   [Impact]
>
>   This is a follow-up of bug #1893551, where we stopped im-config from
>   interfering in case of a GNOME desktop. Even if Budgie uses the same
>   applicable GNOME components, we didn't change it for Budgie at that
>   time since IBus input methods were not reliably reflected in the
>   Keyboard Layout applet.
>
>   However, that issue has been fixed now. Also, the most common ibus
>   crash type is now Budgie related:
>
>   https://errors.ubuntu.com/problem/f0690c64c769b06c2ce0513667bd7a52f53ebd27
>
>   We have reasons to hope that letting im-config back off also for
>   Budgie will reduce the number of crashes as has already happened for
>   standard Ubuntu (see comment #2 at bug #1879958). At least we have
>   nothing to lose by trying...
>
>   [Test case]
>
>   I'm not aware of a way to reproduce the crashes, and thus can't
>   confirm in advance that the proposed upload makes a difference.
>
>   However, we should confirm that IBus input methods can be used
>   smoothly on Budgie:
>
>   * Install Budgie in a VM
>
>   * Install the version of im-config from -proposed
>
>   * Install ibus-libpinyin
>
>   * Add the Keyboard Layout applet in Budgie Desktop Settings
>
>   * Re-login
>
>   * Add Intelligent Pinyin to the input sources in Settings
>
>   * Confirm that switching between the input sources works
> without problems and that you can input Chinese characters
>
>   [Regression risk]
>
>   When used, im-config does two things: It launches an IM framework and
>   sets some IM related variables. The test case serves the purpose of
>   confirming that those things are properly accomplished without im-
>   config in case of IBus. So given a successful verification the
>   regression risk due to the proposed change should be low.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1901460/+subscriptions

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

Title:
  Back off also if IBus on Budgie

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Focal:
  Fix Committed
Status in im-config source package in Groovy:
  Fix Committed
Status in im-config package in Debian:
  Unknown

Bug description:
  [Impact]

  This is a follow-up of bug #1893551, where we stopped im-config from
  interfering in case of a GNOME desktop. Even if Budgie uses the same
  applicable GNOME components, we didn't change it for Budgie at that
  time since IBus input methods were not reliably reflected in the
  Keyboard Layout applet.

  However, that issue has been fixed now. Also, the most common ibus
  crash type is now Budgie related:

  https://errors.ubuntu.com/problem/f0690c64c769b06c2ce0513667bd7a52f53ebd27

  We have reasons to hope that letting im-config back off also for
  Budgie will reduce the number of crashes as has already happened for
  standard Ubuntu (see comment #2 at bug #1879958). At least we have
  nothing to lose by trying...

  [Test case]

  I'm not aware of a way to reproduce the crashes, and thus can't
  confirm in advance that the proposed upload makes a difference.

  However, we should confirm that IBus input methods can be used
  smoothly on Budgie:

  * Install Budgie in a VM

  * Install the version of im-config from -proposed

  * Install ibus-libpinyin

  * Add the Keyboard Layout applet in Budgie Desktop Settings

  * Re-login

  * Add Intelligent Pinyin to the input sources in Settings

  * Confirm that switching between the input sources works
without problems 

[Desktop-packages] [Bug 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions in groovy)

[fossfreedom]

For 20.04 and 20.10 using the TearFree option has provided a workaround
solution for me.

Separately Sam (the issue reporter) has confirmed the same solution for
his intel graphics

https://askubuntu.com/questions/1066722/intel-screen-tearing-
ubuntu-18-04

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0AJ00
  dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1898541] Re: [FFe] Update to 3.38.0

[fossfreedom]

On behalf of UB - no objections here +1.  Many thanks for doing this.
much appreciated.

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

Title:
  [FFe] Update to 3.38.0

Status in gnome-software package in Ubuntu:
  New

Bug description:
  It would be good if we could ship gnome-software 3.38.0 with groovy.

  These are the 3.37.92 changes:

  Add sysprof support for profiling jobs
  Add webflow and basic auth support to flatpak plugin
  Coalesce refresh operations where possible
  Correctly mark layered rpm-ostree local packages as removable
  Fix flatpak bundle installation
  Handle invalid snap auth data
  Improve flatpak progress reporting for transactions
  Improve the heuristic for detecting old-style AppStream override files
  Many performance improvements in many areas of the code
  Only delete the firmware archive if we downloaded it to the cache
  Show a pulsing progress bar if progress is unknown
  Support loading appstream files from custom install prefix
  Use the runtime fwupd version for the user agent

  3.38.0 is a pure translation update.

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

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

Re: [Desktop-packages] [Bug 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions in groovy)

[fossfreedom]

Ok. On my low end celeron based intel graphics laptop the existing 20.04.1
version of mutter on the iso has this blinking problem.

So the uplift to v3.36.6 version of mutter in proposed does not regress
further than it already is.

On Mon, 5 Oct 2020, 14:39 David Mohammed, 
wrote:

> Daniel,
>
>   I note that the mutter reported was using mutter 3.36.6 - this is
> currently in focal proposed as well.
>
> I'll do a quick test later - do you think this is a potential blocker
> issue for the mutter migration to release?
>
> On Mon, 5 Oct 2020 at 11:00, Daniel van Vugt <1896...@bugs.launchpad.net>
> wrote:
> >
> > ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1445
> >https://gitlab.gnome.org/GNOME/mutter/-/issues/1445
> >
> > ** Also affects: mutter via
> >https://gitlab.gnome.org/GNOME/mutter/-/issues/1445
> >Importance: Unknown
> >Status: Unknown
> >
> > ** No longer affects: mutter
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1896654).
> > https://bugs.launchpad.net/bugs/1896627
> >
> > Title:
> >   Windows flicker when being resized with the mouse (Xorg sessions in
> >   groovy)
> >
> > Status in GNOME Shell:
> >   Unknown
> > Status in gnome-shell package in Ubuntu:
> >   Triaged
> > Status in mutter package in Ubuntu:
> >   Triaged
> >
> > Bug description:
> >   When resizing a window with the mouse by dragging the edge or corner,
> >   the window begins to flicker.  It only flickers when actively being
> >   resized, and when I stop dragging, it looks normal.  This behavior is
> >   does not occur on same pc in 20.04.
> >
> >   ProblemType: Bug
> >   DistroRelease: Ubuntu 20.10
> >   Package: xorg 1:7.7+19ubuntu14
> >   ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
> >   Uname: Linux 5.8.0-18-generic x86_64
> >   ApportVersion: 2.20.11-0ubuntu45
> >   Architecture: amd64
> >   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
> >   CasperMD5CheckResult: skip
> >   CompositorRunning: None
> >   CurrentDesktop: Budgie:GNOME
> >   CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg:
> read kernel buffer failed: Operation not permitted
> >   Date: Tue Sep 22 10:21:51 2020
> >   DistUpgraded: Fresh install
> >   DistroCodename: groovy
> >   DistroVariant: ubuntu
> >   ExtraDebuggingInterest: Yes, if not too technical
> >   GraphicsCard:
> >Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
> (prog-if 00 [VGA controller])
> >  Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
> >   InstallationDate: Installed on 2020-09-22 (0 days ago)
> >   InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64
> (20200921)
> >   MachineType: LENOVO 20FJS0AJ00
> >   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic
> root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
> >   SourcePackage: xorg
> >   Symptom: display
> >   UpgradeStatus: No upgrade log present (probably fresh install)
> >   dmi.bios.date: 10/07/2016
> >   dmi.bios.release: 1.13
> >   dmi.bios.vendor: LENOVO
> >   dmi.bios.version: N1KET26W (1.13 )
> >   dmi.board.asset.tag: Not Available
> >   dmi.board.name: 20FJS0AJ00
> >   dmi.board.vendor: LENOVO
> >   dmi.board.version: SDK0J40697 WIN
> >   dmi.chassis.asset.tag: No Asset Information
> >   dmi.chassis.type: 10
> >   dmi.chassis.vendor: LENOVO
> >   dmi.chassis.version: None
> >   dmi.ec.firmware.release: 1.5
> >   dmi.modalias:
> dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
> >   dmi.product.family: ThinkPad T560
> >   dmi.product.name: 20FJS0AJ00
> >   dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
> >   dmi.product.version: ThinkPad T560
> >   dmi.sys.vendor: LENOVO
> >   version.compiz: compiz N/A
> >   version.libdrm2: libdrm2 2.4.102-1ubuntu1
> >   version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
> >   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
> >   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
> >   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
> >   version.xserver-xorg-video-ati: xserver-xorg-video-ati
> 1:19.1.0-1ubuntu1
> >   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200714-1
> >   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.16-1
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/gnome-shell/+bug/1896627/+subscriptions
>

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug 

Re: [Desktop-packages] [Bug 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions in groovy)

[fossfreedom]

Daniel,

  I note that the mutter reported was using mutter 3.36.6 - this is
currently in focal proposed as well.

I'll do a quick test later - do you think this is a potential blocker
issue for the mutter migration to release?

On Mon, 5 Oct 2020 at 11:00, Daniel van Vugt <1896...@bugs.launchpad.net> wrote:
>
> ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1445
>https://gitlab.gnome.org/GNOME/mutter/-/issues/1445
>
> ** Also affects: mutter via
>https://gitlab.gnome.org/GNOME/mutter/-/issues/1445
>Importance: Unknown
>Status: Unknown
>
> ** No longer affects: mutter
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1896654).
> https://bugs.launchpad.net/bugs/1896627
>
> Title:
>   Windows flicker when being resized with the mouse (Xorg sessions in
>   groovy)
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Triaged
> Status in mutter package in Ubuntu:
>   Triaged
>
> Bug description:
>   When resizing a window with the mouse by dragging the edge or corner,
>   the window begins to flicker.  It only flickers when actively being
>   resized, and when I stop dragging, it looks normal.  This behavior is
>   does not occur on same pc in 20.04.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.10
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
>   Uname: Linux 5.8.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu45
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: Budgie:GNOME
>   CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
> kernel buffer failed: Operation not permitted
>   Date: Tue Sep 22 10:21:51 2020
>   DistUpgraded: Fresh install
>   DistroCodename: groovy
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
> (prog-if 00 [VGA controller])
>  Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
>   InstallationDate: Installed on 2020-09-22 (0 days ago)
>   InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
> (20200921)
>   MachineType: LENOVO 20FJS0AJ00
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
> root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/07/2016
>   dmi.bios.release: 1.13
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N1KET26W (1.13 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20FJS0AJ00
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0J40697 WIN
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: None
>   dmi.ec.firmware.release: 1.5
>   dmi.modalias: 
> dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
>   dmi.product.family: ThinkPad T560
>   dmi.product.name: 20FJS0AJ00
>   dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
>   dmi.product.version: ThinkPad T560
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.102-1ubuntu1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.917+git20200714-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1896627/+subscriptions

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  

Re: [Desktop-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 Desktop
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:

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1896654] Re: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie)

[fossfreedom]

I do not see any window flickering with QEMU hosting 20.10 guest.  So
specific to intel i915? Sorry - I cannot test radeon or Nvidia.

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

Title:
  Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie)

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker. It only flickers when actively being
  resized, and when I stop dragging, it looks normal. This behavior is
  does not occur on same pc in 20.04. Sometimes the flickering is black,
  sometimes the flickering makes the wallpaper visible, even when there
  is a window behind the window being resized.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Sep 22 14:48:00 2020
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896654] Re: Windows flicker when resizing with mouse

[fossfreedom]

Should note - testing mutter package  3.38.0-1ubuntu1

** Summary changed:

- Windows flicker when resizing with mouse
+ Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie

** Summary changed:

- Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie
+ Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie)

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

Title:
  Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie)

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker. It only flickers when actively being
  resized, and when I stop dragging, it looks normal. This behavior is
  does not occur on same pc in 20.04. Sometimes the flickering is black,
  sometimes the flickering makes the wallpaper visible, even when there
  is a window behind the window being resized.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Sep 22 14:48:00 2020
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896654] Re: Windows flicker when resizing with mouse

[fossfreedom]

Note - this affects GNOME-Shell on Xorg as well.

Confirmed with intel i915 driver.

GNOME-Shell on Wayland there are no window flicker

So most probably a regression in mutter (since budgie and GNOME-Shell
share the same window manager) in the X11 handling.

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

Title:
  Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie)

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker. It only flickers when actively being
  resized, and when I stop dragging, it looks normal. This behavior is
  does not occur on same pc in 20.04. Sometimes the flickering is black,
  sometimes the flickering makes the wallpaper visible, even when there
  is a window behind the window being resized.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Sep 22 14:48:00 2020
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1893113] Re: [SRU] Rhythmbox: Cannot add more music after a collection has been created

[fossfreedom]

Enabled the proposed repo and confirmed that v0.19.3-1.1 of the package
installed without issues.

Running through the test case I can confirm that the import button is
now visible and can be used to import music.

Ran through a few regression tests to confirm that other sources toolbar
options were unaffected.

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

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

Title:
  [SRU] Rhythmbox: Cannot add more music after a collection has been
  created

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Fix Released
Status in rhythmbox-plugin-alternative-toolbar source package in Focal:
  Fix Committed
Status in rhythmbox-plugin-alternative-toolbar source package in Groovy:
  Fix Released

Bug description:
  Impact]

   * After a music collection has been first initialised with music
 tracks, the user loses the ability to add more tracks at a later
 date with the modern headerbar interface that is the default for
 Ubuntu and Ubuntu Budgie
   * Currently the workaround is unintuitive - they have to disable
 the plugin or change to the traditional interface.  They
 can then add more tracks using Rhythmbox's "Import" button on the
 main view source toolbar.
   * With the headerbar modern interface, Rhythmbox's "Import" button is
 hidden.  Previously the option was accessible via the menu
 which was a Ubuntu specific patch which was dropped at 20.04
   * The fix is not to manipulate the main view source toolbar buttons
 i.e. to leave all buttons such as the Import button visible

  [Test Case]

   * Ensure that the plugin is enabled in preferences and that the
 "modern" tickbox is enabled
   * Use "View - Show Source Toolbar" examine the source toolbar
 shown on the main Music source.
   * Using software-properties-gtk, enable the developer proposed
 repository and install the package
 rhythmbox-plugins-alternative-toolbar
   * Restart rhythmbox.  Check the buttons in the Music Source Toolbar
   * The import button should be visible.  Click the button and import
 more tracks as normal.

  [Regression Potential]

   * I suppose the worse-case scenario is that there is some hidden
 code in the headerbar interface that was expecting one or more
 buttons in the source toolbar to be hidden.  If such code existed
 unexpected functionality might be affected causing the plugin
 to malfunction
   * I've done a code-review and have found no evidence of such function.
   * This has been uploaded to Debian and has been available for a couple
 of weeks - by the time of this SRU release there should be more
 than enough time for both communities to verify that there are no
 adverse affects. 
   * The plugin can easily be disabled by the user or swapped to the alternative
 interfaces available if necessary.

  [Other Info]
   N/A

  ---

  Original description

  Please refer:

  https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1790

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1893113/+subscriptions

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