[Desktop-packages] [Bug 2081749] [NEW] package ubuntu-settings 24.04.4 failed to install/upgrade: unable to stat './usr/share/ubuntu-wayland/applications' (which was about to be installed): Bad messag

[Aaron Durow]

Public bug reported:

error

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: ubuntu-settings 24.04.4
Uname: Linux 6.8.0-44-generic x86_64
Architecture: amd64
Date: Mon Sep 23 10:32:42 2024
ErrorMessage: unable to stat './usr/share/ubuntu-wayland/applications' (which 
was about to be installed): Bad message
PackageArchitecture: all
SourcePackage: ubuntu-settings
Title: package ubuntu-settings 24.04.4 failed to install/upgrade: unable to 
stat './usr/share/ubuntu-wayland/applications' (which was about to be 
installed): Bad message

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


** Tags: amd64 apport-package

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

Title:
  package ubuntu-settings 24.04.4 failed to install/upgrade: unable to
  stat './usr/share/ubuntu-wayland/applications' (which was about to be
  installed): Bad message

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  error

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-settings 24.04.4
  Uname: Linux 6.8.0-44-generic x86_64
  Architecture: amd64
  Date: Mon Sep 23 10:32:42 2024
  ErrorMessage: unable to stat './usr/share/ubuntu-wayland/applications' (which 
was about to be installed): Bad message
  PackageArchitecture: all
  SourcePackage: ubuntu-settings
  Title: package ubuntu-settings 24.04.4 failed to install/upgrade: unable to 
stat './usr/share/ubuntu-wayland/applications' (which was about to be 
installed): Bad message

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

[Aaron Rainbolt]

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

** Also affects: wslu (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu Noble)
Milestone: None => ubuntu-24.04

** Changed in: wslu (Ubuntu Noble)
Milestone: None => ubuntu-24.04

-- 
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 ubuntu-meta package in Ubuntu:
  New
Status in wslu package in Ubuntu:
  New
Status in ubuntu-meta source package in Noble:
  New
Status in wslu source package in Noble:
  New

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/ubuntu-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 2060898] [NEW] Trying to install gimp-help-en threatens to install wslu

[Aaron Rainbolt]

Public bug reported:

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.

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

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

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

-- 
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 ubuntu-meta package in Ubuntu:
  New
Status in wslu package in Ubuntu:
  New

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 l

[Desktop-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

[Aaron Rainbolt]

We rewrote the update notifier in Qt/C++ and got rid of the aptdaemon
dependency earlier in the Noble cycle, so this is now resolved in Noble.

** Changed in: lubuntu-update-notifier (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  Confirmed
Status in apturl package in Ubuntu:
  Confirmed
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Confirmed
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-update-notifier package in Ubuntu:
  Fix Released
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in oem-config package in Ubuntu:
  Confirmed
Status in sessioninstaller package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

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

[Aaron Rainbolt]

I believe bwrap was ignored intentionally, as the point of the apparmor
change was to prevent arbitrary apps from making unprivileged user
namespaces with capabilities. Allowing Bubblewrap to do so would provide
a loophole. Same reason `unshare` isn't allowed to make unprivileged
namespaces with capabilities.

Perhaps something about libgnome-desktop is incorrectly assuming it
needs capabilities that it doesn't actually need? Or is the ability to
make unprivileged user namespaces with no capabilities failing somehow?

-- 
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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist

[Aaron Rainbolt]

I might try to SRU it into Jammy eventually (perhaps after the release
of Noble), but Focal is now unsupported from the perspective of all
flavors and I don't think Ubuntu Desktop has any use for software-
properties-qt as it has software-properties-gtk (I believe). Marking
Focal as Won't Fix for this reason.

** Changed in: software-properties (Ubuntu Focal)
   Status: Triaged => Won't Fix

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

Title:
  software-properties-{qt,kde} attempts to use KUrl but it doesn't exist

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Focal:
  Won't Fix
Status in software-properties source package in Jammy:
  Triaged
Status in software-properties source package in Kinetic:
  Won't Fix
Status in software-properties source package in Lunar:
  Triaged

Bug description:
  Release: Kubuntu 18.04
  Version: 0.96.24.32.1

  When clicking the "Import Key" button in the "Authentication" section
  of the panel it throws this error:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
 line 667, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  While this doesn't crash the program it causes nothing to happen when
  clicking the button. Running the program in a terminal reveals the
  error being printed to stderr.

  After debugging it appears KUrl doesn't exist anywhere and I'm not
  sure if's a python module that has changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 2049280] Re: udisks2 core dump

[Aaron Hernandez]

Hi!!

I present a similar issue


Here my data. Hope can help me.

$ sudo systemctl status udisks2
× udisks2.service - Disk Manager
 Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; preset: 
enabled)
 Active: failed (Result: core-dump) since Sun 2024-03-24 03:23:50 CST; 
19min ago
   Docs: man:udisks(8)
Process: 2615 ExecStart=/usr/libexec/udisks2/udisksd (code=dumped, 
signal=TRAP)
   Main PID: 2615 (code=dumped, signal=TRAP)
CPU: 11ms

mar 24 03:23:50 OldMachine systemd[1]: Starting udisks2.service - Disk 
Manager...
mar 24 03:23:50 OldMachine udisksd[2615]: udisks daemon version 2.10.1 starting
mar 24 03:23:50 OldMachine udisksd[2615]: failed to load module swap: 
/lib/x86_64-linux-gnu/libbd_swap.so.3: invalid ELF header
mar 24 03:23:50 OldMachine udisksd[2615]: Failed to load the 'swap' libblockdev 
plugin
mar 24 03:23:50 OldMachine systemd[1]: udisks2.service: Main process exited, 
code=dumped, status=5/TRAP
mar 24 03:23:50 OldMachine systemd[1]: udisks2.service: Failed with result 
'core-dump'.
mar 24 03:23:50 OldMachine systemd[1]: Failed to start udisks2.service - Disk 
Manager.


$ sudo apt search udisks2|grep -i install

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10


$ uname -a
Linux OldMachine 6.5.0-26-generic #26-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar  5 
21:19:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux


$ swapon -s
FilenameTypeSizeUsed
Priority
/swapfile   file2097148 0   
-2


$  apt search udisks2|grep -i install

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.


$ sudo lshw -c storage
  *-nvme
   descripción: NVMe device
   producto: SKHynix_HFS512GD9TNI-L2B0B
   fabricante: SK hynix
   id físico: 0
   información del bus: pci@:55:00.0
   nombre lógico: /dev/nvme0
   versión: 11720C10
   serie: CJA4N765010304Q5N
   anchura: 64 bits
   reloj: 33MHz
   capacidades: nvme pm msi msix pciexpress nvm_express bus_master cap_list
   configuración: driver=nvme latency=0 
nqn=nqn.2014.08.org.nvmexpress:1c5c1c5cCJA4N765010304Q5N   
SKHynix_HFS512GD9TNI-L2B0B state=live
   recursos: irq:16 memoria:ae00-ae003fff memoria:ae005000-ae005fff 
memoria:ae004000-ae004fff

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

Title:
  udisks2 core dump

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Running systemctl status on udisks2 shows core-dump being created.

  $ sudo systemctl status udisks2
  × udisks2.service - Disk Manager
   Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; preset: 
enabled)
   Active: failed (Result: core-dump) since Sat 2024-01-13 23:07:14 EET; 4s 
ago
     Docs: man:udisks(8)
  Process: 14345 ExecStart=/usr/libexec/udisks2/udisksd (code=dumped, 
signal=TRAP)
     Main PID: 14345 (code=dumped, signal=TRAP)
  CPU: 14ms

  Jan 13 23:07:14 testo systemd[1]: Starting udisks2.service - Disk Manager...
  Jan 13 23:07:14 testo udisksd[14345]: udisks daemon version 2.10.1 starting
  Jan 13 23:07:14 testo udisksd[14345]: failed to load module swap: 
/lib/x86_64-linux-gnu/libbd_swap.so.3: invalid ELF header
  Jan 13 23:07:14 testo udisksd[14345]: Failed to load the 'swap' libblockdev 
plugin
  Jan 13 23:07:14 testo systemd[1]: udisks2.service: Main process exited, 
code=dumped, status=5/TRAP
  Jan 13 23:07:14 testo systemd[1]: udisks2.service: Failed with result 
'core-dump'.
  Jan 13 23:07:14 testo systemd[1]: Failed to start udisks2.service - Disk 
Manager.

  Ubuntu version:

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  Kernel version:

  $ uname -a
  Linux testo 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 
14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Swap status:

  $ swapon -s
  FilenameTypeSizeUsed  
  Priority
  /swap.img   file8388604 0 
  -2

  Udisks2 package installation:

  $ apt search udisks2|grep -i install

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  libudisks2-0/mantic-updates,now 2.10.1-1ubuntu1.1 amd64 [installed,automatic]
  udisks2/mantic-updates,now 2.10.1-1ubuntu1.1 amd64 [installed,automatic]

  Storage specs:

  $ lshw -c storage
    *-nvme
     description: NVMe device
     product: SKHynix_HFS001TD9TNI-L2B0B
     vendor: SK hynix
     physical id: 0
     bus info: pci@:55:00.0
     logical name: /dev/nvme0
     version:

[Desktop-packages] [Bug 2047705] [NEW] Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration

[Aaron Rainbolt]

Public bug reported:

Lubuntu uses Qt as the primary framework for most of the apps we ship.
However, some functionality we ship in Lubuntu doesn't have a Qt
application that provides that functionality, so we have some GTK3 apps
that we ship as well. Starting in Lubuntu 24.04, we are adding and
enabling the breeze-gtk-theme package, providing more uniform theming
between Qt and GTK apps on Lubuntu. However, this bug makes this
impossible.

As we do not ship xsettingsd, but instead use the XDG specification for
shipping configuration, we are attempting to place the default
configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg-
Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini.
This solutions works for GTK2 apps, however GTK3 apps silently ignore
the vendored configuration file and are using a different theme.

As it turns out, this is because the /etc directory is given higher
priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration
files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini
file that sets Yaru as the default theme. GTK3 applications end up
selecting this configuration file rather than  /etc/xdg/xdg-
Lubuntu/gtk-3.0/settings.ini.

/etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini
file should go, as it makes it difficult for flavors who rely on XDG
configuration to override it without risking a file conflict.
(Technically I guess a flavor package *could* use dpkg-divert to simply
"get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the
wrong way to approach this.)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libgtk-3-0 3.24.38-5ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Fri Dec 29 10:08:23 2023
InstallationDate: Installed on 2023-10-22 (69 days ago)
InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

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

Title:
  Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to
  Yaru and preventing flavors from overriding it with XDG configuration

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Lubuntu uses Qt as the primary framework for most of the apps we ship.
  However, some functionality we ship in Lubuntu doesn't have a Qt
  application that provides that functionality, so we have some GTK3
  apps that we ship as well. Starting in Lubuntu 24.04, we are adding
  and enabling the breeze-gtk-theme package, providing more uniform
  theming between Qt and GTK apps on Lubuntu. However, this bug makes
  this impossible.

  As we do not ship xsettingsd, but instead use the XDG specification
  for shipping configuration, we are attempting to place the default
  configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg-
  Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini.
  This solutions works for GTK2 apps, however GTK3 apps silently ignore
  the vendored configuration file and are using a different theme.

  As it turns out, this is because the /etc directory is given higher
  priority than /etc/xdg/xdg-Lubuntu when searching for XDG
  configuration files, and as it happens, libgtk-3-0 ships a
  /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme.
  GTK3 applications end up selecting this configuration file rather than
  /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini.

  /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's
  settings.ini file should go, as it makes it difficult for flavors who
  rely on XDG configuration to override it without risking a file
  conflict. (Technically I guess a flavor package *could* use dpkg-
  divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but
  that seems like the wrong way to approach this.)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libgtk-3-0 3.24.38-5ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Fri Dec 29 10:08:23 2023
  InstallationDate: Installed on 2023-10-22 (69 days ago)
  InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+subscriptions


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

[Desktop-packages] [Bug 2003168] Re: Dash-to-dock and Ubuntu Dock may accidentally call each other [JS ERROR: TypeError: dockManager is null]

[Aaron Lichtman]

If Ubuntu Dock and dash-to-dock conflict, can the GNOME extension
manager prohibit you from enabling both at the same time?

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

Title:
  Dash-to-dock and Ubuntu Dock may accidentally call each other [JS
  ERROR: TypeError: dockManager is null]

Status in Dash to dock:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  SIdebar, files gets unresponsive after unlocking locked season.

  Clicking on search bar also freezes the whole season. Issue requires
  Restarting GTK3 or restarting the season.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-59.65-generic 5.15.78
  Uname: Linux 5.15.0-59-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 18 13:35:36 2023
  InstallationDate: Installed on 2021-06-20 (576 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/2003168/+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 1886271] Re: HEIF support should be installed by default

[Aaron Lichtman]

** Patch added: "0001-Add-HEIF-HEIC-support-by-default-on-desktop.patch"
   
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1886271/+attachment/5669349/+files/0001-Add-HEIF-HEIC-support-by-default-on-desktop.patch

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

Title:
  HEIF support should be installed by default

Status in Default settings and artwork for Baltix OS:
  Triaged
Status in eog package in Ubuntu:
  Confirmed

Bug description:
  The HEIF image file format [1] is getting quite popular, mainly
  because this is now the default image format for iOS [2].
  Unfortunately, this is not supported by default in Ubuntu (20.04). In
  practice, this means that if someone sends you a picture from an
  iPhone, you won't be able to look at it (and the error message in eog
  is just saying this "is not a image",  not hinting at all that
  installing a small package could solve it).

  Therefore, I'd recommend installing by default the following two extra 
packages. This is about 60kB: 
  heif-gdk-pixbuf
  heif-thumbnailer

  
  [1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format
  [2] https://www.imyfone.com/phone-data-transfer/what-is-iphone-heic/

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1886271/+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 1886271] Re: HEIF support should be installed by default

[Aaron Lichtman]

@mantas: I made the metapackage changes you mentioned here:
https://git.launchpad.net/~alichtman/ubuntu/+source/ubuntu-
meta/commit/?id=c67add66d28fd38cddfcdd9798339f8040b6589c

I opened a MR here:
https://code.launchpad.net/~alichtman/ubuntu/+source/ubuntu-
meta/+git/ubuntu-meta/+merge/442067. I'm not really sure if it's
targeting the right destination branch. It's my first ubuntu
contribution.

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

Title:
  HEIF support should be installed by default

Status in Default settings and artwork for Baltix OS:
  Triaged
Status in eog package in Ubuntu:
  Confirmed

Bug description:
  The HEIF image file format [1] is getting quite popular, mainly
  because this is now the default image format for iOS [2].
  Unfortunately, this is not supported by default in Ubuntu (20.04). In
  practice, this means that if someone sends you a picture from an
  iPhone, you won't be able to look at it (and the error message in eog
  is just saying this "is not a image",  not hinting at all that
  installing a small package could solve it).

  Therefore, I'd recommend installing by default the following two extra 
packages. This is about 60kB: 
  heif-gdk-pixbuf
  heif-thumbnailer

  
  [1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format
  [2] https://www.imyfone.com/phone-data-transfer/what-is-iphone-heic/

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1886271/+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 2016429] [NEW] Video-related errors during early bootup

[Aaron Rainbolt]

Public bug reported:

Note that this *could* be the Linux kernel or GRUB doing this, but I'm
not sure and Plymouth seems like a possible culprit, thus why it's
getting the report.

Steps to reproduce:

1. Download and boot any one of the Lunar Final ISOs on a BIOS system.
2. Install Ubuntu and reboot into the installed system.
3. Observe the console output during bootup.

Expected result: If any errors show up on the screen, they should be
non-alarming and look easily ignorable.

Actual result: The following two somewhat alarming errors appear on the
screen:

error: no server is specified.
error: no suitable video mode found.

The system then proceeds to boot up and everything appears normal.

This has been happening for a while, and I dismissed it as being
possibly related to the VM software I was using. However I was able to
reproduce it on physical hardware (an HP Pavilion dv7 laptop) today and
so thought it was worth a bug report.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: plymouth 22.02.122-3ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Sun Apr 16 14:38:48 2023
DefaultPlymouth: /usr/share/plymouth/themes/lubuntu-logo/lubuntu-logo.plymouth
InstallationDate: Installed on 2023-04-16 (0 days ago)
InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414)
Lsusb:
 Bus 002 Device 003: ID 5986:0143 Acer, Inc HP Webcam
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=92390da8-245d-4543-8074-8af0abdb05f9 ro quiet 
cryptdevice=UUID=5b17b927-2884-49a9-83d6-1ba23dfefe59:luks-5b17b927-2884-49a9-83d6-1ba23dfefe59
 root=/dev/mapper/luks-5b17b927-2884-49a9-83d6-1ba23dfefe59 splash vt.handoff=7
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=92390da8-245d-4543-8074-8af0abdb05f9 ro quiet 
cryptdevice=UUID=5b17b927-2884-49a9-83d6-1ba23dfefe59:luks-5b17b927-2884-49a9-83d6-1ba23dfefe59
 root=/dev/mapper/luks-5b17b927-2884-49a9-83d6-1ba23dfefe59 splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2010
