[Desktop-packages] [Bug 1871849] Re: Full screen videos suddenly change scale when using fractional scaling

[Mutlu Can YILMAZ]

This cause Steam, Dolphin and Lutris/Wine games not to cover all the
screen/looks cropped. It also causes screens to go black. Moreover,
multi-monitor settings also randomly change.

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

Title:
  Full screen videos suddenly change scale when using fractional scaling

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  firefox does not properly play full screen videos using fractional scale at 
125%
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-29 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-24-generic x86_64
  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/ubuntu/+source/mutter/+bug/1871849/+subscriptions


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

[Desktop-packages] [Bug 326631] Re: Open program in the same workspace that it's initiated

[brad1138]

You replied, "sorry that we do not always have the capacity to review
all reported bugs in a timely manner" in a bug post that hasn't been
posted to in over 10 years.

Pretty sure that isn't relevant anymore. I stopped using Linux around 10
years ago...

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

Title:
  Open program in the same workspace that it's initiated

Status in One Hundred Papercuts:
  Expired
Status in metacity package in Ubuntu:
  Expired

Bug description:
  Using Ubuntu 8.10.

  Reproduce/what happens:
  1. open a program in workspace X (by whatever means - double clicking a file, 
choosing from the menu, panels...)
  2. switch to workspace Y while the program is loading
  3. the program opens in the active/showing workspace, workspace Y

  I expect the program to open in workspace X, where I started the
  program.

  
  This is a bug report for Brainstorm idea 17398, where more motivation for 
this to be implemented is provided .

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


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

[Desktop-packages] [Bug 326631] Re: Open program in the same workspace that it's initiated

[Launchpad Bug Tracker]

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  Open program in the same workspace that it's initiated

Status in One Hundred Papercuts:
  Expired
Status in metacity package in Ubuntu:
  Expired

Bug description:
  Using Ubuntu 8.10.

  Reproduce/what happens:
  1. open a program in workspace X (by whatever means - double clicking a file, 
choosing from the menu, panels...)
  2. switch to workspace Y while the program is loading
  3. the program opens in the active/showing workspace, workspace Y

  I expect the program to open in workspace X, where I started the
  program.

  
  This is a bug report for Brainstorm idea 17398, where more motivation for 
this to be implemented is provided .

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


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

[Desktop-packages] [Bug 326631] Re: Open program in the same workspace that it's initiated

[Launchpad Bug Tracker]

[Expired for metacity (Ubuntu) because there has been no activity for 60
days.]

** Changed in: metacity (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Open program in the same workspace that it's initiated

Status in One Hundred Papercuts:
  Expired
Status in metacity package in Ubuntu:
  Expired

Bug description:
  Using Ubuntu 8.10.

  Reproduce/what happens:
  1. open a program in workspace X (by whatever means - double clicking a file, 
choosing from the menu, panels...)
  2. switch to workspace Y while the program is loading
  3. the program opens in the active/showing workspace, workspace Y

  I expect the program to open in workspace X, where I started the
  program.

  
  This is a bug report for Brainstorm idea 17398, where more motivation for 
this to be implemented is provided .

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


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

[Desktop-packages] [Bug 1869237] Re: Ubuntu 18.04.4 LTS AutoScreen Lock will not disable

[Launchpad Bug Tracker]

[Expired for gnome-settings-daemon (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Ubuntu 18.04.4 LTS  AutoScreen Lock will not disable

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

Bug description:
  I cannot prevent the screen from locking.

  The Privacy Settings are off but it continues to lock the screen.

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


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

[Desktop-packages] [Bug 1952164] Re: cups.path repeatedly goes into systemd failed state

[Todd Taft]

Discovered this was a system-wide problem, not specifically related to cups.
Backup program was holding open a very high number if inotify watches and this 
was causing issues for other programs (including cups).
Solution was to add a conf file in /etc/sysctl.d that set a higher value for 
fs.inotify.max_user_watches than the default (and then force a reload).

In my case, this seems to work:
echo "fs.inotify.max_user_watches=131072" >> /etc/sysctl.d/999-local.conf
sysctl -p /etc/sysctl.d/999-local.conf

Note that this solution may cause other issues on systems with low
memory.

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

Title:
  cups.path repeatedly goes into systemd failed state

Status in cups package in Ubuntu:
  Invalid

Bug description:
  cups.path is repeatedly entering a failed state in systemd.  Attempts
  to restart the unit or even reboot the machine are, at best, temporary
  solutions.

  # systemctl status cups.path
  ● cups.path - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.path; enabled; vendor preset: 
enabled)
   Active: failed (Result: resources)
 Triggers: ● cups.service

  Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
  # journalctl -u cups.path
  -- Logs begin at Tue 2021-11-23 22:54:38 EST, end at Wed 2021-11-24 21:42:42 
EST. --
  Nov 23 22:54:51 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
  -- Reboot --
  Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.

  Despite what the log messages suggest, none of my (non-snap) filesystems are 
full (or even close to full):
  # df
  Filesystem
 1K-blocks  Used   Available Use% Mounted on
  udev  
  32731616 032731616   0% /dev
  tmpfs 
   6556256  2536 6553720   1% /run
  /dev/mapper/kangaroovg-rootlv 
   5095040553996 4262516  12% /
  
/dev/disk/by-id/dm-uuid-LVM-kxWkbFRXPo6GoeQURytO8JUpXOtGnGzNRQG28DNWnEi0JYl1Vkx1r7uvSiDwfZDb
20511312   724339212202960  38% /usr
  tmpfs 
  32781264  102432780240   1% /dev/shm
  tmpfs 
  5120 45116   1% /run/lock
  tmpfs 
  32781264 032781264   0% /sys/fs/cgroup
  none  
   4194304  3504 4190800   1% /tmp
  /dev/mapper/kangaroovg-varlv  
   5095040   1743876 3072636  37% /var
  /dev/nvme1n1p2
999320246420  684088  27% /boot
  /dev/mapper/kangaroovg-srvlv  
   5095040 20520 4795992   1% /srv
  /dev/mapper/kangaroovg-usrlocallv 
   5095040 31820 4784692   1% /usr/local
  /dev/mapper/kangaroovg-homelv 
  51343840  1300229235703724  27% /home
  /dev/mapper/kangaroovg-varliblv   
   5095040   1306604 3509908  28% /var/lib
  /dev/nvme1n1p1
523248  5360  517888   2% /boot/efi
  /dev/loop0
 56832 56832   0 100% /snap/core18/2128
  /dev/loop2
 33152 33152   0 100% /snap/snapd/12883
  /dev/loop1

[Desktop-packages] [Bug 1952164] Re: cups.path repeatedly goes into systemd failed state

[Todd Taft]

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

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

Title:
  cups.path repeatedly goes into systemd failed state

Status in cups package in Ubuntu:
  Invalid

Bug description:
  cups.path is repeatedly entering a failed state in systemd.  Attempts
  to restart the unit or even reboot the machine are, at best, temporary
  solutions.

  # systemctl status cups.path
  ● cups.path - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.path; enabled; vendor preset: 
enabled)
   Active: failed (Result: resources)
 Triggers: ● cups.service

  Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
  # journalctl -u cups.path
  -- Logs begin at Tue 2021-11-23 22:54:38 EST, end at Wed 2021-11-24 21:42:42 
EST. --
  Nov 23 22:54:51 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
  -- Reboot --
  Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
  Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.

  Despite what the log messages suggest, none of my (non-snap) filesystems are 
full (or even close to full):
  # df
  Filesystem
 1K-blocks  Used   Available Use% Mounted on
  udev  
  32731616 032731616   0% /dev
  tmpfs 
   6556256  2536 6553720   1% /run
  /dev/mapper/kangaroovg-rootlv 
   5095040553996 4262516  12% /
  
/dev/disk/by-id/dm-uuid-LVM-kxWkbFRXPo6GoeQURytO8JUpXOtGnGzNRQG28DNWnEi0JYl1Vkx1r7uvSiDwfZDb
20511312   724339212202960  38% /usr
  tmpfs 
  32781264  102432780240   1% /dev/shm
  tmpfs 
  5120 45116   1% /run/lock
  tmpfs 
  32781264 032781264   0% /sys/fs/cgroup
  none  
   4194304  3504 4190800   1% /tmp
  /dev/mapper/kangaroovg-varlv  
   5095040   1743876 3072636  37% /var
  /dev/nvme1n1p2
999320246420  684088  27% /boot
  /dev/mapper/kangaroovg-srvlv  
   5095040 20520 4795992   1% /srv
  /dev/mapper/kangaroovg-usrlocallv 
   5095040 31820 4784692   1% /usr/local
  /dev/mapper/kangaroovg-homelv 
  51343840  1300229235703724  27% /home
  /dev/mapper/kangaroovg-varliblv   
   5095040   1306604 3509908  28% /var/lib
  /dev/nvme1n1p1
523248  5360  517888   2% /boot/efi
  /dev/loop0
 56832 56832   0 100% /snap/core18/2128
  /dev/loop2
 33152 33152   0 100% /snap/snapd/12883
  /dev/loop1
 72064 72064   0 100% /snap/lxd/21029
  /dev/mapper/disharmony--kangaroo--qsan--vg-disharmony--kangaroo--qsan--lv 
5325329320 198368460  4858509228   4% /srv/disharmony
  /dev/mapper/git--kangaroo--qsan--vg-git--kangaroo--qsan--lv   
1055836596 77852  1002055476   1% /srv/git
  /dev/mapper/qsaniscsiunisonvg-unisonlv
5366618112 385871460  4980746652   

[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

[Nicholas Garth]

Thanks for posting the fix, I tired it out on my Yoga 9 14ITL5 on both
the Fedora 35 5.14.18-300.fc35.x86_64 kernel and the Ubuntu 21.10
5.13.0-19-generic kernel with minimal luck. With DAC1 and DAC2 at
maximum, the rear speaker sounds like nothing is coming out of it. When
DAC1 is turned down to 0, there is audio coming out of the rear speaker,
however, the audio output quality is rather poor and tinny.

Looking at the kernel source,
https://github.com/torvalds/linux/commit/9ebaef0540a981093bce5df15af32354d32391d9
it appears that the kernel version the fix was first released in was
5.13rc4 and looks to appear in all newer tags, so the fix should be in
use on my system. Based on the experiences shown above, what I'm
experiencing doesn't seem to be the right behaviour.

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1952164] [NEW] cups.path repeatedly goes into systemd failed state

[Todd Taft]

Public bug reported:

cups.path is repeatedly entering a failed state in systemd.  Attempts to
restart the unit or even reboot the machine are, at best, temporary
solutions.

# systemctl status cups.path
● cups.path - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.path; enabled; vendor preset: 
enabled)
 Active: failed (Result: resources)
   Triggers: ● cups.service

Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
# journalctl -u cups.path
-- Logs begin at Tue 2021-11-23 22:54:38 EST, end at Wed 2021-11-24 21:42:42 
EST. --
Nov 23 22:54:51 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
Nov 23 23:19:17 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.
-- Reboot --
Nov 24 04:33:31 kangaroo.unclet.net systemd[1]: Started CUPS Scheduler.
Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed to enter 
waiting state: No space left on device
Nov 24 10:48:43 kangaroo.unclet.net systemd[1]: cups.path: Failed with result 
'resources'.

