date:20220407

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  In the last 24 hours, my system has started having skipping/stuttering
  audio when gaming, or watching videos on youtube in chrome, and no
  audio at all when using VLC to play music files or watching youtube in
  Firefox.

  I believe I did a system update in the last week or so but I don't
  know if that is the cause.

  Description: Ubuntu 20.04.4 LTS
  Release: 20.04

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 00:05:34 2022
  InstallationDate: Installed on 2020-08-31 (582 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful
  Symptom_Card: G930 - Logitech G930 Headset
  Symptom_PulseAudioLog:
   Apr 05 23:40:42 nzxt dbus-daemon[1169]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.40' (uid=125 pid=1765 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Apr 05 23:41:59 nzxt systemd[1655]: pulseaudio.service: Succeeded.
   Apr 05 23:42:09 nzxt systemd[1655]: pulseaudio.socket: Succeeded.
   Apr 05 23:49:33 nzxt sudo[8926]: root : TTY=unknown ; PWD=/home/raj ; 
USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; 
COMMAND=/usr/bin/xdg-open 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/b77c80a0-b575-11ec-b9ed-40a8f0305cb4?
   Apr 05 23:54:56 nzxt sudo[11680]: root : TTY=unknown ; PWD=/home/raj ; 
USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; 
COMMAND=/usr/bin/xdg-open 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/77aee818-b576-11ec-b78d-40a8f0308420?
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Desktop-packages] [Bug 1967995] Re: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound

2022-04-07 Thread Max

Similar issue for me with a Jabra Evolve 75 headset. As soon as
microphone is used, e.g. for a call, the driver seems to get into a
corrupted state where sound from speakers have crackling sound as long
as microphone is active. The issue doesn't appear when starting with
kernel 5.13.0-35. Looks like there have been some changes to usb-audio
drivers with kernel version 5.13.0-37.

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