dmi.bios.release: 15.29
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1D
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 363C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 32.25
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.ec.firmware.release: 50.37
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:br15.29:efr50.37:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:skuVM188UA#ABA:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.sku: VM188UA#ABA
dmi.product.version: 039D222412102
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug iso-testing lunar

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

Title:
  Video-related errors during early bootup

Status in plymouth package in Ubuntu:
  New

Bug description:
  Note that this *could* be the Linux kernel or GRUB doing this, but I'm
  not sure and Plymouth seems like a possible culprit, thus why it's
  getting the report.

  Steps to reproduce:

  1. Download and boot any one of the Lunar Final ISOs on a BIOS system.
  2. Install Ubuntu and reboot into the installed system.
  3. Observe the console output during bootup.

  Expected result: If any errors show up on the screen, they should be
  non-alarming and look easily ignorable.

  Actual result: The following two somewhat alarming errors appear on
  the screen:

  error: no server is specified.
  error: no suitable video mode found.

  The system then proceeds to boot up and everything appears normal.

  This has been happening for a while, and I dismissed it as being
  possibly related to the VM software I was using. However I was able to
  reproduce it on physical hardware (an HP Pavilion dv7 laptop) today
  and so thought it was worth a bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: plymouth 22.02.122-3ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-

[Desktop-packages] [Bug 2013369] [NEW] indicator-messages-service crashes shortly after logging in

[Aaron Rainbolt]

Public bug reported:

Steps to reproduce:

1. Boot the latest Ubuntu Cinnamon Lunar Beta ISO.
2. Click "Try Ubuntu Cinnamon".
3. Wait for a bit.

Expected result: Nothing should crash.

Actual result: indicator-messages-service crashes and an Apport window
is displayed as a result.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.480
CurrentDesktop: X-Cinnamon
Date: Thu Mar 30 16:01:26 2023
LiveMediaBuild: Ubuntu-Cinnamon 23.04 "Lunar Lobster" - Beta amd64 (20230329.1)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: indicator-messages
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-messages (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar

** Description changed:

  Steps to reproduce:
  
  1. Boot the latest Ubuntu Cinnamon Lunar Beta ISO.
  2. Click "Try Ubuntu Cinnamon".
  3. Wait for a bit.
  
  Expected result: Nothing should crash.
  
- Actual result: indicator-messages-service crashes and displays an Apport
- window as a result.
+ Actual result: indicator-messages-service crashes and an Apport window
+ is displayed as a result.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.480
  CurrentDesktop: X-Cinnamon
  Date: Thu Mar 30 16:01:26 2023
  LiveMediaBuild: Ubuntu-Cinnamon 23.04 "Lunar Lobster" - Beta amd64 
(20230329.1)
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  indicator-messages-service crashes shortly after logging in

Status in indicator-messages package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Boot the latest Ubuntu Cinnamon Lunar Beta ISO.
  2. Click "Try Ubuntu Cinnamon".
  3. Wait for a bit.

  Expected result: Nothing should crash.

  Actual result: indicator-messages-service crashes and an Apport window
  is displayed as a result.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.480
  CurrentDesktop: X-Cinnamon
  Date: Thu Mar 30 16:01:26 2023
  LiveMediaBuild: Ubuntu-Cinnamon 23.04 "Lunar Lobster" - Beta amd64 
(20230329.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/2013369/+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 2012160] Re: Proprietary Broadcom WiFi drivers are not compiled and loaded when installing Ubuntu MATE with proprietary drivers enabled

[Aaron Rainbolt]

Booted from an Ubuntu Desktop Legacy ISO, and ran "ubuntu-drivers
devices" and "ubuntu-drivers list" to get more info.

ubuntu-drivers devices:

== /sys/devices/pci:00/:00:1c.3/:24:00.0 ==
modalias : pci:v14E4d4359sv103Csd182Cbc02sc80i00
vendor   : Broadcom Inc. and subsidiaries
model: BCM43228 802.11a/b/g/n (BCM943228HM4L 802.11a/b/g/n 2x2 Wi-Fi 
Adapter)
driver   : broadcom-sta-dkms - distro non-free


ubuntu-drivers list

broadcom-sta-dkms, (kernel modules provided by broadcom-sta-dkms)


(Note that I typed these across since the live env didn't have Internet
access, if I messed something up I'll go get an Ethernet cable and try
again with termbin.)

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

Title:
  Proprietary Broadcom WiFi drivers are not compiled and loaded when
  installing Ubuntu MATE with proprietary drivers enabled

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Hardware: HP Elitebook 8570p, UEFI, no secure boot, Broadcom WiFi, 16
  GB RAM, 120 GB SSD, 3rd Gen Intel Core i5.

  Steps to reproduce:

  1. Flash the latest daily image of Ubuntu MATE Lunar to a USB drive.
  2. Boot a laptop with Broadcom WiFi from the drive.
  3. Select "Try or Install Ubuntu MATE" at the GRUB menu.
  4. Click "Install Ubuntu MATE".
  5. Accept all default settings until you reach the "Installation type" screen.
  6. Check the box to install proprietary drivers.
  7. Proceed to the next screen.

  Expected result: ubuntu-drivers should be run in the background,
  detecting the WiFi chipset and installing the needed bcmwl-kernel-
  source driver. WiFi should become enabled when this happens, while
  still in the live ISO session.

  Actual result: ubuntu-drivers runs for a very short time according to
  the installer screen, then the next screen appears and WiFi is still
  disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubiquity 23.04.4
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.480
  CurrentDesktop: MATE
  Date: Sun Mar 19 02:10:21 2023
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 23.04 "Lunar Lobster" - Alpha amd64 (20230318)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2012160/+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 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

Looks like Sean was right - removing libva-wayland2 and then rebooting
resolved the issue.

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

I can't reproduce this on Ubuntu MATE (though I can make other things
crash sadly).

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

Interestingly, I'm not getting any XFCE-related crashes when I use
gnome-boxes rather than QEMU. The process that is crashing is actually
X.

I got a backtrace from it:

(gdb) bt -full
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=)
at ./nptl/pthread_kill.c:44
tid = 
ret = 0
pd = 
old_mask = {__val = {0}}
ret = 
pd = 
old_mask = 
ret = 
tid = 
ret = 
resultvar = 
resultvar = 
__arg3 = 
__arg2 = 
__arg1 = 
_a3 = 
_a2 = 
_a1 = 
__futex = 
resultvar = 
__arg3 = 
__arg2 = 
__arg1 = 
_a3 = 
_a2 = 
_a1 = 
__futex = 
__private = 
__oldval = 
#1  __pthread_kill_internal (signo=6, threadid=)
at ./nptl/pthread_kill.c:78
No locals.
#2  __GI___pthread_kill (threadid=, signo=signo@entry=6)
at ./nptl/pthread_kill.c:89
No locals.
#3  0x7f39b123c406 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/posix/raise.c:26
ret = 
#4  0x7f39b122287c in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20}, 
  sa_mask = {__val = {0 }}, sa_flags = 67108868, 
  sa_restorer = 0x7f39b123c4b0 <__restore_rt>}
#5  0x558075c86b60 in OsAbort () at ../../../../os/utils.c:1352
No locals.
#6  0x558075c8c319 in AbortServer () at ../../../../os/log.c:879
No locals.
#7  0x558075c8d359 in FatalError (
f=f@entry=0x558075cbee90 "Caught signal %d (%s). Server aborting\n")
at ../../../../os/log.c:1017
args = {{gp_offset = 24, fp_offset = 48, 
overflow_arg_area = 0x7ffd9edeb5a0, 
reg_save_area = 0x7ffd9edeb4d0}}
args2 = {{gp_offset = 8, fp_offset = 48, 
overflow_arg_area = 0x7ffd9edeb5a0, 
reg_save_area = 0x7ffd9edeb4d0}}
beenhere = 1
#8  0x558075c83ddc in OsSigHandler (unused=, 
sip=, signo=6) at ../../../../os/osinit.c:156
No locals.
#9  OsSigHandler (signo=6, sip=, unused=)
at ../../../../os/osinit.c:110
No locals.
#10 
No locals.
#11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=)
at ./nptl/pthread_kill.c:44
tid = 
ret = 0
pd = 
old_mask = {__val = {139885759425152}}
ret = 
pd = 
old_mask = 
ret = 
tid = 
ret = 
resultvar = 
resultvar = 
__arg3 = 
__arg2 = 
__arg1 = 
_a3 = 
_a2 = 
_a1 = 
__futex = 
resultvar = 
__arg3 = 
__arg2 = 
__arg1 = 
_a3 = 
_a2 = 
_a1 = 
__futex = 
__private = 
__oldval = 
#12 __pthread_kill_internal (signo=6, threadid=)
at ./nptl/pthread_kill.c:78
No locals.
#13 __GI___pthread_kill (threadid=, signo=signo@entry=6)
at ./nptl/pthread_kill.c:89
No locals.
#14 0x7f39b123c406 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/posix/raise.c:26
ret = 
#15 0x7f39b122287c in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20}, 
  sa_mask = {__val = {94010244971792, 110, 0, 139885763323770, 0, 
  49245412224, 0, 140727268852584, 15975794021409362944, 5, 
  18446744073709550696, 11, 94010220322512, 122, 94010220302986, 
  94010220853328}}, sa_flags = -1322649741, 
  sa_restorer = 0x7f39b13b677a <_nl_C_name>}
#16 0x7f39b122279b in __assert_fail_base (
fmt=0x7f39b13b9f68 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", 
assertion=assertion@entry=0x558075c9528a "key->initialized", 
file=file@entry=0x558075c99ed0 "../../../../../../include/privates.h", 
line=line@entry=122, 
function=function@entry=0x558075cb9580 <__PRETTY_FUNCTION__.7> 
"dixGetPrivateAddr") at ./assert/assert.c:92
str = 0x55807741bd10 "\273\2238/\205U"
total = 4096
#17 0x7f39b1233b86 in __assert_fail (
assertion=assertion@entry=0x558075c9528a "key->initialized", 
file=file@entry=0x558075c99ed0 "../../../../../../include/privates.h", 
line=line@entry=122, 
function=function@entry=0x558075cb9580 <__PRETTY_FUNCTION__.7> 
"dixGetPrivateAddr") at ./assert/assert.c:101
No locals.
#18 0x558075c3ba25 in dixGetPrivateAddr (
key=0x558075d57020 , privates=0x71)
at ../../../../../../include/privates.h:122
__PRETTY_FUNCTION__ = "dixGetPrivateAddr"
#19 0x558075c3dd25 in dixGetPrivateAddr (key=, 
privates=) at ../../../../../../include/privates.h:167
__PRETTY_FUNCTION__ = "dixGetPrivateAddr"
#20 dixLookupPrivate (key=, privates=)
at ../../../../../../include/privates.h:165
No locals.
#21 DRI2Authenticate (client=client@entry=0x558077415b80, 
pScreen=, magic=1)
at ../../../../../../hw/xfree86/dri2/dri2.c:1365
 

[Desktop-packages] [Bug 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

And there's more random crashes. (xiccd being the next one to go kaput)
All of this in a pure QEMU VM.

My guess is xfce4-power-manager crashes thanks to GLib and that takes
down other stuff at random. Not sure how that would be triggered by the
third-party software option, but that's what I'm seeing here.

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

Hmm, and now xfce4-power-manager.

Looking at the stacktrace when xfce4-power-manager goes awry, it's
GLib's fault. Which means we probably have another slice allocator
removal causing problems.

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 2013071] Re: Session crash after initial login

[Aaron Rainbolt]

I notice a blueman-applet crash when I reproduce this.

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

Latest patch has requested changes. Bug has been submitted to upstream
Debian here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033385

** Bug watch added: Debian Bug tracker #1033385
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033385

** Patch added: "glib_crash_bugfix_v5.patch"
   
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751/+attachment/5657088/+files/glib_crash_bugfix_v5.patch

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could [not] work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on link/something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

Gah, ok, one more try. I failed to update the debian/copyright file last
time. This version has the updated copyright file.

** Patch added: "glib_crash_bugfix.patch"
   
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751/+attachment/5657032/+files/glib_crash_bugfix.patch

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could [not] work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on link/something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

After a discussion with dbungert, we're using a different patch instead.
This one is possibly upstream already, which makes it superior to the
original patch I was suggesting since it means less maintenance overhead
in the future.

** Patch added: "glib_crash_bugfix.patch"
   
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751/+attachment/5657030/+files/glib_crash_bugfix.patch

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could [not] work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on link/something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

New patch, same approach, but with a fallback added if itPrev turns out
to be null.

** Patch added: "glib_crash_bugfix.patch"
   
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751/+attachment/5656971/+files/glib_crash_bugfix.patch

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could [not] work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on link/something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

One worry I am having with my patch now is, what happens if the first
element is the one being modified? Then itPrev is a null pointer. I
*think* from looking at the GLib code that g_list_next will then return
null when it it handed itPrev, which means "it" will be set to null,
which I believe will trigger the end of the loop. Assuming I know what
I'm looking at, that could put Openbox in an unusual state that could
cause problems later down the road.

To get around that, I can add a check to see if itPrev is null, and if
so, it will set "it" to stacking_list, which is where it is supposed to
end up.

(I'm trying to *not* use the patch from Arch Linux's forums, since I
really hate the fact that it has to loop through a bunch of the list
every time it modifies an element. That seems quite inefficient.)

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could [not] work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on link/something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

(One extra bit of info that I realized was left out - according to the
comment on the Arch Linux forums here:
https://bbs.archlinux.org/viewtopic.php?pid=2090270#p2090270 the first
loop iteration succeeds. It's not until the second iteration (after the
list has been modified) that the crash occurs. Thus why I believe the
one-item case to be safe.

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could [not] work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on link/something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

OK, so I'm not entirely sure testing the one item case is even possible
since the crash happens when switching from a fullscreen window (which
implies that there are at least two windows). However, this is what I
did, and everything was successful (no crashes).

1. Boot a Lubuntu Lunar ISO, and install the patched Openbox into it.
2. Log out.
3. Log in, but with a plain Openbox session. No desktop, no panel, no LXQt, 
just Openbox.
4. Open a terminal emulator, and run "firefox &" followed by "diswon 
". Then close the terminal emulator.
5. Fullscreen Firefox with F11.
6. Attempt to "switch" out of Firefox with Alt+Tab. No crashes occur.
7. Open Wikipedia.
8. Right-click on a link and click "Open in new window". No crashes occur (this 
is what was able to reliably trigger the crash before).
9. Switch between the fullscreen and non-fullscreen window with Alt+Tab. Still 
no crashes.
10: Fullscreen the second Firefox window and switch between them with Alt+Tab. 
Still no crashes.
11: Take both Firefox windows out of fullscreen and switch between them. Still 
no crashes.


I did a bit more than that, but that should cover the one-item and two-item 
test cases.

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

@dbungert: While the patch that simply copies the list is a possible way
of doing things, a very experienced user on the Arch Linux forums had
concerns about doing things that way, see
https://bbs.archlinux.org/viewtopic.php?pid=2090570#p2090570 "But
creating a copy of the list is inefficient and only glosses over the
actual problem (and probably will cause X11 errors and/or behavioral
differences - maybe maintain them b/c of the status quo ante)"

In the two-item case, as long as the rest of Openbox code keeps the list
consistent after removing *and adding* an item (because keep in mind the
code doesn't just remove stuff, it also adds stuff), everything should
be fine. itPrev->next should point to a valid item unless the underlying
list has become corrupted.

In the one item case, the first iteration through the loop works, and
with only one item, there will only be one iteration through the loop,
so presumably the crash won't happen unless the one item case triggers a
crash in some other way.

I'll test both and report back what happens.

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

I don't have upload access to this package yet (it's not in the Lubuntu
packageset apparently) so I'm uploading the patch here so that it can be
sponsored.

** Patch added: "glib_crash_bugfix.patch"
   
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751/+attachment/5656433/+files/glib_crash_bugfix.patch

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

** Changed in: openbox (Ubuntu)
 Assignee: (unassigned) => Aaron Rainbolt (arraybolt3)

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011751] Re: openbox crashed with SIGABRT

[Aaron Rainbolt]

I believe we have a working patch for the problem. A quick summary of
what it looks like is happening:

Openbox maintains a list of windows organized by stacking order from
highest to lowest. This is a doubly-linked list.

There is a function in Openbox called client_calc_layer that uses a
pointer into this list to walk through it while modifying it. When
client_calc_layer modifies the list, it also messes up the pointer that
it is actively using to walk through the list. The next element that
Openbox loads contains a dangling pointer, and that promptly results in
a segfault when Openbox tries to dereference that pointer.