Despite what the log messages suggest, none of my (non-snap) filesystems are 
full (or even close to full):
# df
Filesystem  
   1K-blocks  Used   Available Use% Mounted on
udev
32731616 032731616   0% /dev
tmpfs   
 6556256  2536 6553720   1% /run
/dev/mapper/kangaroovg-rootlv   
 5095040553996 4262516  12% /
/dev/disk/by-id/dm-uuid-LVM-kxWkbFRXPo6GoeQURytO8JUpXOtGnGzNRQG28DNWnEi0JYl1Vkx1r7uvSiDwfZDb
20511312   724339212202960  38% /usr
tmpfs   
32781264  102432780240   1% /dev/shm
tmpfs   
5120 45116   1% /run/lock
tmpfs   
32781264 032781264   0% /sys/fs/cgroup
none
 4194304  3504 4190800   1% /tmp
/dev/mapper/kangaroovg-varlv
 5095040   1743876 3072636  37% /var
/dev/nvme1n1p2  
  999320246420  684088  27% /boot
/dev/mapper/kangaroovg-srvlv
 5095040 20520 4795992   1% /srv
/dev/mapper/kangaroovg-usrlocallv   
 5095040 31820 4784692   1% /usr/local
/dev/mapper/kangaroovg-homelv   
51343840  1300229235703724  27% /home
/dev/mapper/kangaroovg-varliblv 
 5095040   1306604 3509908  28% /var/lib
/dev/nvme1n1p1  
  523248  5360  517888   2% /boot/efi
/dev/loop0  
   56832 56832   0 100% /snap/core18/2128
/dev/loop2  
   33152 33152   0 100% /snap/snapd/12883
/dev/loop1  
   72064 72064   0 100% /snap/lxd/21029
/dev/mapper/disharmony--kangaroo--qsan--vg-disharmony--kangaroo--qsan--lv   
  5325329320 198368460  4858509228   4% /srv/disharmony
/dev/mapper/git--kangaroo--qsan--vg-git--kangaroo--qsan--lv 
  1055836596 77852  1002055476   1% /srv/git
/dev/mapper/qsaniscsiunisonvg-unisonlv  
  5366618112 385871460  4980746652   8% /srv/unison
/dev/mapper/qsaniscsilinuxbackupvg-linuxbackuplv
  5366618112  96643028  5269975084   2% /srv/linux-backup
/dev/mapper/qsaniscsisystemarchivevg-systemarchivelv
  5366618112 745069628  4621548484  14% /srv/system-archive
tmpfs   