Title:
  [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  In the last 24 hours, my system has started having skipping/stuttering
  audio when gaming, or watching videos on youtube in chrome, and no
  audio at all when using VLC to play music files or watching youtube in
  Firefox.

  I believe I did a system update in the last week or so but I don't
  know if that is the cause.

  Description: Ubuntu 20.04.4 LTS
  Release: 20.04

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 00:05:34 2022
  InstallationDate: Installed on 2020-08-31 (582 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful
  Symptom_Card: G930 - Logitech G930 Headset
  Symptom_PulseAudioLog:
   Apr 05 23:40:42 nzxt dbus-daemon[1169]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.40' (uid=125 pid=1765 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Apr 05 23:41:59 nzxt systemd[1655]: pulseaudio.service: Succeeded.
   Apr 05 23:42:09 nzxt systemd[1655]: pulseaudio.socket: Succeeded.
   Apr 05 23:49:33 nzxt sudo[8926]: root : TTY=unknown ; PWD=/home/raj ; 
USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; 
COMMAND=/usr/bin/xdg-open 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/b77c80a0-b575-11ec-b9ed-40a8f0305cb4?
   Apr 05 23:54:56 nzxt sudo[11680]: root : TTY=unknown ; PWD=/home/raj ; 
USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; 
COMMAND=/usr/bin/xdg-open 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/77aee818-b576-11ec-b78d-40a8f0308420?
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 I AORUS PRO WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 I AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Desktop-packages] [Bug 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

** Changed in: ubuntu-mate-settings (Ubuntu)
   Status: Triaged => In Progress

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

** Changed in: mate-desktop-environment (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mate-desktop-environment (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

** Changed in: ubuntu-mate-settings (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-mate-settings (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  In Progress
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  In Progress
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-04-07 Thread Dave Jones

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

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

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


-- 
Mailing list: https://launchpad.net/~desktop-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

2022-04-07 Thread Bartłomiej Żogała

It's not about 2.6Mb storage space taken. It's about what those 2.6Mb of
logic does, how transparent the whole process is and how many potential
security vulnerabilities it may introduce due to not having one
transparent entrypoint for activation. You are exactly following
Microsoft way to telemetry, where there are multiple toggles around the
system but telemetry it's already so deeply integrated that you never
can be sure if it was completely disabled.

You do benefit not only from your paying customers base but from whole
open source community work up to day. Including this portal and all
feedback passed automatically/manually from users which run Ubuntu on
their hardware. So saying that you don't care about non paying customers
seems a bit arrogant here.

Isn't the fact that you have seperate restricted repository backed on
the same concept of lack of full trust ? There is whole group of people
who e.g don't have Nvidia software on their hardware and they have a
chocice, why they shouldn't have the same choice with Canonical software
?

-- 
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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

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

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

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Fix Committed
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Fix Committed
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

2022-04-07 Thread Francois Thirioux

I hit this bug in Jammy, up to date including GS 42.0 latest.
See attachment.

I noticed it because Dock from Dash extension relies on windows count to
switch to app or to overview...

** Attachment added: "Screenshot from 2022-04-07 14-04-45.png"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/+attachment/5577898/+files/Screenshot%20from%202022-04-07%2014-04-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/1932328

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

Status in GNOME Shell:
  Unknown
Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Invalid

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

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


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

[Desktop-packages] [Bug 1967127] Re: [FFe] update libarchive to 3.6.0

** Changed in: libarchive (Ubuntu)
Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: evince (Ubuntu)
Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: libarchive (Ubuntu)
Status: Triaged => Fix Committed

** Changed in: evince (Ubuntu)
Status: New => In Progress

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

Title:
[FFe] update libarchive to 3.6.0

Status in evince package in Ubuntu:
In Progress
Status in libarchive package in Ubuntu:
Fix Committed

Bug description:
I request a Feature Freeze Exception to update libarchive from 3.5.2
to 3.6.0 and build evince with libarchive 3.6.

This will allow us to drop 2 revert commits we added to evince to build with
the older libarchive.
https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b

Changes
---
https://github.com/libarchive/libarchive/releases/tag/v3.6.0
https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0

Other Changes
-
1. libarchive: I am cherry-picking a security fix for CVE-2022-26280
2. libarchive: debian/rules was only running dh_auto_test if 'check' was set
in DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set.
That way we run the build tests by default.

I'm forwarding both those changes to Debian soon.

Build logs
--

https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra

https://buildd.debian.org/status/package.php?p=evince

Testing done

No errors in the install logs

Evince still works fine to open a variety of PDFs and a .cbz file I have.
File Roller still works fine to open a variety of compressed file types.

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

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

[Desktop-packages] [Bug 1968167] [NEW] FFe: xf86-input-wacom 1.0.0

2022-04-07 Thread Timo Aaltonen

Public bug reported:

Hi,

The Wacom X driver has a new Debian maintainer now, so the package has
seen some janitorial changes to the packaging, plus a new upstream
release.

We currently have 0.39.0, 0.40.0 added some new device support:

>>>
xf86-input-wacom-0.40.0 jigpu released this Feb 03, 2021

This release of xf86-input-wacom provides bugfixes and improved support for 
several Wacom products. In particular, the "pan" action now behaves more 
appropriately in relative mode and heavy multi-touch use should no longer cause 
strange touch behavior. This release also adds support for the softkeys which 
some Cintiq models provide, although additional work in XKB and the desktop 
environment is necessary for them to be fully functional.
<<<

Instead of listing all the commits between 0.40.0 and 1.0.0, a blog post
explaining the 1.0.0 release might be more appropriate:

http://who-t.blogspot.com/2022/02/the-xf86-input-wacom-driver-
hits-10.html

So in summary, the driver has been refactored to allow easier debugging
and testing. There shouldn't be user-visible changes in it.


I've tested 1.0.0 on an Intuos 5m, and it's working fine.

** Affects: xf86-input-wacom (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  FFe: xf86-input-wacom 1.0.0

Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  Hi,

  The Wacom X driver has a new Debian maintainer now, so the package has
  seen some janitorial changes to the packaging, plus a new upstream
  release.

  We currently have 0.39.0, 0.40.0 added some new device support:

  >>>
  xf86-input-wacom-0.40.0 jigpu released this Feb 03, 2021

  This release of xf86-input-wacom provides bugfixes and improved support for 
several Wacom products. In particular, the "pan" action now behaves more 
appropriately in relative mode and heavy multi-touch use should no longer cause 
strange touch behavior. This release also adds support for the softkeys which 
some Cintiq models provide, although additional work in XKB and the desktop 
environment is necessary for them to be fully functional.
  <<<

  Instead of listing all the commits between 0.40.0 and 1.0.0, a blog
  post explaining the 1.0.0 release might be more appropriate:

  http://who-t.blogspot.com/2022/02/the-xf86-input-wacom-driver-
  hits-10.html

  So in summary, the driver has been refactored to allow easier
  debugging and testing. There shouldn't be user-visible changes in it.

  
  I've tested 1.0.0 on an Intuos 5m, and it's working fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1968167/+subscriptions


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

[Desktop-packages] [Bug 1968179] [NEW] [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted

2022-04-07 Thread Klas

Public bug reported:

I noticed some dynamic distortion starting today. It is not periodic but
rather seems to be effected by the music played. Running a VM i do not
get the same problem with windows. The distortion is also heard through
the Analog port of my Lenovo USB C Dock Gen 2. I checked with different
headphones/speakers the problem persists.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.13
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  7 16:21:40 2022
InstallationDate: Installed on 2020-07-31 (615 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 successful
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic
Symptom_Jack: Black Headphone Out, Right
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2020
dmi.bios.release: 1.20
dmi.bios.vendor: LENOVO
dmi.bios.version: DTCN20WW(V1.06)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 14ARE05
dmi.ec.firmware.release: 1.20
dmi.modalias: 
dmi:bvnLENOVO:bvrDTCN20WW(V1.06):bd06/09/2020:br1.20:efr1.20:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05:
dmi.product.family: IdeaPad 5 14ARE05
dmi.product.name: 81YM
dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05
dmi.product.version: IdeaPad 5 14ARE05
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

** Description changed:

- I noticed so dynamic distortion starting today. It is not periodic but
+ I noticed some dynamic distortion starting today. It is not periodic but
  rather seems to be effected by the music played. Running a VM i do not
  get the same problem with windows. The distortion is also heard through
  the Analog port of my Lenovo USB C Dock Gen 2. I checked with different
  headphones/speakers the problem persists.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 16:21:40 2022
  InstallationDate: Installed on 2020-07-31 (615 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 
successful
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2020
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DTCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14ARE05
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrDTCN20WW(V1.06):bd06/09/2020:br1.20:efr1.20:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05:
  dmi.product.family: IdeaPad 5 14ARE05
  dmi.product.name: 81YM
  dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05
  dmi.product.version: IdeaPad 5 14ARE05
  dmi.sys.vendor: LENOVO

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

[Desktop-packages] [Bug 1968179] Re: [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted

2022-04-07 Thread Klas

** Attachment added: "Short recording of the failing second test tone"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1968179/+attachment/5577925/+files/signal-2022-04-07-163532.aac

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

Title:
  [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I noticed some dynamic distortion starting today. It is not periodic
  but rather seems to be effected by the music played. Running a VM i do
  not get the same problem with windows. The distortion is also heard
  through the Analog port of my Lenovo USB C Dock Gen 2. I checked with
  different headphones/speakers the problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 16:21:40 2022
  InstallationDate: Installed on 2020-07-31 (615 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 
successful
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2020
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DTCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14ARE05
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrDTCN20WW(V1.06):bd06/09/2020:br1.20:efr1.20:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05:
  dmi.product.family: IdeaPad 5 14ARE05
  dmi.product.name: 81YM
  dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05
  dmi.product.version: IdeaPad 5 14ARE05
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1956603] Re: > Internal error: Could not resolve keysym ...

2022-04-07 Thread madigal

** Changed in: libx11 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: x11-xkb-utils (Ubuntu)
   Status: Confirmed => Invalid

** Project changed: xlibs => libx11-xcb-perl (Ubuntu)

** Changed in: libx11-xcb-perl (Ubuntu)
   Status: Unknown => Invalid

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

Title:
  > Internal error:   Could not resolve keysym ...

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11-xcb-perl package in Ubuntu:
  Invalid
Status in x11-xkb-utils package in Ubuntu:
  Invalid

Bug description:
  Get lot of such warnings into Jammy logged;
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNIN

[Desktop-packages] [Bug 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

2022-04-07 Thread Treviño

So... Per sé the issue only affect apps that are bundled / static linked
with old Gdk version, while there may be many around in snaps and
flatpaks, I think it's better to workaround the issue at mutter level
too, so we'll handle both there and in the platform snap.

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

Title:
  Cannot use Drag and Drop in gnome-shell 42 (Wayland session)

Status in Mozilla Firefox:
  New
Status in Mutter:
  Unknown
Status in firefox package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

  A similar behavior can also be observed in gedit, nautilus and other
  GNOME applications whether they are confined or not (while snapped
  ones seems to underline the issue more)

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


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

[Desktop-packages] [Bug 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

This bug was fixed in the package mate-desktop-environment -
1.26.0+1ubuntu5

---
mate-desktop-environment (1.26.0+1ubuntu5) jammy; urgency=medium

  * Invoke x-terminal-emulator. (LP: #1873750)

 -- Martin Wimpress   Thu, 07 Apr 2022 11:26:51 +0100

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Fix Released
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Fix Released
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator

This bug was fixed in the package ubuntu-mate-settings - 22.04.13

---
ubuntu-mate-settings (22.04.13) jammy; urgency=medium

  * Invoke x-terminal-emulator. (LP: #1873750)

 -- Martin Wimpress   Wed, 06 Apr 2022 17:34:04 +0100

** Changed in: ubuntu-mate-settings (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: mate-desktop-environment (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Custom Application Launcher with Application in Terminal enabled
  should use user-specified terminal emulator

Status in brisk-menu package in Ubuntu:
  Invalid
Status in classicmenu-indicator package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in mate-desktop-environment package in Ubuntu:
  Fix Released
Status in mate-menu package in Ubuntu:
  Invalid
Status in mate-menus package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Fix Released
Status in vala-panel-appmenu package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 20.04 LTS
  2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
  3. Install terminal-based application - Midnight Commander, by `sudo apt-get 
install mc`
  3. Set Tilix as default terminal in `mate-default-applications-properties` or 
programmatically:

    gsettings set org.mate.applications-terminal exec "'tilix'"

  4. Set Tilix as alternative for x-terminal-emulator by update-
  alternatives:

    update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper
    sudo update-alternatives --set x-terminal-emulator 
/usr/bin/tilix.wrapper

  5. Reboot
  6. Add Custom Application Launcher to the MATE Panel:

    Type: Application in Terminal
    Name: mc
    Command: mc

  7. Click the icon of just created Custom Application Launcher

  Expected results:

  * Midnight Commander is opened in the user-defined terminal - in Tilix

  Actual results:

  * Midnight Commander is default terminal - in MATE Terminal

  Notes:
  * This also happens with desktop-files installed by Midnight Commander, it 
opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, 
Dock, + menu, Advanced Mate Menu (`mate-menu` package)
  * What is interesting, the + respects user preferences and uses Tilix
  * Also ++ opens Tilix as expected.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mate-panel 1.24.0-2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Apr 20 10:48:51 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1967198] Re: gnome-initial-setup icon in dock is badly sized

https://launchpad.net/ubuntu/+source/ubuntu-settings/22.04.6

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

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

Title:
  gnome-initial-setup icon in dock is badly sized

Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  I noticed this while testing the beta jammy image (20220329) on arm64,
  but I checked and I see the same issue on amd64 as well. The best way
  I can describe it, is that it looks squished, as if it was sized
  incorrectly. I'll attach a screenshot showing the problem also.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-initial-setup 42.0.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19
  Uname: Linux 5.15.0-1003-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 21:12:45 2022
  ImageMediaBuild: 20220329
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)

** Tags added: dt-302

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

Title:
  [jammy regression] webkit apps do not display content (yelp, epiphany,
  gnome-online-accounts etc)

Status in Gnome DevHelp:
  Invalid
Status in Mesa:
  Unknown
Status in Webkit:
  Unknown
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init

** Tags added: dt-303

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

Title:
  gnome-shell crashed with SIGTRAP from error "Can't create a
  GtkStyleContext without a display connection" in
  gtk_style_context_init

Status in gnome-shell package in Ubuntu:
  Triaged
Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  GNOME Shell isn't meant to use GTK at all, but it's repeatedly
  crashing in GTK since the introduction of GNOME 40.

  https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
  https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844
  https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad
  https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4

  This seems to be a result of Xwayland crashing and gnome-shell then
  trying to recover (and failing). Although gnome-shell shouldn't be
  using GTK, and Wayland sessions shouldn't be dependent on having an
  X11 server (Xwayland) available. Fixing either of those should resolve
  this.

  WORKAROUND:

  sudo apt remove libcanberra-gtk3-module

  TEST CASE:

  1. Log into a Wayland session.
  2. Open a Terminal.
  3. $ xrandr   # Just to ensure Xwayland starts
  4. $ killall Xwayland

  Expected: gnome-shell still responds.
  Observed: gnome-shell freezes or exits.

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 29 15:11:43 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-10-27 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_writer_default()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1967777] Re: xdg-desktop-portal-gnome uses libadwaita & doesn't respect Ubuntu default themes

This bug was fixed in the package libadwaita-1 - 1.1.0-1ubuntu2

---
libadwaita-1 (1.1.0-1ubuntu2) jammy; urgency=medium

  * Depend on gsettings-desktop-schemas, needed for yaru patch

 -- Jeremy Bicha   Wed, 06 Apr 2022 16:03:48 -0400

** Changed in: libadwaita-1 (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  xdg-desktop-portal-gnome uses libadwaita & doesn't respect Ubuntu
  default themes

Status in libadwaita-1 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in libadwaita-1 source package in Jammy:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Fix Released

Bug description:
  xdg-desktop-portal-gnome 42 uses libadwaita. It uses the libadwaita
  style with blue buttons & different grays. It doesn't respect the
  Ubuntu default themes coloring.

  This is the only "app" in the default Ubuntu 22.04 LTS install that
  uses libadwaita. (And there are only 2 or 3 apps in universe that do.)

  The easiest way to handle this is to revert the commits that switched
  xdg-desktop-portal-gnome to libadwaita.

  Note that you'll probably need to log out and log back in after
  installing the update to see the changes.

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


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

[Desktop-packages] [Bug 1967593] Re: kernel modules going missing after reboot

2022-04-07 Thread Łukasz Zemczak

** Tags removed: rls-jj-incoming

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

Title:
  kernel modules going missing after reboot

Status in cloud-initramfs-tools package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  New
Status in linux-lowlatency package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  EDIT: There are no accurate results in the package search, but it is
  for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for
  the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it
  is not kernel specific. It must be a problem with configuration, but
  reinstalling doesnt fix it.

  EDIT2: it turns out this is caused by the cloud-initramfs-copymods
  package mounting over modules locations. Removed it and reinstalled
  kernel modules package (extras didnt seem necessary, but probably
  prudent too).


  This affects several different kernels I've tried in 22.04.

  This post basically sums it up:
  
https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot
  detailed answer: https://unix.stackexchange.com/a/499580/346155

  And this one from upgrading from 20.04 to 22.04:
  
https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade

  Basically, for some reason the kernel modules are being mounted over
  after reboot.

  My image was built on top of a cloud-init image, but removing the recommeded 
package "cloud-initramfs-copymods" that mounts over modules didnt work for me. 
Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules 
did fix my issue for this module. But how many others will not be available?
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   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
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:

  Tags:  jammy uec-images
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago)
  UserGroups: libvirt sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   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
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Dri

[Desktop-packages] [Bug 1967593] Re: kernel modules going missing after reboot

2022-04-07 Thread Matthieu Clemenceau

** Tags added: fr-2225

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

Title:
  kernel modules going missing after reboot

Status in cloud-initramfs-tools package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  New
Status in linux-lowlatency package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  EDIT: There are no accurate results in the package search, but it is
  for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for
  the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it
  is not kernel specific. It must be a problem with configuration, but
  reinstalling doesnt fix it.

  EDIT2: it turns out this is caused by the cloud-initramfs-copymods
  package mounting over modules locations. Removed it and reinstalled
  kernel modules package (extras didnt seem necessary, but probably
  prudent too).


  This affects several different kernels I've tried in 22.04.

  This post basically sums it up:
  
https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot
  detailed answer: https://unix.stackexchange.com/a/499580/346155

  And this one from upgrading from 20.04 to 22.04:
  
https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade

  Basically, for some reason the kernel modules are being mounted over
  after reboot.

  My image was built on top of a cloud-init image, but removing the recommeded 
package "cloud-initramfs-copymods" that mounts over modules didnt work for me. 
Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules 
did fix my issue for this module. But how many others will not be available?
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   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
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:

  Tags:  jammy uec-images
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago)
  UserGroups: libvirt sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   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
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_h

[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

2022-04-07 Thread Matthieu Clemenceau

** Tags added: fr-2226

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  In Progress
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

2022-04-07 Thread Łukasz Zemczak

** Changed in: systemd (Ubuntu)
   Status: Confirmed => In Progress

** Tags removed: rls-jj-incoming

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  In Progress
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1966589] Re: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1`

2022-04-07 Thread Łukasz Zemczak

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  release upgrade fails due to `firefox package pre-installation script
  subprocess returned error exit status 1`

Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date
  27.03.2022)

  The upgrader was unable to connect to the snap store in order to
  install the firefox snap

  The upgrade was performed with GUI - do-release-upgrade -d -m desktop
  -f DistUpgradeViewKDE

  The error "could not install the upgrades" was received.
  I closed the error and then received th dialog box message "upgrade complete 
but there were errors during the upgrade process"

  After rebooting I received an upgrade notification and the Firefox
  snap was installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: LXQt
  Date: Sun Mar 27 13:08:26 2022
  InstallationDate: Installed on 2022-03-27 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kf  950 F pulseaudio
  BuildID: 20220322144853
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: LXQt
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 22.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  IpRoute:
   default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 
   192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 
metric 100
  Package: ubuntu-release-upgrader
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=98.0.2/20220322144853 (In use)
  RunningIncompatibleAddons: False
  Tags:  jammy
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.2
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 1968194] [NEW] Not available as Calendar app in g-c-c

2022-04-07 Thread Francois Thirioux

Public bug reported:

Ubuntu Jammy, GS 42.0, TB 91.8 snap.

I don't see TB in Calendar as available default app.
I remember it should be possible now?

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

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

Title:
  Not available as Calendar app in g-c-c

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Ubuntu Jammy, GS 42.0, TB 91.8 snap.

  I don't see TB in Calendar as available default app.
  I remember it should be possible now?

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


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

[Desktop-packages] [Bug 1968195] [NEW] websocket transport is never enabled

2022-04-07 Thread msaxl

Public bug reported:

freerdp supports an rdp gateway with websocket transport since 2.3.0.

There was however a backport bug that never enabled this feature since
the introduction to disable this feature (by /gt:auto,no-websockets)

the relevant stable push is https://github.com/FreeRDP/FreeRDP/pull/7786

Note that the upstream master branch had never this problem, so that
feature should be tested by many people.

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

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

Title:
  websocket transport is never enabled

Status in freerdp package in Ubuntu:
  New

Bug description:
  freerdp supports an rdp gateway with websocket transport since 2.3.0.

  There was however a backport bug that never enabled this feature since
  the introduction to disable this feature (by /gt:auto,no-websockets)

  the relevant stable push is
  https://github.com/FreeRDP/FreeRDP/pull/7786

  Note that the upstream master branch had never this problem, so that
  feature should be tested by many people.

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


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

[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2022-04-07 Thread Gauthier Jolly

I started 156 instances for both:

 * an impish image with systemd 248.3-1ubuntu8.5
 * a focal image with systemd 245.4-4ubuntu3.16

In both images, I also removed the workaround in
/etc/systemd/system/dbus.service.d
(Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=1) to make sure I was really
testing the fix.

None of the instances shown any provisioning issue (cloud-init was
always done withing 5min). This was the main symptom we were observing
previously with this issue.

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Committed
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Kesc

[Desktop-packages] [Bug 1762133] Re: gvfsd-smb-browse crashed with SIGABRT

2022-04-07 Thread Mike Wood

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

I am still seeing this issue in 4/2022 (as stated; when not using smb
share). Along with a /usr/lib/udisks2/udisksd crash. Attempting to go to
bug #1725476 generates "bug 1725476 cannot be found".It appears the
duplicate bug is #1724609.

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

Title:
  gvfsd-smb-browse crashed with SIGABRT

Status in gvfs package in Ubuntu:
  New

Bug description:
  I was not even using a SMB share when gvfsd-smb-browse crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.36.0-1ubuntu1
  Uname: Linux 4.15.15-041515-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr  7 22:06:05 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.64 
/org/gtk/gvfs/exec_spaw/10
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   _talloc_free () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
   gencache_parse () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
   gencache_get_data_blob () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  Title: gvfsd-smb-browse crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo

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


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

[Desktop-packages] [Bug 1724609] Re: gvfsd-smb-browse crashed with SIGABRT

2022-04-07 Thread Mike Wood

Fyi Still seeing this in Ubuntu 18.04.5 LTS 4/2022 along with a
/usr/lib/udisks2/udisksd crash

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

Title:
  gvfsd-smb-browse crashed with SIGABRT

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  no idea how it crashed. I don't use smb services.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 14:14:33 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  ExecutableTimestamp: 1506994454
  InstallationDate: Installed on 2013-09-03 (1499 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.22 
/org/gtk/gvfs/exec_spaw/4
  ProcCwd: /home/j-lallement
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   _talloc_realloc () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   talloc_asprintf_append () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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


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

[Desktop-packages] [Bug 1908634] Re: [USB-Audio - DAC-X6, playback] Underruns, dropouts or crackling sound

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [USB-Audio - DAC-X6, playback] Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I was playing back from SoundCloud where I pay for Go and use the
  "High Quality" streaming settings.

  I'm also working on a react native app and this issue seems to happen
  after I start the bundle server (react-native start). I can't show you
  the code because I'm selling it.

  I connected my headphones through an FX-Audio DAC-X6, a FiiO K3 Type-C
  USB DAC, and my motherboard and I get the exact same crackling, so
  it's defiantly a software issue.

  As for the actual sounds, the popping sound like a momentary drop in
  all sound, I don't have an oscilloscope but I suspect the pops would
  look like ~15ish milliseconds of 0 volts right in the middle of the
  sound wave. Also these pops are repetitive, like there's a pattern to
  them starting with a big one and then smaller ones at regular
  intervals leading me to think some number isn't getting processed
  properly. Now that I think about it I might have been experiencing
  this bug ever since Ubuntu 19.10 but haven't noticed it up until I got
  these high impedance headphones and now have to turn up my DAC to
  twice the gain. It doesn't sound like static, but more like a single
  clap but slowed down.

  I have already followed a menagerie of solutions (2 most recent ones):

  https://wiki.ubuntu.com/Audio/PositionReporting

  https://itectec.com/ubuntu/ubuntu-annoying-click-popping-sound-on-
  ubuntu-20-04/

  And none of them have made a difference.

  Appended you will find an audio file where I put my headphones on my
  condenser mic and played a 440hz tone in an attempt to record the
  pops. It's alittle quiet, so I'd recommend trying to amplify it. I
  hoped I could use Audacity to visually identify the pops in the actual
  waveform but I wasn't sure what I was looking for.

  I really want this fixed because right now I absolutely can't use my
  headphones, I literally feel each and every pop and it hurts. If you
  have any further questions or want to test on my hardware, please
  email me at dan.ha...@gmail.com. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Dec 17 22:49:22 2020
  InstallationDate: Installed on 2020-12-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DACX6 failed
  Symptom_Card: DAC-X6 - DAC-X6
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - DAC-X6, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V17.12
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 760GM-P34(FX) (MS-7641)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV17.12:bd11/28/2012:svnMSI:pnMS-7641:pvr4.0:rvnMSI:rn760GM-P34(FX)(MS-7641):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7641
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-12-17T22:21:33.927437

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


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

[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2022-04-07 Thread Nick Rosbrook

** Tags removed: verification-needed verification-needed-focal 
verification-needed-impish
** Tags added: verification-done verification-done-focal 
verification-done-impish

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Committed
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[17293

[Desktop-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init

2022-04-07 Thread Heather Ellsworth

If the solution is to remove libcanberra-gtk3-module and since it hasn't
been touched since 2012, do we need to provide it at all?

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

Title:
  gnome-shell crashed with SIGTRAP from error "Can't create a
  GtkStyleContext without a display connection" in
  gtk_style_context_init

Status in gnome-shell package in Ubuntu:
  Triaged
Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  GNOME Shell isn't meant to use GTK at all, but it's repeatedly
  crashing in GTK since the introduction of GNOME 40.

  https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
  https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844
  https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad
  https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4

  This seems to be a result of Xwayland crashing and gnome-shell then
  trying to recover (and failing). Although gnome-shell shouldn't be
  using GTK, and Wayland sessions shouldn't be dependent on having an
  X11 server (Xwayland) available. Fixing either of those should resolve
  this.

  WORKAROUND:

  sudo apt remove libcanberra-gtk3-module

  TEST CASE:

  1. Log into a Wayland session.
  2. Open a Terminal.
  3. $ xrandr   # Just to ensure Xwayland starts
  4. $ killall Xwayland

  Expected: gnome-shell still responds.
  Observed: gnome-shell freezes or exits.

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 29 15:11:43 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-10-27 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_writer_default()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1762133] Re: gvfsd-smb-browse crashed with SIGABRT

2022-04-07 Thread Laurent Bonnaud

** This bug is no longer a duplicate of private bug 1725476

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

Title:
  gvfsd-smb-browse crashed with SIGABRT

Status in gvfs package in Ubuntu:
  New

Bug description:
  I was not even using a SMB share when gvfsd-smb-browse crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.36.0-1ubuntu1
  Uname: Linux 4.15.15-041515-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr  7 22:06:05 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.64 
/org/gtk/gvfs/exec_spaw/10
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   _talloc_free () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
   gencache_parse () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
   gencache_get_data_blob () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  Title: gvfsd-smb-browse crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin plugdev 
sambashare staff sudo

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


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

[Desktop-packages] [Bug 1967885] Re: blanking locks screen although screen lock is disabled

2022-04-07 Thread Jurgen Schellaert

Possibly related to bug #1968208, which I reported today: frozen gnome-
shell after logging in/unlocking.

This new bug would indicate that gnome-shell indeed randomly crashes.
The behaviour is inconsistent, though. Sometimes it does not crash at
all, at other times it does but it does not always cause the desktop to
freeze.

I can add a photo, as your requested, but I wonder whether that would
add anything. The lock screen  is simply the log-in screen that
traditionally comes up when the system is booted.

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

Title:
  blanking locks screen although screen lock is disabled

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I disabled screen lock from Settings > Privacy > Screen. Even so, I am
  forced to log in any time my screen has blanked.

  When I inspect dconf-editor (org.gnome.desktop.lockdown), I see that
  locking is indeed active.

  This looks like a discrepancy between the settings mechanism and
  dconf.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 16:06:06 2022
  InstallationDate: Installed on 2022-03-27 (8 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1968208] Re: gnome-shell frozen after failed suspend; gnome-shell crashed with SIGSEGV in meta_window_get_window_type()

2022-04-07 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1965897, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1968208/+attachment/5577955/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1968208/+attachment/5577957/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1968208/+attachment/5577962/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1968208/+attachment/5577963/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1968208/+attachment/5577964/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968208/+attachment/5577967/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968208/+attachment/5577968/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1965897
   gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) 
from meta_window_actor_queue_destroy() from 
meta_compositor_real_remove_window() from meta_window_unmanage() from 
meta_display_unmanage_windows()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell frozen after failed suspend; gnome-shell crashed with
  SIGSEGV in meta_window_get_window_type()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  As reported two days ago (bug #1967885), my monitor is locked when the
  screen blanks, even though I have turned locking off.

  Today, I notice two further issues.  First, autosuspend fails - the
  system puts on the screen lock instead. Second, after unlocking, I
  find that gnome-shell is unresponsive. when I run Alt + F2 and then r
  to have gnome-shell restarted, apport informs me that gnome-shell has
  (or had) crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  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-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 19:44:10 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-27 (11 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
video
  separator:

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


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

[Desktop-packages] [Bug 1967127] Re: [FFe] update libarchive to 3.6.0

This bug was fixed in the package libarchive - 3.6.0-1ubuntu1

---
libarchive (3.6.0-1ubuntu1) jammy; urgency=medium

  * Sync with Debian. (LP: #1967127)
- Includes upstream fixes for CVE-2021-36976
  * debian/rules: fix broken check for nocheck DEB_BUILD_OPTION
  * SECURITY UPDATE: possible out-of-bounds read
- Cherry-pick CVE-2022-26280.patch to fix zipx_lzma_alone_init()
- CVE-2022-26280

libarchive (3.6.0-1) unstable; urgency=medium

  * New upstream version (Closes: #1007120):
- update the upstream copyright information
- drop some patches that were taken from the upstream source:
  - lzip-large-dict
  - upstream-fix-32bit-size-cast
  - upstream-fixup-file-flags
  - upstream-fixup-symlinks
- add another spelling correction to the typos patch
- update the line numbers in the typos patch
  * Add the year 2022 to my debian/* copyright notice.
  * Reorder the copyright file so that it makes sense.

 -- Jeremy Bicha   Wed, 06 Apr 2022 16:33:16 -0400

** Changed in: libarchive (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-36976

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-26280

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

Title:
  [FFe] update libarchive to 3.6.0

Status in evince package in Ubuntu:
  In Progress
Status in libarchive package in Ubuntu:
  Fix Released

Bug description:
  I request a Feature Freeze Exception to update libarchive from 3.5.2
  to 3.6.0 and build evince with libarchive 3.6.

  This will allow us to drop 2 revert commits we added to evince to build with 
the older libarchive.
  https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b

  Changes
  ---
  https://github.com/libarchive/libarchive/releases/tag/v3.6.0
  https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0

  Other Changes
  -
  1. libarchive: I am cherry-picking a security fix for CVE-2022-26280
  2. libarchive: debian/rules was only running dh_auto_test if 'check' was set 
in DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set. 
That way we run the build tests by default.

  I'm forwarding both those changes to Debian soon.

  Build logs
  --
  
https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra

  https://buildd.debian.org/status/package.php?p=evince

  Testing done
  
  No errors in the install logs

  Evince still works fine to open a variety of PDFs and a .cbz file I have.
  File Roller still works fine to open a variety of compressed file types.

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


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

[Desktop-packages] [Bug 1968209] Re: gjs-console assert failure: free(): invalid pointer

2022-04-07 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1946165, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1968209/+attachment/5577970/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1968209/+attachment/5577972/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1968209/+attachment/5577976/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1968209/+attachment/5577977/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1968209/+attachment/5577978/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968209/+attachment/5577979/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968209/+attachment/5577980/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1946165

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gjs-console assert failure: free(): invalid pointer

Status in gjs package in Ubuntu:
  New

Bug description:
  Perhaps related to first use and customization of the Dash to Panei
  gnome-extension

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.72.0-1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 20:09:29 2022
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2022-03-19 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions
  Signal: 6
  SourcePackage: gjs
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f3b416d6b8c 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f3b416d4764 "free(): invalid pointer") at 
./malloc/malloc.c:5664
   _int_free (av=, p=, have_lock=0) at 
./malloc/malloc.c:4439
   __GI___libc_free (mem=) at ./malloc/malloc.c:3391
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
  Title: gjs-console assert failure: free(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1968213] [NEW] Icon theme reverts to Yaru when entering Appearance settings

2022-04-07 Thread Karol

Public bug reported:

I upgraded to the 22.04 beta last week from 21.10. I use a custom icon
theme. Whenever I enter the Appearance tab in settings the icon theme is
set back to Yaru.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.4-1ubuntu9
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  7 20:47:41 2022
InstallationDate: Installed on 2022-02-02 (64 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
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

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

Title:
  Icon theme reverts to Yaru when entering Appearance settings

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

Bug description:
  I upgraded to the 22.04 beta last week from 21.10. I use a custom icon
  theme. Whenever I enter the Appearance tab in settings the icon theme
  is set back to Yaru.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu9
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 20:47:41 2022
  InstallationDate: Installed on 2022-02-02 (64 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  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/1968213/+subscriptions


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

[Desktop-packages] [Bug 1968213] Re: Icon theme reverts to Yaru when entering Appearance settings

2022-04-07 Thread Karol

If I select a custom accent color (let's say red) and then change the
icon theme through gnome-tweaks, then when enetering the Appearance
settings the theme will change to the appropriate Yaru variant (Yaru-red
in this example)

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

Title:
  Icon theme reverts to Yaru when entering Appearance settings

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

Bug description:
  I upgraded to the 22.04 beta last week from 21.10. I use a custom icon
  theme. Whenever I enter the Appearance tab in settings the icon theme
  is set back to Yaru.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu9
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 20:47:41 2022
  InstallationDate: Installed on 2022-02-02 (64 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  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/1968213/+subscriptions


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

[Desktop-packages] [Bug 1968215] [NEW] [FFe] include a new webextensions portal to be used by firefox and other confined browsers

Public bug reported:

The request is to add the new webextensions portal which is up for
review upstream on https://github.com/flatpak/xdg-desktop-
portal/pull/705

The patch to add to the package would be https://patch-
diff.githubusercontent.com/raw/flatpak/xdg-desktop-portal/pull/705.patch

The code has been written by James from the Desktop Team and reviewed by
Olivier from Desktop and got a security review from Alex.

The regression potential is null since that's a new feature

The code is needed for the firefox messaging protocol to keep working
which is seen as an important feature that would regress in the deb to
snap transition otherwise.

The feature has been discussed on https://forum.snapcraft.io/t/native-
messaging-support-in-strictly-confined-browser-snaps

Olivier is working on getting the firefox side of the changes ready but
those aren't part of this FFe since they will be integrated as the
firefox snap gets updated

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: High
 Status: New

** Changed in: xdg-desktop-portal (Ubuntu)
   Importance: Undecided => High

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

Title:
   [FFe] include a new webextensions portal to be used by firefox and
  other confined browsers

Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  The request is to add the new webextensions portal which is up for
  review upstream on https://github.com/flatpak/xdg-desktop-
  portal/pull/705

  The patch to add to the package would be https://patch-
  diff.githubusercontent.com/raw/flatpak/xdg-desktop-
  portal/pull/705.patch

  The code has been written by James from the Desktop Team and reviewed
  by Olivier from Desktop and got a security review from Alex.

  The regression potential is null since that's a new feature

  The code is needed for the firefox messaging protocol to keep working
  which is seen as an important feature that would regress in the deb to
  snap transition otherwise.

  The feature has been discussed on https://forum.snapcraft.io/t/native-
  messaging-support-in-strictly-confined-browser-snaps

  Olivier is working on getting the firefox side of the changes ready
  but those aren't part of this FFe since they will be integrated as the
  firefox snap gets updated

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


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

[Desktop-packages] [Bug 1968214] [NEW] [FFe] include a new webextensions portal to be used by firefox and other confined browsers

Public bug reported:

The request is to add the new webextensions portal which is up for review 
upstream on
https://github.com/flatpak/xdg-desktop-portal/pull/705

The patch to add to the package would be
https://patch-diff.githubusercontent.com/raw/flatpak/xdg-desktop-portal/pull/705.patch

The code has been written by James from the Desktop Team and reviewed by
Olivier from Desktop and got a security review from Alex.

The regression potential is null since that's a new feature

The code is needed for the firefox messaging protocol to keep working
which is seen as an important feature that would regress in the deb to
snap transition otherwise.

The feature has been discussed on https://forum.snapcraft.io/t/native-
messaging-support-in-strictly-confined-browser-snaps

Olivier is working on getting the firefox side of the changes ready but
those aren't part of this FFe since they will be integrated as the
firefox snap gets updated

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: High
 Status: Invalid

** Description changed:

  The request is to add the new webextensions portal which is up for review 
upstream on
  https://github.com/flatpak/xdg-desktop-portal/pull/705
  
- The patch to add to the package would be 
+ The patch to add to the package would be
  
https://patch-diff.githubusercontent.com/raw/flatpak/xdg-desktop-portal/pull/705.patch
  
  The code has been written by James from the Desktop Team and reviewed by
  Olivier from Desktop and got a security review from Alex.
  
  The regression potential is null since that's a new feature
  
  The code is needed for the firefox messaging protocol to keep working
- which is seen as an important feature
+ which is seen as an important feature that would regress in the deb to
+ snap transition otherwise.
+ 
+ The feature has been discussed on https://forum.snapcraft.io/t/native-
+ messaging-support-in-strictly-confined-browser-snaps
+ 
+ Olivier is working on getting the firefox side of the changes ready but
+ those aren't part of this FFe since they will be integrated as the
+ firefox snap gets updated

** Changed in: xdg-desktop-portal (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- [FFe] include new webextensions portal to be used by firefox
+ [FFe] include a new webextensions portal to be used by firefox and other 
confined browsers

** Changed in: xdg-desktop-portal (Ubuntu)
   Status: New => Invalid

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

Title:
  [FFe] include a new webextensions portal to be used by firefox and
  other confined browsers

Status in xdg-desktop-portal package in Ubuntu:
  Invalid

Bug description:
  The request is to add the new webextensions portal which is up for review 
upstream on
  https://github.com/flatpak/xdg-desktop-portal/pull/705

  The patch to add to the package would be
  
https://patch-diff.githubusercontent.com/raw/flatpak/xdg-desktop-portal/pull/705.patch

  The code has been written by James from the Desktop Team and reviewed
  by Olivier from Desktop and got a security review from Alex.

  The regression potential is null since that's a new feature

  The code is needed for the firefox messaging protocol to keep working
  which is seen as an important feature that would regress in the deb to
  snap transition otherwise.

  The feature has been discussed on https://forum.snapcraft.io/t/native-
  messaging-support-in-strictly-confined-browser-snaps

  Olivier is working on getting the firefox side of the changes ready
  but those aren't part of this FFe since they will be integrated as the
  firefox snap gets updated

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


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

[Desktop-packages] [Bug 1968216] Re: gnome-session-binary crashed with SIGSEGV in g_signal_emit_valist()

2022-04-07 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1945430, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1968216/+attachment/5577985/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1968216/+attachment/5577987/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1968216/+attachment/5577990/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1968216/+attachment/5577991/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1968216/+attachment/5577992/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968216/+attachment/5577993/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968216/+attachment/5577994/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1945430

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-session-binary crashed with SIGSEGV in g_signal_emit_valist()

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Apport generated this crash report after I logged in to 22.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-session-bin 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Apr  7 15:02:44 2022
  ExecutablePath: /usr/libexec/gnome-session-binary
  InstallationDate: Installed on 2022-04-05 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  ProcCmdline: /usr/libexec/gnome-session-binary --autostart 
/usr/share/gdm/greeter/autostart
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f96fea70483 : mov
(%rax),%rdi
   PC (0x7f96fea70483) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_by_name () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
   ?? ()
   g_hash_table_find () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-session-binary crashed with SIGSEGV in g_signal_emit_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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


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

[Desktop-packages] [Bug 1958376] Re: [SRU] Backport Gnome Shell high-contrast dock fix

2022-04-07 Thread Treviño

** Tags added: rls-ff-incoming

** Also affects: yaru-theme (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [SRU] Backport Gnome Shell high-contrast dock fix

Status in yaru-theme package in Ubuntu:
  Fix Released
Status in yaru-theme source package in Focal:
  New

Bug description:
  [Impact]

   * When switching to High Contrast on Ubuntu Impish, the Ubuntu Dock detaches 
from the margin, changes look and expands.
   
   * Backport the patches to supported versions of Ubuntu will fix the user 
experience, and will polish the desktop look and feel.

  [Test Plan]

   * Open "Settings" app;
   
   * Go to "Accessibility" page;
   
   * Enable "High Contrast" option with the switch;
   
   * See dock problem;
   
   * Related launchpad bug: 
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1946042

  [Other Info]
   
   * This issue affects all supported versions of Ubuntu:
   
 - The original patch has been pushed here: 
https://github.com/ubuntu/yaru/pull/3089
 - A patch for "focal" has been pushed here: 
https://github.com/ubuntu/yaru/pull/3223
 - A patch for "impish" has been pushed here: 
https://github.com/ubuntu/yaru/pull/3224
 
   * The problem was that the High Contrast variant of Yaru wasn't import dock 
styling.

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


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

[Desktop-packages] [Bug 1958375] Re: [SRU] Backport GTK transparent tab fixes

2022-04-07 Thread Treviño

** Tags added: rls-ff-incoming

** Also affects: yaru-theme (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [SRU] Backport GTK transparent tab fixes

Status in yaru-theme package in Ubuntu:
  Fix Released
Status in yaru-theme source package in Focal:
  New

Bug description:
  [Impact]

   * When using transparent tab background in two apps (guake and 
gnome-terminal), it results a broken tabbar which can be totally unusable.
   
   * Backport the patches to supported versions of Ubuntu will fix the user 
experience in those apps, and will polish the desktop look and feel.

  [Test Plan]

   * Two apps got problems using transparent tabbar background, but the bug is 
simpler reproducible using "gnome-terminal":
   
 - Using Ubuntu 20.04, open "gnome-terminal";
 
 - Open app settings in hamburger menu;
 
 - Select your current profile in left sidebar;
 
 - Go to "Colors" tab;
 
 - Check "Use transparent background" checkbox, and select a transparent 
background using the related slider;
 
 - Close setting window;
 
 - Open a new tab using the button in the headerbar;
 
 - You should see a black background tabbar;
 
 - See related issue in Yaru repository: 
https://github.com/ubuntu/yaru/issues/2481
 
   * To reproduce the "guake" issue, you can see the related issue: 
https://github.com/ubuntu/yaru/issues/2149
   
   * The "guake" issue is more problematic because the full tabbar is 
transparent, so you can't read tabbar text.

  [Where problems could occur]

   * All fixes strictly target those apps and no other, to avoid any
  side effect.

  [Other Info]
   
   * The "gnome-terminal" issue is only related to Ubuntu 20.04, and a patch 
has been pushed to "ubuntu/focal" branch of the Yaru repository. The related PR 
is here: https://github.com/ubuntu/yaru/pull/2979
   
   * The "guake" issue affect all versions of Ubuntu. A patch has been pushed 
to "ubuntu/focal", "ubuntu/impish" and "master" branches of the Yaru 
repository. The related PR are here:
   
 - For the "master" branch: https://github.com/ubuntu/yaru/pull/3218
 - For the "ubuntu/impish" branch: https://github.com/ubuntu/yaru/pull/3219
 - For the "ubuntu/focal" branch: https://github.com/ubuntu/yaru/pull/3220
 
   * The patch add a fixed background to the tabbar of both apps.

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


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

[Desktop-packages] [Bug 1968213] Re: Icon theme reverts to Yaru when entering Appearance settings

2022-04-07 Thread Paul White

I can confirm this. As comment #2 but worded differently:

Set icon theme to Adwaita (in Tweaks)
Note a specific Adwaita icon on the Dock
Open Settings | Appearance
Icon will immediately change to the relevant Yaru version.


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

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

Title:
  Icon theme reverts to Yaru when entering Appearance settings

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

Bug description:
  I upgraded to the 22.04 beta last week from 21.10. I use a custom icon
  theme. Whenever I enter the Appearance tab in settings the icon theme
  is set back to Yaru.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu9
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 20:47:41 2022
  InstallationDate: Installed on 2022-02-02 (64 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  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/1968213/+subscriptions


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

[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/418883

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  In Progress
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 269441] Re: Trash always full

Caja did not exist in 2008.

** No longer affects: ubuntu-mate

** Changed in: caja (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/269441

Title:
  Trash always full

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

Bug description:
  I've seen other users having problems with that the trash appears
  empty even though it isn't. I have the opposite problem: my trash icon
  on the desktop always appears full, even if empty.

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


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

[Desktop-packages] [Bug 1930312] Re: USB disks and SD cards mount for wrong user

** No longer affects: ubuntu-mate

** Changed in: caja (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  USB disks and SD cards mount for wrong user

Status in caja package in Ubuntu:
  Invalid
Status in gvfs package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  I have MATE 20.04 LTS installed on a laptop with 4 users. Plugging in SD 
cards and USB sticks works perfectly, unless there is someone else logged in on 
the machine.
  eg:
  1- user A logs in, then walks away and screen locks
  2- user B switches to the login screen and logs in as user B
  3- user B plugs in a USB stick, but it doesn't mount for user B
  4- (hidden from sight) user A gets an "authentication is required to mount... 
/dev/sdb1" error and the window is asking for admin password
  - details of this are:
  polkit.subject-pid: 102318
  polkit.caller-pid: 806
  Action: org.freedesktop.udisks2.filesystem-mount-other-seat
  Vendor: The Udisks Project

  user B has no indication on why it didn't mount. If they click on the
  USB stick in the Caja side bar, they get an "Unable to mount USB Disk
  - an operation is already pending"

  So it seems that automount is trying to show the USB stick to the
  inactive user A, totally blocking user B. (user B doesn't even get the
  chance to enter an admin password to override)

  the only solution is basically to "switch account", log in as user A and log 
them out.
  (this clearly doesn't work if user B doesn't know their password!)

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


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

[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking

2022-04-07 Thread Olivier Tilloy

Crash report for gnome-session-binary:
https://errors.ubuntu.com/oops/d5e2d4b2-b62f-11ec-a2f0-fa163ef35206

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

Title:
  Blanked screen doesn't wake up after locking

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

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


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

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

2022-04-07 Thread Norbert

** Tags added: jammy

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

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

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

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

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

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

  ---

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

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

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


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

[Desktop-packages] [Bug 1968235] [NEW] Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz

2022-04-07 Thread iMac

Public bug reported:

I recently started using a Cable-Matters-201355 with my XPS 9380 (8th
Gen TB3).  The dock supports dual 4K DP @ 60Hz via thunderbolt with PD
input. (HBR3 compliant USB-C Dock (DSC/DP1.4 support) that uses all 4
high speed lanes to get dual 60Hz)

Both displays boot mirrored when powered up (Dell Logo, Grub, Kernel
output) however go blank just as wayland starts up.

Unplugging one of them allows the other to appear at 3840x2160@60Hz,
after which I have to execute the following process to get both up and
running.

1) Change the refresh rate of the active display to 30Hz, apply in Screen 
Display settings dialog
2) Plug the 2nd monitor in; At this point both appear in Screen Display dialog 
@60Hz, but the 2nd remains blank
3) Change both to 30Hz, apply; At this point the 2nd screen turns on
4) Change both to 60Hz, apply; At this point both are working at 60Hz, my 
desired end state

Inspection of edid seems fine (below), other than the DisplaySize
showing 27" instead of 32". Monitors are identical.

Previously, I might be able to script my steps above using xrandr, but
that seems to no longer be the case with 21.10 and wayland. I seem to be
limited to the Screen Display dialog.

Since I can fix by simply re-applying the settings, it seems like a bug
on startup.  If I could find a CLI option to allow me to script this
somehow, that workaround would be just fine for myself.

Lid open/closed, power via the 201344 or direct via other TB-PD port has
no impact.

Here's hoping for a bugfix in 22.04 or at least a way to script the
display configuration.

$ cat /sys/class/drm/card0-DP-4/edid | parse-edid
Checksum Correct

Section "Monitor"
 Identifier "LG HDR 4K"
 ModelName "LG HDR 4K"
 VendorName "GSM"
 # Monitor Manufactured week 5 of 2021
 # EDID version 1.4
 # Digital Display
 DisplaySize 600 340
 Gamma 2.20
 Option "DPMS" "true"
 Horizsync 30-135
 VertRefresh 56-61
 # Maximum pixel clock is 560MHz
 #Not giving standard mode: 1152x864, 60Hz
 #Not giving standard mode: 1280x1024, 60Hz
 #Not giving standard mode: 1280x720, 60Hz
 #Not giving standard mode: 1600x900, 60Hz
 #Not giving standard mode: 1920x1080, 60Hz
 #Not giving standard mode: 1280x800, 60Hz

 #Extension block found. Parsing...
 Modeline   "Mode 6" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync 
+vsync
 Modeline   "Mode 0" 519.38 3840 3864 3880 3896 2160 2214 2219  +hsync 
-vsync
 Modeline   "Mode 1" 266.64 3840 3848 3992 4000 2160 2214 2219  +hsync 
-vsync
 Modeline   "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync 
+vsync
 Modeline   "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync 
+vsync
 Modeline   "Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
 Modeline   "Mode 5" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
 Modeline   "Mode 7" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync 
-vsync
 Option "PreferredMode" "Mode 6"
EndSection

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

** Description changed:

  I recently started using a Cable-Matters-201355 with my XPS 9380 (8th
  Gen TB3).  The dock supports dual 4K DP @ 60Hz via thunderbolt with PD
  input. (HBR3 compliant USB-C Dock (DSC/DP1.4 support) that uses all 4
  high speed lanes to get dual 60Hz)
  
  Both displays boot mirrored when powered up (Dell Logo, Grub, Kernel
  output) however go blank just as wayland starts up.
  
  Unplugging one of them allows the other to appear at 3840x2160@60Hz,
  after which I have to execute the following process to get both up and
  running.
  
  1) Change the refresh rate of the active display to 30Hz, apply in Screen 
Display settings dialog
  2) Plug the 2nd monitor in; At this point both appear in Screen Display 
dialog @60Hz, but the 2nd remains blank
  3) Change both to 30Hz, apply; At this point the 2nd screen turns on
  4) Change both to 60Hz, apply; At this point both are working at 60Hz, my 
desired end state
  
  Inspection of edid seems fine (below), other than the DisplaySize
- showing 27" instead of 32"
+ showing 27" instead of 32". Monitors are identical.
  
  Previously, I might be able to script my steps above using xrandr, but
  that seems to no longer be the case with 21.10 and wayland. I seem to be
  limited to the Screen Display dialog.
  
  Since I can fix by simply re-applying the settings, it seems like a bug
  on startup.  If I could find a CLI option to allow me to script this
  somehow, that workaround would be just fine for myself.
  
  Lid open/closed, power via the 201344 or direct via other TB-PD port has
  no impact.
  
  Here's hoping for a bugfix in 22.04 or at least a way to script the
  display configuration.
  
- 
  $ cat /sys/class/drm/card0-DP-4/edid | parse-edid
  Checksum Correct
  
  Section "Monitor"
-   Identifier "LG HDR 4K"
-   ModelName "LG HDR 4K"
-   VendorName "GSM"
-   # Monitor Manufactured week 5 of 2021
-   # EDID version 1.4
-

Re: [Desktop-packages] [Bug 1960860] Re: Ubuntu 22.04:cheese not showing webcam output

2022-04-07 Thread Stephen Waines

Hello

It's all good you can close this ticket.

On April 5, 2022 6:25:52 a.m. Sebastien Bacher <1960...@bugs.launchpad.net> 
wrote:

> Thank you for your bug report, do you have the same issue if you start
>
> $ GST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink
>
> ?
>
> ** Changed in: cheese (Ubuntu)
>   Importance: Undecided => Low
>
> ** Changed in: cheese (Ubuntu)
>   Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1960860
>
> Title:
>  Ubuntu 22.04:cheese not showing webcam output
>
> Status in cheese package in Ubuntu:
>  Incomplete
>
> Bug description:
>  ubuntu 22.04 latest updates.
>  cheese not detecting video output of webcam
>  this worked in 20.04 with this laptop.
>
>  apport-collect to follow
>  ---
>  ProblemType: Bug
>  ApportVersion: 2.20.11-0ubuntu76
>  Architecture: amd64
>  CasperMD5CheckResult: unknown
>  CurrentDesktop: ubuntu:GNOME
>  DistroRelease: Ubuntu 22.04
>  InstallationDate: Installed on 2021-12-04 (72 days ago)
>  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
>  MachineType: Dell Inc. Inspiron 5765
>  Package: cheese 41.1-1
>  PackageArchitecture: amd64
>  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
>  RelatedPackageVersions:
>   cheese41.1-1
>   cheese-common 41.1-1
>  Tags: third-party-packages jammy wayland-session gstreamer-ok
>  Uname: Linux 5.15.0-18-generic x86_64
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>  _MarkForUpload: True
>  dmi.bios.date: 07/17/2017
>  dmi.bios.release: 5.3
>  dmi.bios.vendor: Dell Inc.
>  dmi.bios.version: 1.1.1
>  dmi.board.name: 0DM01M
>  dmi.board.vendor: Dell Inc.
>  dmi.board.version: A00
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Dell Inc.
>  dmi.chassis.version: 1.1.1
>  dmi.modalias: 
>  
> dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A:
>  dmi.product.family: Inspiron
>  dmi.product.name: Inspiron 5765
>  dmi.product.sku: 076A
>  dmi.product.version: 1.1.1
>  dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1960860/+subscriptions

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

Title:
  Ubuntu 22.04:cheese not showing webcam output

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 22.04 latest updates.
  cheese not detecting video output of webcam
  this worked in 20.04 with this laptop.

  apport-collect to follow
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-12-04 (72 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 5765
  Package: cheese 41.1-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  RelatedPackageVersions:
   cheese41.1-1
   cheese-common 41.1-1
  Tags: third-party-packages jammy wayland-session gstreamer-ok
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/17/2017
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.name: 0DM01M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku076A:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5765
  dmi.product.sku: 076A
  dmi.product.version: 1.1.1
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK

** No longer affects: ubuntu-mate

** Changed in: mate-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  1366x768 screen resolution broken, all other resolutions OK

Status in libdrm package in Ubuntu:
  Confirmed
Status in mate-control-center package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use
  a resolution of 1366x768. Screenshot attached. I am using an Asus
  vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD.

  I found someone in reddit reporting the same problem:
  
https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/

  All other screen resolutions OK.

  
  Many thanks

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


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

[Desktop-packages] [Bug 1914311] Re: Random sound and volume outputs when multiple audio hardware is enabled

** No longer affects: ubuntu-mate

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

** Changed in: mate-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  Random sound and volume outputs when multiple audio hardware is
  enabled

Status in mate-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is an intermittant problem that I have been having:

  When using a laptop with an analog soundcard that is not plugged but
  has a hdmi cable plugged into that same laptop's hdmi port, it
  sometimes(once every 5 times maybe?) happen that MATE remembers to
  default to hdmi output audio hardware as it was lastly used at last
  session shutdown. The rest of the time, MATE defaults back to using
  the analog audio output as default hardware.

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


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

[Desktop-packages] [Bug 1855770] Re: Unable to disable ssh component of gnome-keyring

** No longer affects: ubuntu-mate

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

Title:
  Unable to disable ssh component of gnome-keyring

Status in gnome-keyring package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Under previous versions of Ubuntu MATE (18.04 in particular), it was
  possible to disable the ssh component of gnome-keyring-daemon either
  by a) unchecking a box in Startup Applications, or b) editing
  ~/.config/autostart/gnome-keyring-ssh.desktop to include "X-MATE-
  Autostart-enabled=false". However, in 19.10 (and possibly before),
  disabling this component seems to be a no-op. This means that I can't
  easily use a gpg smartcard for ssh keys.

  To replicate:
* Disable gnome-keyring-ssh, either by unchecking the box in Startup 
Applications or by editing the .desktop file directly.
* Log out and in again.
* At a command prompt, run "echo $SSH_AUTH_SOCK".

  Expected behavior: get ssh-agent or gnupg-agent socket info.

  Actual behavior: get "/run/user/1000/keyring/ssh"

  I can see from `ps aux` that gnome-keyring-daemon is not having its
  components started separately, but rather just launched with
  `/usr/bin/gnome-keyring-daemon --daemonize --login`.

  I see on the release notes "Fixed a gnome-keyring timeout in mate-
  session-manager" -- is it possible that now gnome-keyring-daemon is
  being started incorrectly?

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


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

[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

2022-04-07 Thread Matthew Ruffell

Hi Jack,

I booted a Fedora 36 Beta live image like you suggested, and cheese
works fine there on my machine.

Their cheese includes the above patch. I had a look around, it has a
5.17 kernel, and gstreamer 1.20.

Ubuntu has gstreamer 1.20.1, and when I booted my machine into a 5.17
kernel, I found that the issue still persists. So it doesn't appear to
be a kernel issue.

Will have to try and keep narrowing it down.

Matthew

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

Title:
  cheese display corrupted under  Ubuntu 22.04

Status in cheese package in Ubuntu:
  In Progress
Status in cheese source package in Jammy:
  In Progress

Bug description:
  The cheese application produces a corrupted display under Ubuntu 22.04
  with a Logitech C525 webcam. When started from the command line,
  cheese produces repeated warnings of the form...

  (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
  There may be a timestamping problem, or this computer is too slow.

  Adding /etc/modprobe.d/uvcvideo.conf

  with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
  is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
  Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
  Wayland and X11 displays with the Nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  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-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 05:15:35 2022
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cheese 41.1-1build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  Tags: wayland-session third-party-packages jammy gstreamer-error
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte

[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password

2022-04-07 Thread Jeff Burdges

I've still not tried other kernels, in part because ubuntu keeps pushing
out new OEM kernels, so I give them all a try, but the same basic
problem persist, either gnome-shell gives only a black screen, or else
the whole system hangs on the purple screen.

I've far more diverse crashes with the latest kernels and the bolt
upgrade:
https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem 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: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  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

[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password

2022-04-07 Thread Jeff Burdges

Another purple screen lockup.  It's now also more common the system runs
how while closed.

** Attachment added: "purple_screen_lockup-8_april.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5578017/+files/purple_screen_lockup-8_april.txt

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem 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: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  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-n

[Desktop-packages] [Bug 1908168] Re: Multimedia keys rendered useless if changing sound hardware while playing video

** No longer affects: ubuntu-mate

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

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

** Changed in: mate-media (Ubuntu)
   Status: New => Invalid

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

Title:
  Multimedia keys rendered useless if changing sound hardware while
  playing video

Status in mate-media package in Ubuntu:
  Invalid
Status in mate-settings-daemon package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  While on a system that has (amonsgt several other) an analog and hdmi
  hardware sound output option available, if I play/pause(*) a video in
  Firefox and then I change the sound hardware output, the volume
  control buttons on my keyboard stop responding.

  Using 20.04.1-latest.

  (*)=case #2: change the sound hardware profile while the video is
  playing, don't pause it.

  <3

  PS: Those multiple audio hardware profiles are overall VERY
  annoying/intrusive from a user perspective...

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


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

[Desktop-packages] [Bug 1406538] Re: Screenshot contains selected area highlight

** Changed in: mate-utils (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Screenshot contains selected area highlight

Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in mate-utils package in Ubuntu:
  Fix Released

Bug description:
  mate-utils_1.8.1-0+rebecca_amd64
  If i choose "select area to grab" i almost constantly get an annoying green 
overlay which is what i just used to highlight the area that i wanted to grab.
  See attached example.
  I'm using Mint MATE x64 17.1, software compositing window manager enabled, 
compiz disabled, VGA AMD radeon 6370M, drivers "xserver-xorg-video-ati" 
7.3.0-1-ubuntu3.1, kernel 3.13.0-37-generic x86_64. 
  I remember this happening since mint 13 or so.

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


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

[Desktop-packages] [Bug 1955505] Re: Wrong context menu font is displayed when using vte 0.66.2-1

** Changed in: vte2.91 (Ubuntu)
   Status: New => Invalid

** Changed in: mate-terminal (Ubuntu)
   Status: New => Triaged

** Changed in: mate-terminal (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mate-terminal (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

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

Title:
  Wrong context menu font is displayed when using vte 0.66.2-1

Status in MATE Desktop:
  Unknown
Status in mate-terminal package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Invalid

Bug description:
  Expected behaviour: Font should display as expected.

  Actual behaviour: A monospace font is displayed instead.

  Steps to reproduce the behaviour:

  1. Install Ubuntu MATE 22.04 LTS
  2. Launch mate-terminal
  3. Do right mouse click to get context menu

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mate-terminal 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Dec 21 23:49:21 2021
  InstallationDate: Installed on 2021-12-21 (0 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211221)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1955505/+subscriptions


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

[Desktop-packages] [Bug 1920985] Re: Orca no longer able to review MATE-Terminal output

** No longer affects: ubuntu-mate

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

** Changed in: mate-terminal (Ubuntu)
   Status: Fix Committed => Invalid

** Changed in: orca (Ubuntu)
   Status: New => Fix Released

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

Title:
  Orca no longer able to review MATE-Terminal output

Status in mate-terminal package in Ubuntu:
  Invalid
Status in orca package in Ubuntu:
  Fix Released

Bug description:
  To reproduce, launch Ubuntu 21.04 Daily, launch the screen reader,
  open a Terminal, and press CAPSLOCK+I to read the current line.

  Expected behavior: Orca would read the line with the prompt where the
  cursor is.

  Actual: Orca reads the menu bar. Using CAPSLOCK+O to move down a line,
  Orca says "Tab list", but further presses of the same key do not yield
  any more speech.

  In 20.10, this works as expected, and I can review the full window
  contents from down at the prompt up to the menu bar, line by line.

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


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

[Desktop-packages] [Bug 1955827] Re: Firefox without 'TitleBar' alters the look of MATE buttons

** No longer affects: ubuntu-mate

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

Title:
  Firefox without 'TitleBar' alters the look of MATE buttons

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I was testing Ubuntu MATE 20.04, and when I was configuring Firefox [95.0.1] 
I noticed that when I customized the toolbar and left it without 'Title Bar' 
the window buttons were cut off.
  I thought it might be a Firefox theme issue but when I changed the theme the 
problem persisted.

  https://subirimagenes.s3.eu-
  central-1.wasabisys.com/subirimagenes/2kYiAJh1dw.png

  
https://subirimagenes.s3.eu-central-1.wasabisys.com/subirimagenes/uJZed9mBAC.png
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-mate   2046 F pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-470-server/libnvidia-gl-470-server_470.57.02-0ubuntu0.20.04.3_amd64.deb
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  Channel: Unavailable
  CurrentDesktop: MATE
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IpRoute:
   default via 192.168.1.1 dev wlp7s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp7s0 scope link metric 1000 
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.3 metric 600
  LiveMediaBuild: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: firefox 91.0+build2-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile0PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntumate.js
   prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=91.0/20210804193234 (In use)
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.11.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/04/2013
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0VRTT1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/04/2013:br1.1:efr1.1:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn0VRTT1:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3420
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-mate   2046 F pulseaudio
  BuildID: 20210804193234
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-470-server/libnvidia-gl-470-server_470.57.02-0ubuntu0.20.04.3_amd64.deb
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  Channel: Unavailable
  CurrentDesktop: MATE
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:3

[Desktop-packages] [Bug 1950094] Re: libreoffice base zone liste choix impossible

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

** No longer affects: ubuntu-mate

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

Title:
  libreoffice base zone liste choix impossible

Status in libreoffice package in Ubuntu:
  New

Bug description:

  Bonjour,

  Ce phénomène existait déjà sous UbuntuMate 20.04. J'ai donc chargé
  UbuntuMate 21.10 afin de voir si une modification avait été apporté à
  un éventuel bogue que je vous soumets.

  Le souci est avec la zone de liste dans LibreOffice Base avec la macro
  ci-dessous sur Événement "A réception du focus".

  Sub ActualiserListe(oEv as Object)
  oEv.Source.Model.Refresh
  End Sub

  pour mettre à jour la zone de liste après modification d'un élément.

  La mise à jour fonctionne bien mais je ne peux pas choisir une
  nouvelle entrée dans la liste. Alors que si je choisis un autre
  événement, comme "souris déplacée alors qu'une touche est pressée"
  beaucoup moins pratique, je ne rencontre pas ce problème.

  Après plusieurs recherches sur le forum OpenOffice il s'avère que la
  fonction marche bien mais que le problème pourrait venir de
  l'environnement Ubuntu.

  Sauriez-vous m'aider pour débloquer ma situation ?

  Dommage que je ne puisse pas joindre mon fichier pour des essais sur
  vos propres machines ce serait plus "parlant".

  Merci.
  Éric

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


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

[Desktop-packages] [Bug 1943813] Re: Problem with bluetooth keyboard: not usable in MATE

** No longer affects: ubuntu-mate

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

Title:
  Problem with bluetooth keyboard: not usable in MATE

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a bluetooth keyboard that I use regularly with other devices. The 
keyboard is Jelly Comb Case with Italian Keyboard for Samsung Galaxy Tab S6 
Lite 10.4 ", Removable Backlit Keyboard in 7 Colors, Italian QWERTY for Sam If 
I try to use it with Ubuntu it only works with the LIVE version. When I install 
Ubuntu it stops working, after updates.
  I have tried with various Ubuntu Mate and also the impish version of Ubuntu 
Mate but, using the same notebook, the computer cannot use it (LIVE yes, 
installed no).

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


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

[Desktop-packages] [Bug 1942797] Re: 21.04 - Printer uncooperative (And incohesive) behavior after PWR ON+OFF+ON

** No longer affects: ubuntu-mate

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

Title:
  21.04 - Printer uncooperative (And incohesive) behavior after PWR
  ON+OFF+ON

Status in cups package in Ubuntu:
  New

Bug description:
  On a clone desktop running 21.04-latest which has the following LAN
  printer connected to it:

  $ lpstat -p130 ↵
  printer _xeroxofficetq1_ is idle.  enabled since Mon 06 Sep 2021 01:33:46 PM
  printer C405 is idle.  enabled since Mon 06 Sep 2021 01:33:46 PM
  printer Xerox-CommonXCPT is idle.  enabled since Wed 21 Jul 2021 09:58:10 AM
  $

  If/when my system is up and I power off the printer, leave it off for
  a few hours, replug the printer back, wait for it to boot and then
  print using that same system's firefox, it will not work.

  But if I open Libre Office Writer and print: then it shall print.

  Immediately after, going back to the firefox window and re-printing
  what has originally failed now prints too!

  Here is what /var/log/cups/ had to say (This happened around 5 minutes
  ago):

  $ cat access_log
  localhost - - [06/Sep/2021:00:00:01 -0400] "POST / HTTP/1.1" 200 349 
Create-Printer-Subscriptions successful-ok
  localhost - - [06/Sep/2021:00:00:01 -0400] "POST / HTTP/1.1" 200 176 
Create-Printer-Subscriptions successful-ok
  localhost - - [06/Sep/2021:10:22:53 -0400] "POST / HTTP/1.1" 401 186 
Renew-Subscription successful-ok
  localhost - dd [06/Sep/2021:10:22:53 -0400] "POST / HTTP/1.1" 200 186 
Renew-Subscription successful-ok
  localhost - - [06/Sep/2021:13:29:16 -0400] "POST /printers/C405 HTTP/1.1" 200 
405871 Print-Job successful-ok
  localhost - - [06/Sep/2021:13:29:19 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 442 Create-Job successful-ok
  localhost - - [06/Sep/2021:13:29:19 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 466895 Send-Document successful-ok
  localhost - - [06/Sep/2021:13:31:37 -0400] "POST /printers/C405 HTTP/1.1" 200 
405871 Print-Job successful-ok
  localhost - - [06/Sep/2021:13:31:40 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 442 Create-Job successful-ok
  localhost - - [06/Sep/2021:13:31:40 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 466823 Send-Document successful-ok
  localhost - - [06/Sep/2021:13:33:19 -0400] "POST /printers/C405 HTTP/1.1" 200 
190 Create-Job successful-ok
  localhost - - [06/Sep/2021:13:33:19 -0400] "POST /printers/C405 HTTP/1.1" 200 
1480 Send-Document successful-ok
  localhost - - [06/Sep/2021:13:33:22 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 396 Create-Job successful-ok
  localhost - - [06/Sep/2021:13:33:22 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 17334 Send-Document successful-ok
  localhost - - [06/Sep/2021:13:33:43 -0400] "POST /printers/C405 HTTP/1.1" 200 
479195 Print-Job successful-ok
  localhost - - [06/Sep/2021:13:33:46 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 442 Create-Job successful-ok
  localhost - - [06/Sep/2021:13:33:46 -0400] "POST /printers/_xeroxofficetq1_ 
HTTP/1.1" 200 468503 Send-Document successful-ok
  $ cat page_log
  C405 dd 1115 [06/Sep/2021:13:29:19 -0400] total 0 - localhost Centre de 
retours en ligne na_letter_8.5x11in_borderless -
  _xeroxofficetq1_ lp 1116 [06/Sep/2021:13:29:38 -0400] total 0 - localhost 
PrtDrv-Rl0gMg - -
  C405 dd 1117 [06/Sep/2021:13:31:40 -0400] total 0 - localhost Centre de 
retours en ligne na_letter_8.5x11in_borderless -
  _xeroxofficetq1_ lp 1118 [06/Sep/2021:13:31:43 -0400] total 0 - localhost 
PrtDrv-Jtjdjo - -
  C405 dd 1119 [06/Sep/2021:13:33:22 -0400] total 0 - localhost Untitled 1 - -
  _xeroxofficetq1_ lp 1120 [06/Sep/2021:13:33:22 -0400] total 0 - localhost 
PrtDrv-RwY6Hm - -
  C405 dd 1121 [06/Sep/2021:13:33:46 -0400] total 0 - localhost Centre de 
retours en ligne na_letter_8.5x11in_borderless -
  _xeroxofficetq1_ lp 1122 [06/Sep/2021:13:33:46 -0400] total 0 - localhost 
PrtDrv-sH8aT0 - -
  $ date
  Mon 06 Sep 2021 01:38:54 PM EDT
  $

  Rewinding back to the previous LOG, THIS is the entry that never went through 
and gave my printer an error:
  _xeroxofficetq1_ lp 1116 [06/Sep/2021:13:29:38 -0400] total 0 - localhost 
PrtDrv-Rl0gMg - -
  C405 dd 1117 [06/Sep/2021:13:31:40 -0400] total 0 - localhost Centre de 
retours en ligne na_letter_8.5x11in_borderless -

  While this is the blank print test I did off Writer which worked:
  _xeroxofficetq1_ lp 1118 [06/Sep/2021:13:31:43 -0400] total 0 - localhost 
PrtDrv-Jtjdjo - -
  C405 dd 1119 [06/Sep/2021:13:33:22 -0400] total 0 - localhost Untitled 1 - -

  While finally having retried printing the original document and... it worked!
  _xeroxofficetq1_ lp 1120 [06/Sep/2021:13:33:22 -0400] total 0 - localhost 
PrtDrv-RwY6Hm - -
  C405 dd 1121 [06/Sep/2021:13:33:46 -0400] total 0 - localhost Centre de 
retours en ligne na_letter_8.5x11in_bo

[Desktop-packages] [Bug 1932005] Re: nm-applet not showing in system tray

** No longer affects: ubuntu-mate

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

Title:
  nm-applet not showing in system tray

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

Bug description:
  Hello all,

  I noticed this morning that the network options (i am not sure if it
  suppose to be nm-applet) is no longer showing in system tray and for a
  while now that KDE Connect indicator is not showing in the system
  tray.

  
  I am currently Ubuntu Mate 20.04 on a raspberry PI400  uname -a
  Linux pi400 5.4.0-1036-raspi #39-Ubuntu SMP PREEMPT Wed May 12 17:37:51 UTC 
2021 aarch64 aarch64 aarch64 GNU/Linux

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

  apt policy network-manager
  network-manager:
Installed: 1.22.10-1ubuntu2.2
Candidate: 1.22.10-1ubuntu2.2
Version table:
   *** 1.22.10-1ubuntu2.2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   1.22.10-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

  Does anyone else have a similar issue?

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


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

[Desktop-packages] [Bug 1937083] Re: [21.04] Funky new printer (Netowkr printer autofind)

** No longer affects: ubuntu-mate

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

Title:
  [21.04] Funky new printer (Netowkr printer autofind)

Status in cups package in Ubuntu:
  New

Bug description:
  Using 21.04-latest on my main desktop, I am using a Xerox Versalink
  C405 via IPv4 and it always worked pretty good.

  Boring pre-ambule:
  I have been running this system for at least 90+ days and yesterday I had the 
black cartridge being switched for a new one and ever since it doesn't work. 
(But it still works from a windoze machine).

  Situation:
  After being unable to print from Linux my first reaction was to reinstall the 
printer. I have therefore went under MATE menu -> printers -> add -> Network 
Printer -> Find Network printer -> 

  Question #1: is it me or in previous UM versions after clicking on
  "finder network printer" after a couple of seconds it automatically
  found and configured it? Actually, when installing 21.04 it had
  automatically found and configured my Xerox printer..

  Question #2: Since nothing is auto-discovered after 2+ minutes of
  waiting in the New printer wizard (Find network printer), I have
  manually forced the printer's IP into the Host text field and then
  pressed on FIND.

  And this is the reason why I am opening this ticket. See the bottom
  picture because I do not think this is normal

  PS: The finality is that I am UNABLE to readd this printer. (But again
  it was automatically installed+configured at OS installation)

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


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

[Desktop-packages] [Bug 1944113]

2022-04-07 Thread Michael Weghorn

*** Bug 14 has been marked as a duplicate of this bug. ***

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

Title:
  Many UI elements (list box, drop down) don't work at all in kf5
  environment

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Many UI elements (list box, drop down) don't work at all in kf5 environment. 
This makes LO unusable.
  For example, try to insert a table from standard toolbar in LO Writer – 
nothing inserted.
  Same happens with other drop down elements (styles, font family, font size, 
font color, font highlight, etc).

  Bug reports at LO's bug tracker:
  https://bugs.documentfoundation.org/show_bug.cgi?id=144037
  https://bugs.documentfoundation.org/show_bug.cgi?id=144562
  https://gerrit.libreoffice.org/c/core/+/122116

  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.11.0-34-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz
  Memory: 7,7 GiB

  Version: 7.2.1.2 / LibreOffice Community
  Build ID: 20(Build:2)
  CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb)
  Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU
  Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions


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

[Desktop-packages] [Bug 1944113]

2022-04-07 Thread Gjunk

confirm that the daily 7.3.3 is fixed.

thank you!

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

Title:
  Many UI elements (list box, drop down) don't work at all in kf5
  environment

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Many UI elements (list box, drop down) don't work at all in kf5 environment. 
This makes LO unusable.
  For example, try to insert a table from standard toolbar in LO Writer – 
nothing inserted.
  Same happens with other drop down elements (styles, font family, font size, 
font color, font highlight, etc).

  Bug reports at LO's bug tracker:
  https://bugs.documentfoundation.org/show_bug.cgi?id=144037
  https://bugs.documentfoundation.org/show_bug.cgi?id=144562
  https://gerrit.libreoffice.org/c/core/+/122116

  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.11.0-34-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz
  Memory: 7,7 GiB

  Version: 7.2.1.2 / LibreOffice Community
  Build ID: 20(Build:2)
  CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb)
  Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU
  Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions


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

[Desktop-packages] [Bug 1944113]

2022-04-07 Thread Ilmari-lauhakangas

Verified, thanks

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

Title:
  Many UI elements (list box, drop down) don't work at all in kf5
  environment

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Many UI elements (list box, drop down) don't work at all in kf5 environment. 
This makes LO unusable.
  For example, try to insert a table from standard toolbar in LO Writer – 
nothing inserted.
  Same happens with other drop down elements (styles, font family, font size, 
font color, font highlight, etc).

  Bug reports at LO's bug tracker:
  https://bugs.documentfoundation.org/show_bug.cgi?id=144037
  https://bugs.documentfoundation.org/show_bug.cgi?id=144562
  https://gerrit.libreoffice.org/c/core/+/122116

  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.11.0-34-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz
  Memory: 7,7 GiB

  Version: 7.2.1.2 / LibreOffice Community
  Build ID: 20(Build:2)
  CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb)
  Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU
  Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3
  Calc: threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions


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

[Desktop-packages] [Bug 1844453]

2022-04-07 Thread Mikekaganski

Also: https://extensions.libreoffice.org/en/extensions/show/oauth2ooo

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

Title:
  [upstream] Access to the Google remote account does not work

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

Bug description:
  I have a Google account with 2FA login, from LibreOffice I try to add the 
remote account, but it doesn't work, it asks me for a 6-digit PIN.
  Investigating to see if it was just my problem, I discovered that this is a 
long-standing LibreOffice bug (1) and seems unresolved.

  The last report confirms this: "2019-07-04 04:44:41 UTC
  This feature doesn't work with my Google account _w/o_
  2FA.

  Bug hasn't be resolved for about 3 years and "very soon"
  we may celebrate 5 years anniversary.  %-("

  1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 17 23:00:10 2019
  InstallationDate: Installed on 2019-02-18 (210 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.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/df-libreoffice/+bug/1844453/+subscriptions


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

[Desktop-packages] [Bug 1844453]

2022-04-07 Thread Mikekaganski

(In reply to Mike Kaganski from comment #92)

FYI: https://github.com/google/gmail-
oauth2-tools/wiki/OAuth2DotPyRunThrough

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

Title:
  [upstream] Access to the Google remote account does not work

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

Bug description:
  I have a Google account with 2FA login, from LibreOffice I try to add the 
remote account, but it doesn't work, it asks me for a 6-digit PIN.
  Investigating to see if it was just my problem, I discovered that this is a 
long-standing LibreOffice bug (1) and seems unresolved.

  The last report confirms this: "2019-07-04 04:44:41 UTC
  This feature doesn't work with my Google account _w/o_
  2FA.

  Bug hasn't be resolved for about 3 years and "very soon"
  we may celebrate 5 years anniversary.  %-("

  1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 17 23:00:10 2019
  InstallationDate: Installed on 2019-02-18 (210 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.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/df-libreoffice/+bug/1844453/+subscriptions


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

[Desktop-packages] [Bug 1966418]

2022-04-07 Thread Michael Catanzaro

I've chatted with Jeremy about this, and he understands that
-DUSE_WPE_RENDERER=OFF was intended to allow a transition period for
distros to package libwpe and wpebackend-fdo, that WebKit developers
don't test it anymore, and that Ubuntu needs to turn it on. I've also
reported bug #238932 to consider making it mandatory in the GTK 4
version of WebKit.

In the meantime, I wonder how hard it would be to upgrade the legacy
internal compositor to support zwp_linux_dmabuf_v1 so that Ubuntu
doesn't have to patch mesa. No clue about that.

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

Title:
  [jammy regression] webkit apps do not display content (yelp, epiphany,
  gnome-online-accounts etc)

Status in Gnome DevHelp:
  Invalid
Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1966418]

2022-04-07 Thread Jeremy Bicha

A very important detail:
Ubuntu builds webkit2gtk with -DUSE_WPE_RENDERER=OFF
This was done because we would need Ubuntu Security Team sign off to get 
wpewebkit in to Ubuntu's 'main' archive section instead of in 'universe'.

It looks like this bug is specific to that config.

Copying from the mesa bug:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/6236#note_1329402

"The issue is that WebKitGTK's internal Wayland compositor needs to
implement zwp_linux_dmabuf_v1 rather than relying on
EGL_WL_bind_wayland_display.

In the meantime, we could revert the part which makes us strictly rely
on dmabuf on the Mesa client side, and keep both in parallel for a
little bit. But WebKitGTK should really be implementing this interface."

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

Title:
  [jammy regression] webkit apps do not display content (yelp, epiphany,
  gnome-online-accounts etc)

Status in Gnome DevHelp:
  Invalid
Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1966418]

2022-04-07 Thread Desktop Rebuild Bot

Adding some context, I disabled wpe in Ubuntu when we landed the version
that added the option because the backend was new and our rules requires
a review from our security and MIR teams before adding new main depends,
which wasn't properly anticipated and not going to done for the incoming
release of Ubuntu.

I should probably have done that by now but I the wpebackend package
description in Debian states 'WebKit browser engine optimized for
embedded devices' which made me wrongly assume that was not the
preferred backend for a desktop usecase.

Which brings us back to today. The wpebackend package will be added to
our review queue but that's not going to be processed in time for the
incoming LTS so we will need another solution. The mesa upstream report
suggests they might be wanting to add code to handle legacy clients
(which webkitgtk built without wpe seems to be for that usecase?).
Ideally the webkitgtk codepath not using WPE would also be fixed since
that's an official upstream option. Our backup plan is probably to try
to revert the changes from mesa if really needed

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

Title:
  [jammy regression] webkit apps do not display content (yelp, epiphany,
  gnome-online-accounts etc)

Status in Gnome DevHelp:
  Invalid
Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)

2022-04-07 Thread Bug Watch Updater

** Changed in: webkit
   Status: Unknown => Confirmed

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

Title:
  [jammy regression] webkit apps do not display content (yelp, epiphany,
  gnome-online-accounts etc)

Status in Gnome DevHelp:
  Invalid
Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1968235] Re: Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz

2022-04-07 Thread iMac

I managed to bring both screens up at 30Hz by passing video resolutions
as kernel parameters

video=DP-3:3840x2160@30 video=DP-4:3840x2160@30

This means I do not have to do any display port replugging on startup.

I still have to manually change the refresh from 30Hz to 60Hz in the
settings. If there was a way to do this via cli, I would have a full
workaround for this issue.

I also noted that I was actually loosing the displays earlier in the
boot process, maybe at some DRM/framebuffer loading point, as I was not
seeing the extra few seconds of green service [OK]s, prior to wayland.

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

Title:
  Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz

Status in wayland package in Ubuntu:
  New

Bug description:
  I recently started using a Cable-Matters-201355 with my XPS 9380 (8th
  Gen TB3).  The dock supports dual 4K DP @ 60Hz via thunderbolt with PD
  input. (HBR3 compliant USB-C Dock (DSC/DP1.4 support) that uses all 4
  high speed lanes to get dual 60Hz)

  Both displays boot mirrored when powered up (Dell Logo, Grub, Kernel
  output) however go blank just as wayland starts up.

  Unplugging one of them allows the other to appear at 3840x2160@60Hz,
  after which I have to execute the following process to get both up and
  running.

  1) Change the refresh rate of the active display to 30Hz, apply in Screen 
Display settings dialog
  2) Plug the 2nd monitor in; At this point both appear in Screen Display 
dialog @60Hz, but the 2nd remains blank
  3) Change both to 30Hz, apply; At this point the 2nd screen turns on
  4) Change both to 60Hz, apply; At this point both are working at 60Hz, my 
desired end state

  Inspection of edid seems fine (below), other than the DisplaySize
  showing 27" instead of 32". Monitors are identical.

  Previously, I might be able to script my steps above using xrandr, but
  that seems to no longer be the case with 21.10 and wayland. I seem to
  be limited to the Screen Display dialog.

  Since I can fix by simply re-applying the settings, it seems like a
  bug on startup.  If I could find a CLI option to allow me to script
  this somehow, that workaround would be just fine for myself.

  Lid open/closed, power via the 201344 or direct via other TB-PD port
  has no impact.

  Here's hoping for a bugfix in 22.04 or at least a way to script the
  display configuration.

  $ cat /sys/class/drm/card0-DP-4/edid | parse-edid
  Checksum Correct

  Section "Monitor"
   Identifier "LG HDR 4K"
   ModelName "LG HDR 4K"
   VendorName "GSM"
   # Monitor Manufactured week 5 of 2021
   # EDID version 1.4
   # Digital Display
   DisplaySize 600 340
   Gamma 2.20
   Option "DPMS" "true"
   Horizsync 30-135
   VertRefresh 56-61
   # Maximum pixel clock is 560MHz
   #Not giving standard mode: 1152x864, 60Hz
   #Not giving standard mode: 1280x1024, 60Hz
   #Not giving standard mode: 1280x720, 60Hz
   #Not giving standard mode: 1600x900, 60Hz
   #Not giving standard mode: 1920x1080, 60Hz
   #Not giving standard mode: 1280x800, 60Hz

   #Extension block found. Parsing...
   Modeline "Mode 6" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync 
+vsync
   Modeline "Mode 0" 519.38 3840 3864 3880 3896 2160 2214 2219  +hsync 
-vsync
   Modeline "Mode 1" 266.64 3840 3848 3992 4000 2160 2214 2219  +hsync 
-vsync
   Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync 
+vsync
   Modeline "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync 
+vsync
   Modeline "Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
   Modeline "Mode 5" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
   Modeline "Mode 7" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync 
-vsync
   Option "PreferredMode" "Mode 6"
  EndSection

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


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

[Desktop-packages] [Bug 1960172] Re: Raspberry Pi: touch keyboard issues

[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Raspberry Pi: touch keyboard issues

Status in mutter package in Ubuntu:
  Expired

Bug description:
  I've been struggling to use my raspberry pi with a hardware keyboard
  connected.

  I have some software engineering experience and would really love to
  know even just where the source code is that controls the touch
  keyboard.

  - When the touch keyboard displays, touch events that are outside the 
keyboard are shifted up on the screen, away from their visuals, such that 
random events can happen when the screen is touched.
  - I do not see a way to disable the touch keyboard, making navigation of 
forms difficult.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-session-bin 40.1.1-1ubuntu1
  ProcVersionSignature: User Name 5.13.0-1015.17-raspi 5.13.19
  Uname: Linux 5.13.0-1015-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  6 07:06:29 2022
  ExecutablePath: /usr/libexec/gnome-session-binary
  ImageMediaBuild: 20210421.1
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to impish on 2021-12-22 (45 days ago)

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


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

[Desktop-packages] [Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]

2022-04-07 Thread AceLan Kao

Can't reproduce this issue with KDE.
And can't boot up the machine with mainline kernel. So, it's hard to bisect if 
it's a kernel issue.

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

Title:
  Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
  KMS update: CRTC property (GAMMA_LUT) not found]

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Screen can't turn back on by clicking keyboard after screen off by meta + l 
key.
  Try to do VT switch can make the screen back, some error poped when I try to 
wake up screen.

  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-03-31 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Tags: wayland-session jammy third-party-packages
  Uname: Linux 5.15.0-23-generic x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1960860] Re: Ubuntu 22.04:cheese not showing webcam output