To solve the problem, I added a patch that makes Openbox save a pointer
to the list element *before* the current element before modifying the
list. When the list is then modified, the still-valid pointer to the
previous list element is used to get a new (and actually usable!)
pointer to the current list element. The old, broken pointer is then
overwritten by the new, working pointer, and the segfaults stop.

Using the patch, I am no longer able to reproduce this bug when
following the testcase (open a browser fullscreen, right-click a link,
and click "Open in new window"). I have the patched Openbox uploaded to
a PPA here: https://launchpad.net/~arraybolt3/+archive/ubuntu/openbox

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 2011758] Re: [REGRESSION] Firefox is ignoring Lubuntu's theme settings entirely

[Aaron Rainbolt]

I reported this upstream as
https://bugzilla.mozilla.org/show_bug.cgi?id=1823086. The answer I got
ultimately was:

-

So there are two things that are different:

* System titlebar is hidden: That's by design, you can go to right click -> 
Customize Toolbar ... and uncheck Titlebar to get the older behavior, see bug 
1812289.
* Selection color etc is different to other GTK3 apps (try apt install gedit 
for example). That's on the Snap config afaict.

-

I guess that makes sense, but it means that if we want the old behavior
back, we'll have to change something on our end.

** Bug watch added: Mozilla Bugzilla #1823086
   https://bugzilla.mozilla.org/show_bug.cgi?id=1823086

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

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

Title:
  [REGRESSION] Firefox is ignoring Lubuntu's theme settings entirely

Status in firefox package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Boot the latest Lubuntu Lunar ISO.
  2. Open KCalc and note the theming on the title bar.
  3. Open Firefox.

  Expected result: Theming should be consistent between all apps,
  including KCalc and Firefox.

  Actual result: Firefox's title bar has distinctively GNOME theming,
  which looks out of place.

  Additional info:

  This bug seems to have coincided with
  bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011753. Since both
  bugs appear Snap-related, this might not be coincidental.

  I'm wondering if maybe Firefox is ignoring or is unable to read XDG
  settings somehow? That seems like it might cause this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: snapd 2.58.3+23.04ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Wed Mar 15 20:48:51 2023
  InstallationDate: Installed on 2023-03-16 (0 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230314)
  SnapChanges: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2011758/+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 2011758] Re: [REGRESSION] Firefox is ignoring Lubuntu's theme settings entirely

[Aaron Rainbolt]

Ah, I thought this was probably related to the new GNOME snap thingy or
possibly a configuration change in the Snap itself. In that instance I
will take it upstream.

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

Title:
  [REGRESSION] Firefox is ignoring Lubuntu's theme settings entirely

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1. Boot the latest Lubuntu Lunar ISO.
  2. Open KCalc and note the theming on the title bar.
  3. Open Firefox.

  Expected result: Theming should be consistent between all apps,
  including KCalc and Firefox.

  Actual result: Firefox's title bar has distinctively GNOME theming,
  which looks out of place.

  Additional info:

  This bug seems to have coincided with
  bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011753. Since both
  bugs appear Snap-related, this might not be coincidental.

  I'm wondering if maybe Firefox is ignoring or is unable to read XDG
  settings somehow? That seems like it might cause this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: snapd 2.58.3+23.04ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Wed Mar 15 20:48:51 2023
  InstallationDate: Installed on 2023-03-16 (0 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230314)
  SnapChanges: no changes found
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2011758/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist

[Aaron Rainbolt]

** Also affects: software-properties (Ubuntu Lunar)
   Importance: Undecided
   Status: Triaged

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

Title:
  software-properties-{qt,kde} attempts to use KUrl but it doesn't exist

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Focal:
  Triaged
Status in software-properties source package in Jammy:
  Triaged
Status in software-properties source package in Kinetic:
  Triaged
Status in software-properties source package in Lunar:
  Triaged

Bug description:
  Release: Kubuntu 18.04
  Version: 0.96.24.32.1

  When clicking the "Import Key" button in the "Authentication" section
  of the panel it throws this error:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
 line 667, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  While this doesn't crash the program it causes nothing to happen when
  clicking the button. Running the program in a terminal reveals the
  error being printed to stderr.

  After debugging it appears KUrl doesn't exist anywhere and I'm not
  sure if's a python module that has changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 1993370] Re: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic

[Aaron Rainbolt]

This bug also affects the latest Jammy daily ISO.

** Also affects: software-properties (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: software-properties (Ubuntu Kinetic)
   Status: New => Fix Committed

** Summary changed:

- Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic
+ Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Jammy 
22.04.2 and Kinetic

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

Title:
  Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio
  Jammy 22.04.2 and Kinetic

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Jammy:
  New
Status in software-properties source package in Kinetic:
  Fix Committed

Bug description:
  Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel
  Core i5, UEFI, no secure boot, Broadcom WiFi.

  OS: Ubuntu Studio Kinetic, Final ISO

  Steps to reproduce:

  1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the 
system normally. (No encryption, allow Internet access during installation 
using some method of connectivity other than WiFi.)
  2. Reboot and log into the newly installed system.
  3. Open a terminal and run "sudo software-properties-kde".
  4. Click "Additional Drivers" in the window that pops up.
  5. Click "Using Broadcom 802.11 Linux STA wireless driver source from 
bcmwl-kernel-source (proprietary)".

  Expected result: The Apply Changes button should become clickable,
  allowing the user to install the driver.

  Actual result: The button remains grayed out, and the following error
  message is printed in the terminal:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1063, in on_driver_selection_changed
  modules_package_obj = self.apt_cache[modules_package]
  TypeError: Expected a string or a pair of strings

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: software-properties-qt 0.99.27
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
  Uname: Linux 5.19.0-1007-lowlatency x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Oct 18 21:33:51 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 
(20221017.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1993370/+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 2003661] [NEW] File drag-n-drop, automatic resolution changing, and shared clipboard are all broken on Kubuntu 22.10

[Aaron Rainbolt]

Public bug reported:

Note that, in my experience, this bug *only* affect Kubuntu 22.10 and
Ubuntu Studio 22.10, however Ubuntu Studio specifically does not support
VMs, and I assume that fixing the problem in Kubuntu will fix the
problem in Ubuntu Studio too.

Steps to reproduce:

1. Install GNOME Boxes on an Ubuntu machine.
2. Install Kubuntu 22.10 into a GNOME Boxes virtual machine.
3. Maximize the GNOME Boxes window.
4. Boot the newly installed system.

Expected result: The VM resolution should change itself to fit the
window perfectly.

Actual result: The VM resolution remains at some default resolution
(1024x768?).

Additional details: Shared clipboard also does not work (the clipboard
of the host and the guest remain separate), and file drag-n-drop from
host to guest does not work (no files are transferred into the guest).
All of these features work out of the box on all flavors of Ubuntu 22.04
(Kubuntu and Ubuntu Studio included), and on all flavors of Ubuntu 22.10
except for Kubuntu and Ubuntu Studio.

Also, I do not remember having tested file drag-n-drop or shared
clipboard on Ubuntu Studio, but I have tested both on Kubuntu.

I believe this is the result of spice-vdagent either failing to start,
dying shortly after starting, or glitching and remaining active but not
actually doing anything its supposed to. If I stop all services related
to spice-vdagent (spice-vdagentd.socket, spice-vdagentd, and spice
vdagent, note the "d" at the end of the first two), ensure that all
spice-vdagent and spice-vdagentd processes are terminated by using
killall, and then run "sudo spice-vdagentd -x" in a terminal, then I am
able to set the VM screen resolution to match the window perfectly.
Shared clipboard and file drag-n-drop still don't work, though.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: spice-vdagent 0.22.1-3
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Sun Jan 22 17:46:18 2023
InstallationDate: Installed on 2023-01-22 (0 days ago)
InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: spice-vdagent
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: spice-vdagent (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic

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

Title:
  File drag-n-drop, automatic resolution changing, and shared clipboard
  are all broken on Kubuntu 22.10

Status in spice-vdagent package in Ubuntu:
  New

Bug description:
  Note that, in my experience, this bug *only* affect Kubuntu 22.10 and
  Ubuntu Studio 22.10, however Ubuntu Studio specifically does not
  support VMs, and I assume that fixing the problem in Kubuntu will fix
  the problem in Ubuntu Studio too.

  Steps to reproduce:

  1. Install GNOME Boxes on an Ubuntu machine.
  2. Install Kubuntu 22.10 into a GNOME Boxes virtual machine.
  3. Maximize the GNOME Boxes window.
  4. Boot the newly installed system.

  Expected result: The VM resolution should change itself to fit the
  window perfectly.

  Actual result: The VM resolution remains at some default resolution
  (1024x768?).

  Additional details: Shared clipboard also does not work (the clipboard
  of the host and the guest remain separate), and file drag-n-drop from
  host to guest does not work (no files are transferred into the guest).
  All of these features work out of the box on all flavors of Ubuntu
  22.04 (Kubuntu and Ubuntu Studio included), and on all flavors of
  Ubuntu 22.10 except for Kubuntu and Ubuntu Studio.

  Also, I do not remember having tested file drag-n-drop or shared
  clipboard on Ubuntu Studio, but I have tested both on Kubuntu.

  I believe this is the result of spice-vdagent either failing to start,
  dying shortly after starting, or glitching and remaining active but
  not actually doing anything its supposed to. If I stop all services
  related to spice-vdagent (spice-vdagentd.socket, spice-vdagentd, and
  spice vdagent, note the "d" at the end of the first two), ensure that
  all spice-vdagent and spice-vdagentd processes are terminated by using
  killall, and then run "sudo spice-vdagentd -x" in a terminal, then I
  am able to set the VM screen resolution to match the window perfectly.
  Shared clipboard and file drag-n-drop still don't work, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: spice-vdagent 0.22.1-3
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sun Jan 22 17:46:18 2023
  InstallationDate: Installed on 2023-01-22 (0 days ago)
  InstallationMedia: Kubun

[Desktop-packages] [Bug 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

[Aaron Rainbolt]

(all those "no longer affects" is me figuring out what I'm doing with
Launchpad bug management and changing my mind about pressing a button,
please disregard)

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

Title:
  xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

Status in lubuntu-default-settings package in Ubuntu:
  In Progress
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu 20.04 daily QA-test on
  hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  
  Displays have been adjusted to my setup (one above the other) but I doubt 
this is an issue

  I suspended system, waited, pressed ESC to wake & it resumed to
  xscreensaver, but 'flurry' was chopped and showing white/black patches
  on display as if glitching... I touched mouse & my session removed.

  opened xscreensaver & preview - yep glitch there too... changed to
  'fliptext' & no issues, but flurry is very jerky with image switching
  to almost-blocky-bad-signal (I think it's alternating between showing
  something else, text; it seems to vary on what I've had on screen
  before screensaver is loaded & continuing to show xscreensaver..)

  attempts to screengrab with delay have failed (just capturing black
  screen)..

  `lshw -C video` reports I'm using nouveau.

  This issue may not relate to 'xserver-xorg-video-nouveau', but I
  suspect it's there. I've performed this test a number of times on
  various boxes without issue (will do so again once I shutdown this).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.432
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Dec  5 04:04:51 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492]
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191204)
  MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash ---
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E1 v01.05
  dmi.board.name: 0A54h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7700 Small Form Factor
  dmi.product.sku: ET090AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1855220/+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 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

[Aaron Rainbolt]

** Tags added: lunar

** Also affects: xserver-xorg-video-nouveau (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: lubuntu-default-settings (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-nouveau (Ubuntu Lunar)
   Importance: Undecided
   Status: Confirmed

** Also affects: lubuntu-default-settings (Ubuntu Lunar)
   Importance: Low
 Assignee: Aaron Rainbolt (arraybolt3)
   Status: In Progress

** No longer affects: lubuntu-default-settings (Ubuntu Kinetic)

** No longer affects: xserver-xorg-video-nouveau (Ubuntu Kinetic)

** No longer affects: xserver-xorg-video-nouveau (Ubuntu Lunar)

** No longer affects: lubuntu-default-settings (Ubuntu Lunar)

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

Title:
  xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

Status in lubuntu-default-settings package in Ubuntu:
  In Progress
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu 20.04 daily QA-test on
  hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  
  Displays have been adjusted to my setup (one above the other) but I doubt 
this is an issue

  I suspended system, waited, pressed ESC to wake & it resumed to
  xscreensaver, but 'flurry' was chopped and showing white/black patches
  on display as if glitching... I touched mouse & my session removed.

  opened xscreensaver & preview - yep glitch there too... changed to
  'fliptext' & no issues, but flurry is very jerky with image switching
  to almost-blocky-bad-signal (I think it's alternating between showing
  something else, text; it seems to vary on what I've had on screen
  before screensaver is loaded & continuing to show xscreensaver..)

  attempts to screengrab with delay have failed (just capturing black
  screen)..

  `lshw -C video` reports I'm using nouveau.

  This issue may not relate to 'xserver-xorg-video-nouveau', but I
  suspect it's there. I've performed this test a number of times on
  various boxes without issue (will do so again once I shutdown this).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.432
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Dec  5 04:04:51 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492]
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191204)
  MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash ---
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E1 v01.05
  dmi.board.name: 0A54h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7700 Small Form Factor
  dmi.product.sku: ET090AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1855220/+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 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

[Aaron Rainbolt]

** Also affects: lubuntu-default-settings (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: lubuntu-default-settings (Ubuntu)
 Assignee: (unassigned) => Aaron Rainbolt (arraybolt3)

** Changed in: lubuntu-default-settings (Ubuntu)
   Importance: Undecided => Low

** Changed in: lubuntu-default-settings (Ubuntu)
   Status: New => In Progress

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

Title:
  xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

Status in lubuntu-default-settings package in Ubuntu:
  In Progress
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu 20.04 daily QA-test on
  hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  
  Displays have been adjusted to my setup (one above the other) but I doubt 
this is an issue

  I suspended system, waited, pressed ESC to wake & it resumed to
  xscreensaver, but 'flurry' was chopped and showing white/black patches
  on display as if glitching... I touched mouse & my session removed.

  opened xscreensaver & preview - yep glitch there too... changed to
  'fliptext' & no issues, but flurry is very jerky with image switching
  to almost-blocky-bad-signal (I think it's alternating between showing
  something else, text; it seems to vary on what I've had on screen
  before screensaver is loaded & continuing to show xscreensaver..)

  attempts to screengrab with delay have failed (just capturing black
  screen)..

  `lshw -C video` reports I'm using nouveau.

  This issue may not relate to 'xserver-xorg-video-nouveau', but I
  suspect it's there. I've performed this test a number of times on
  various boxes without issue (will do so again once I shutdown this).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.432
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Dec  5 04:04:51 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492]
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191204)
  MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash ---
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E1 v01.05
  dmi.board.name: 0A54h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7700 Small Form Factor
  dmi.product.sku: ET090AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1855220/+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 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

[Aaron Rainbolt]

Interesting. For me, the problem is easily reproducible on an Acer
Chromebook C720 with a 2nd gen Intel Celeron with an Intel iGPU. And I
*think* (though can't remember for sure) that this happens on a Compaq
laptop around here with an AMD iGPU. All of these with single screens.
So I don't think it can be NVIDIA-specific.

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

Title:
  xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu 20.04 daily QA-test on
  hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  
  Displays have been adjusted to my setup (one above the other) but I doubt 
this is an issue

  I suspended system, waited, pressed ESC to wake & it resumed to
  xscreensaver, but 'flurry' was chopped and showing white/black patches
  on display as if glitching... I touched mouse & my session removed.

  opened xscreensaver & preview - yep glitch there too... changed to
  'fliptext' & no issues, but flurry is very jerky with image switching
  to almost-blocky-bad-signal (I think it's alternating between showing
  something else, text; it seems to vary on what I've had on screen
  before screensaver is loaded & continuing to show xscreensaver..)

  attempts to screengrab with delay have failed (just capturing black
  screen)..

  `lshw -C video` reports I'm using nouveau.

  This issue may not relate to 'xserver-xorg-video-nouveau', but I
  suspect it's there. I've performed this test a number of times on
  various boxes without issue (will do so again once I shutdown this).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.432
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Dec  5 04:04:51 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492]
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191204)
  MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash ---
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E1 v01.05
  dmi.board.name: 0A54h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7700 Small Form Factor
  dmi.product.sku: ET090AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1855220/+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 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

[Aaron Rainbolt]

I've noticed this problem also on slower systems of mine (an Acer
Chromebook C720 for instance). This leads me to believe that system
speed (or perhaps graphics subsystem speed?) is the culprit here, as
other systems work with flurry just fine.

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

Title:
  xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Lubuntu 20.04 daily QA-test on
  hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  
  Displays have been adjusted to my setup (one above the other) but I doubt 