[Desktop-packages] [Bug 1952122] Re: Libre Office now requires a gvfsd-admin login on all documents

[Daniel van Vugt]

That sounds like a problem with your filesystem or mount. Certainly it
has nothing to do with GNOME Shell.

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

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

Title:
  Libre Office now requires a gvfsd-admin login on all documents

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Recently appeared.  Libre Office ALL Docs have had their Security
  Permissions changed to Me/user/root as Read & Write.

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


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

[Desktop-packages] [Bug 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps)

[Daniel van Vugt]

** No longer affects: mutter

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  Maximize vertically/horizontally doesn't work (in some apps)

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1952154] Re: [HP Pavilion dv6 Notebook PC, IDT 92HD75B3X5, Speaker, Internal] Pulseaudio fails to detect card

[yehia2amer]

It turns out that after following the below guide, I found that another package 
called timidity is conflicting with PulseAudio and causing it to fail detecting 
my audio devices.
So I uninstalled it and PulseAudio is now working fine.

sudo apt-get remove timidity

https://wiki.archlinux.org/title/PulseAudio/Troubleshooting#The_only_device_shown_is_%22dummy_output%22_or_newly_connected_cards_are_not_detected

I ran this command:
HP-Pavilion-dv6-Notebook-PC:~$ sudo fuser -v /dev/snd/*
 USERPID ACCESS COMMAND
/dev/snd/controlC0:timidity852F timidity
/dev/snd/controlC1:rana  7346  F pulseaudio
/dev/snd/pcmC0D0p:   timidity852 F...m timidity
/dev/snd/seq:timidity852 F timidity
/dev/snd/timer:  timidity852 f timidity


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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/699628

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

Title:
  [HP Pavilion dv6 Notebook PC, IDT 92HD75B3X5, Speaker, Internal]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  [HP Pavilion dv6 Notebook PC, IDT 92HD75B3X5, Speaker, Internal]
  Pulseaudio fails to detect card

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rana   1031 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 25 03:08:15 2021
  InstallationDate: Installed on 2021-11-16 (8 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel MID
  Symptom_Jack: Speaker, Internal
  Title: [HP Pavilion dv6 Notebook PC, IDT 92HD75B3X5, Speaker, Internal] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2010
  dmi.bios.release: 15.28
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 50.37
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1C:bd05/17/2010:br15.28:efr50.37:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:skuWE049EA#ABV:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.sku: WE049EA#ABV
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

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


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

[Desktop-packages] [Bug 1951072] Re: gnome-shell using too much memory after some time running

[Daniel van Vugt]

Great!

Sorry Launchpad still has problems with Cyrillic characters in that
filename so can't view the image in comment #15.

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  gnome-shell using too much memory after some time running

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  It is using too much memory. Tried disabling extensions, but it
  doesn't help

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 16 11:10:55 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-07 (1500 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-09-26 (50 days ago)

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


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

[Desktop-packages] [Bug 1952154] [NEW] [HP Pavilion dv6 Notebook PC, IDT 92HD75B3X5, Speaker, Internal] Pulseaudio fails to detect card

[yehia2amer]

Public bug reported:

[HP Pavilion dv6 Notebook PC, IDT 92HD75B3X5, Speaker, Internal]
Pulseaudio fails to detect card

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  rana   1031 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 25 03:08:15 2021
InstallationDate: Installed on 2021-11-16 (8 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel MID
Symptom_Jack: Speaker, Internal
Title: [HP Pavilion dv6 Notebook PC, IDT 92HD75B3X5, Speaker, Internal] 
Pulseaudio fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2010
dmi.bios.release: 15.28
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3659
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 32.25
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.ec.firmware.release: 50.37
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1C:bd05/17/2010:br15.28:efr50.37:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:skuWE049EA#ABV:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.sku: WE049EA#ABV
dmi.product.version: 049D212412102
dmi.sys.vendor: Hewlett-Packard

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


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

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

Title:
  [HP Pavilion dv6 Notebook PC, IDT 92HD75B3X5, Speaker, Internal]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [HP Pavilion dv6 Notebook PC, IDT 92HD75B3X5, Speaker, Internal]
  Pulseaudio fails to detect card

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rana   1031 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 25 03:08:15 2021
  InstallationDate: Installed on 2021-11-16 (8 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel MID
  Symptom_Jack: Speaker, Internal
  Title: [HP Pavilion dv6 Notebook PC, IDT 92HD75B3X5, Speaker, Internal] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2010
  dmi.bios.release: 15.28
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 50.37
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1C:bd05/17/2010:br15.28:efr50.37:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:skuWE049EA#ABV:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.sku: WE049EA#ABV
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

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


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

[Desktop-packages] [Bug 1952147] [NEW] no way to list drivers "ubuntu-drivers list --gpgpu" will install

[Michael Hudson-Doyle]

Public bug reported:

I'm pretty sure that "ubuntu-drivers install --gpgpu" will install
something if and only if "ubuntu-drivers list --gpgpu" has non-empty
output, but the logic of which of the things list returns gets installed
seems a bit non-trivial

The context for this is in the server installer, I want to say "we think
you should install nvidia-headless-no-dkms-470-server and linux-modules-
nvidia-470-server-generic", shall we go ahead and install them?

My current spike just says "there are some drivers you might want to
install, shall we install them?" which just seems a bit opaque

Alberto suggested a flag so that I could run "ubuntu-drivers list
--gpgpu --recommended" in the installer. I should just make very clear
that I'd want "ubuntu-drivers list --recommended" (i.e. without --gpgpu)
to work the same way :)

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

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

Title:
  no way to list drivers "ubuntu-drivers list --gpgpu" will install

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

Bug description:
  I'm pretty sure that "ubuntu-drivers install --gpgpu" will install
  something if and only if "ubuntu-drivers list --gpgpu" has non-empty
  output, but the logic of which of the things list returns gets
  installed seems a bit non-trivial

  The context for this is in the server installer, I want to say "we
  think you should install nvidia-headless-no-dkms-470-server and linux-
  modules-nvidia-470-server-generic", shall we go ahead and install
  them?

  My current spike just says "there are some drivers you might want to
  install, shall we install them?" which just seems a bit opaque

  Alberto suggested a flag so that I could run "ubuntu-drivers list
  --gpgpu --recommended" in the installer. I should just make very clear
  that I'd want "ubuntu-drivers list --recommended" (i.e. without
  --gpgpu) to work the same way :)

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


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

[Desktop-packages] [Bug 1951072] Re: gnome-shell using too much memory after some time running

[Yuriy Padlyak]

without snap manager extension

** Attachment added: "Знімок екрана з 2021-11-24 22-25-37.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1951072/+attachment/5543119/+files/%D0%97%D0%BD%D1%96%D0%BC%D0%BE%D0%BA%20%D0%B5%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%B7%202021-11-24%2022-25-37.png

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

Title:
  gnome-shell using too much memory after some time running

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It is using too much memory. Tried disabling extensions, but it
  doesn't help

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 16 11:10:55 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-07 (1500 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-09-26 (50 days ago)

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


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

[Desktop-packages] [Bug 1951072] Re: gnome-shell using too much memory after some time running

[Yuriy Padlyak]

So, it was snap-manager@fthx..

I remember installing it sometimes before the ubuntu version upgrade, I
guess. And it was gone from the notifications panel, but probably still
eating memory in the background :)

Thanks for all the help, Daniel! Not gnome-shell issue, then, it seems

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

Title:
  gnome-shell using too much memory after some time running

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It is using too much memory. Tried disabling extensions, but it
  doesn't help

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 16 11:10:55 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-07 (1500 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-09-26 (50 days ago)

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


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

[Desktop-packages] [Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::

[niqo]

Here is mine:

Ubuntu: 21.10
Gnome version: 40.4.0
Window System: X11
Nvidia Driver: 495.44


syslog sample:
Nov 24 10:41:04 niqo-Alienware-Aurora-R11 gnome-shell[2570]: Attempting to run 
a JS callback during garbage collection. This is most likely caused by 
destroying a Clutter actor or GTK widget with ::destroy signal connected, or 
using the destroy(), dispose(), or remove() vfuncs. Because it would crash the 
application, it has been blocked.
Nov 24 10:41:04 niqo-Alienware-Aurora-R11 gnome-shell[2570]: The offending 
callback was SourceFunc().
Nov 24 10:41:04 niqo-Alienware-Aurora-R11 gnome-shell[2570]: Attempting to run 
a JS callback during garbage collection. This is most likely caused by 
destroying a Clutter actor or GTK widget with ::destroy signal connected, or 
using the destroy(), dispose(), or remove() vfuncs. Because it would crash the 
application, it has been blocked.
Nov 24 10:41:04 niqo-Alienware-Aurora-R11 gnome-shell[2570]: The offending 
callback was SourceFunc().
Nov 24 10:41:04 niqo-Alienware-Aurora-R11 gnome-shell[2570]: Attempting to run 
a JS callback during garbage collection. This is most likely caused by 
destroying a Clutter actor or GTK widget with ::destroy signal connected, or 
using the destroy(), dispose(), or remove() vfuncs. Because it would crash the 
application, it has been blocked.
Nov 24 10:41:04 niqo-Alienware-Aurora-R11 gnome-shell[2570]: The offending 
callback was SourceFunc().
Nov 24 10:41:04 niqo-Alienware-Aurora-R11 gnome-shell[2570]: Attempting to run 
a JS callback during garbage collection. This is most likely caused by 
destroying a Clutter actor or GTK widget with ::destroy signal connected, or 
using the destroy(), dispose(), or remove() vfuncs. Because it would crash the 
application, it has been blocked.
Nov 24 10:41:04 niqo-Alienware-Aurora-R11 gnome-shell[2570]: The offending 
callback was SourceFunc().

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

Title:
  gnome-shell fills syslog: Attempting to run a JS callback during
  garbage collection. This is most likely caused by destroying a Clutter
  actor or GTK widget with ::destroy signal connected, or using the
  destroy(), dispose(), or remove() vfuncs. Because it would crash the
  application, it has been blocked. The offending callback was
  SourceFunc().

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Issue is explained in detail here:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Dec 16 18:56:56 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-01 (258 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

[Robie Basak]

Before I was relying on the information presented here and the changelog
in the upload to consider regression risk. Today I reviewed the patches
in more detail expecting to find what has been described. What's going
on in 01_modem-quectel.patch? This says "add support for EM120/160 PCIe
modules" and it seems to be adding support for a PCIe variant of a modem
in the code that already supports a USB variant. But your changelog just
says "Support manual firmware upgrading" with no mention of support for
additional modems. Are you actually additionally adding support for this
modem hardware where support didn't exist previously? I see no mention
of additional additional modem support anywhere in this bug so far.

If so, then will you be able to test the regular functionality of these
modems - both USB and PCIe - during SRU verification please? Do you have
these two modems available? This would be to ensure that 1) the changes
to modemmanager that relate to the USB variant haven't regressed; and 2)
the changes to add support for the PCIe variant is actually working. If
you can do this, then please add this to the Test Plan. If not, then
further discussion is needed.

It looks like Impish no longer carries this patch as 1.16.6-2ubuntu1 was
removed, so we also need an upload of this to Impish please.

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

Title:
  Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  The modem certification requires that different modem firmware is used for 
different network carrier.
  This needs the firmware upgrading capability during the modem certification 
process.

  The modem manufacture vendors (Foxconn and Quectel) provided utilities to do 
modem's firmware upgrading manually.(LP#1943774, LP#1943780)
  These utilities are verified to be working when the recent versions(> v 
1.18.2) of ModemManager are used with.

  To support manual firmware upgrading on the current Focal release which is 
using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2.
  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
  * for Foxconn T99W175
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
    
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154

  The firmware upgrading was verified using the patched ModemManager v 1.16.6 
with the following 2 modems:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot
  7. Verify if the upgraded modem firmware is still working

  [Where problems could occur]

  The requested update has 2 parts:

  1. Informative
     1.1 Provide more information about modems whose drivers use WWAN subsystem 
in kernel 5.13
     1.2 Modem manufacture's private utilities can use this information to do 
modem's FW upgrading manually

  2. Changes are specific to Foxconn and Quectel modems
     2.1 Modified code are only used by Foxconn and Quectel modems during their 
FW upgrading. (matched by vendor_id and product_id)

  In current Ubuntu's certification records for modem:
  * No other modem uses WWAN subsystem in kernel 5.13
  * Modem's FW update is not supported via ModemManager ( < v1.18 )

  There is no certificated modems can do the firmware upgrading flow for the 
regression test.
  This update should not affect existing modems.

  The problem would be limited to these two mentioned modems.
  Each carrier mapping .conf file is for a specific modem.
  ModemManager will load one of the carrier mapping conf files via the modem 
manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.)
  We cannot verify if the carrier mapping is correct. This relies on the 
manufacturer to provide the correct mapping.

  The carrier mapping .conf files is verified by modem’s manufacture according 
to 

[Desktop-packages] [Bug 1949924] Re: yelp crashes in wayland session with NVIDIA 470

[Bug Watch Updater]

** Changed in: egl-wayland
   Status: New => Fix Released

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

Title:
  yelp crashes in wayland session with NVIDIA 470

Status in NVIDIA / egl-wayland:
  Fix Released
Status in egl-wayland package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid

Bug description:
  $ yelp
  yelp: ../src/wayland-thread.c:87: wlExternalApiLock: Assertion `!"failed to 
lock pthread mutex"' failed.
  Aborted (core dumped)

  This does not happen in Debian testing, and it also works as expected
  in an Ubuntu on Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 41.1-1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  5 02:51:43 2021
  InstallationDate: Installed on 2019-11-10 (725 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1949924/+subscriptions


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

[Desktop-packages] [Bug 1947820] Re: [SRU] Backport xorg-server 1.20.13 to focal

[Timo Aaltonen]

pyfai? the list only shows aptdaemon failing on arm64, and it has been
failing for a long time now, so we can disregard that one

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

Title:
  [SRU] Backport xorg-server 1.20.13  to focal

Status in OEM Priority Project:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The delay phenomenon is serious in 'External display mode' during the 
'On-demand' mode working.
  Please reference lp:1940247 and lp:1919118.

  [Fix]
   I installed 21.10 on Raptor12(ThinkPad-P15-Gen-2i), with xorg-server 
2:1.20.13-1ubuntu1 and nvidia-495.38 test driver, this issue is solved. But in 
20.04, it's still 2:1.20.11-1ubuntu1~20.04.2.

  [Test]
  On Raptor12(ThinkPad-P15-Gen-2i), P17 Gen 2 and P1 Gen 4, with latest 20.04, 
it could be reproduced.

  [Where problems could occur]
  Although the nvidia driver is not released, I thought it's no harm to upgrade 
xorg-server first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1947820/+subscriptions


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

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Sergio Durigan Junior]

** Tags removed: server-todo

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Fix Released
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1952086] Re: Double click titlebar toggle-maximize-horizontally/vertically not working

[André Hertler]

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

** This bug has been marked a duplicate of bug 1698083
   Maximize vertically/horizontally doesn't work (in some apps)

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

Title:
  Double click titlebar toggle-maximize-horizontally/vertically not
  working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Double clicking gnome window titlebar not performing action set with 
gsettings nor gnome-tweaks.
  Instead double clicking will maximize the window as if the action 
"toggle-maximize" was performed.

  Changing the setting in gnome-tweaks show up in dconf. But the action
  is not performed.

  Example:

  dconf watch /
  /org/gnome/desktop/wm/preferences/action-double-click-titlebar
'toggle-maximize-horizontally'

  Steps to reproduce:
  1. Run gnome-tweaks
  2. Click "Window Titlebars"
  3. Set "Titlebar Actions - Double click" and select "Toggle Maximize 
Horizontally"
  4. Double click a gnome-terminal titlebar.

  Results: Window maximizes fully

  Expected results: Window maximizes on the horizontal axis only.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04.3 LTS
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 500
  DisplayManager: gdm3

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


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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

[paquin pierre]

I can confirm crash on latest 20.04 is still there.

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1952122] [NEW] Libre Office now requires a gvfsd-admin login on all documents

[MartyC1]

Public bug reported:

Recently appeared.  Libre Office ALL Docs have had their Security
Permissions changed to Me/user/root as Read & Write.

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

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

Title:
  Libre Office now requires a gvfsd-admin login on all documents

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Recently appeared.  Libre Office ALL Docs have had their Security
  Permissions changed to Me/user/root as Read & Write.

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


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

[Desktop-packages] [Bug 1952107] [NEW] Google Contacts API Deprecated

[Yeshayohu Zirkind]

Public bug reported:

I opened Evolution today and a red banner appeared on top with the
following message:

> Failed to connect address book “ : Contacts”

> Invalid request URI or header, or unsupported nonstandard parameter:
Contacts API is being deprecated. Migrate to People API to retain
programmatic access to Google Contacts. See
https://developers.google.com/people/contacts-api-migration.

I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?


[0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
[1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  
  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1952107/+subscriptions


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

[Desktop-packages] [Bug 1949924] Re: yelp crashes in wayland session with NVIDIA 470

[Launchpad Bug Tracker]

This bug was fixed in the package egl-wayland - 1:1.1.9-1.1

---
egl-wayland (1:1.1.9-1.1) unstable; urgency=medium

  * Non-maintainer upload
  * d/p/egl-wayland-retrieve-DRM-device-name-before-acquiring-.patch:
- Cherry picked upstream commit to fix lock issue (LP: #1949924)

 -- Gunnar Hjalmarsson   Wed, 24 Nov 2021 04:39:34
+0100

** Changed in: egl-wayland (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  yelp crashes in wayland session with NVIDIA 470

Status in NVIDIA / egl-wayland:
  New
Status in egl-wayland package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid

Bug description:
  $ yelp
  yelp: ../src/wayland-thread.c:87: wlExternalApiLock: Assertion `!"failed to 
lock pthread mutex"' failed.
  Aborted (core dumped)

  This does not happen in Debian testing, and it also works as expected
  in an Ubuntu on Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yelp 41.1-1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  5 02:51:43 2021
  InstallationDate: Installed on 2019-11-10 (725 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1949924/+subscriptions


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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

[Nec]

Hello,

This bug is not solved at all. After having hit it (xubuntu 21.10, Chromium 
96.0.4664.45, snap2.53.2, I still can not open .vmrc URLs.
When looking at the master git repo here :
https://github.com/jdstrand/snapd/blob/5190924a895e6344b57e9670727bf079d014dbe3/usersession/userd/launcher_test.go#L78
one read that the whitelisted allowedURL schemes are still hard-coded.

Seriously?

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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


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

[Desktop-packages] [Bug 1945770] Re: firefox: Fail to build against OpenSSL 3.0

[Olivier Tilloy]

Rico just mentioned on IRC that Simon confirmed that building against
OpenSSL 3.0 works with the firefox beta branch.

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

Title:
  firefox: Fail to build against OpenSSL 3.0

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Hello,

  As part of a rebuild against OpenSSL3, this package failed to build on one or
  several architectures. You can find the details of the rebuild at 

  https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html

  or for the amd64 failed build, directly at
  
https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098525/+files/buildlog_ubuntu-impish-amd64.firefox_92.0+build3-0ubuntu2.0~ssl3ppa1.1_BUILDING.txt.gz

  We're planning to transition to OpenSSL 3.0 for the 22.04 release, and 
consider
  this issue as blocking for this transition.

  You can find general migration informations at
  https://www.openssl.org/docs/manmaster/man7/migration_guide.html
  For your tests, you can build against libssl-dev as found in the PPA
  schopin/openssl-3.0.0

  Looking at the build failure, the problem lies in the openssl-sys crate.
  It seems the version 0.9.64 of this crate should fix the failure:
  
https://github.com/sfackler/rust-openssl/blob/master/openssl-sys/CHANGELOG.md#v0964---2021-06-18

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


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

[Desktop-packages] [Bug 1948533] Re: (No Subject)

[Tiphen Ti]

for Marc Deslauriers

Hi,
openvpn doesnt create any file in /etc/NetworkManager/system-connections
(I dont have any script up option in my openvpn config files since I want 
network manager to define dns not openvpn, it worked perfect untill ubunut 
version 21.1

here for the wired connection: in /etc/NetworkManager/system-connections


[ipv4]
dns=1.1.1.1;
dns-search=
ignore-auto-dns=true
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=disabled



>
> If you look into the openvpn configuration file that Network Manager
> creates for your connection in /etc/NetworkManager/system-connections,
> could you please paste the [ipv4] and [ipv6] sections?
>
> ** No longer affects: ubuntu
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
> ** Information type changed from Public Security to Public
>
> -
>
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1948533
>
> Title:
> any dns defined in network-manager doesnt go in openvpn tunnel (leaks
> on gnome/mate/xubuntu only in 21.10)
>
> Status in network-manager package in Ubuntu:
> Incomplete
>
> Bug description:
> in all linux including ubuntu up to version 21.04, when dns is set to not 
> automatic in network manager and one dns is set manually (exemple 1.1.1.1) 
> when openvpn is used the dns is going through the vpn tunnel.
> On ubuntu 21.10 (I tested ubuntu, ubuntu mate and xubuntu)I can affirm the 
> dns in this case is not going trough the vpn.it is leaking.I have used ubuntu 
> for years this is first time this problem occurs (21.10).(and it s not just a 
> question of packages because on my arch linux installs I never had such 
> problem, so it must be a config problem.
>
> (when using packages stubby or dnscrypt-proxy (to encrypt dns queries)
> and dns 127.0.0.1 is set in network-manager the dns does goes trough
> the vpn (but stubby service needs to be sometimes reloded, it is less
> reliable that it used to be with previous versions of ubuntu)
>
> (I cannot speculate where the bug is from (network-manager, systemd
> resolved etc)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1948533/+subscriptions

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

Title:
  any dns defined in network-manager doesnt go in openvpn tunnel (leaks
  on gnome/mate/xubuntu only in 21.10)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  in all linux including ubuntu up to version 21.04, when dns is set to not 
automatic in network manager and one dns is set manually (exemple 1.1.1.1) when 
openvpn is used the dns is going through the vpn tunnel.
  On ubuntu 21.10 (I tested ubuntu, ubuntu mate and xubuntu)I can affirm the 
dns in this case is not going trough the vpn.it is leaking.I have used ubuntu 
for years this is first time this problem occurs (21.10).(and it s not just a 
question of packages because on my arch linux installs I never had such 
problem, so it must be a config problem.

  (when using packages stubby or dnscrypt-proxy (to encrypt dns queries)
  and dns 127.0.0.1 is set in network-manager the dns does goes trough
  the vpn (but stubby service needs to be sometimes reloded, it is less
  reliable that it used to be with previous versions of ubuntu)

  (I cannot speculate where the bug is from (network-manager, systemd
  resolved etc)

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


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

[Desktop-packages] [Bug 1949553] Re: Backport packages for 20.04.4 HWE stack

[Timo Aaltonen]

see Debian bugs

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994873
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994955

we can't keep valgrind enabled, or libdrm.pc would be broken

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

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

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Incomplete
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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

[Desktop-packages] [Bug 1942290] Re: Folding menus do not work anymore (on Wayland)

[Launchpad Bug Tracker]

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

** Changed in: thunderbird (Ubuntu)
   Status: New => Confirmed

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

Title:
  Folding menus do not work anymore (on Wayland)

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When trying to access any folding menus (eg. in View top-level menu
  such as Headers, Sort by, Threads, etc.) these menus do not expand any
  more.

  This seems to be bound to Wayland only as it work as expected under
  X11 using Gnome shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: thunderbird 1:78.13.0+build1-0ubuntu0.21.04.2
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christoph   6475 F pipewire-media-
   /dev/snd/seq:christoph   6474 F pipewire
  BuildID: 20210802223056
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Wed Sep  1 07:59:50 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-08-31 (1461 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-0680c0c5-c5cc-4fcd-8a7f-a4cde0210404
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=78.13.0/20210802223056 (In use)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs:
   bp-0680c0c5-c5cc-4fcd-8a7f-a4cde0210404
   bp-8a568d4d-03fa-4892-aa74-169250210331
   bp-a3a6396d-cf62-424a-85dd-3772f0210328
   bp-5c7f6431-4927-4afd-8eca-f673e0210328
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to hirsute on 2021-04-23 (130 days ago)
  dmi.bios.date: 06/09/2021
  dmi.bios.release: 2.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.16.0
  dmi.board.name: 0PF86Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.16.0:bd06/09/2021:br2.16:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.product.sku: 075B
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073

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


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

[Desktop-packages] [Bug 1952086] [NEW] Double click titlebar toggle-maximize-horizontally/vertically not working

[André Hertler]

Public bug reported:

Double clicking gnome window titlebar not performing action set with gsettings 
nor gnome-tweaks.
Instead double clicking will maximize the window as if the action 
"toggle-maximize" was performed.

Changing the setting in gnome-tweaks show up in dconf. But the action is
not performed.

Example:

dconf watch /
/org/gnome/desktop/wm/preferences/action-double-click-titlebar
  'toggle-maximize-horizontally'

Steps to reproduce:
1. Run gnome-tweaks
2. Click "Window Titlebars"
3. Set "Titlebar Actions - Double click" and select "Toggle Maximize 
Horizontally"
4. Double click a gnome-terminal titlebar.

Results: Window maximizes fully

Expected results: Window maximizes on the horizontal axis only.

ProblemType: Bug
DistroRelease: Ubuntu 20.04.3 LTS
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 500
DisplayManager: gdm3

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

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

Title:
  Double click titlebar toggle-maximize-horizontally/vertically not
  working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Double clicking gnome window titlebar not performing action set with 
gsettings nor gnome-tweaks.
  Instead double clicking will maximize the window as if the action 
"toggle-maximize" was performed.

  Changing the setting in gnome-tweaks show up in dconf. But the action
  is not performed.

  Example:

  dconf watch /
  /org/gnome/desktop/wm/preferences/action-double-click-titlebar
'toggle-maximize-horizontally'

  Steps to reproduce:
  1. Run gnome-tweaks
  2. Click "Window Titlebars"
  3. Set "Titlebar Actions - Double click" and select "Toggle Maximize 
Horizontally"
  4. Double click a gnome-terminal titlebar.

  Results: Window maximizes fully

  Expected results: Window maximizes on the horizontal axis only.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04.3 LTS
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 500
  DisplayManager: gdm3

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


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

[Desktop-packages] [Bug 1952083] [NEW] Add support for Beige Goby

[Timo Aaltonen]

Public bug reported:

Impact]

New hardware support for AMD's Beige Goby needs a commit backported to
mesa. This is only needed on focal, skipping hirsute (no kernel support
there). Fixed in impish and up.

[Test plan]

Install updates, boot a BG machine and check that the desktop has full
hardware acceleration.

[Where problems could occur]

Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
could go wrong.

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: mesa (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Also affects: mesa (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Description changed:

  Impact]
  
  New hardware support for AMD's Beige Goby needs a commit backported to
  mesa. This is only needed on focal, skipping hirsute (no kernel support
- there).
+ there). Fixed in impish and up.
  
  [Test plan]
  
  Install updates, boot a BG machine and check that the desktop has full
  hardware acceleration.
  
  [Where problems could occur]
  
  Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
  could go wrong.

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

Title:
  Add support for Beige Goby

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New

Bug description:
  Impact]

  New hardware support for AMD's Beige Goby needs a commit backported to
  mesa. This is only needed on focal, skipping hirsute (no kernel
  support there). Fixed in impish and up.

  [Test plan]

  Install updates, boot a BG machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
  could go wrong.

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


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

[Desktop-packages] [Bug 1947820] Re: [SRU] Backport xorg-server 1.20.13 to focal

[Bin Li]

For autopkgtest for pyfai/0.19.0+dfsg1-1build1, it prompts 'timed out',
but I don't know what's the reason.

autopkgtest [08:38:39]: test command2:  - - - - - - - - - - results - - - - - - 
- - - -
command2 FAIL timed out
autopkgtest [08:38:40]:  summary
command1 FAIL non-zero exit status 1
command2 FAIL timed out

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

Title:
  [SRU] Backport xorg-server 1.20.13  to focal

Status in OEM Priority Project:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The delay phenomenon is serious in 'External display mode' during the 
'On-demand' mode working.
  Please reference lp:1940247 and lp:1919118.

  [Fix]
   I installed 21.10 on Raptor12(ThinkPad-P15-Gen-2i), with xorg-server 
2:1.20.13-1ubuntu1 and nvidia-495.38 test driver, this issue is solved. But in 
20.04, it's still 2:1.20.11-1ubuntu1~20.04.2.

  [Test]
  On Raptor12(ThinkPad-P15-Gen-2i), P17 Gen 2 and P1 Gen 4, with latest 20.04, 
it could be reproduced.

  [Where problems could occur]
  Although the nvidia driver is not released, I thought it's no harm to upgrade 
xorg-server first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1947820/+subscriptions


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

[Desktop-packages] [Bug 1947820] Autopkgtest regression report (xorg-server/2:1.20.13-1ubuntu1~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xorg-server 
(2:1.20.13-1ubuntu1~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

aptdaemon/1.1.1+bzr982-0ubuntu32.3 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#xorg-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] Backport xorg-server 1.20.13  to focal

Status in OEM Priority Project:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The delay phenomenon is serious in 'External display mode' during the 
'On-demand' mode working.
  Please reference lp:1940247 and lp:1919118.

  [Fix]
   I installed 21.10 on Raptor12(ThinkPad-P15-Gen-2i), with xorg-server 
2:1.20.13-1ubuntu1 and nvidia-495.38 test driver, this issue is solved. But in 
20.04, it's still 2:1.20.11-1ubuntu1~20.04.2.

  [Test]
  On Raptor12(ThinkPad-P15-Gen-2i), P17 Gen 2 and P1 Gen 4, with latest 20.04, 
it could be reproduced.

  [Where problems could occur]
  Although the nvidia driver is not released, I thought it's no harm to upgrade 
xorg-server first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1947820/+subscriptions


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

[Desktop-packages] [Bug 1949553] Autopkgtest regression report (xorg-server/2:1.20.13-1ubuntu1~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xorg-server 
(2:1.20.13-1ubuntu1~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

aptdaemon/1.1.1+bzr982-0ubuntu32.3 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#xorg-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Incomplete
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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

[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

[Luke Faraone]

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

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


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

[Desktop-packages] [Bug 1949297] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

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

Bug description:
  currently using older kernel since graphic crashs on latest kernel
  while booting

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.11.0-38-generic
  Date: Sun Oct 31 06:39:04 2021
  InstallationDate: Installed on 2021-05-16 (167 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageVersion: 340.108-0ubuntu5.20.04.2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1949297/+subscriptions


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

[Desktop-packages] [Bug 1945770] Re: firefox: Fail to build against OpenSSL 3.0

[Sebastien Bacher]

** Changed in: firefox (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  firefox: Fail to build against OpenSSL 3.0

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Hello,

  As part of a rebuild against OpenSSL3, this package failed to build on one or
  several architectures. You can find the details of the rebuild at 

  https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html

  or for the amd64 failed build, directly at
  
https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098525/+files/buildlog_ubuntu-impish-amd64.firefox_92.0+build3-0ubuntu2.0~ssl3ppa1.1_BUILDING.txt.gz

  We're planning to transition to OpenSSL 3.0 for the 22.04 release, and 
consider
  this issue as blocking for this transition.

  You can find general migration informations at
  https://www.openssl.org/docs/manmaster/man7/migration_guide.html
  For your tests, you can build against libssl-dev as found in the PPA
  schopin/openssl-3.0.0

  Looking at the build failure, the problem lies in the openssl-sys crate.
  It seems the version 0.9.64 of this crate should fix the failure:
  
https://github.com/sfackler/rust-openssl/blob/master/openssl-sys/CHANGELOG.md#v0964---2021-06-18

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


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

[Desktop-packages] [Bug 1945086] Re: nautilus crashed with SIGSEGV in delete_outdated_error_traps().

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1934579
   Nautilus crashes when opening places from the dock contextmenu

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

Title:
  nautilus crashed with SIGSEGV in delete_outdated_error_traps().

Status in nautilus package in Ubuntu:
  New

Bug description:
  nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push().

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: nautilus 1:40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 26 11:16:00 2021
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2021-09-24 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7fd85136f10f:mov0x8(%rbp),%rax
   PC (0x7fd85136f10f) ok
   source "0x8(%rbp)" (0x55fd0084) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_x11_display_error_trap_push () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_x11_screen_supports_net_wm_hint () from 
/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:
   evince40.4-2
   file-roller   3.40.0-2
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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


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

[Desktop-packages] [Bug 1950912] Re: [upstream] Drop-down Calendar menus unreadable in Thunderbird

[Sebastien Bacher]

** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [upstream] Drop-down Calendar menus unreadable in Thunderbird

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  I'm using Thunderbird 91.2.1 in Impish with the Dark Theme.

  The drop-down menus for editing Calendar events (such as options for
  Repeat: and Reminder:) have light text on a light background, and are
  hence unreadable.

  This only started with the move to Impish.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gml44103277 F pulseaudio
  BuildID: 20211020014537
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Nov 14 18:03:28 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-08-13 (458 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp64s0 scope link metric 1000
   192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago)
  dmi.bios.date: 11/15/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TPCS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N151CU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N150CU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist LTD

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


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

[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

[Marian Rainer-Harbach]

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

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


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

[Desktop-packages] [Bug 1945679] Re: character duplicates and log duplicates OS icons and unattended update last night. that was me. i guess. 18.0 > 20.0 upgrade.

[Sebastien Bacher]

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

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

At a minimum, we need:

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

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

Thank you!

** Changed in: firefox (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  character duplicates and log duplicates OS icons and unattended update
  last night. that was me. i guess. 18.0 > 20.0 upgrade.

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Let me know if I can help more thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 92.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  c  1607 F pulseaudio
   /dev/snd/pcmC0D0p:   c  1607 F...m pulseaudio
  BuildID: 20210903235534
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 09:46:22 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:358
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2021-09-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IpRoute:
   default via 192.168.1.1 dev wlx00c0ca9587ea proto dhcp metric 600 
   169.254.0.0/16 dev wlx00c0ca9587ea scope link metric 1000 
   192.168.1.0/24 dev wlx00c0ca9587ea proto kernel scope link src 192.168.1.9 
metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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:358
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=92.0/20210903235534 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to focal on 2021-09-30 (0 days ago)
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: 8CC8400GVQ
  dmi.board.name: 8446
  dmi.board.vendor: HP
  dmi.board.version: 
  dmi.chassis.asset.tag: 8CC8400GVQ
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd05/07/2019:svnHP:pnHPAll-in-One22-c0xx:pvr:rvnHP:rn8446:rvr:cvnHP:ct13:cvr:
  dmi.product.family: 103C_53311M HP OPP
  dmi.product.name: HP All-in-One 22-c0xx
  dmi.product.sku: 3LB95AA#ABA
  dmi.sys.vendor: HP

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


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

[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

[Marian Rainer-Harbach]

The same applies to Chromium, please set it to medium as well, Luka.
Thanks!

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

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


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

[Desktop-packages] [Bug 1944788] Re: URI defined for connectivity check is relative to search domain

[Sebastien Bacher]

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

Thank you for your bug report, that was discussed in bug #1880258 and is
fixed in the current Ubuntu serie

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** This bug has been marked a duplicate of bug 1880258
   Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce 
NXDOMAIN warning noise

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

Title:
  URI defined for connectivity check is relative to search domain

Status in network-manager package in Ubuntu:
  New

Bug description:
  The connectivity check URI as defined in
  /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf is not an
  absolute FQDN (doesn't end in a dot). As such, resolving connectivity-
  check.ubuntu.com generates queries for connectivity-
  check.ubuntu.com.localdomain (assuming a common default search domain
  of "localdomain") in addition to the expected connectivity-
  check.ubuntu.com . Or, if your ISP provided search domain is
  myisp.net, then connectivity-check.ubuntu.com.myisp.net is also
  queried.

  To reduce unintended traffic, may I suggest a trailing dot to ensure
  the host portion of the URI is a FQDN? Ex:

  uri=http://connectivity-check.ubuntu.com./

  # lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  # apt-cache policy network-manager-config-connectivity-ubuntu
  network-manager-config-connectivity-ubuntu:
    Installed: 1.22.10-1ubuntu2.2
    Candidate: 1.22.10-1ubuntu2.2
    Version table:
   *** 1.22.10-1ubuntu2.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.22.10-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages

  # What I expected to happen:
  Sep 23 18:48:45 dnsmasq[415]: query[] connectivity-check.ubuntu.com from 
192.168.0.111
  Sep 23 18:48:45 dnsmasq[415]: query[] connectivity-check.ubuntu.com from 
192.168.0.111
  Sep 23 18:50:55 dnsmasq[415]: query[A] connectivity-check.ubuntu.com from 
192.168.0.111
  (requests resulting in NXDOMAIN or NODATA-IPv6 are made twice)

  # What happened instead:
  Sep 23 17:02:49 dnsmasq[415]: query[] connectivity-check.ubuntu.com from 
192.168.0.111
  Sep 23 17:02:49 dnsmasq[415]: query[] connectivity-check.ubuntu.com from 
192.168.0.111
  Sep 23 17:02:49 dnsmasq[415]: query[] 
connectivity-check.ubuntu.com.localdomain from 192.168.0.111
  Sep 23 17:02:49 dnsmasq[415]: query[] 
connectivity-check.ubuntu.com.localdomain from 192.168.0.111
  Sep 23 17:04:42 dnsmasq[415]: query[A] connectivity-check.ubuntu.com from 
192.168.0.111

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


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

[Desktop-packages] [Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume

[Sebastien Bacher]

It probably doesn't make sense to fix hirsute at this point unless you
need the fix there?

** Changed in: pulseaudio (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: pulseaudio (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Changed in: pulseaudio (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: pulseaudio (Ubuntu Focal)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: pulseaudio (Ubuntu Impish)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: pulseaudio (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  [SRU] pulseaudio: restore hdmi audio be active output after resume

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Hirsute:
  Won't Fix
Status in pulseaudio source package in Impish:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  On the machines with legacy HDA audio driver, when users plug a hdmi/dp 
monitor, the active output device is still speaker, need users to manually 
select the hdmi, then the hdmi audio will be the users' preference, once it is 
plugged, it should become the active output automatically. But with the current 
PA, after reboot and suspend/resume, the hdmi can't change to be active output 
automatically anymore.

  [Fix]
  Backport an upstream fix, this will fix the issue of "preferred ports being 
cleaned by a mistake"

  [Test]
  On a machine with legacy HDA audio driver, install the patched pulseaudio, 
then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi 
audio to be active, with the hdmi monitor plugged and reboot, suspend and 
resume, check what is the active output, it is still the hdmi audio.

  [Where problems could occur]
  This patch is in the card-restore.c, if it could introduce regression, it 
will be on the default active input/output devices, for example, users select a 
input or output device to be active, after reboot, if those devices are 
available, they should be active, but they could be replaced by other devices 
if a regression is introduced. But this possibility is very low since we tested 
the patch on a couple of desktop and laptop machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1951667/+subscriptions


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

[Desktop-packages] [Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume

[Sebastien Bacher]

Upstream fix has landed in
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/484b6986

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

Title:
  [SRU] pulseaudio: restore hdmi audio be active output after resume

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Hirsute:
  In Progress
Status in pulseaudio source package in Impish:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  On the machines with legacy HDA audio driver, when users plug a hdmi/dp 
monitor, the active output device is still speaker, need users to manually 
select the hdmi, then the hdmi audio will be the users' preference, once it is 
plugged, it should become the active output automatically. But with the current 
PA, after reboot and suspend/resume, the hdmi can't change to be active output 
automatically anymore.

  [Fix]
  Backport an upstream fix, this will fix the issue of "preferred ports being 
cleaned by a mistake"

  [Test]
  On a machine with legacy HDA audio driver, install the patched pulseaudio, 
then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi 
audio to be active, with the hdmi monitor plugged and reboot, suspend and 
resume, check what is the active output, it is still the hdmi audio.

  [Where problems could occur]
  This patch is in the card-restore.c, if it could introduce regression, it 
will be on the default active input/output devices, for example, users select a 
input or output device to be active, after reboot, if those devices are 
available, they should be active, but they could be replaced by other devices 
if a regression is introduced. But this possibility is very low since we tested 
the patch on a couple of desktop and laptop machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1951667/+subscriptions


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

[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

[paquin pierre]

Hello,

Thanks for your answers. I did a full update/upgrade and install latest
displaylink driver. I'll let you know if crash still here.

"X server crash in iris driver" subject is still open, no news since 8
months. Any way to know if it's still in progress or if it's on pause? I
just try to know if this problem will be still there in next Ubuntu LTS
release.

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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