this is an issue

  I suspended system, waited, pressed ESC to wake & it resumed to
  xscreensaver, but 'flurry' was chopped and showing white/black patches
  on display as if glitching... I touched mouse & my session removed.

  opened xscreensaver & preview - yep glitch there too... changed to
  'fliptext' & no issues, but flurry is very jerky with image switching
  to almost-blocky-bad-signal (I think it's alternating between showing
  something else, text; it seems to vary on what I've had on screen
  before screensaver is loaded & continuing to show xscreensaver..)

  attempts to screengrab with delay have failed (just capturing black
  screen)..

  `lshw -C video` reports I'm using nouveau.

  This issue may not relate to 'xserver-xorg-video-nouveau', but I
  suspect it's there. I've performed this test a number of times on
  various boxes without issue (will do so again once I shutdown this).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.432
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Dec  5 04:04:51 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492]
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191204)
  MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash ---
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E1 v01.05
  dmi.board.name: 0A54h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7700 Small Form Factor
  dmi.product.sku: ET090AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1855220/+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 1974179] Re: Kubuntu: Noto Color Emoji

[Aaron Rainbolt]

Thank you for taking the time to report this bug. I'm having a hard time
reproducing this on my end, could you provide more exact steps on how to
reproduce this so that we can debug this easier? In particular, you say
that this bug affects a "GUI developed in Qt" - is this an application
that you've downloaded and are trying to run, or is this a custom-made
application using your own code? If it's an app, could you tell us what
app? And if it's your own code, could you provide us with a small sample
project that is able to reproduce the bug?

** Changed in: fonts-noto-color-emoji (Ubuntu)
   Status: New => Incomplete

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

Title:
  Kubuntu: Noto Color Emoji

Status in fonts-noto-color-emoji package in Ubuntu:
  Incomplete

Bug description:
  I am working on Kubuntu 22.04 LTS. It has been observed that with some
  GUI was not opening due to the Font Type Noto Color Emoji. Disabling
  this the GUI was successfully opened. executing the command

  "#display /usr/share/fonts/truetype/noto/NotoColorEmoji.ttf"

  Result: unable to read font
  /tmp/magick-8NkJdrn3QxnVQQtkhvTzrKd9bDXlxihn' @
  error/annotate.c/RenderFreetype/1481. non-conforming drawing primitive
  definition text' @ error/draw.c/RenderMVGContent/4404.

  Opens a blank page without any content.
  This affects GUI developed in QT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1974179/+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 1886653] Re: cups-pki-expired

[Aaron]

Same error; same printer; same issue as Thomas above.

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

Title:
  cups-pki-expired

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The printer always goes to stopped state in Ubuntu 20.04. Print
  properties window has status message saying: "cups-pki-expired". I
  have HP color laserjet m552, which Ubuntu discovers directly from the
  local network and configures automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 14:40:00 2020
  InstallationDate: Installed on 2019-11-03 (247 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: 
implicitclass://HP_Color_LaserJet_M552_5F80BF_/
  MachineType: LENOVO 81H1
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago)
  dmi.bios.date: 08/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8PCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 530S-14ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
  dmi.product.family: ideapad 530S-14ARR
  dmi.product.name: 81H1
  dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
  dmi.product.version: Lenovo ideapad 530S-14ARR
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1886653/+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 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools

[Aaron Renny Varghese]

I agree with Jeremy Bicha here. Canonical needs to make money and those
ads aren't spammy at all. However I do want to see an option to turn
Ubuntu Advantage/Pro and promotional content off, for those who don't
want it.

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

Title:
  ubuntu-minimal depends on ubuntu-advantage-tools

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  This is counter to #1566183 There is no reason to enforce desktop
  users who manage machine on their own to install ubuntu-advantage-
  tools, especially when this is 'minimal' version.  This should include
  only essential packages to make the OS functional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+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 1993370] [NEW] Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic

[Aaron Rainbolt]

Public bug reported:

Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel Core
i5, UEFI, no secure boot, Broadcom WiFi.

OS: Ubuntu Studio Kinetic, Final ISO

Steps to reproduce:

1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the 
system normally. (No encryption, allow Internet access during installation 
using some method of connectivity other than WiFi.)
2. Reboot and log into the newly installed system.
3. Open a terminal and run "sudo software-properties-kde".
4. Click "Additional Drivers" in the window that pops up.
5. Click "Using Broadcom 802.11 Linux STA wireless driver source from 
bcmwl-kernel-source (proprietary)".

Expected result: The Apply Changes button should become clickable,
allowing the user to install the driver.

Actual result: The button remains grayed out, and the following error
message is printed in the terminal:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1063, in on_driver_selection_changed
modules_package_obj = self.apt_cache[modules_package]
TypeError: Expected a string or a pair of strings

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: software-properties-qt 0.99.27
ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
Uname: Linux 5.19.0-1007-lowlatency x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Oct 18 21:33:51 2022
InstallationDate: Installed on 2022-10-19 (0 days ago)
InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 
(20221017.1)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kinetic

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

Title:
  Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio
  Kinetic

Status in software-properties package in Ubuntu:
  New

Bug description:
  Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel
  Core i5, UEFI, no secure boot, Broadcom WiFi.

  OS: Ubuntu Studio Kinetic, Final ISO

  Steps to reproduce:

  1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the 
system normally. (No encryption, allow Internet access during installation 
using some method of connectivity other than WiFi.)
  2. Reboot and log into the newly installed system.
  3. Open a terminal and run "sudo software-properties-kde".
  4. Click "Additional Drivers" in the window that pops up.
  5. Click "Using Broadcom 802.11 Linux STA wireless driver source from 
bcmwl-kernel-source (proprietary)".

  Expected result: The Apply Changes button should become clickable,
  allowing the user to install the driver.

  Actual result: The button remains grayed out, and the following error
  message is printed in the terminal:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1063, in on_driver_selection_changed
  modules_package_obj = self.apt_cache[modules_package]
  TypeError: Expected a string or a pair of strings

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: software-properties-qt 0.99.27
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
  Uname: Linux 5.19.0-1007-lowlatency x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Oct 18 21:33:51 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 
(20221017.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1993370/+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 1993359] Re: profile snap-update-ns.firefox is denied

[Aaron Rainbolt]

Also affects normal installations (ext4, no encryption). Installed,
rebooted, logged in, searched logs and found messages.

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

Title:
  profile snap-update-ns.firefox is denied

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  profile snap-update-ns.firefox is denied

  on fresh kinetic boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1993359/+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 1993318] [NEW] ZFS + Encryption installations of Ubuntu Desktop suffer various severe problems related to the package manager

[Aaron Rainbolt]

Public bug reported:

This is *probably* the wrong package, but it's the best I can figure for
this, so here goes.

Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5,
UEFI, no secure boot. Testing done in VirtualBox, BIOS, 4 GB RAM, 50 GB
SSD. OS is Ubuntu Desktop, Kinetic Final ISO.

Steps to reproduce:

1. Boot the Ubuntu desktop ISO.
2. Select "Try Ubuntu" (don't select "Install Ubuntu" if you're in VirtualBox 
or you won't be able to see important buttons).
3. Click the application menu, search for "Display", and change the screen 
resolution to something bigger than 800x600 (I use 1360x768).
4. Start the installer and proceed with the installation process.
5. When you get to the "Installation type" screen, select "Advanced Options", 
and enable ZFS + Encryption.
6. Proceed with the rest of the installation as normal.
7. Reboot into the newly installed system.
8. Attempt to log in.

Expected result: You should be logged in and arrive at a GNOME desktop.

Actual result: You are immediately dropped back to the login screen/

Notes: The fall back to the login screen will occur whether you use
Wayland or Xorg. If you switch to a TTY and log in, you will see an
error related to a missing file, /var/lib/dpkg/status. "sudo apt update"
will error out as a result of this missing file. Running "sudo touch
/var/lib/dpkg/status" will allow "sudo apt update" to function, and you
will then be able to log into the GNOME desktop.

Once you log in, you'll notice that Firefox is missing (bug #1993279),
and you will likely be presented with a ton of error messages and other
scary junk. At least one of those error messages will be related to
update-manager.

Once you get past that whole mess, the system seems to work OK (I'm
typing on the VM that I produced this mess on). I still notice a "System
program problem detected" window pop up at least once after booting the
VM, but it otherwise functions normally so far.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: zsys (not installed)
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 18 09:55:27 2022
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: zsys
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kinetic

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

Title:
  ZFS + Encryption installations of Ubuntu Desktop suffer various severe
  problems related to the package manager

Status in zsys package in Ubuntu:
  New

Bug description:
  This is *probably* the wrong package, but it's the best I can figure
  for this, so here goes.

  Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core
  i5, UEFI, no secure boot. Testing done in VirtualBox, BIOS, 4 GB RAM,
  50 GB SSD. OS is Ubuntu Desktop, Kinetic Final ISO.

  Steps to reproduce:

  1. Boot the Ubuntu desktop ISO.
  2. Select "Try Ubuntu" (don't select "Install Ubuntu" if you're in VirtualBox 
or you won't be able to see important buttons).
  3. Click the application menu, search for "Display", and change the screen 
resolution to something bigger than 800x600 (I use 1360x768).
  4. Start the installer and proceed with the installation process.
  5. When you get to the "Installation type" screen, select "Advanced Options", 
and enable ZFS + Encryption.
  6. Proceed with the rest of the installation as normal.
  7. Reboot into the newly installed system.
  8. Attempt to log in.

  Expected result: You should be logged in and arrive at a GNOME
  desktop.

  Actual result: You are immediately dropped back to the login screen/

  Notes: The fall back to the login screen will occur whether you use
  Wayland or Xorg. If you switch to a TTY and log in, you will see an
  error related to a missing file, /var/lib/dpkg/status. "sudo apt
  update" will error out as a result of this missing file. Running "sudo
  touch /var/lib/dpkg/status" will allow "sudo apt update" to function,
  and you will then be able to log into the GNOME desktop.

  Once you log in, you'll notice that Firefox is missing (bug #1993279),
  and you will likely be presented with a ton of error messages and
  other scary junk. At least one of those error messages will be related
  to update-manager.

  Once you get past that whole mess, the system seems to work OK (I'm
  typing on the VM that I produced this mess on). I still notice a
  "System program problem det

[Desktop-packages] [Bug 1991936] Re: No AAC codec for Pipewire on Ubuntu Kinetic

[Aaron Rainbolt]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1991936

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Package changed: linux (Ubuntu) => pipewire (Ubuntu)

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

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

Title:
  No AAC codec for Pipewire on Ubuntu Kinetic

Status in pipewire package in Ubuntu:
  Confirmed

Bug description:
  The AAC codec is not showing up in the sound settings when a device
  that is capable of that codec is connected, but other supported codecs
  do work.Tested using the Sony WH1000XM4 and other bluetooth devices
  that support the codec.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1991936/+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 1991530] Re: After upgrading to Ubuntu 22.10-beta I lost the sound.

[Aaron Rainbolt]

Can you try running "sudo apt install firmware-sof-signed" and see if
that resolves the problem?

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

Title:
  After upgrading to Ubuntu 22.10-beta I lost the sound.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  In the list of devices for testing sound I get only "Dummy Output".
  With 22.04 everything was ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 14:27:59 2022
  InstallationDate: Installed on 2019-07-01 (1190 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0YET50W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NB002BPG
  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.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590:
  dmi.product.family: ThinkPad E590
  dmi.product.name: 20NB002BPG
  dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590
  dmi.product.version: ThinkPad E590
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1991530/+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 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )

[Aaron Rainbolt]

I'm not sure if this problem is happening on Linux Mint 21 or Ubuntu
22.04.1. While Linux Mint is based on Ubuntu, it is not the same as
Ubuntu, and may have behaviors (and bugs!) that differ from Ubuntu's.
Could you clarify which Linux distro you're experiencing this problem
on?

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

Title:
  Cannot move file to trash, do you want to delete immediately?" on EXT4
  partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on
  ubuntu 20.04 )

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain the message in title.

  how can i use trash again please ?

  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1

  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0

  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0

  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0

  LABEL=WD8PRO2   /Vidéos/WD8PRO2
  ext4defaults 0   0

  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0

  trash is working for filesysteme mounted on /media/WD8PRO1 but not in
  FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS
  .

  Exactly same file systeme mounted on same directory , with same trash
  directory is working fine on ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+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 1988703] [NEW] Ubuntu logo is not shown in the bottom in GDM

[Aaron Renny Varghese]

Public bug reported:

On Ubuntu 22.10 daily builds, the Ubuntu logo in the bottom is not
present. I first found it in a VM and then booted up a live USB and got
the same result.

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


** Tags: gdm logo ubuntu

** Attachment added: "ubuntu logo not present here, couldn't screenshot"
   
https://bugs.launchpad.net/bugs/1988703/+attachment/5613674/+files/IMG_20220904_223656.jpg

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

Title:
  Ubuntu logo is not shown in the bottom in GDM

Status in gdm3 package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 daily builds, the Ubuntu logo in the bottom is not
  present. I first found it in a VM and then booted up a live USB and
  got the same result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1988703/+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 1988100] Re: Video thumbnails fail to generate

[Aaron]

If I run it as root it runs for a few seconds and responds "Killed"

But; something suspicious is happening because I just went to check the
exact output and I got this:

$ sudo totem-video-thumbnailer -v sample.mp4 sample.png
TotemVideoThumbnailer-Message: 17:38:03.906: Initialised libraries, about to 
create video widget
TotemVideoThumbnailer-Message: 17:38:03.908: setting URI 
file:///home/aaron/tmp/sample.mp4
TotemVideoThumbnailer-Message: 17:38:03.908: Video widget created
TotemVideoThumbnailer-Message: 17:38:03.908: About to open video file
OpenBLAS blas_thread_init: pthread_create failed for thread 7 of 16: Resource 
temporarily unavailable
OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max

So I am a liar now. But this works:

$ sudo totem-video-thumbnailer -vl sample.mp4 sample.png
TotemVideoThumbnailer-Message: 17:40:03.840: Initialised libraries, about to 
create video widget
TotemVideoThumbnailer-Message: 17:40:03.842: setting URI 
file:///home/aaron/tmp/sample.mp4
TotemVideoThumbnailer-Message: 17:40:03.842: Video widget created
TotemVideoThumbnailer-Message: 17:40:03.842: About to open video file
TotemVideoThumbnailer-Message: 17:40:03.948: Checking whether file has cover
TotemVideoThumbnailer-Message: 17:40:03.949: Opened video file: 'sample.mp4'
TotemVideoThumbnailer-Message: 17:40:03.949: About to seek to 0.33
TotemVideoThumbnailer-Message: 17:40:03.978: About to get frame for iter 0
TotemVideoThumbnailer-Message: 17:40:03.985: Frame for iter 0 is interesting
TotemVideoThumbnailer-Message: 17:40:03.988: Saving captured screenshot to 
sample.png

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

Title:
  Video thumbnails fail to generate

Status in totem package in Ubuntu:
  New

Bug description:
  totem-video-thumbnailer appears to be crashing and so no video
  thumbnails are generated. This is what happens when I run it manually:

  $ totem-video-thumbnailer -v sample.mp4 sample.png
  TotemVideoThumbnailer-Message: 11:08:44.734: Initialised libraries, about to 
create video widget
  TotemVideoThumbnailer-Message: 11:08:44.739: setting URI 
file:///home/aaron/tmp/sample.mp4
  TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
  TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.806:
  failed to create thread: Error creating thread: Resource temporarily
  unavailable

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.808: failed 
to create thread: Error creating thread: Resource temporarily unavailable
  terminate called after throwing an instance of 'std::bad_alloc'
    what():  std::bad_alloc
  Aborted

  Passing the -l flag causes it to work fine.

  Also, in other tests, which I fail to replicate now, I saw this error:
  OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max

  As a workaround I have installed ffmpegthumbnailer and $ln -s
  /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer
  ~/.local/share/thumbnailers/ffmpegthumbnailer.thumbnailer

  This has things working for me, but does not really address the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 10:53:06 2022
  InstallationDate: Installed on 2021-09-24 (339 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: totem
  UpgradeStatus: Upgraded to jammy on 2022-07-19 (41 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-09-27T12:02:48.414586

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1988100/+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 1988100] Re: Video thumbnails fail to generate

[Aaron]

** Summary changed:

- Video thumbnails fail to genetate
+ Video thumbnails fail to generate

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

Title:
  Video thumbnails fail to generate

Status in totem package in Ubuntu:
  New

Bug description:
  totem-video-thumbnailer appears to be crashing and so no video
  thumbnails are generated. This is what happens when I run it manually:

  $ totem-video-thumbnailer -v sample.mp4 sample.png
  TotemVideoThumbnailer-Message: 11:08:44.734: Initialised libraries, about to 
create video widget
  TotemVideoThumbnailer-Message: 11:08:44.739: setting URI 
file:///home/aaron/tmp/sample.mp4
  TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
  TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.806:
  failed to create thread: Error creating thread: Resource temporarily
  unavailable

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.808: failed 
to create thread: Error creating thread: Resource temporarily unavailable
  terminate called after throwing an instance of 'std::bad_alloc'
    what():  std::bad_alloc
  Aborted

  Passing the -l flag causes it to work fine.

  Also, in other tests, which I fail to replicate now, I saw this error:
  OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max

  As a workaround I have installed ffmpegthumbnailer and $ln -s
  /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer
  ~/.local/share/thumbnailers/ffmpegthumbnailer.thumbnailer

  This has things working for me, but does not really address the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 10:53:06 2022
  InstallationDate: Installed on 2021-09-24 (339 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: totem
  UpgradeStatus: Upgraded to jammy on 2022-07-19 (41 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-09-27T12:02:48.414586

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1988100/+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 1988100] Re: Video thumbnails fail to genetate

[Aaron]

> Don't be alarmed by that. Those two limits are correct and normal

Fair enough. I only mentioned it because I noted that the -l flag
allowed the process to complete.

Sadly I have nothing in /var/crash. I see a couple of gnome-shell
reports on errors.ubuntu.com but they are from back in March this year.

To be honest, I'm not sure how long this has been going on for. It could
have been years. I just happened to notice and be in the mood to do
something about it today.

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

Title:
  Video thumbnails fail to genetate

Status in totem package in Ubuntu:
  New

Bug description:
  totem-video-thumbnailer appears to be crashing and so no video
  thumbnails are generated. This is what happens when I run it manually:

  $ totem-video-thumbnailer -v sample.mp4 sample.png
  TotemVideoThumbnailer-Message: 11:08:44.734: Initialised libraries, about to 
create video widget
  TotemVideoThumbnailer-Message: 11:08:44.739: setting URI 
file:///home/aaron/tmp/sample.mp4
  TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
  TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.806:
  failed to create thread: Error creating thread: Resource temporarily
  unavailable

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.808: failed 
to create thread: Error creating thread: Resource temporarily unavailable
  terminate called after throwing an instance of 'std::bad_alloc'
    what():  std::bad_alloc
  Aborted

  Passing the -l flag causes it to work fine.

  Also, in other tests, which I fail to replicate now, I saw this error:
  OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max

  As a workaround I have installed ffmpegthumbnailer and $ln -s
  /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer
  ~/.local/share/thumbnailers/ffmpegthumbnailer.thumbnailer

  This has things working for me, but does not really address the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 10:53:06 2022
  InstallationDate: Installed on 2021-09-24 (339 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: totem
  UpgradeStatus: Upgraded to jammy on 2022-07-19 (41 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-09-27T12:02:48.414586

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1988100/+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 1988100] Re: Video thumbnails fail to genetate

[Aaron]

** Description changed:

  totem-video-thumbnailer appears to be crashing and so no video
  thumbnails are generated. This is what happens when I run it manually:
  
  $ totem-video-thumbnailer -v sample.mp4 sample.png
  TotemVideoThumbnailer-Message: 11:08:44.734: Initialised libraries, about to 
create video widget
  TotemVideoThumbnailer-Message: 11:08:44.739: setting URI 
file:///home/aaron/tmp/sample.mp4
  TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
  TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file
  
  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.806:
  failed to create thread: Error creating thread: Resource temporarily
  unavailable
  
  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.808: failed 
to create thread: Error creating thread: Resource temporarily unavailable
  terminate called after throwing an instance of 'std::bad_alloc'
-   what():  std::bad_alloc
+   what():  std::bad_alloc
  Aborted
  
  Passing the -l flag causes it to work fine.
  
  Also, in other tests, which I fail to replicate now, I saw this error:
  OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max
  
  As a workaround I have installed ffmpegthumbnailer and $ln -s
  /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer
- ffmpegthumbnailer.thumbnailer
+ ~/.local/share/thumbnailers/ffmpegthumbnailer.thumbnailer
  
  This has things working for me, but does not really address the problem.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 10:53:06 2022
  InstallationDate: Installed on 2021-09-24 (339 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: totem
  UpgradeStatus: Upgraded to jammy on 2022-07-19 (41 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-09-27T12:02:48.414586

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

Title:
  Video thumbnails fail to genetate

Status in totem package in Ubuntu:
  New

Bug description:
  totem-video-thumbnailer appears to be crashing and so no video
  thumbnails are generated. This is what happens when I run it manually:

  $ totem-video-thumbnailer -v sample.mp4 sample.png
  TotemVideoThumbnailer-Message: 11:08:44.734: Initialised libraries, about to 
create video widget
  TotemVideoThumbnailer-Message: 11:08:44.739: setting URI 
file:///home/aaron/tmp/sample.mp4
  TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
  TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.806:
  failed to create thread: Error creating thread: Resource temporarily
  unavailable

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.808: failed 
to create thread: Error creating thread: Resource temporarily unavailable
  terminate called after throwing an instance of 'std::bad_alloc'
    what():  std::bad_alloc
  Aborted

  Passing the -l flag causes it to work fine.

  Also, in other tests, which I fail to replicate now, I saw this error:
  OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max

  As a workaround I have installed ffmpegthumbnailer and $ln -s
  /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer
  ~/.local/share/thumbnailers/ffmpegthumbnailer.thumbnailer

  This has things working for me, but does not really address the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 10:53:06 2022
  InstallationDate: Installed on 2021-09-24 (339 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: totem
  UpgradeStatus: Upgraded to jammy on 2022-07-19 (41 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-09-27T12:02:48.414586

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1988100/+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 1988100] [NEW] Video thumbnails fail to genetate

[Aaron]

Public bug reported:

totem-video-thumbnailer appears to be crashing and so no video
thumbnails are generated. This is what happens when I run it manually:

$ totem-video-thumbnailer -v sample.mp4 sample.png
TotemVideoThumbnailer-Message: 11:08:44.734: Initialised libraries, about to 
create video widget
TotemVideoThumbnailer-Message: 11:08:44.739: setting URI 
file:///home/aaron/tmp/sample.mp4
TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file

(totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.806:
failed to create thread: Error creating thread: Resource temporarily
unavailable

(totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.808: failed to 
create thread: Error creating thread: Resource temporarily unavailable
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted

Passing the -l flag causes it to work fine.

Also, in other tests, which I fail to replicate now, I saw this error:
OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max

As a workaround I have installed ffmpegthumbnailer and $ln -s
/usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer
ffmpegthumbnailer.thumbnailer

This has things working for me, but does not really address the problem.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 30 10:53:06 2022
InstallationDate: Installed on 2021-09-24 (339 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-07-19 (41 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2021-09-27T12:02:48.414586

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


** Tags: amd64 apport-bug jammy

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

Title:
  Video thumbnails fail to genetate

Status in totem package in Ubuntu:
  New

Bug description:
  totem-video-thumbnailer appears to be crashing and so no video
  thumbnails are generated. This is what happens when I run it manually:

  $ totem-video-thumbnailer -v sample.mp4 sample.png
  TotemVideoThumbnailer-Message: 11:08:44.734: Initialised libraries, about to 
create video widget
  TotemVideoThumbnailer-Message: 11:08:44.739: setting URI 
file:///home/aaron/tmp/sample.mp4
  TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
  TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.806:
  failed to create thread: Error creating thread: Resource temporarily
  unavailable

  (totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08:44.808: failed 
to create thread: Error creating thread: Resource temporarily unavailable
  terminate called after throwing an instance of 'std::bad_alloc'
what():  std::bad_alloc
  Aborted

  Passing the -l flag causes it to work fine.

  Also, in other tests, which I fail to replicate now, I saw this error:
  OpenBLAS blas_thread_init: RLIMIT_NPROC 125184 current, 125184 max

  As a workaround I have installed ffmpegthumbnailer and $ln -s
  /usr/share/thumbnailers/ffmpegthumbnailer.thumbnailer
  ffmpegthumbnailer.thumbnailer

  This has things working for me, but does not really address the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 10:53:06 2022
  InstallationDate: Installed on 2021-09-24 (339 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: totem
  UpgradeStatus: Upgraded to jammy on 2022-07-19 (41 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-09-27T12:02:48.414586

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1988100/+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 1987579] [NEW] "Remove Hyperlink" feature causes text duplication and corruption when removing email hyperlinks inside angle brackets

[Aaron Rainbolt]

Public bug reported:

This may be the single weirdest bug report I've ever made.

Steps to Reproduce:
1: Open LibreOffice Calc.
2: In any cell of the spreadsheet, type:

   

   The email address placed inside the angle brackets can be whatever you want, 
but the angle brackets are necessary for the bug to surface (at least usually).
3: Press Enter. The email address will automatically be turned into a hyperlink.
4: Right-click the automatically created hyperlink, and click "Remove 
Hyperlink".

Expected result:
The actual text of the cell should remain unchanged, but the hyperlink itself 
should be removed.

Actual result:
The text within the cell morphs into the following:


 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  "Remove Hyperlink" feature causes text duplication and corruption when
  removing email hyperlinks inside angle brackets

Status in libreoffice package in Ubuntu:
  New

Bug description:
  This may be the single weirdest bug report I've ever made.

  Steps to Reproduce:
  1: Open LibreOffice Calc.
  2: In any cell of the spreadsheet, type:

 

 The email address placed inside the angle brackets can be whatever you 
want, but the angle brackets are necessary for the bug to surface (at least 
usually).
  3: Press Enter. The email address will automatically be turned into a 
hyperlink.
  4: Right-click the automatically created hyperlink, and click "Remove 
Hyperlink".

  Expected result:
  The actual text of the cell should remain unchanged, but the hyperlink itself 
should be removed.

  Actual result:
  The text within the cell morphs into the following:

  
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987579/+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 1987229] Re: 22.04 Cannot Restore Files from Backup

[Aaron Rainbolt]

Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but it is better to raise problems you are having in the
support tracker at https://answers.launchpad.net/ubuntu if you are
uncertain if they are bugs. If you would prefer live chat support, you
can find an IRC support channel for your flavor of Ubuntu here:
https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with
your problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org. For help on reporting bugs, see
https://help.ubuntu.com/community/ReportingBugs.

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/duplicity/+question/702866

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

Title:
  22.04 Cannot Restore Files from Backup

Status in duplicity package in Ubuntu:
  Invalid

Bug description:
  My system upgraded to 22.04.  I was having issues unable to boot.
  I created a backup of all my files in the Recovery Mode.  Onto an external 
500 GB Hard drive.
  I reformatted the hard drive and re-installed 22.04.
  Now going to Applications > Utilities > Backup.
  I select to Restore from a backup.
  And I receive this error:  Failed to read duplicity-full-signatures. 
20220818T155126Z.sigtar.gz: CRC check failed 0xc5eba518!=0xae357fd0

  When I click Retry I get the same error.

  I searched for another backup restore application and found what looks like 
the same version of Backups used to create the back ups.
  When I click Restore From a Previous Backup.
  I select the 500 GB hard drive and type the Folder name containing the 
backups.
  I get the same error.

  I have searched community but only find things from version 17 or
  earlier.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1987229/+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 1983000] Re: IDK

[Aaron Rainbolt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

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

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

Title:
  IDK

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  IDK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Thu Jul 28 00:08:14 2022
  DistUpgraded: 2022-06-04 14:01:52,153 DEBUG /openCache(), new cache size 77115
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2021-04-26 (457 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP EliteBook 850 G1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic 
root=UUID=92e691d6-a214-4b1a-9cf6-48a28f570055 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2022-06-04 (53 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.release: 1.40
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.40
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 21.89
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.40:bd07/13/2017:br1.40:efr21.89:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:skuG4M89US#ABA:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G1
  dmi.product.sku: G4M89US#ABA
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[Aaron Rainbolt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

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

** This bug has been marked a duplicate of bug 1983000
   IDK

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

Title:
  IDK

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  IDK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Thu Jul 28 00:08:14 2022
  DistUpgraded: 2022-06-04 14:01:52,153 DEBUG /openCache(), new cache size 77115
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2021-04-26 (457 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP EliteBook 850 G1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic 
root=UUID=92e691d6-a214-4b1a-9cf6-48a28f570055 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2022-06-04 (53 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.release: 1.40
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.40
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 21.89
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.40:bd07/13/2017:br1.40:efr21.89:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:skuG4M89US#ABA:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G1
  dmi.product.sku: G4M89US#ABA
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[Aaron Rainbolt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

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

** This bug has been marked a duplicate of bug 1983000
   IDK

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

Title:
  IDK

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  IDK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Thu Jul 28 00:08:14 2022
  DistUpgraded: 2022-06-04 14:01:52,153 DEBUG /openCache(), new cache size 77115
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2021-04-26 (457 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP EliteBook 850 G1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic 
root=UUID=92e691d6-a214-4b1a-9cf6-48a28f570055 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2022-06-04 (53 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.release: 1.40
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.40
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 21.89
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.40:bd07/13/2017:br1.40:efr21.89:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:skuG4M89US#ABA:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G1
  dmi.product.sku: G4M89US#ABA
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1983002/+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 1982959] Re: When I send an email in Thunderbird in the Ubuntu 22.04 Daily Build from 07/27/2022 08:35 , the desktop environment crashes.

[Aaron Rainbolt]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please boot the same daily ISO that produced this problem, and execute 
the following command only once, as it will automatically gather debugging 
information, in a terminal:
apport-collect 1982959

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Package changed: ubuntu => thunderbird (Ubuntu)

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

Title:
  When I send an email in Thunderbird in the Ubuntu 22.04 Daily Build
  from  07/27/2022 08:35  , the desktop environment crashes.

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Whenever I send an email in Thunderbird in Ubuntu 22.04 Daily Build
  from  07/27/2022 08:35, the desktop environment crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1982959/+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 1982879] Re: Multiple problems when using screenshot

[Aaron Rainbolt]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1982879

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Multiple problems when using screenshot

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Sometimes the preinstalled applications for screenshots causing panic in X11. 
alt+tab gets disabled.
  when using interactive window of browser and selecting clip it captures full 
screen even though I select shift+prnt or it picks a random square.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1982879/+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 1982885] Re: Firefox does not scroll with touch input

[Aaron Rainbolt]

Thank you for taking the time to report this bug and help make Ubuntu
better. Firefox is provided by a snap published by Mozilla, and they may
not be aware of this issue. Please contact them via
https://support.mozilla.org/kb/file-bug-report-or-feature-request-
mozilla and link the bug report here so it can be further tracked. Thank
you!

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

Title:
  Firefox does not scroll with touch input

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox does not scroll with the usual touch gesture of swiping up or
  down on the screen. This action just selects text on the page as
  though the left mouse button was depressed and the cursor moved across
  the page.

  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  Snapstore version 103.0-1 latest stable

  Possibly related to being packaged as a snap (have noticed this
  behaviour on Fedora using the firefox snap).

  It's still possible to scroll by dragging the scrollbar but this
  essentially breaks firefox on touch systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1982885/+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 1982889] Re: Display-Wayland. Cannot map USB touch input to video output

[Aaron Rainbolt]

Changing the package this bug affects to gdm3 as I believe that is the
package that includes the Wayland implementation in Ubuntu.

** Package changed: ubuntu => gdm3 (Ubuntu)

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

Title:
  Display-Wayland. Cannot map USB touch input to video output

Status in mutter package in Ubuntu:
  New

Bug description:
  Ubuntu Display-Wayland, Two USB touch inputs are mapping to one
  display monitor. I can not do map USB touch input to video output.

  On Display-X11, I can do "xinput map-to-output {device_id}
  {display_name}" to map touchscreen USB input to video output.

  Please help, tell me what to do.
  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1982889/+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 1982551] Re: Print is failed via USB

[Aaron Rainbolt]

I added back the "Our analysis" section from the old bug report since it
has a wealth of useful debugging data. Thank you for going to so much
trouble to make this report, all that debugging you did may prove
extremely useful.

** Description changed:

  Phenomenon:
  After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it 
can be printed at the first time, but after the second or multiple times, the 
job will be canceled.
  
  Comment:
  1.Wait a few minutes and the job still won't be printed.
  2.After unplugging in and plugging in the USB cable, the job can be printed
  3.The problem does not occur via network printing.
  4.Other systems (such as Windows, Mac OS) do not have this problem.
+ 
+ Our analysis:
+ 1.We think that part of the data was lost via USB transmission
+ 
+ 2.In CUPS ErrorLog, the job has been delivered completely.
+ (refer to error_log->[Job 313])
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting renderer with command: 
\"printf \"%%!PS-Adobe-3.0
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] Title: 
(/home/rits/文档/17540黑白-2017.doc)
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] %%
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] 
%%\\n/lppswd()def\\n/usrcode()def\\n/sppswd()def\\nmark\\n/usrcode 
where{pop}{/usrcode()def}ifelse\\n(rits) usrcode (20`date +%y%m%d%R | sed 
\'s/://\'`) {setuserinfo} stopped\\ncleartomark\\nmark {\\n<<\\n /JobType 0\\n 
/JobInfo <<\\n /UserID (rits)\\n /Time (20`date +%y%m%d%R | sed \'s/://\'`)\\n 
/HostLoginName (rits)\\n /HostName (rits-OptiPlex-3010)\\n >>\\n>> 
/RDeviceProcSet /ProcSet findresource /SetJobType get exec\\n}stopped 
cleartomark\\nmark{\\nuserdict /RPS_BPdict 2 dict put\\nuserdict /RPS_BPdict 
get begin /RPS_BP_MEDIAPOSITION null def end\\n} stopped 
cleartomark\\nmark{\\nuserdict /RPS_BPdict get begin\\n/RPS_BP_MEDIATYPE (Auto) 
def end\\n} stopped cleartomark\\nmark{\\n<<\\n/BannerPageMode 
false\\n/MediaPosition null\\n/MediaType null\\n>>\\n/RDeviceProcSet\\n/ProcSet 
findresource\\n/SetBannerPage get exec\\n} stopped cleartomark\\n\"; cat;\"
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid3\" 
(generation 1)
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid4\" 
(generation 2)
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"renderer\" 
(generation 2)
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] JCL: \033%-12345X@PJL
+ D [21/Jul/2022:15:21:17 +0800] [Job 313] 
+ 
+ I [21/Jul/2022:15:21:25 +0800] [Job 313] Job completed.
+ 
+ 3.However, I found an error on USB Request Block (URB) with Wireshark on 
Ubuntu 18.04
+ [Error: undefined; Off fendingCommand: BPdict Flushing: rest of job (to end 
of file) will be ignored] appeared at [URB BULK IN]
+ (refer to usb2.pcapng, snapshot.pn)
+ 
+ 4.We extracted the accepted data on the printer side, the data is really lost.
+ (refer to prt00016.prn,
+ prt00013.prn is the data of normal print)
  
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  CUPS 2.2.7
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.9
  ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
  Uname: Linux 5.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 22 15:43:30 2022
  InstallationDate: Installed on 2022-07-05 (16 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Dell Inc. OptiPlex 3010
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic 
root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 042P49
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 3010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

Title:
  Print is failed via USB

Status in cups package in Ubuntu:
  New

Bug description:
  Phenomenon:
  After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it 
can be printed at the first time, but after the second or multiple times, the 
job will be canceled.

  Comment:
  1.Wait a few minutes and the job still won't be printed.
  2.After unplugging in and plugging in the USB cable, the job can be printed
  3.The problem does not occur via network printing.
  4.Other systems (such as Windows, Mac OS) do not have this problem.

  Our analysis:
  1.We think that part of the data was lost via USB transmission

  2.In CUPS ErrorLog

[Desktop-packages] [Bug 1982551] Re: Print is failed via USB

[Aaron Rainbolt]

And it's happening with multiple printers as well? (Asking to narrow
down where the problem might be)

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

Title:
  Print is failed via USB

Status in cups package in Ubuntu:
  New

Bug description:
  Phenomenon:
  After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it 
can be printed at the first time, but after the second or multiple times, the 
job will be canceled.

  Comment:
  1.Wait a few minutes and the job still won't be printed.
  2.After unplugging in and plugging in the USB cable, the job can be printed
  3.The problem does not occur via network printing.
  4.Other systems (such as Windows, Mac OS) do not have this problem.

  Our analysis:
  1.We think that part of the data was lost via USB transmission

  2.In CUPS ErrorLog, the job has been delivered completely.
  (refer to error_log->[Job 313])
  D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting renderer with command: 
\"printf \"%%!PS-Adobe-3.0
  D [21/Jul/2022:15:21:17 +0800] [Job 313] Title: 
(/home/rits/文档/17540黑白-2017.doc)
  D [21/Jul/2022:15:21:17 +0800] [Job 313] %%
  D [21/Jul/2022:15:21:17 +0800] [Job 313] 
%%\\n/lppswd()def\\n/usrcode()def\\n/sppswd()def\\nmark\\n/usrcode 
where{pop}{/usrcode()def}ifelse\\n(rits) usrcode (20`date +%y%m%d%R | sed 
\'s/://\'`) {setuserinfo} stopped\\ncleartomark\\nmark {\\n<<\\n /JobType 0\\n 
/JobInfo <<\\n /UserID (rits)\\n /Time (20`date +%y%m%d%R | sed \'s/://\'`)\\n 
/HostLoginName (rits)\\n /HostName (rits-OptiPlex-3010)\\n >>\\n>> 
/RDeviceProcSet /ProcSet findresource /SetJobType get exec\\n}stopped 
cleartomark\\nmark{\\nuserdict /RPS_BPdict 2 dict put\\nuserdict /RPS_BPdict 
get begin /RPS_BP_MEDIAPOSITION null def end\\n} stopped 
cleartomark\\nmark{\\nuserdict /RPS_BPdict get begin\\n/RPS_BP_MEDIATYPE (Auto) 
def end\\n} stopped cleartomark\\nmark{\\n<<\\n/BannerPageMode 
false\\n/MediaPosition null\\n/MediaType null\\n>>\\n/RDeviceProcSet\\n/ProcSet 
findresource\\n/SetBannerPage get exec\\n} stopped cleartomark\\n\"; cat;\"
  D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid3\" 
(generation 1)
  D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"kid4\" 
(generation 2)
  D [21/Jul/2022:15:21:17 +0800] [Job 313] Starting process \"renderer\" 
(generation 2)
  D [21/Jul/2022:15:21:17 +0800] [Job 313] JCL: \033%-12345X@PJL
  D [21/Jul/2022:15:21:17 +0800] [Job 313] 
  
  I [21/Jul/2022:15:21:25 +0800] [Job 313] Job completed.

  3.However, I found an error on USB Request Block (URB) with Wireshark on 
Ubuntu 18.04
  [Error: undefined; Off fendingCommand: BPdict Flushing: rest of job (to end 
of file) will be ignored] appeared at [URB BULK IN]
  (refer to usb2.pcapng, snapshot.pn)

  4.We extracted the accepted data on the printer side, the data is really lost.
  (refer to prt00016.prn,
  prt00013.prn is the data of normal print)

  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  CUPS 2.2.7

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.9
  ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
  Uname: Linux 5.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 22 15:43:30 2022
  InstallationDate: Installed on 2022-07-05 (16 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Dell Inc. OptiPlex 3010
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic 
root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 042P49
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 3010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551/+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 1982551] Re: Print is failed via USB

[Aaron Rainbolt]

This may sound silly, but try a different USB cable between your printer
and the system. That will help rule out a USB cable problem. (Even
though Windows and macOS don't have this problem, there's still a chance
that the USB cable is at fault.)

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

Title:
  Print is failed via USB

Status in cups package in Ubuntu:
  New

Bug description:
  Phenomenon:
  After installing the driver (such as RICOH IM C6000 PS) via USB protocol, it 
can be printed at the first time, but after the second or multiple times, the 
job will be canceled.

  Comment:
  1.Wait a few minutes and the job still won't be printed.
  2.After unplugging in and plugging in the USB cable, the job can be printed
  3.The problem does not occur via network printing.
  4.Other systems (such as Windows, Mac OS) do not have this problem.

  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  CUPS 2.2.7

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.9
  ProcVersionSignature: Ubuntu 5.4.0-122.138~18.04.1-generic 5.4.192
  Uname: Linux 5.4.0-122-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 22 15:43:30 2022
  InstallationDate: Installed on 2022-07-05 (16 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Dell Inc. OptiPlex 3010
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-122-generic 
root=UUID=72470cc0-4db9-4b77-b9de-77d32b61feb5 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 042P49
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/16/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA02:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 3010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551/+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 1982001] Re: Snap-based Firefox spams apparmor messages in journal

[Aaron Rainbolt]

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

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

Title:
  Snap-based Firefox spams apparmor messages in journal

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  The current awfully-slow firefox package which is provided via snap
  has an excessive log spamming bug: On various system interactions (not
  only in the browser but for example by using the media-next button) a
  lot of apparmor notifications are triggered:

  Jul 18 16:32:05 UML033 kernel: audit: type=1400 audit(1658154725.146:718): 
apparmor="DENIED" operation="open" profile="snap.firefox.firefox" 
name="/home/[private]/.xsession-errors" pid=3300 comm="pool-firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  [REPEATS] 
  Jul 18 16:32:06 UML033 audit[3300]: AVC apparmor="DENIED" operation="open" 
profile="snap.firefox.firefox" name="/home/[private]/.xsession-errors" pid=3300 
comm="pool-firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  [REPEATS]

  This is particular annoying for all users who are actively using
  apparmor in combination with aa-notify: It floods the whole desktop.
  There is also no obvious way to access the apparmor configuration file
  of the snapped firefox. There are also other reports on the internet
  that the apparmor configuration in this version of firefox fails to
  provide the targeted security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1982001/+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 1981995] Re: incorrect system load format

[Aaron Rainbolt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thank you!

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Incomplete

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

Title:
  incorrect system load format

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  Welcome to Ubuntu 22.04 LTS (GNU/Linux 5.15.0-1014-azure x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

System information as of Mon Jul 18 13:43:37 UTC 2022

System load:  0.60205078125 Processes: 114
Usage of /:   4.0% of 61.84GB   Users logged in:   1
Memory usage: 64%   IPv4 address for eth0: 10.0.0.4
Swap usage:   0%

=> There is 1 zombie process.

  
  0 updates can be applied immediately.

  
  Last login: Mon Jul 18 13:43:12 2022 from *
  ubuntu@server1:~$ uptime
   13:43:41 up  1:36,  4 users,  load average: 0.63, 0.18, 0.07
  ubuntu@server1:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1981995/+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 1981996] Re: Remmina external tools not working

[Aaron Rainbolt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thank you!

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

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

Title:
  Remmina external tools not working

Status in remmina package in Ubuntu:
  Incomplete

Bug description:
  Remmina external tools is not work well.
  If i run Remmina on terminal i can see the output in the terminal, but when i 
run Remmina from the menu it does not open a windows like before.
  It worked well in Ubuntu 18.04.
  I have "terminator" installed and configured as "x-terminal-emulator".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: remmina-common 1.4.25+dfsg-1
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 18 10:51:24 2022
  InstallationDate: Installed on 2022-06-02 (45 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1981996/+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 1982001] Re: Snap-based Firefox spams apparmor messages in journal

[Aaron Rainbolt]

Thank you for taking the time to report this bug and help make Ubuntu
better. Firefox is provided by a snap published by Mozilla, and they may
not be aware of this issue. Please contact them via
https://support.mozilla.org/kb/file-bug-report-or-feature-request-
mozilla and link the bug report here so it can be further tracked. Thank
you!

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

Title:
  Snap-based Firefox spams apparmor messages in journal

Status in firefox package in Ubuntu:
  New

Bug description:
  The current awfully-slow firefox package which is provided via snap
  has an excessive log spamming bug: On various system interactions (not
  only in the browser but for example by using the media-next button) a
  lot of apparmor notifications are triggered:

  Jul 18 16:32:05 UML033 kernel: audit: type=1400 audit(1658154725.146:718): 
apparmor="DENIED" operation="open" profile="snap.firefox.firefox" 
name="/home/[private]/.xsession-errors" pid=3300 comm="pool-firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  [REPEATS] 
  Jul 18 16:32:06 UML033 audit[3300]: AVC apparmor="DENIED" operation="open" 
profile="snap.firefox.firefox" name="/home/[private]/.xsession-errors" pid=3300 
comm="pool-firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  [REPEATS]

  This is particular annoying for all users who are actively using
  apparmor in combination with aa-notify: It floods the whole desktop.
  There is also no obvious way to access the apparmor configuration file
  of the snapped firefox. There are also other reports on the internet
  that the apparmor configuration in this version of firefox fails to
  provide the targeted security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1982001/+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 1981839] Re: Unable to save a bookmark

[Aaron Rainbolt]

That's fine, it happens. Is it OK if I mark this as Invalid, or is the
problem still there?

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

Title:
  Unable to save a bookmark

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 22.10 I'm unable to save a bookmark. Same problem with 
  Firefox snap installed:  102.0.1-1   (1551) 
  firefox-trunk:   Installed: 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1
  both with X11 and Wayland session.
  After saving a bookmark the star on right of the bar becomes red, but 
bookmark does not appear in the bookmark list.

  corrado@corrado-n3-kk-0512:~$ inxi -Fxx
  System:
Host: corrado-n3-kk-0512 Kernel: 5.15.0-27-generic arch: x86_64 bits: 64
  compiler: gcc v: 11.2.0 Desktop: GNOME v: 42.2 tk: GTK v: 3.24.34
  wm: gnome-shell dm: GDM3 Distro: Ubuntu 22.10 (Kinetic Kudu)
  Machine:
Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: 
  UEFI: American Megatrends v: P1.10 date: 05/11/2017
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 800 min/max: 800/3900 cores: 1: 800 2: 800 3: 800
  4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen9.5 ports: active: HDMI-A-1 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0
  chip-ID: 8086:5912
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:4 chip-ID: 046d:0990
Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: 
fbdev,vesa
  gpu: i915 display-ID: 0
Monitor-1: HDMI-A-1 model: LG (GoldStar) FULL HD res: 1920x1080 dpi: 102
  diag: 551mm (21.7")
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.1.3
  direct render: Yes
  Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock
  driver: snd_hda_intel bus-ID: 1-7:4 v: kernel chip-ID: 046d:0990
  bus-ID: 00:1f.3 chip-ID: 8086:a170
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo
Sound Server-1: ALSA v: k5.15.0-27-generic running: yes
Sound Server-2: PulseAudio v: 16.1 running: no
Sound Server-3: PipeWire v: 0.3.53 running: yes
  Network:
Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel
  port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8
IF: enp0s31f6 state: down mac: 70:85:c2:44:7b:86
Device-2: Ralink RT2501/RT2573 Wireless Adapter type: USB driver: rt73usb
  bus-ID: 3-1.3.3:4 chip-ID: 148f:2573
IF: wlx000ee8f7f7e6 state: up mac: 00:0e:e8:f7:f7:e6
  Drives:
Local Storage: total: 2.05 TiB used: 34.8 GiB (1.7%)
ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB
  speed: 31.6 Gb/s lanes: 4 serial: 50026B72823D1475 temp: 29.9 C
ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB
  speed: 6.0 Gb/s serial: 21122DB99114
ID-3: /dev/sdb vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB
  speed: 6.0 Gb/s serial: 21122DA80425
ID-4: /dev/sdc vendor: Toshiba model: DT01ACA100 size: 931.51 GiB
  speed: 6.0 Gb/s serial: 37PYNGAFS
  Partition:
ID-1: / size: 39.08 GiB used: 34.79 GiB (89.0%) fs: ext4
  dev: /dev/nvme0n1p3
ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat
  dev: /dev/nvme0n1p1
  Swap:
ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
  dev: /dev/sda2
  Sensors:
System Temperatures: cpu: 29.0 C pch: 49.0 C mobo: 33.5 C
Fan Speeds (RPM): fan-1: 0 fan-2: 2389 fan-3: 0 fan-4: 2500 fan-5: 0
  fan-6: 0
Power: 12v: N/A 5v: N/A 3.3v: 3.41 vbat: 3.15
  Info:
Processes: 242 Uptime: 11h 5m Memory: 7.47 GiB used: 2.69 GiB (36.0%)
Init: systemd v: 251 target: graphical (5) default: graphical Compilers:
gcc: N/A Packages: 1901 apt: 1892 snap: 9 Shell: Bash v: 5.1.16
running-in: kgx inxi: 3.3.19
  corrado@corrado-n3-kk-0512:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: firefox-trunk 104.0~a1~hg20220712r623561-0ubuntu0.22.10.1~umd1 
[origin: LP-PPA-ubuntu-mozilla-daily]
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado   32626 F wireplumber
   /dev/snd/controlC1:  corrado   32626 F wireplumber
   /dev/snd/seq:corrado   32623 F pipewire
  BuildID: 20220712070743
  CasperMD5CheckResult: pass
  Channel: nightly
  CurrentDesktop: ubu

[Desktop-packages] [Bug 1973157] [NEW] After an encrypted installation, no splash screen or prompt is displayed asking me to remove the installation disk. Pressing any key (not just Enter) causes the

[Aaron Rainbolt]

Public bug reported:

This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. The host system specs
are the same as here:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150

At step 24, when I click the "Restart now" button, the screen goes
black, except for one solid, non-blinking underline-like cursor in the
upper-left corner of the VM screen. It appears to just stay there, never
showing me the prompt to remove the installation media and press Enter
to reboot. Additionally, I can press any key (not just Enter) to trigger
a system reboot at this point.

Steps to reproduce the bug:

1: Download the Ubuntu Kinetic daily ISO from 2022-05-11. Here's the link: 
http://cdimage.ubuntu.com/daily-live/20220511.1/kinetic-desktop-amd64.iso
2: Open virt-manager, and ensure that you have a connection to "QEMU/KVM User 
session". (If you don't, you can create this connection in virt-manager by 
clicking "File", "Add Connection", selecting "QEMU/KVM user session" in the 
"Hypervisor" drop down, then clicking "Connect".
3: Create a new VM under QEMU/KVM user session. Select the Kinetic ISO 
downloaded above, set the OS to "Ubuntu 21.04" (that's the newest version my 
virt-manager recognizes), and give it 4 GB RAM, 2 CPU cores, and 20 GB of disk 
space.
4: Follow the steps in this test procedure: 
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/247872/testcases/1451/results

Expected results: In step 24, after clicking the "Restart Now" button, I
should be told to remove the installation media and press Enter to
reboot. Only the Enter key should cause a reboot.

Actual results: Prompt is never displayed, any key will trigger the
reboot (one time I did "Shift+0" because I was accidentally typing in
the VM rather than in a text document, and one time I think I did "j" -
both triggered a reboot).

Note: Apport isn't able to open my boot.log file for some odd reason, so
I've manually copied it out of my system and attached it.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: plymouth 0.9.5+git20211018-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May 12 04:20:05 2022
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2022-05-12 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220511.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.14.0-2
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-6.0
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.14.0-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.0:cvnQEMU:ct1:cvrpc-q35-6.0:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-6.0
dmi.sys.vendor: QEMU

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


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

** Attachment added: "boot.log"
   https://bugs.launchpad.net/bugs/1973157/+attachment/5589093/+files/boot.log

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

Title:
  After an encrypted installation, no splash screen or prompt is
  displayed asking me to remove the installation disk. Pressing any key
  (not just Enter) causes the system to reboot.

Status in plymouth package in Ubuntu:
  New

Bug description:
  This bug was discovered while doing an Ubuntu QA test, "Install
  (entire disk with lvm and encryption)" for Ubuntu Kinetic. The host
  system specs are the same as here:
  https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150

  At step 24, when I click the "Restart n

[Desktop-packages] [Bug 1973156] [NEW] Strange graphical glitch during Ubuntu installation when clicking "Install Now" after inputting disk encryption details

[Aaron Rainbolt]

Public bug reported:

This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. I'm using the same
host system specs as in this bug report:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150

While running the test, in step 14, immediately after clicking "Install
Now", the VM appears to be processing the information its been given,
when suddenly there's a sharp graphical glitch. It's hard to describe,
it's sorta like the screen gets torn and stretched left and right for a
second or something - you'll have to actually reproduce the bug to get a
good idea of what it's doing.

Steps to reproduce the bug:

1: Download the Ubuntu Kinetic daily ISO from 2022-05-11. Here's the link: 
http://cdimage.ubuntu.com/daily-live/20220511.1/kinetic-desktop-amd64.iso
2: Open virt-manager, and ensure that you have a connection to "QEMU/KVM User 
session". (If you don't, you can create this connection in virt-manager by 
clicking "File", "Add Connection", selecting "QEMU/KVM user session" in the 
"Hypervisor" drop down, then clicking "Connect".
3: Create a new VM under QEMU/KVM user session. Select the Kinetic ISO 
downloaded above, set the OS to "Ubuntu 21.04" (that's the newest version my 
virt-manager recognizes), and give it 4 GB RAM, 2 CPU cores, and 20 GB of disk 
space.
4: Follow the steps in this test procedure: 
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/247872/testcases/1451/results

Expected results: In step 14, after clicking "Install Now", the VM
should pause for a bit, processing the data you've given it, and then
the screen should advance without any glitches.

Actual results: After clicking "Install Now", the screen throws a fit
for a bit before going back to normal. Everything seems normal after the
glitch.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gdm3 42.0-1ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May 12 04:08:49 2022
InstallationDate: Installed on 2022-05-12 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220511.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Strange graphical glitch during Ubuntu installation when clicking
  "Install Now" after inputting disk encryption details

Status in gdm3 package in Ubuntu:
  New

Bug description:
  This bug was discovered while doing an Ubuntu QA test, "Install
  (entire disk with lvm and encryption)" for Ubuntu Kinetic. I'm using
  the same host system specs as in this bug report:
  https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150

  While running the test, in step 14, immediately after clicking
  "Install Now", the VM appears to be processing the information its
  been given, when suddenly there's a sharp graphical glitch. It's hard
  to describe, it's sorta like the screen gets torn and stretched left
  and right for a second or something - you'll have to actually
  reproduce the bug to get a good idea of what it's doing.

  Steps to reproduce the bug:

  1: Download the Ubuntu Kinetic daily ISO from 2022-05-11. Here's the link: 
http://cdimage.ubuntu.com/daily-live/20220511.1/kinetic-desktop-amd64.iso
  2: Open virt-manager, and ensure that you have a connection to "QEMU/KVM User 
session". (If you don't, you can create this connection in virt-manager by 
clicking "File", "Add Connection", selecting "QEMU/KVM user session" in the 
"Hypervisor" drop down, then clicking "Connect".
  3: Create a new VM under QEMU/KVM user session. Select the Kinetic ISO 
downloaded above, set the OS to "Ubuntu 21.04" (that's the newest version my 
virt-manager recognizes), and give it 4 GB RAM, 2 CPU cores, and 20 GB of disk 
space.
  4: Follow the steps in this test procedure: 
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/247872/testcases/1451/results

  Expected results: In step 14, after clicking "Install Now", the VM
  should pause for a bit, processing the data you've given it, and then
  the screen should advance without any glitches.

  Actual results: After clicking "Install Now", the screen throws a fit
  for a bit before going back to normal. Everything seems normal after
  the glitch.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gdm3 42.0-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0u

[Desktop-packages] [Bug 1973150] [NEW] Fresh encrypted installation, no field is displayed for entering decryption password, but blindly entering the password succeeds

[Aaron Rainbolt]

Public bug reported:

This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. I'm doing this within
a virtual machine - the host OS is Ubuntu Studio 21.10 running on an HP
Z220 SFF Workstation, UEFI, no secure boot, 16 GB of RAM, quad-core
Intel Xeon with no hyperthreading. I placed the VM disk image on a SATA
SSD different than the SSD the host OS is installed on.

After following the steps in the testcase mentioned above and rebooting
the system, I was presented with a solid black screen. Opening the
System Monitor on the host OS revealed that the VM was using almost no
CPU. I tried blindly entering the disk's decryption password into the VM
by clicking in the black screen of the VM, typing the password, and
hitting Enter. Upon doing so, the VM's CPU usage immediately spiked, and
I was presented with a login screen in the VM not too long after. I was
able to log in and get to the desktop, where I'm currently typing this
bug report.

Steps to reproduce the bug:

1: Download the Ubuntu Kinetic daily ISO from 2022-05-11. Here's the link: 
http://cdimage.ubuntu.com/daily-live/20220511.1/kinetic-desktop-amd64.iso
2: Open virt-manager, and ensure that you have a connection to "QEMU/KVM User 
session". (If you don't, you can create this connection in virt-manager by 
clicking "File", "Add Connection", selecting "QEMU/KVM user session" in the 
"Hypervisor" drop down, then clicking "Connect".
3: Create a new VM under QEMU/KVM user session. Select the Kinetic ISO 
downloaded above, set the OS to "Ubuntu 21.04" (that's the newest version my 
virt-manager recognizes), and give it 4 GB RAM, 2 CPU cores, and 20 GB of disk 
space.
4: Follow the steps in this test procedure: 
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/247872/testcases/1451/results

Expected results: Upon rebooting in step 25, you should be presented
with a field to input the disk decryption password into.

Actual results: You are presented with a black screen, but you can
blindly enter the password into the VM and get it to boot.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: plymouth 0.9.5+git20211018-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May 12 03:33:04 2022
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2022-05-12 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220511.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.14.0-2
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-6.0
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.14.0-2:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.0:cvnQEMU:ct1:cvrpc-q35-6.0:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-6.0
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-bug encryption kinetic wayland-session

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

Title:
  Fresh encrypted installation, no field is displayed for entering
  decryption password, but blindly entering the password succeeds

Status in plymouth package in Ubuntu:
  New

Bug description:
  This bug was discovered while doing an Ubuntu QA test, "Install
  (entire disk with lvm and encryption)" for Ubuntu Kinetic. I'm doing
  this within a virtual machine - the host OS is Ubuntu Studio 21.10
  running on an HP Z220 SFF Workstation, UEFI, no secure boot, 16 GB of
  RAM, quad-core Intel Xeon with no hyperthreading. I placed the VM disk
  image on a S

[Desktop-packages] [Bug 1972991] [NEW] 22.04 Totem crashes on launch (segmentation fault)

[Aaron Whitehouse]

Public bug reported:

Hello,

Since upgrading (fresh reinstall) to 22.04, I have had issues with Totem
crashing.

I have not been able to pin down when it works and when it doesn't, as
playing the same videos seems to work sometimes and not work others.
After it crashes, trying to open it again normally does not work and
trying to launch totem from the commandline gives a segmentation fault.

Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Segmentation fault (core dumped)

$ totem
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 11 13:10:48 2022
InstallationDate: Installed on 2022-04-24 (16 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


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

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

Title:
  22.04 Totem crashes on launch (segmentation fault)

Status in totem package in Ubuntu:
  New

Bug description:
  Hello,

  Since upgrading (fresh reinstall) to 22.04, I have had issues with
  Totem crashing.

  I have not been able to pin down when it works and when it doesn't, as
  playing the same videos seems to work sometimes and not work others.
  After it crashes, trying to open it again normally does not work and
  trying to launch totem from the commandline gives a segmentation
  fault.

  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XX

[Desktop-packages] [Bug 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)

[Aaron Whitehouse]

(And Firefox gave me a notification about hitting version 100, so it
presumably did update)

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

Title:
  Ubuntu Dock does not show indicator for open Firefox (after snap
  refresh?)

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

Bug description:
  I am using the Firefox Snap on a fresh install of 22.04 (using
  defaults, as far as I know).

  Normally, Firefox shows an indicator in the Dock showing that it is
  running (the orange dot) and gives the ability to choose between open
  windows.

  At the moment, I have Firefox windows open, but nothing is shown in
  the Dock (as if it is closed).

  My suspicion is that the snap was refreshed while running and this
  confused Gnome Shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 13:31:40 2022
  InstallationDate: Installed on 2022-04-24 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+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 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)

[Aaron Whitehouse]

** Attachment added: "As expected, closing and reopening Firefox makes it work 
as expected"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587903/+files/Screenshot%20from%202022-05-09%2013-44-45.png

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

Title:
  Ubuntu Dock does not show indicator for open Firefox (after snap
  refresh?)

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

Bug description:
  I am using the Firefox Snap on a fresh install of 22.04 (using
  defaults, as far as I know).

  Normally, Firefox shows an indicator in the Dock showing that it is
  running (the orange dot) and gives the ability to choose between open
  windows.

  At the moment, I have Firefox windows open, but nothing is shown in
  the Dock (as if it is closed).

  My suspicion is that the snap was refreshed while running and this
  confused Gnome Shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 13:31:40 2022
  InstallationDate: Installed on 2022-04-24 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+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 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)

[Aaron Whitehouse]

** Attachment added: "Screenshot of the dock"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587901/+files/Screenshot%20from%202022-05-09%2013-32-20.png

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

Title:
  Ubuntu Dock does not show indicator for open Firefox (after snap
  refresh?)

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

Bug description:
  I am using the Firefox Snap on a fresh install of 22.04 (using
  defaults, as far as I know).

  Normally, Firefox shows an indicator in the Dock showing that it is
  running (the orange dot) and gives the ability to choose between open
  windows.

  At the moment, I have Firefox windows open, but nothing is shown in
  the Dock (as if it is closed).

  My suspicion is that the snap was refreshed while running and this
  confused Gnome Shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 13:31:40 2022
  InstallationDate: Installed on 2022-04-24 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+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 1972545] [NEW] Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)

[Aaron Whitehouse]

Public bug reported:

I am using the Firefox Snap on a fresh install of 22.04 (using defaults,
as far as I know).

Normally, Firefox shows an indicator in the Dock showing that it is
running (the orange dot) and gives the ability to choose between open
windows.

At the moment, I have Firefox windows open, but nothing is shown in the
Dock (as if it is closed).

My suspicion is that the snap was refreshed while running and this
confused Gnome Shell.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May  9 13:31:40 2022
InstallationDate: Installed on 2022-04-24 (14 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "journalctl -b 0 > log"
   https://bugs.launchpad.net/bugs/1972545/+attachment/5587897/+files/log

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

Title:
  Ubuntu Dock does not show indicator for open Firefox (after snap
  refresh?)

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

Bug description:
  I am using the Firefox Snap on a fresh install of 22.04 (using
  defaults, as far as I know).

  Normally, Firefox shows an indicator in the Dock showing that it is
  running (the orange dot) and gives the ability to choose between open
  windows.

  At the moment, I have Firefox windows open, but nothing is shown in
  the Dock (as if it is closed).

  My suspicion is that the snap was refreshed while running and this
  confused Gnome Shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 13:31:40 2022
  InstallationDate: Installed on 2022-04-24 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+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 1970185] Re: 20.04 does not remember preferred bluetooth headset microphone

[Aaron Whitehouse]

** Attachment added: "Headset back on, output has gone back to the headset but 
microphone has not"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583423/+files/Screenshot%20from%202022-04-25%2009-43-46.png

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

Title:
  20.04 does not remember preferred bluetooth headset microphone

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

Bug description:
  In Gnome's sound settings, it takes a sensible approach for my Bluetooth 
headset speaker:
  1) I set it as my preferred audio Output Device
  2) I turn the headset off and it disappears, reverting to the built in 
speakers
  3) I turn the headset on again and it switches back to using the Bluetooth 
headset speaker

  This sensible approach is not taken for the microphone. The same flow for the 
microphone is:
  1) Set the headset microphone as the default
  2) Turn the headset off and it reverts to the internal microphone
  3) Turn the headset back on and it stays as the internal microphone

  I have attached screenshots in case they help explain.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 09:44:42 2022
  InstallationDate: Installed on 2022-04-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+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 1970185] Re: 20.04 does not remember preferred bluetooth headset microphone

[Aaron Whitehouse]

** Attachment added: "Headset turned off, input and output revert to internal 
ones"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583422/+files/Screenshot%20from%202022-04-25%2009-43-27.png

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

Title:
  20.04 does not remember preferred bluetooth headset microphone

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

Bug description:
  In Gnome's sound settings, it takes a sensible approach for my Bluetooth 
headset speaker:
  1) I set it as my preferred audio Output Device
  2) I turn the headset off and it disappears, reverting to the built in 
speakers
  3) I turn the headset on again and it switches back to using the Bluetooth 
headset speaker

  This sensible approach is not taken for the microphone. The same flow for the 
microphone is:
  1) Set the headset microphone as the default
  2) Turn the headset off and it reverts to the internal microphone
  3) Turn the headset back on and it stays as the internal microphone

  I have attached screenshots in case they help explain.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 09:44:42 2022
  InstallationDate: Installed on 2022-04-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+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 1970185] [NEW] 20.04 does not remember preferred bluetooth headset microphone

[Aaron Whitehouse]

Public bug reported:

In Gnome's sound settings, it takes a sensible approach for my Bluetooth 
headset speaker:
1) I set it as my preferred audio Output Device
2) I turn the headset off and it disappears, reverting to the built in speakers
3) I turn the headset on again and it switches back to using the Bluetooth 
headset speaker

This sensible approach is not taken for the microphone. The same flow for the 
microphone is:
1) Set the headset microphone as the default
2) Turn the headset off and it reverts to the internal microphone
3) Turn the headset back on and it stays as the internal microphone

I have attached screenshots in case they help explain.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.4-1ubuntu12
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 25 09:44:42 2022
InstallationDate: Installed on 2022-04-24 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Headset on, headset mic and speaker set as input and 
output devices"
   
https://bugs.launchpad.net/bugs/1970185/+attachment/5583417/+files/Screenshot%20from%202022-04-25%2009-42-41.png

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

Title:
  20.04 does not remember preferred bluetooth headset microphone

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

Bug description:
  In Gnome's sound settings, it takes a sensible approach for my Bluetooth 
headset speaker:
  1) I set it as my preferred audio Output Device
  2) I turn the headset off and it disappears, reverting to the built in 
speakers
  3) I turn the headset on again and it switches back to using the Bluetooth 
headset speaker

  This sensible approach is not taken for the microphone. The same flow for the 
microphone is:
  1) Set the headset microphone as the default
  2) Turn the headset off and it reverts to the internal microphone
  3) Turn the headset back on and it stays as the internal microphone

  I have attached screenshots in case they help explain.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 09:44:42 2022
  InstallationDate: Installed on 2022-04-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+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 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time

[Michael Aaron Murphy]

Fixed 2 days ago in updated gdm package.

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

Title:
  System fallback to gdm login screen when hot-plugging a external
  monitor in 1st time

Status in OEM Priority Project:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  [Steps to reproduce]
  1. Install Jammy daily build
  2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037
  3. reboot with no attach monitor
  4. attach monitor after booting

  [Expect result]
  external monitor works directly

  [Actual result]
  system go back to gdm login screen

  [Additional information]
  1. the external port is connecting to dGPU.
  2. happens on wayland only
  3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 14 21:22:47 2022
  InstallationDate: Installed on 2022-04-13 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969121/+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 10883]

[Aaron Wolf]

(In reply to wolftune from comment #67)
> The shift+click workaround does NOT work for me when using the normal 
> interface with the curvy-arrow "reply" buttons. No matter what I do, the 
> account default for HTML or plain stays.

I now have shift+click working in the normal interface since I got a
more recent Thunderbird update since a couple months ago.

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

Title:
  Stuck in proportional font mode

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

Bug description:
  If you start a message in HTML mode, choosing Options->Format->Plain Text Only
  switches to plain text mode but the compose window does not switch to a
  monospace font. Starting a message in plain text mode uses the correct font.

  https://bugzilla.mozilla.org/show_bug.cgi?id=216132:
  https://bugzilla.mozilla.org/show_bug.cgi?id=216132

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/10883/+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 1958778] Re: Laptop not waking up from suspend, or waking up with random noise on screen.

[Aaron Kriegman]

Update: I suspended my computer again. This time when I opened it the
monitor worked, the laptop screen was black, and the mouse had
completely disappeared.

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

Title:
  Laptop not waking up from suspend, or waking up with random noise on
  screen.

Status in xorg package in Ubuntu:
  New

Bug description:
  Starting today my laptop will not wake up from suspend no matter what
  I try. After closing my laptop or leaving it alone for a while, the
  screen goes black like normal, but then no matter how much I mash the
  keyboard, touch the mouse, press the power button etc. the screen will
  not turn on. The power light is still on when this happens, so the
  computer is on. I've had to resort to holding the power button to
  restart every time.

  The behavior only changed (and got even weirder) when I plugged my
  monitor into my laptop. Things worked normally until my laptop went
  into standby. This time the monitor woke up as normal, and my laptop
  screen became filled with colorful static. I'm able to use the
  computer as normal on the monitor, which is how I'm filing this
  report.

  I should note that I installed routine updates yesterday through
  Software Updater, which is likely what triggered these issues. I also
  had a possibly related bug yesterday (after updating) where my
  laptop's fan stopped working. I restarted once and the fan still
  wouldn't turn on. I switched to my Windows partition and the fan
  started working. Then when I switched back to my Ubuntu partition the
  fan was working normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 17:11:50 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2021-08-04 (171 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 81X2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=464df196-22f9-4ea4-989d-dda2cb0a5ec5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2020
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrEECN31WW:bd12/18/2020:br1.31:efr1.20:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:skuLENOVO_MT_81X2_BU_idea_FM_IdeaPadFlex514ARE05:
  dmi.product.family: IdeaPad Flex 5 14ARE05
  dmi.product.name: 81X2
  dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
  dmi.product.version: IdeaPad Flex 5 14ARE05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1958778/+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 1958778] [NEW] Laptop not waking up from suspend, or waking up with random noise on screen.

[Aaron Kriegman]

Public bug reported:

Starting today my laptop will not wake up from suspend no matter what I
try. After closing my laptop or leaving it alone for a while, the screen
goes black like normal, but then no matter how much I mash the keyboard,
touch the mouse, press the power button etc. the screen will not turn
on. The power light is still on when this happens, so the computer is
on. I've had to resort to holding the power button to restart every
time.

The behavior only changed (and got even weirder) when I plugged my
monitor into my laptop. Things worked normally until my laptop went into
standby. This time the monitor woke up as normal, and my laptop screen
became filled with colorful static. I'm able to use the computer as
normal on the monitor, which is how I'm filing this report.

I should note that I installed routine updates yesterday through
Software Updater, which is likely what triggered these issues. I also
had a possibly related bug yesterday (after updating) where my laptop's
fan stopped working. I restarted once and the fan still wouldn't turn
on. I switched to my Windows partition and the fan started working. Then
when I switched back to my Ubuntu partition the fan was working
normally.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 23 17:11:50 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Renoir [17aa:3f1a]
InstallationDate: Installed on 2021-08-04 (171 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 81X2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=464df196-22f9-4ea4-989d-dda2cb0a5ec5 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2020
dmi.bios.release: 1.31
dmi.bios.vendor: LENOVO
dmi.bios.version: EECN31WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Flex 5 14ARE05
dmi.ec.firmware.release: 1.20
dmi.modalias: 
dmi:bvnLENOVO:bvrEECN31WW:bd12/18/2020:br1.31:efr1.20:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:skuLENOVO_MT_81X2_BU_idea_FM_IdeaPadFlex514ARE05:
dmi.product.family: IdeaPad Flex 5 14ARE05
dmi.product.name: 81X2
dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
dmi.product.version: IdeaPad Flex 5 14ARE05
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Laptop not waking up from suspend, or waking up with random noise on
  screen.

Status in xorg package in Ubuntu:
  New

Bug description:
  Starting today my laptop will not wake up from suspend no matter what
  I try. After closing my laptop or leaving it alone for a while, the
  screen goes black like normal, but then no matter how much I mash the
  keyboard, touch the mouse, press the power button etc. the screen will
  not turn on. The power light is still on when this happens, so the
  computer is on. I've had to resort to holding the power button to
  restart every time.

  The behavior only changed (and got even weirder) when I plugged my
  monitor into my laptop. Things worked normally until my laptop went
  into standby. This time the monitor woke up as normal, and my laptop
  screen became filled with colorful static. I'm able to use the
  computer as normal on the monitor, which is how I'm filing this
  report.

  I should note that I installed routine updates yesterday through
  Software Updater, which is like

[Desktop-packages] [Bug 10883]

[Aaron Wolf]

The shift+click workaround does NOT work for me when using the normal
interface with the curvy-arrow "reply" buttons. No matter what I do, the
account default for HTML or plain stays.

I figured out that the shift+click works ONLY if I choose "reply" from a
menu, either the "Message" menu or from contextual menu with a right-
click.

Seems absurd that the functionality is clearly present but the UI has
nearly no way to access it in a straightforward sense.

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

Title:
  Stuck in proportional font mode

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

Bug description:
  If you start a message in HTML mode, choosing Options->Format->Plain Text Only
  switches to plain text mode but the compose window does not switch to a
  monospace font. Starting a message in plain text mode uses the correct font.

  https://bugzilla.mozilla.org/show_bug.cgi?id=216132:
  https://bugzilla.mozilla.org/show_bug.cgi?id=216132

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/10883/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow

[aaron]

Thanks Bas,  this bug really make the system unusable.  Very annoying.
Any workaround would be appreciate.

I guess this issue is talking about similar thing.
https://github.com/DisplayLink/evdi/issues/181

** Bug watch added: github.com/DisplayLink/evdi/issues #181
   https://github.com/DisplayLink/evdi/issues/181

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

Title:
  Ubuntu 20.04 and Displaylink is extremely slow

Status in Nouveau Xorg driver:
  Unknown
Status in OEM Priority Project:
  New
Status in xf86-video-amd:
  Unknown
Status in X.Org X server:
  Unknown
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  In Progress
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  In Progress
Status in xorg-server source package in Hirsute:
  In Progress
Status in xorg-server source package in Impish:
  Fix Released

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow

[aaron]

Still no fix or workaround?  Having a fresh ubuntu 20.04 installed.
nvidia 470.86
xserver-xorg-core  2:1.20.13-1ubuntu1~20.04.2
5.11.0-43-generic

HP zbook, G5.

External monitor, Xorg high cpu load, external monitor random slow.

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

Title:
  Ubuntu 20.04 and Displaylink is extremely slow

Status in Nouveau Xorg driver:
  Unknown
Status in OEM Priority Project:
  New
Status in xf86-video-amd:
  Unknown
Status in X.Org X server:
  Unknown
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  In Progress
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  In Progress
Status in xorg-server source package in Hirsute:
  In Progress
Status in xorg-server source package in Impish:
  Fix Released

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1938867] Re: Logitech K400R keyboard not entering text into input fields on Raspberry Pi 4

[Aaron Whitehouse]

Ah interesting, thanks Daniel. I did not realise Raspberry Pis were
doing Wayland by default.

Yes, it works as expected in xorg, but not in Wayland.

It's a Raspberry Pi 4 Model B - 8GB, in case that was not clear from my
logs.

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

Title:
  Logitech K400R keyboard not entering text into input fields on
  Raspberry Pi 4

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this
  (TV) machine is a wireless Logitech K400r combined keyboard/trackpad.

  When I first installed, I do not think there were any issues with the
  keyboard. When I did updates, my keyboard half-stopped working. It is
  very odd -- the keyboard is obviously working, as I can enter in my
  password on the lock screen or press Ctrl+Alt t for a terminal, but
  then I cannot enter anything into the terminal, Firefox input fields
  or anything else. Even more strangely, when I attach a second USB
  keyboard, both that new keyboard and my K400r work perfectly.When I
  unplug the USB keyboard, it stops working again.

  I'm not sure where this problem is, but:
  $ apt policy xserver-xorg-input-all
  xserver-xorg-input-all:
Installed: 1:7.7+22ubuntu1

  Please let me know if I can provide anything further to help diagnose
  this.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg-input-all 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-1015.16-raspi 5.11.22
  Uname: Linux 5.11.0-1015-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  4 08:46:44 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20210421
  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 
video=HDMI-A-1:1280x720M@60 smsc95xx.macaddr=E4:5F:01:48:E1:03 
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.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1938867/+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 1938867] [NEW] Keyboard not entering text into input fields

[Aaron Whitehouse]

Public bug reported:

I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this
(TV) machine is a wireless Logitech K400r combined keyboard/trackpad.

When I first installed, I do not think there were any issues with the
keyboard. When I did updates, my keyboard half-stopped working. It is
very odd -- the keyboard is obviously working, as I can enter in my
password on the lock screen or press Ctrl+Alt t for a terminal, but then
I cannot enter anything into the terminal, Firefox input fields or
anything else. Even more strangely, when I attach a second USB keyboard,
both that new keyboard and my K400r work perfectly.When I unplug the USB
keyboard, it stops working again.

I'm not sure where this problem is, but:
$ apt policy xserver-xorg-input-all
xserver-xorg-input-all:
  Installed: 1:7.7+22ubuntu1

Please let me know if I can provide anything further to help diagnose
this.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xserver-xorg-input-all 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-1015.16-raspi 5.11.22
Uname: Linux 5.11.0-1015-raspi aarch64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: arm64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  4 08:46:44 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 
ImageMediaBuild: 20210421
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 
video=HDMI-A-1:1280x720M@60 smsc95xx.macaddr=E4:5F:01:48:E1:03 
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.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: apport-bug arm64 arm64-image hirsute raspi-image ubuntu wayland-session

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

Title:
  Keyboard not entering text into input fields

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this
  (TV) machine is a wireless Logitech K400r combined keyboard/trackpad.

  When I first installed, I do not think there were any issues with the
  keyboard. When I did updates, my keyboard half-stopped working. It is
  very odd -- the keyboard is obviously working, as I can enter in my
  password on the lock screen or press Ctrl+Alt t for a terminal, but
  then I cannot enter anything into the terminal, Firefox input fields
  or anything else. Even more strangely, when I attach a second USB
  keyboard, both that new keyboard and my K400r work perfectly.When I
  unplug the USB keyboard, it stops working again.

  I'm not sure where this problem is, but:
  $ apt policy xserver-xorg-input-all
  xserver-xorg-input-all:
Installed: 1:7.7+22ubuntu1

  Please let me know if I can provide anything further to help diagnose
  this.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg-input-all 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-1015.16-raspi 5.11.22
  Uname: Linux 5.11.0-1015-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  4 08:46:44 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20210421
  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 
video=HDMI-A-1:1280x720M@60 smsc95xx.macaddr=E4:5F:01:48:E1:03 
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)
 

[Desktop-packages] [Bug 1923718] [NEW] Can't rename bookmarks in Nautilus

[Aaron]

Public bug reported:

In Nautilus File Manager, when trying to rename the bookmark of a
(remote) directory through the context menu, the "rename" option is not
clickable. Instead the click activates the option to drag the entry of
the bookmark to a different position.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: nautilus 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 14 08:00:42 2021
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 763)'
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
InstallationDate: Installed on 2021-02-02 (70 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince3.38.0-1
 file-roller   3.38.0-1
 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1
 nautilus-share0.7.3-2ubuntu3

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


** Tags: amd64 apport-bug groovy

** Attachment added: "Screenshot showing the context menu after clicking on 
"rename""
   
https://bugs.launchpad.net/bugs/1923718/+attachment/5487662/+files/Screenshot%20from%202021-04-14%2008-16-22.png

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

Title:
  Can't rename bookmarks in Nautilus

Status in nautilus package in Ubuntu:
  New

Bug description:
  In Nautilus File Manager, when trying to rename the bookmark of a
  (remote) directory through the context menu, the "rename" option is
  not clickable. Instead the click activates the option to drag the
  entry of the bookmark to a different position.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: nautilus 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 08:00:42 2021
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 763)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2021-02-02 (70 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince3.38.0-1
   file-roller   3.38.0-1
   nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1
   nautilus-share0.7.3-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1923718/+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 1915377] [NEW] Nautilus crashes on rename

[Aaron]

Public bug reported:


Bug Description:
I wanted to rename a directory.
Nautilus crashes with error 'Files not responding'.
Name contains A-Z, a-z, 0-9, Underscore, Hyphen.

Versions:
Ubuntu
Description:Ubuntu 20.10
Release:20.10
Nautilus (Files)
1:3.38.1-1ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: nautilus 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 11 08:22:41 2021
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 1006)'
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
InstallationDate: Installed on 2021-02-02 (8 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince3.38.0-1
 file-roller   3.38.0-1
 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1
 nautilus-share0.7.3-2ubuntu3

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

Title:
  Nautilus crashes on rename

Status in nautilus package in Ubuntu:
  New

Bug description:
  
  Bug Description:
  I wanted to rename a directory.
  Nautilus crashes with error 'Files not responding'.
  Name contains A-Z, a-z, 0-9, Underscore, Hyphen.

  Versions:
  Ubuntu
  Description:  Ubuntu 20.10
  Release:  20.10
  Nautilus (Files)
  1:3.38.1-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: nautilus 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 11 08:22:41 2021
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 1006)'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2021-02-02 (8 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince3.38.0-1
   file-roller   3.38.0-1
   nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1
   nautilus-share0.7.3-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1915377/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow

[Aaron Cardinal]

Patch has little to no effect on my laptop.  It's especially noticeable
when playing video.

Dell Inspiron 13 5368 2-in-1 Laptop
Processor:  Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz
Memory:  12125MB (4913MB used)
Operating System:  Ubuntu 20.04.1 LTS
Kernel:  Linux 5.4.0-48-generic (x86_64)
Version:  #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020
C Library:  GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.1) 2.31
Date/Time:  Sun 04 Oct 2020 12:24:04 PM EDT

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

Title:
  Ubuntu 20.04 and Displaylink is extremely slow

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1875015/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[LI CHEN AARON]

Same version of ubuntu and same bluetooth earbuds work fine on different
desktop but not on my laptop. Does this have something to do with model
of the bluetooth as well?

Information collected from my laptop (not working)

[Jabra Elite 65t]# info 70:BF:92:22:3B:71
Device 70:BF:92:22:3B:71 (public)
Name: Jabra Elite 65t
Alias: Jabra Elite 65t
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific   (-deca-fade-deca-deafdecacaff)
UUID: Serial Port   (1101--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: bluetooth:v0067p247Ed0222
ManufacturerData Key: 0x0067
ManufacturerData Value:
  03 07 01 4c 03 0b 7e 24  ...L..~$

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

[Aaron Wagner]

Possibly related to this:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405

That bug focuses on the soft lockup but nouveau has come up as a factor.

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+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 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

[Aaron Wagner]

Just upgraded to 16.04 LTS and that works as well. To be clear, for both
14.04 and 16.04, the proprietary NVIDIA drivers are available via the
nvidia-304 package, but I'm not using those. The nouveau driver itself
works on 14.04 and 16.04.

FWIW, back when I tried running 18.04/20.04, when programs were hanging
I checked dmesg and saw errors of the form "watchdog: BUG: soft lockup -
CPU#3 stuck for 22s"

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+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 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

[Aaron Wagner]

I have been experiencing a similar problem with a GeForce 7300 GT on a
Mac Pro 1,1. I also have visual artifacts in 18.04 and 20.04. With
18.04, there are no artifacts or other problems during installation from
a DVD, but when booting the installed system there are artifacts after
login and eventually programs start hanging. With 20.04, the
installation program itself has artifacts when running off the DVD.

Just did a clean install of 14.04.6 and that works fine.

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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