date:20220606

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

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

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

Title:
  Screen auto rotates randomly after suspend

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  iio-sensor-proxy: 3.3-0ubuntu6
  mutter: 42.0-3ubuntu2

  
  Since update to Ubuntu 22.04:

  If i leave screen rotation in GNOME enabled and come back form suspend
  mode (open/close Laptop) the screen is rotated wrong. Mostly 90
  degrees left from normal view axis.

  Expected behaviour:

  The screen should not rotate until logged in again or there should be
  a delay before choosing an new rotation whilst laptop is opened.

  Same problem seems to be present in older iio-sensor-proxy versions.

  Mabye affected to Mutter and or iio-sensor-proxy

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


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

[Desktop-packages] [Bug 1934243] Re: thunderbird drag-n-drop move messages fails on Wayland

2022-06-06 Thread Walter

You say "drag-n-drop sometimes fails to work when moving messages. I
attempt to drag a message (or a collection of messages) from one folder
to another, but the attempt to drag fails and nothing happens".

In https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1977715 I
also report that it sometimes fails. But in my case Thunderbird becomes
completely unresponsive.

Could be related.

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

Title:
  thunderbird drag-n-drop move messages fails on Wayland

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 21.04 when I use Thunderbird, drag-n-drop sometimes fails to
  work when moving messages. I attempt to drag a message (or a
  collection of messages) from one folder to another, but the attempt to
  drag fails and nothing happens.

  This occurs when I use the default (Wayland) login. The problem does
  not occur when I use X.org login.

  The problem is intermittent; it may take a few moves for the failures
  to start occurring.

  I reported this issue in bug#1934185 but that bug report is primarily
  about Ubuntu Dock and I was asked to file a separate bug report about
  Thunderbird.

  To file this bug report, I ran "ubuntu-bug" under X.org but the bug
  actually occurs only under Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: thunderbird 1:78.11.0+build1-0ubuntu0.21.04.2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eggert1613919 F pulseaudio
   /dev/snd/controlC1:  eggert1613919 F pulseaudio
  BuildID: 20210528153351
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  1 00:21:11 2021
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2018-08-03 (1062 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.1.1 dev enp5s0 proto static metric 100 
   169.254.0.0/16 dev enp5s0 scope link metric 1000 
   192.168.0.0/24 via 192.168.1.8 dev enp5s0 proto static metric 1 
   192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.9 metric 100 
   192.168.86.0/24 via 192.168.1.7 dev enp5s0 proto static metric 1
  MostRecentCrashID: bp-5d346b68-65ef-4a14-bd19-5d5520200408
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=78.11.0/20210528153351
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-5d346b68-65ef-4a14-bd19-5d5520200408
  UpgradeStatus: Upgraded to hirsute on 2021-06-03 (27 days ago)
  dmi.bios.date: 11/28/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3108
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8C WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3108:bd11/28/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Desktop-packages] [Bug 1958019]

2022-06-06 Thread cam

Songine,

Can you provide more info about your specific model? You should be able 
to get that from running "lshw".

For the top of my output, I get:
version: Legion 7 16ITHg6

On 6/4/22 17:46, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #628 from Songine (donglingluoy...@gmail.com) ---
> Yeah, both the speaker and headphones work fine with correct channel.
>
> And still work after resuming from suspend/hibernate.
>
> Also fine after hotplug events, whatever it is playing or not.
>
> Thanks for your patch a lot!
>
> (In reply to Cameron Berkenpas from comment #627)
>> Great!
>>
>> Some probably silly questions:
>> 1) Do both speakers work? Do you get left channel sound out of the left
>> speaker and right channel sound out of the right speaker?
>>
>> 2) After resuming from suspend/hibernate, does your sound still work?
>>
>> 3) What if you insert headphones and remove them? Does sound still work?
>> Try removing the headphones both while sound is not playing and while
>> it's not.
>>
>> Given that this old quirk works for your laptop, I think all of the
>> above will be fine and I can work toward getting  this submitted.
>>
>>
>> On 6/3/2022 5:34 PM, bugzilla-dae...@kernel.org wrote:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>>>
>>> --- Comment #626 from Songine (donglingluoy...@gmail.com) ---
>>> (In reply to Cameron Berkenpas from comment #625)
 Did you test this yourself?

 On 6/3/22 00:11, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> Songine (donglingluoy...@gmail.com) changed:
>
>   What|Removed |Added
>
>> 
> CC|
> |donglingluoy...@gmail.com
>
> --- Comment #624 from Songine (donglingluoy...@gmail.com) ---
> (In reply to Cameron Berkenpas from comment #429)
>> Created attachment 298789 [details]
>> linux-legion-sound-0.0.13.patch
>>
>> auto mute is now properly disabled as per Takashi's suggestion.
>>
>> This patch is against the latest Linus tree, but applies against 5.14.3
 just
>> fine.
>>
>> This patch includes the presumptive commit message and credit given to
>> various people.
>>
>> Going through the Linux commit log, it seems full names and email
 addresses
>> aren't needed, so I have a thank you list in the patch with the
>> following:
>> Andreas Holzer, Vincent Morel, sycxyc, Max Christian Pohle
>>
>> If you want to be mentioned (or if you know of someone who you think
>> that
>> should be included), please let me know!
>>
>> Here's a link to the patch submission:
>>
>> https://mailman.alsa-project.org/pipermail/alsa-devel/2021-September/189698.
>> html
> Hello, there is a device could use the patch, could you help me add it to
 the
> patch file?
>
> SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021",
> ALC287_FIXUP_YOGA7_14ITL_SPEAKERS),
>
>>> Yes, tested, and I am enjoging my speaker now.�[U+1F603]�
>>>

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266

[Desktop-packages] [Bug 1958019]

2022-06-06 Thread donglingluoying

Sure.

songine@DEBIAN-DUET2021:~$ sudo lshw
debian-duet2021 
description: Detachable
product: 82MA (LENOVO_MT_82MA_BU_idea_FM_Yoga DuetITL 2021)
vendor: LENOVO
version: Yoga DuetITL 2021
serial: YX027470
width: 64 bits
capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32

(In reply to Cameron Berkenpas from comment #629)
> Songine,
> 
> Can you provide more info about your specific model? You should be able 
> to get that from running "lshw".
> 
> For the top of my output, I get:
> version: Legion 7 16ITHg6
> 
> On 6/4/22 17:46, bugzilla-dae...@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >
> > --- Comment #628 from Songine (donglingluoy...@gmail.com) ---
> > Yeah, both the speaker and headphones work fine with correct channel.
> >
> > And still work after resuming from suspend/hibernate.
> >
> > Also fine after hotplug events, whatever it is playing or not.
> >
> > Thanks for your patch a lot!
> >
> > (In reply to Cameron Berkenpas from comment #627)
> >> Great!
> >>
> >> Some probably silly questions:
> >> 1) Do both speakers work? Do you get left channel sound out of the left
> >> speaker and right channel sound out of the right speaker?
> >>
> >> 2) After resuming from suspend/hibernate, does your sound still work?
> >>
> >> 3) What if you insert headphones and remove them? Does sound still work?
> >> Try removing the headphones both while sound is not playing and while
> >> it's not.
> >>
> >> Given that this old quirk works for your laptop, I think all of the
> >> above will be fine and I can work toward getting  this submitted.
> >>
> >>
> >> On 6/3/2022 5:34 PM, bugzilla-dae...@kernel.org wrote:
> >>> https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >>>
> >>> --- Comment #626 from Songine (donglingluoy...@gmail.com) ---
> >>> (In reply to Cameron Berkenpas from comment #625)
>  Did you test this yourself?
> 
>  On 6/3/22 00:11, bugzilla-dae...@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >
> > Songine (donglingluoy...@gmail.com) changed:
> >
> >   What|Removed |Added
> >
> >>
> 
> > CC|
> > |donglingluoy...@gmail.com
> >
> > --- Comment #624 from Songine (donglingluoy...@gmail.com) ---
> > (In reply to Cameron Berkenpas from comment #429)
> >> Created attachment 298789 [details]
> >> linux-legion-sound-0.0.13.patch
> >>
> >> auto mute is now properly disabled as per Takashi's suggestion.
> >>
> >> This patch is against the latest Linus tree, but applies against
> 5.14.3
>  just
> >> fine.
> >>
> >> This patch includes the presumptive commit message and credit given to
> >> various people.
> >>
> >> Going through the Linux commit log, it seems full names and email
>  addresses
> >> aren't needed, so I have a thank you list in the patch with the
> >> following:
> >> Andreas Holzer, Vincent Morel, sycxyc, Max Christian Pohle
> >>
> >> If you want to be mentioned (or if you know of someone who you think
> >> that
> >> should be included), please let me know!
> >>
> >> Here's a link to the patch submission:
> >>
> >>
> https://mailman.alsa-project.org/pipermail/alsa-devel/2021-September/189698.
> >> html
> > Hello, there is a device could use the patch, could you help me add it
> to
>  the
> > patch file?
> >
> > SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021",
> > ALC287_FIXUP_YOGA7_14ITL_SPEAKERS),
> >
> >>> Yes, tested, and I am enjoging my speaker now.�[U+1F603]�
> >>>

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date:

[Desktop-packages] [Bug 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]

2022-06-06 Thread pakaoraki

I report also this bug, which seams to be related to nvidia on Wayland.

I made few test on my hybrid graphic laptop (Dell xps with GTX1050 Ti ):

- Fresh Ubuntu install on Wayland (no nvidia driver): OK.
- With Nvidia 510 driver, on-demand profile set, login Xorg: OK.
- With Nvidia 510 driver, on-demand profile set, login with Wayland: FAILED. I  
got this error:

Gdk-Message: 12:20:26.270: Error 71 (Protocol error) dispatching to Wayland 
display.
I got similar result also with Nvidia profile set instead of on-demand.

- With Nvidia 510 driver, INTEL profile set, login with Wayland: OK.


With Flatpak app (NVIDIA/Wayland):
- Install gnome-extensions with flatpak run org.gnome.Extensions:

The app start BUT you I can’t access to the extensions settings. The
sub-windows can’t open, I got this in logs when I press “setting” button
of an listed extension:

Sender gnome-shell, WL: error in client communication (pid 16887)
Sender: gjs ,Error reading events from display: Protocol error
Sender gnome-shell, Window manager warning: Ping serial 2322697 was reused for 
window W118, previous use was for window W111.

-I also test another similar app on flatpak call 
com.mattjakeman.ExtensionManager:
The app start but when trying to open extensions settings, the sub-windows does 
not open and I got this logs too:

Sender: gjs, Error flushing display: Protocol error
Sender gnome-shell, WL: error in client communication (pid 17125)

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

Title:
  gnome-extensions-app fails to start [Error reading events from
  display: Protocol error]

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

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


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

[Desktop-packages] [Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace

2022-06-06 Thread Andy Chi

I use `thread apply all bt full` to capture the gdb debug message and
use `journalctl -b 0 /usr/bin/gnome-shell` to capture journal log.

** Attachment added: "gnome-shell-stack-trace-202206062108.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5595073/+files/gnome-shell-stack-trace-202206062108.tar.gz

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

Title:
  system freeze and gnome-shell reports multiple stack trace

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New

Bug description:
  [Summary]
  The system will run into freeze if I connect the external monitor through 
DP/HDMI with dongle DA310 or Docking WD19TB

  [Steps to reproduce]
  1. Attact DA310 or WD19TB to DUT
  2. Cold Boot into OS
  3. Plug the DP/HDMI cable to DA310 or WD19TB
  4. Check the external monitor has signal
  5. Click keyboard or move mouse to check system can work well

  [Expected result]
  System won't be freeze with external monitor.

  [Actual result]
  System will be freeze.
  It can be recovered after unplug the external monitor sometime.

  [gnome-shell stack trace]
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]:   ubuntu : TTY=pts/2 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
opened for user root(uid=0) by ubuntu(uid=1001)
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
closed for user root
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.

  This system is using OLED (3456x2160) panel, and I can't reproduce this issue 
on FHD panel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-17 (75 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  Package: gnome-shell 42.1-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-35-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/oem-priority/+bug/1976204/+subscriptions


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

[Desktop-packages] [Bug 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental

2022-06-06 Thread Marc Deslauriers

My understanding is the Debian experimental version doesn't support both
at the same time, it's one or the other depending on which binary
package you install. We definitely don't want that.

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

Title:
  [security review] Sync policykit-1 0.120-6 (main) from Debian
  experimental

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 0.120-6 (main) from Debian experimental

  Changelog entries since current kinetic version 0.105-33:
  https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

  It appears the Debian maintainer is considering switching Debian to the
  updated version in time for the next Debian Stable release (so uploading
  to unstable later this year).

  My requested deadline is August 25, Ubuntu 22.10 Feature Freeze.

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


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

[Desktop-packages] [Bug 1977790] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1977790/+attachment/5595162/+files/Dependencies.txt

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

Title:
  Window could be glitched with Intel + NVIDIA GPU laptops, and prime-
  select set to intel

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  [Summary]
  Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be 
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.

  Either setting gfx.x11-egl-force-disabled to true in about:config, or
  setting prime-select to on-demand or nvidia, makes the issue
  unreproducible.

  Note that through GUI, prime-select cannot be set to intel.

  Reproducibility: 1/8

  [Reproduce Steps]
  1. Run `sudo prime-select intel` in Terminal then reboot
  2. Open Firefox window
  3. Close Firefox window
  4. Repeat until window is glitched (usually Firefox being transparent except 
the borders of the window)

  [Results]
  Expected: Firefox should not have its window glitched
  Actual: Firefox is glitched with window being transparent but the border, and 
every window on top of it draws on the Firefox window.  Video attached.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1753 F pulseaudio
  BuildID: 20220330194208
  CasperMD5CheckResult: skip
  Channel: Unavailable
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-spearow-14p+X215
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-05-25 (12 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IpRoute:
   default via 10.102.142.1 dev enp0s31f6 proto dhcp metric 100 
   default via 10.102.136.1 dev wlp0s20f3 proto dhcp metric 600 
   10.102.136.0/22 dev wlp0s20f3 proto kernel scope link src 10.102.139.188 
metric 600 
   10.102.142.0/23 dev enp0s31f6 proto kernel scope link src 10.102.142.246 
metric 100 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  NoProfiles: True
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: firefox 99.0+build2-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.14.0-1034-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/16/2022
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: RAID
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd05/16/2022:br1.3:svnDellInc.:pnPrecision3470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0BC1:
  dmi.product.family: Precision
  dmi.product.name: Precision 3470
  dmi.product.sku: 0BC1
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 1977790] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1977790/+attachment/5595165/+files/Lspci.txt

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

Title:
  Window could be glitched with Intel + NVIDIA GPU laptops, and prime-
  select set to intel

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  [Summary]
  Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be 
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.

  Either setting gfx.x11-egl-force-disabled to true in about:config, or
  setting prime-select to on-demand or nvidia, makes the issue
  unreproducible.

  Note that through GUI, prime-select cannot be set to intel.

  Reproducibility: 1/8

  [Reproduce Steps]
  1. Run `sudo prime-select intel` in Terminal then reboot
  2. Open Firefox window
  3. Close Firefox window
  4. Repeat until window is glitched (usually Firefox being transparent except 
the borders of the window)

  [Results]
  Expected: Firefox should not have its window glitched
  Actual: Firefox is glitched with window being transparent but the border, and 
every window on top of it draws on the Firefox window.  Video attached.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1753 F pulseaudio
  BuildID: 20220330194208
  CasperMD5CheckResult: skip
  Channel: Unavailable
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-spearow-14p+X215
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-05-25 (12 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IpRoute:
   default via 10.102.142.1 dev enp0s31f6 proto dhcp metric 100 
   default via 10.102.136.1 dev wlp0s20f3 proto dhcp metric 600 
   10.102.136.0/22 dev wlp0s20f3 proto kernel scope link src 10.102.139.188 
metric 600 
   10.102.142.0/23 dev enp0s31f6 proto kernel scope link src 10.102.142.246 
metric 100 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  NoProfiles: True
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: firefox 99.0+build2-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.14.0-1034-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/16/2022
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: RAID
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd05/16/2022:br1.3:svnDellInc.:pnPrecision3470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0BC1:
  dmi.product.family: Precision
  dmi.product.name: Precision 3470
  dmi.product.sku: 0BC1
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 1977790] PciNetwork.txt

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1977790/+attachment/5595166/+files/PciNetwork.txt

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

Title:
  Window could be glitched with Intel + NVIDIA GPU laptops, and prime-
  select set to intel

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  [Summary]
  Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be 
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.

  Either setting gfx.x11-egl-force-disabled to true in about:config, or
  setting prime-select to on-demand or nvidia, makes the issue
  unreproducible.

  Note that through GUI, prime-select cannot be set to intel.

  Reproducibility: 1/8

  [Reproduce Steps]
  1. Run `sudo prime-select intel` in Terminal then reboot
  2. Open Firefox window
  3. Close Firefox window
  4. Repeat until window is glitched (usually Firefox being transparent except 
the borders of the window)

  [Results]
  Expected: Firefox should not have its window glitched
  Actual: Firefox is glitched with window being transparent but the border, and 
every window on top of it draws on the Firefox window.  Video attached.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1753 F pulseaudio
  BuildID: 20220330194208
  CasperMD5CheckResult: skip
  Channel: Unavailable
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-spearow-14p+X215
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-05-25 (12 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IpRoute:
   default via 10.102.142.1 dev enp0s31f6 proto dhcp metric 100 
   default via 10.102.136.1 dev wlp0s20f3 proto dhcp metric 600 
   10.102.136.0/22 dev wlp0s20f3 proto kernel scope link src 10.102.139.188 
metric 600 
   10.102.142.0/23 dev enp0s31f6 proto kernel scope link src 10.102.142.246 
metric 100 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  NoProfiles: True
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: firefox 99.0+build2-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.14.0-1034-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/16/2022
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: RAID
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd05/16/2022:br1.3:svnDellInc.:pnPrecision3470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0BC1:
  dmi.product.family: Precision
  dmi.product.name: Precision 3470
  dmi.product.sku: 0BC1
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 1977790] IpAddr.txt

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1977790/+attachment/5595163/+files/IpAddr.txt

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

Title:
  Window could be glitched with Intel + NVIDIA GPU laptops, and prime-
  select set to intel

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  [Summary]
  Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be 
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.

  Either setting gfx.x11-egl-force-disabled to true in about:config, or
  setting prime-select to on-demand or nvidia, makes the issue
  unreproducible.

  Note that through GUI, prime-select cannot be set to intel.

  Reproducibility: 1/8

  [Reproduce Steps]
  1. Run `sudo prime-select intel` in Terminal then reboot
  2. Open Firefox window
  3. Close Firefox window
  4. Repeat until window is glitched (usually Firefox being transparent except 
the borders of the window)

  [Results]
  Expected: Firefox should not have its window glitched
  Actual: Firefox is glitched with window being transparent but the border, and 
every window on top of it draws on the Firefox window.  Video attached.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1753 F pulseaudio
  BuildID: 20220330194208
  CasperMD5CheckResult: skip
  Channel: Unavailable
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-spearow-14p+X215
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-05-25 (12 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IpRoute:
   default via 10.102.142.1 dev enp0s31f6 proto dhcp metric 100 
   default via 10.102.136.1 dev wlp0s20f3 proto dhcp metric 600 
   10.102.136.0/22 dev wlp0s20f3 proto kernel scope link src 10.102.139.188 
metric 600 
   10.102.142.0/23 dev enp0s31f6 proto kernel scope link src 10.102.142.246 
metric 100 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  NoProfiles: True
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: firefox 99.0+build2-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.14.0-1034-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/16/2022
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: RAID
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd05/16/2022:br1.3:svnDellInc.:pnPrecision3470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0BC1:
  dmi.product.family: Precision
  dmi.product.name: Precision 3470
  dmi.product.sku: 0BC1
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 1977790] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1977790/+attachment/5595161/+files/CurrentDmesg.txt

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

Title:
  Window could be glitched with Intel + NVIDIA GPU laptops, and prime-
  select set to intel

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  [Summary]
  Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be 
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.

  Either setting gfx.x11-egl-force-disabled to true in about:config, or
  setting prime-select to on-demand or nvidia, makes the issue
  unreproducible.

  Note that through GUI, prime-select cannot be set to intel.

  Reproducibility: 1/8

  [Reproduce Steps]
  1. Run `sudo prime-select intel` in Terminal then reboot
  2. Open Firefox window
  3. Close Firefox window
  4. Repeat until window is glitched (usually Firefox being transparent except 
the borders of the window)

  [Results]
  Expected: Firefox should not have its window glitched
  Actual: Firefox is glitched with window being transparent but the border, and 
every window on top of it draws on the Firefox window.  Video attached.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1753 F pulseaudio
  BuildID: 20220330194208
  CasperMD5CheckResult: skip
  Channel: Unavailable
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-spearow-14p+X215
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-05-25 (12 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IpRoute:
   default via 10.102.142.1 dev enp0s31f6 proto dhcp metric 100 
   default via 10.102.136.1 dev wlp0s20f3 proto dhcp metric 600 
   10.102.136.0/22 dev wlp0s20f3 proto kernel scope link src 10.102.139.188 
metric 600 
   10.102.142.0/23 dev enp0s31f6 proto kernel scope link src 10.102.142.246 
metric 100 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  NoProfiles: True
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: firefox 99.0+build2-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.14.0-1034-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/16/2022
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: RAID
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd05/16/2022:br1.3:svnDellInc.:pnPrecision3470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0BC1:
  dmi.product.family: Precision
  dmi.product.name: Precision 3470
  dmi.product.sku: 0BC1
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 1977790] Re: Window could be glitched with Intel + NVIDIA GPU laptops, and prime-select set to intel

apport information

** Tags added: apport-collected focal

** Description changed:

  [Summary]
  Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be 
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.
  
  Either setting gfx.x11-egl-force-disabled to true in about:config, or
  setting prime-select to on-demand or nvidia, makes the issue
  unreproducible.
  
  Note that through GUI, prime-select cannot be set to intel.
  
  Reproducibility: 1/8
  
  [Reproduce Steps]
  1. Run `sudo prime-select intel` in Terminal then reboot
  2. Open Firefox window
  3. Close Firefox window
  4. Repeat until window is glitched (usually Firefox being transparent except 
the borders of the window)
  
  [Results]
  Expected: Firefox should not have its window glitched
  Actual: Firefox is glitched with window being transparent but the border, and 
every window on top of it draws on the Firefox window.  Video attached.
+ --- 
+ ProblemType: Bug
+ AddonCompatCheckDisabled: False
+ ApportVersion: 2.20.11-0ubuntu27.23
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  u  1753 F pulseaudio
+ BuildID: 20220330194208
+ CasperMD5CheckResult: skip
+ Channel: Unavailable
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-focal-amd64-20200502-85+fossa-spearow-14p+X215
+ DistroRelease: Ubuntu 20.04
+ ForcedLayersAccel: False
+ InstallationDate: Installed on 2022-05-25 (12 days ago)
+ InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
+ IpRoute:
+  default via 10.102.142.1 dev enp0s31f6 proto dhcp metric 100 
+  default via 10.102.136.1 dev wlp0s20f3 proto dhcp metric 600 
+  10.102.136.0/22 dev wlp0s20f3 proto kernel scope link src 10.102.139.188 
metric 600 
+  10.102.142.0/23 dev enp0s31f6 proto kernel scope link src 10.102.142.246 
metric 100 
+  169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
+ NoProfiles: True
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: firefox 99.0+build2-0ubuntu0.20.04.2
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RunningIncompatibleAddons: False
+ Tags:  focal
+ Uname: Linux 5.14.0-1034-oem x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 05/16/2022
+ dmi.bios.release: 1.3
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.3.2
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.asset.tag: RAID
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd05/16/2022:br1.3:svnDellInc.:pnPrecision3470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0BC1:
+ dmi.product.family: Precision
+ dmi.product.name: Precision 3470
+ dmi.product.sku: 0BC1
+ dmi.sys.vendor: Dell Inc.

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

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

Title:
  Window could be glitched with Intel + NVIDIA GPU laptops, and prime-
  select set to intel

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  [Summary]
  Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be 
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.

  Either setting gfx.x11-egl-force-disabled to true in about:config, or
  setting prime-select to on-demand or nvidia, makes the issue
  unreproducible.

  Note that through GUI, prime-select cannot be set to intel.

  Reproducibility: 1/8

  [Reproduce Steps]
  1. Run `sudo prime-select intel` in Terminal then reboot
  2. Open Firefox window
  3. Close Firefox window
  4. Repeat until window is glitched (usually Firefox being transparent except 
the borders of the window)

  [Results]
  Expected: Firefox should not have its window glitched
  Actual: Firefox is glitched with window being transparent but the border, and 
every window on top of it draws on the Firefox window.  Video attached.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1753 F pulseaudio
  BuildID: 20220330194208
  CasperMD5CheckResult: skip
  Channel: Unavailable
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more

[Desktop-packages] [Bug 1977655] Re: Nautilus Open Files and Save File... dialogs keep growing

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

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

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

Title:
  Nautilus Open Files and Save File... dialogs keep growing

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  In Firefox and Chrome, each time the Open File(s) or Save File...
  dialog opens, it grows in size. Eventually, it fills the whole screen.
  See attached screen recording taken from Firefox 101.0 (Mozilla
  Firefox Snap for Ubuntu canonical-002 - 1.0).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  4 10:00:40 2022
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
  InstallationDate: Installed on 2022-05-01 (34 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-dropbox  2019.02.14-1ubuntu1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

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


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

[Desktop-packages] [Bug 1972034] Re: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box

2022-06-06 Thread Trogdor

Works as expected in Gedit <-- Name is highlighted, starting to type changes 
name.
Does not work: Firefox <-- Name is highlighted, starting to type does nothing.
Does not work: Brave
Works: VSCode

Interesting... never noticed, but depending on which is doing the
saving, there are two very similar looking but different save dialogs
opened (see attached. Top is browser dialog, bottom is gedit dialog).


** Attachment added: "Save Dialogs: top browser, bottom Gedit"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1972034/+attachment/5595137/+files/Save%20Dialogs.png

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

Title:
  On browser download/save dialog, filename in name box is highlighted
  as if it is active, but typing doesn't edit name unless  you click
  into the box

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  This has bugged me for many years now, and figure as long as the kinks
  are being worked out on this bug:
  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971516 I
  should bring it up:

  When you download a file from a browser, the save dialog pops up, and
  the filename in the name box at the top is highlighted (just the name,
  not the extension), which is the universal symbol for "I'm
  highlighted, start typing and you'll overwrite me!"

  However, typing does nothing unless you click the box, at which point
  the cursor is in the middle of the name, and you have re-highlight if
  you want to rename the file.

  This is still confusing to me after many years.

  Expected behaviour:

  Either: Filename is highlighted and you can start typing to replace
  the name (but not the extension)

  Or: Filname is NOT highlighted by default, indicating you are not
  ready to edit.

  Since Ubuntu 20.04... possibly longer.

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


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

[Desktop-packages] [Bug 1949776] Re: [MIR] wireplumber

2022-06-06 Thread Steve Langasek

Override component to main
wireplumber 0.4.10-2 in kinetic: universe/misc -> main
gir1.2-wp-0.4 0.4.10-2 in kinetic amd64: universe/introspection/optional/100% 
-> main
gir1.2-wp-0.4 0.4.10-2 in kinetic arm64: universe/introspection/optional/100% 
-> main
gir1.2-wp-0.4 0.4.10-2 in kinetic armhf: universe/introspection/optional/100% 
-> main
gir1.2-wp-0.4 0.4.10-2 in kinetic ppc64el: universe/introspection/optional/100% 
-> main
gir1.2-wp-0.4 0.4.10-2 in kinetic riscv64: universe/introspection/optional/100% 
-> main
gir1.2-wp-0.4 0.4.10-2 in kinetic s390x: universe/introspection/optional/100% 
-> main
libwireplumber-0.4-0 0.4.10-2 in kinetic amd64: universe/libs/optional/100% -> 
main
libwireplumber-0.4-0 0.4.10-2 in kinetic arm64: universe/libs/optional/100% -> 
main
libwireplumber-0.4-0 0.4.10-2 in kinetic armhf: universe/libs/optional/100% -> 
main
libwireplumber-0.4-0 0.4.10-2 in kinetic ppc64el: universe/libs/optional/100% 
-> main
libwireplumber-0.4-0 0.4.10-2 in kinetic riscv64: universe/libs/optional/100% 
-> main
libwireplumber-0.4-0 0.4.10-2 in kinetic s390x: universe/libs/optional/100% -> 
main
libwireplumber-0.4-dev 0.4.10-2 in kinetic amd64: 
universe/libdevel/optional/100% -> main
libwireplumber-0.4-dev 0.4.10-2 in kinetic arm64: 
universe/libdevel/optional/100% -> main
libwireplumber-0.4-dev 0.4.10-2 in kinetic armhf: 
universe/libdevel/optional/100% -> main
libwireplumber-0.4-dev 0.4.10-2 in kinetic ppc64el: 
universe/libdevel/optional/100% -> main
libwireplumber-0.4-dev 0.4.10-2 in kinetic riscv64: 
universe/libdevel/optional/100% -> main
libwireplumber-0.4-dev 0.4.10-2 in kinetic s390x: 
universe/libdevel/optional/100% -> main
wireplumber 0.4.10-2 in kinetic amd64: universe/video/optional/100% -> main
wireplumber 0.4.10-2 in kinetic arm64: universe/video/optional/100% -> main
wireplumber 0.4.10-2 in kinetic armhf: universe/video/optional/100% -> main
wireplumber 0.4.10-2 in kinetic ppc64el: universe/video/optional/100% -> main
wireplumber 0.4.10-2 in kinetic riscv64: universe/video/optional/100% -> main
wireplumber 0.4.10-2 in kinetic s390x: universe/video/optional/100% -> main
25 publications overridden.


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

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

Title:
  [MIR] wireplumber

Status in wireplumber package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  The package wireplumber is already in Ubuntu universe.
  The package wireplumber build for the architectures it is designed to work on.
  It currently builds and works for architetcures: amd64 arm64 armhf ppc64el 
riscv64
  Link to package https://launchpad.net/ubuntu/+source/wireplumber

  It's currently failing to build on s390x, which isn't Ubuntu specific and has 
been reported upstream
  https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/49

  [Rationale]
  - The package wireplumber is required in Ubuntu main for

  Pipewire deprecated pipewire-media-session which was provided by the
  same source and requires now either wireplumber or the legacy
  pipewire-media-session which was split in a new source. The upstream
  recommendation is to use wireplumber.

  [Security]
  - No CVEs/security issues in this software in the past
  - no `suid` or `sgid` binaries
  - no executables in `/sbin` and `/usr/sbin`
  - Package installs a service, but they are safe because it has reduced 
permission and its own user
  - Packages does not open privileged ports (ports < 1024)
  - Packages does not contain extensions to security-sensitive software

  [Quality assurance - function/usage]
  - The package works well right after install

  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu and has few non important 
reports
    - Ubuntu https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug
    - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=wireplumber
  - The package does not deal with exotic hardware we cannot support

  [Quality assurance - testing]
  - The package runs a test suite on build time, if it fails
    it makes the build fail, link to build log 
https://launchpadlibrarian.net/564480200/buildlog_ubuntu-jammy-amd64.wireplumber_0.4.4-1_BUILDING.txt.gz
  - The package does not run an autopkgtest since it's role is mostly to route 
audio and video streams according to the hardware configuration available which 
isn't easy a fit for the testing infrastructure.

  We added a testplan for our audio stack on
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Pipewire which also
  covers the dependencies (wireplumber, libfreeaptx, libldac)

  [Quality assurance - packaging]
  - debian/watch is present and works

  - lintian has only minor issues

  # lintian --pedantic
  W: wireplumber source: dependency-is-not-multi-archified 
libwireplumber-0.4-dev depends on

[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide

2022-06-06 Thread Andreas Hasenack

Related: https://bugs.launchpad.net/ubuntu/+source/crypto-
policies/+bug/1926664

(I might create a task here for crypto-policies and close the bug above)

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Fix Released
Status in sssd package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

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


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

[Desktop-packages] [Bug 1977790] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1977790/+attachment/5595167/+files/ProcCpuinfoMinimal.txt

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

Title:
  Window could be glitched with Intel + NVIDIA GPU laptops, and prime-
  select set to intel

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  [Summary]
  Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be 
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.

  Either setting gfx.x11-egl-force-disabled to true in about:config, or
  setting prime-select to on-demand or nvidia, makes the issue
  unreproducible.

  Note that through GUI, prime-select cannot be set to intel.

  Reproducibility: 1/8

  [Reproduce Steps]
  1. Run `sudo prime-select intel` in Terminal then reboot
  2. Open Firefox window
  3. Close Firefox window
  4. Repeat until window is glitched (usually Firefox being transparent except 
the borders of the window)

  [Results]
  Expected: Firefox should not have its window glitched
  Actual: Firefox is glitched with window being transparent but the border, and 
every window on top of it draws on the Firefox window.  Video attached.
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1753 F pulseaudio
  BuildID: 20220330194208
  CasperMD5CheckResult: skip
  Channel: Unavailable
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-spearow-14p+X215
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-05-25 (12 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IpRoute:
   default via 10.102.142.1 dev enp0s31f6 proto dhcp metric 100 
   default via 10.102.136.1 dev wlp0s20f3 proto dhcp metric 600 
   10.102.136.0/22 dev wlp0s20f3 proto kernel scope link src 10.102.139.188 
metric 600 
   10.102.142.0/23 dev enp0s31f6 proto kernel scope link src 10.102.142.246 
metric 100 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  NoProfiles: True
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: firefox 99.0+build2-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.14.0-1034-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/16/2022
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: RAID
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd05/16/2022:br1.3:svnDellInc.:pnPrecision3470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0BC1:
  dmi.product.family: Precision
  dmi.product.name: Precision 3470
  dmi.product.sku: 0BC1
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 1977776] Re: Update gnome-shell to 42.2

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Committed

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

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

Title:
  Update gnome-shell to 42.2

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.2/NEWS

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

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

  Test Case 2
  ---
  Because a GNOME Shell update years ago broke some GNOME Shell extensions, 
it's also requested that we do a basic test of all the extensions included in 
the Ubuntu repositories.

  https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from-
  universe-and-stop-auto-syncs/18437/9

  Install all the extensions.
  Log out and then log back in.
  Use one of the Extensions apps to enable all the extensions.
  Verify that they can all be enabled without showing an error.

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

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

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

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

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


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

[Desktop-packages] [Bug 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock

2022-06-06 Thread Dana Yatsuta

Minor problem I have with the fix: dock is not supposed to be hidden
when there are no windows overlapping with it; however it will hide
anyway if you right click an icon and then click elsewhere to close the
context menu. It will keep hiding until you have some window overlap
with dock area, then its behavior resets to normal.

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

Title:
  Dock auto-hides when a right click context menu is opened while a
  window is under the dock

Status in Dash to dock:
  New
Status in ubuntu-dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Triaged

Bug description:
  [Impact]

  If the dock is set to auto-hide and a window is under the dock, then
  the dock hides prematurely when a menu is opened from one of its
  icons. This only seems to happen with GNOME 42.

  [Test Plan]

  1. Set the dock to auto hide.
  2. Move a window under the dock's position so that it wants to auto-hide.
  3. Open the dock and right click on one of the icons to open a menu.

  Expected: Dock stays open while the menu is open.
  Observed: Dock closes while the menu is open.

  [Where problems could occur]

  This fix may affect any scenarios relating to the dock auto-hiding.

  [Other Info]

  Upstream fixes:
  ubuntu-dock: https://github.com/micheleg/dash-to-dock/pull/1739
  dash-to-dock: https://github.com/micheleg/dash-to-dock/pull/1751

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+subscriptions


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

[Desktop-packages] [Bug 1976354] Re: Jetbrains IDE doesn't focus when click from overview

2022-06-06 Thread Daniel van Vugt

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

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


** This bug has been marked a duplicate of bug 1969574
   [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android 
Studio) with mouse in workspace

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

Title:
  Jetbrains IDE doesn't focus when click from overview

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Bug summary

  I use the activities view to show all open windows. If I click on
  Android Studio, it will not move into foreground. The other windows
  remain as they are. It works with other apps like Chrome or Tilix.

  Steps to reproduce

  
  Move any app into the foreground (e.g., Chrome)
  Open activities overview by clicking the button on the top left
  Click on the android studio window

  What happened

  The android studio window does not move into foreground

  What did you expect to happen

  The android studio window will move into foreground

  Extra info

  The bug was already reported in gnome project. See
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5395. It seems it
  was already fixed in https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/5515#note_1461731.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue May 31 11:14:26 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-22 (2046 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-05-23 (8 days ago)

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


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

[Desktop-packages] [Bug 1977790] [NEW] Window could be glitched with Intel + NVIDIA GPU laptops, and prime-select set to intel

Public bug reported:

[Summary]
Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be glitched 
with laptops with Intel + NVIDIA GPU, and prime-select set to intel.

Either setting gfx.x11-egl-force-disabled to true in about:config, or
setting prime-select to on-demand or nvidia, makes the issue
unreproducible.

Note that through GUI, prime-select cannot be set to intel.

Reproducibility: 1/8

[Reproduce Steps]
1. Run `sudo prime-select intel` in Terminal then reboot
2. Open Firefox window
3. Close Firefox window
4. Repeat until window is glitched (usually Firefox being transparent except 
the borders of the window)

[Results]
Expected: Firefox should not have its window glitched
Actual: Firefox is glitched with window being transparent but the border, and 
every window on top of it draws on the Firefox window.  Video attached.

** Affects: oem-priority
 Importance: Undecided
 Status: New

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


** Tags: oem-priority originate-from-1977786 somerville

** Attachment added: "img_2430_resize.mov"
   
https://bugs.launchpad.net/bugs/1977790/+attachment/5595155/+files/img_2430_resize.mov

** Tags added: oem-priority originate-from-1977786 somerville

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

Title:
  Window could be glitched with Intel + NVIDIA GPU laptops, and prime-
  select set to intel

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  [Summary]
  Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be 
glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel.

  Either setting gfx.x11-egl-force-disabled to true in about:config, or
  setting prime-select to on-demand or nvidia, makes the issue
  unreproducible.

  Note that through GUI, prime-select cannot be set to intel.

  Reproducibility: 1/8

  [Reproduce Steps]
  1. Run `sudo prime-select intel` in Terminal then reboot
  2. Open Firefox window
  3. Close Firefox window
  4. Repeat until window is glitched (usually Firefox being transparent except 
the borders of the window)

  [Results]
  Expected: Firefox should not have its window glitched
  Actual: Firefox is glitched with window being transparent but the border, and 
every window on top of it draws on the Firefox window.  Video attached.

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


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

[Desktop-packages] [Bug 1977655] Re: Nautilus Open Files and Save File... dialogs keep growing

2022-06-06 Thread Trogdor

Related: 
https://askubuntu.com/questions/1405901/ubuntu-22-04-ui-issues-in-app-file-selector-save-prompt-saving-files-and-new-w

Possibly Related:
https://gitlab.gnome.org/GNOME/gtk/-/issues/4136


** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4136
   https://gitlab.gnome.org/GNOME/gtk/-/issues/4136

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

Title:
  Nautilus Open Files and Save File... dialogs keep growing

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  In Firefox and Chrome, each time the Open File(s) or Save File...
  dialog opens, it grows in size. Eventually, it fills the whole screen.
  See attached screen recording taken from Firefox 101.0 (Mozilla
  Firefox Snap for Ubuntu canonical-002 - 1.0).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  4 10:00:40 2022
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
  InstallationDate: Installed on 2022-05-01 (34 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-dropbox  2019.02.14-1ubuntu1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

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


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

[Desktop-packages] [Bug 1977776] Re: Update gnome-shell to 42.2

This bug was fixed in the package gnome-shell - 42.2-0ubuntu1

---
gnome-shell (42.2-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #196)

 -- Jeremy Bicha   Mon, 06 Jun 2022 20:30:49 -0400

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-shell to 42.2

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.2/NEWS

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

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

  Test Case 2
  ---
  Because a GNOME Shell update years ago broke some GNOME Shell extensions, 
it's also requested that we do a basic test of all the extensions included in 
the Ubuntu repositories.

  https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from-
  universe-and-stop-auto-syncs/18437/9

  Install all the extensions.
  Log out and then log back in.
  Use one of the Extensions apps to enable all the extensions.
  Verify that they can all be enabled without showing an error.

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

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

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

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

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


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

[Desktop-packages] [Bug 1977782] [NEW] Unable to open any file:/// URL

2022-06-06 Thread David Kastrup

Public bug reported:

The way this configures/installs the snap makes it impossible to open
any file either from the command-line or by specifying a link of the
file:/// kind.  That makes firefox unusable for browsing local HTML
documentation.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-35.36-lowlatency 5.15.35
Uname: Linux 5.15.0-35-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Tue Jun  7 02:27:27 2022
InstallationDate: Installed on 2011-10-14 (3888 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: Upgraded to jammy on 2022-01-28 (130 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Unable to open any file:/// URL

Status in firefox package in Ubuntu:
  New

Bug description:
  The way this configures/installs the snap makes it impossible to open
  any file either from the command-line or by specifying a link of the
  file:/// kind.  That makes firefox unusable for browsing local HTML
  documentation.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-35.36-lowlatency 5.15.35
  Uname: Linux 5.15.0-35-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Jun  7 02:27:27 2022
  InstallationDate: Installed on 2011-10-14 (3888 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-01-28 (130 days ago)

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


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

[Desktop-packages] [Bug 1970758] Re: Update libadwaita-1 to 1.1.1

This bug was fixed in the package libadwaita-1 - 1.1.2-1ubuntu1

---
libadwaita-1 (1.1.2-1ubuntu1) kinetic; urgency=medium

  * Merge with Debian. Remaining changes:
- Depend on gsettings-desktop-schemas, needed for yaru patch
- debian/patches: Support yaru accent colors using adwaita theming

libadwaita-1 (1.1.2-1) unstable; urgency=medium

  * Team upload

  [ Nathan Pratta Teodosio ]
  * New upstream release

  [ Jeremy Bicha ]
  * Mark autopkgtests as superficial

libadwaita-1 (1.1.1-1) unstable; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release (LP: #1970758)

  [ Marco Trevisan (Treviño) ]
  * debian/control: Add libxml2-utils as B-D to get xmllint

 -- Nathan Pratta Teodosio   Fri, 03 Jun
2022 11:05:32 -0300

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

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

Title:
  Update libadwaita-1 to 1.1.1

Status in libadwaita-1 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  --

  Test Case
  -

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
libadwaita

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

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


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

[Desktop-packages] [Bug 1976547] Re: Update gnome-remote-desktop to 42.2

This bug was fixed in the package gnome-remote-desktop - 42.2-1ubuntu1

---
gnome-remote-desktop (42.2-1ubuntu1) kinetic; urgency=medium

  * Merge with Debian. Remaining change:
- Lower gnome-control-center dependency to 41

gnome-remote-desktop (42.2-1) unstable; urgency=medium

  * New upstream release (LP: #1976547)

 -- Jeremy Bicha   Wed, 01 Jun 2022 14:57:45 -0400

** Changed in: gnome-remote-desktop (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-remote-desktop to 42.2

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  This is a new stable release in the GNOME 42 series

  Test Case #1
  
  Install all updates. Log out and log back in.
  Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote 
Desktop Sharing.
  Turn it off then on because there may be a gnome-control-center bug with 
initial enabling.

  From a second computer, connect to the first computer using Remmina.

  The Remote Desktop page on the first computer provides the username
  and password to use. I wasn't able to get the "Remote Desktop Address"
  to work (maybe avahi doesn't work well?) so just use the first
  computer's IP address.

  So something like:
  RDP jeremy@192.168.1.1

  Ensure that the connection works.

  Test Case #2
  
  Do test case #1 but this time also enable the Legacy VNC option on the Remote 
Desktop Sharing page.
  Connect using VNC instead and ensure that the connection works.

  What Could Go Wrong
  ---
  RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)

  RDP Sharing can be used for providing remote support so it's important
  that this feature works well because it may be difficult for the
  remote admin to fix issues in person.

  gnome-remote-desktop is part of GNOME Core and falls under the GNOME
  Stable Release Update microrelease exception

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

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


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

[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2022-06-06 Thread Jorge Pérez Lara

#23 yes. My laptop is a Nvidia+Intel hybrid laptop. Internal screen now
wakes up (although the lockscreen blurred background is shown black, but
that's a minor issue for me), and external one works perfectly.

I never had performance issues, and once I get past the lockscreen it
just works. Again, on Fedora I simply did not have such a problem. I
wonder what did Canonical do on Ubuntu for this bug to appear.

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

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

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


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

[Desktop-packages] [Bug 1977776] [NEW] Update gnome-shell to 42.2

Public bug reported:

Impact
--
There is a new bugfix release in the stable 42 series.

https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.2/NEWS

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

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

Test Case 2
---
Because a GNOME Shell update years ago broke some GNOME Shell extensions, it's 
also requested that we do a basic test of all the extensions included in the 
Ubuntu repositories.

https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from-
universe-and-stop-auto-syncs/18437/9

Install all the extensions.
Log out and then log back in.
Use one of the Extensions apps to enable all the extensions.
Verify that they can all be enabled without showing an error.

What Could Go Wrong
---
GNOME Shell is the heart of the Ubuntu desktop experience.

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

Smaller bugs could interrupt people's workflows.

GNOME Shell is included in the GNOME micro release exception

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

** Affects: gnome-shell (Ubuntu)
 Importance: Low
 Status: Triaged

** Affects: gnome-shell (Ubuntu Jammy)
 Importance: Low
 Status: Triaged


** Tags: jammy upgrade-software-version

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

** Changed in: gnome-shell (Ubuntu Jammy)
   Importance: Undecided => Low

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

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

Title:
  Update gnome-shell to 42.2

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Jammy:
  Triaged

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.2/NEWS

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

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

  Test Case 2
  ---
  Because a GNOME Shell update years ago broke some GNOME Shell extensions, 
it's also requested that we do a basic test of all the extensions included in 
the Ubuntu repositories.

  https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from-
  universe-and-stop-auto-syncs/18437/9

  Install all the extensions.
  Log out and then log back in.
  Use one of the Extensions apps to enable all the extensions.
  Verify that they can all be enabled without showing an error.

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

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

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

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

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


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

[Desktop-packages] [Bug 1962630] Re: Video playback crashes with SIGSEGV in KernelDll_AllocateStates (intel-media-driver)

2022-06-06 Thread Daniel van Vugt

Upstream fix proposed: https://github.com/intel/media-driver/pull/1423

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

Title:
  Video playback crashes with SIGSEGV in KernelDll_AllocateStates
  (intel-media-driver)

Status in Libva:
  New
Status in intel-media-driver package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid
Status in intel-media-driver source package in Jammy:
  Triaged
Status in totem source package in Jammy:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/a09f9aa6132a1f12a9e44103be3ca0a859abfa2d

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libgstreamer1.0-0 1.20.0-1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 27 15:56:18 2022
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-10 (1177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7fd4c2239ccf:cmpl   $0x1,(%rbx)
   PC (0x7fd4c2239ccf) ok
   source "$0x1" ok
   destination "(%rbx)" (0x7fd57824ec90) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
   () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
   () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
   () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
   () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  Title: totem crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  separator:

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


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

[Desktop-packages] [Bug 1977715] [NEW] thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from INBOX

2022-06-06 Thread Walter

Public bug reported:

SUMMARY
---

When moving e-mail from my INBOX to subfolders Thunderbird hangs and
goes into an unusable state. The '"Thunderbird Mail" is not responding'
pops up, and there is no option but to 'Force Quit' (because 'Wait'
isn't helping).

This does not happen for every move. But yesterday when sorting my
INBOX, it happened more than 5 times in total.


DESCRIPTION
---

When moving mail,
- I select one or more from the middle pane;
- drag it/them to the left (folder pane).
- There, I hover above the right folder and wait for it to highlight.
- Upon highlight, I release the mouse.

Normally this moves the e-mail(s) to that folder, but now I get a
deadlock in about 1 out of 20 moves.

On Focal, I used all versions, including
- 1:91.7.0+build2-0ubuntu0.20.04.1
- 1:91.8.1+build1-0ubuntu0.20.04.1
- 1:91.9.1+build1-0ubuntu0.20.04.1

On Jammy, I'm at:
- 1:91.9.1+build1-0ubuntu0.22.04.1

The first time I noticed this issue, was while I'm on Jammy. But, I
hadn't cleaned my mailbox in a while, so it _might_ be related to the
Thunderbird version. Although I my money would be on the version in
conjunction with Jammy (Wayland?).)


OBSERVATIONS


- My INBOX is not big. It contained 2,500 mails or so. (And very few
large e-mails.) The destination folders aren't particularly big either.
And I didn't see a pattern related to which destination folder.

- When starting thunderbird from the command line, I get lots of these:

###!!! [Parent][DispatchAsyncMessage] Error: 
PClientManager::Msg_ExpectFutureClientSource Processing error: message was 
deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: 
PClientManager::Msg_ForgetFutureClientSource Processing error: message was 
deserialized, but the handler returned false (indicating failure)
Unsupported modifier, resource creation failed.
XXX: resource creation failed
IPDL protocol error: Handler returned error code!

  (But I have no idea what they mean, or whether those log lines were
emitted in the Focal version.)

- Thunderbird runs as a family of three:

/usr/lib/thunderbird/thunderbird
\_ /usr/lib/thunderbird/thunderbird -contentproc -childID 1 -isForBrowser 
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021 
-appdir /usr/lib/thunderbird 549186 true tab
\_ /usr/lib/thunderbird/thunderbird -contentproc -childID 2 -isForBrowser 
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021 
-appdir /usr/lib/thunderbird 549186 true tab

- Main PID has 248 threads, child 1 has 23, child 2 has 22.


ENVIRONMENT
---

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename:   jammy

$ env | grep ^[GXW] | sort | grep -v GPG
GDMSESSION=ubuntu
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
GNOME_SETUP_DISPLAY=:1
GNOME_SHELL_SESSION_MODE=ubuntu
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/6a49f69b_ac07_4c6d_b681_a0dada8d38d3
GNOME_TERMINAL_SERVICE=:1.704
GTK_MODULES=gail:atk-bridge
WAYLAND_DISPLAY=wayland-0
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.0J31M1
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg
XDG_CURRENT_DESKTOP=ubuntu:GNOME
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=ubuntu
XDG_SESSION_TYPE=wayland
XMODIFIERS=@im=ibus


CHILD 1 STRACE
--

(the following keeps repeating every 2 or 3 seconds)

$ sudo strace -tt -fp 549263 -e'!futex,poll,epoll_wait,restart_syscall'
strace: Process 549263 attached with 23 threads
[pid 549277] 11:04:12.121020 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.121709 read(8, "\372", 1) = 1
[pid 549263] 11:04:12.122327 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.122635 write(13, "\0", 1) = 1
[pid 549265] 11:04:12.122921 read(12, "\0", 1) = 1
[pid 549265] 11:04:12.123142 sendmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\4\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2733\377\377"...,
 iov_len=64}, 
{iov_base="\10\223\2\351\0\230\264f\372\";9E\314\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 
iov_len=28}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT 

[pid 549263] 11:04:12.123327 read(8,  
[pid 549265] 11:04:12.123393 <... sendmsg resumed>) = 92
[pid 549263] 11:04:12.123634 <... read resumed>"\372", 1) = 1
[pid 549265] 11:04:12.123759 recvmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\1\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377$f\0\0"...,
 iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT) = 
92
[pid 549265] 11:04:12.123978 write(9, "\372", 1) = 1
[pid 549265] 11:04:12.124299 recvmsg(3, {msg_namelen=0}, MSG_DONTWAIT) = -1 
EAGAIN (Resource temporarily unavailable)
[pid 549263] 11:04:12.124966 read(8, "\372", 1) = 1
[pid

[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2022-06-06 Thread Zingam

Hi Jorge, do you have an external monitor connected via HDMI and an
internal display (a laptop with hybrid graphics Intel + NVIDIA) too? I
can't test this right now.

My original bug report is a big messy. It is more like three separate issue 
into one.
1. Internal monitor doesn't wake up after sleep
2. External monitor doesn't get turned off during sleep
3. Poor performance.
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971149

All described issues aren't present in an Xorg session.

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

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

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


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

[Desktop-packages] [Bug 1969340] Re: onboard hover click cant be activated

2022-06-06 Thread psfox2001

done 3 days ago but not sure to done it correctly

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

Title:
  onboard hover click cant be activated

Status in Onboard:
  New
Status in onboard package in Ubuntu:
  New

Bug description:
  Hover click cant be activated on ubuntu 21.10 
  i launch onboard in a terminal and when
   i try to activate Hover click,  i see the following error :
  (mousetweaks:2139) : CRITICAL ** 11:06:12:270 : Not running in X11 
environment. Aborting 

  same problem in  ubuntu mate 21.10 (with mousetweaks installed) and
  ubuntu 22.04 beta

  I have physical disability
  ,, the Hover click is very important for me
  Thanks

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


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

[Desktop-packages] [Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace

2022-06-06 Thread Andy Chi

Hi @3v1n0,

[steps]
1. Install gnome-shell-dbgsym_42.1-0ubuntu0.1_amd64.ddeb, 
libglib2.0-dev-bin-dbgsym_2.72.1-1_amd64.ddeb, 
libmutter-test-10-dbgsym_42.1-0ubuntu1_amd64.ddeb, 
libglib2.0-0-dbgsym_2.72.1-1_amd64.ddeb, 
libglib2.0-tests-dbgsym_2.72.1-1_amd64.ddeb, 
mutter-10-tests-dbgsym_42.1-0ubuntu1_amd64.ddeb, 
libglib2.0-bin-dbgsym_2.72.1-1_amd64.ddeb, 
libmutter-10-0-dbgsym_42.1-0ubuntu1_amd64.ddeb and 
mutter-dbgsym_42.1-0ubuntu1_amd64.ddeb
2. Plug external monitor
3. Execute `sudo gdb -p $(pidof /usr/bin/gnome-shell) /usr/bin/gnome-shell`
4. Ctrl+C and `bt`
5. `call (void) gjs_dumpstack()`

[journal log]
六  06 16:23:27 ubuntu-XPS-13-9310 gnome-shell[1071]: The offending callback was 
SourceFunc().
 六  06 16:23:27 ubuntu-XPS-13-9310 gnome-shell[1071]: Attempting to run a JS 
callback during garbage collection. This is most likely caused by destroying a 
Clutter a
ctor 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
.

** Attachment added: "20220606-gnome-shell.log.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5595044/+files/20220606-gnome-shell.log.tar.gz

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

Title:
  system freeze and gnome-shell reports multiple stack trace

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New

Bug description:
  [Summary]
  The system will run into freeze if I connect the external monitor through 
DP/HDMI with dongle DA310 or Docking WD19TB

  [Steps to reproduce]
  1. Attact DA310 or WD19TB to DUT
  2. Cold Boot into OS
  3. Plug the DP/HDMI cable to DA310 or WD19TB
  4. Check the external monitor has signal
  5. Click keyboard or move mouse to check system can work well

  [Expected result]
  System won't be freeze with external monitor.

  [Actual result]
  System will be freeze.
  It can be recovered after unplug the external monitor sometime.

  [gnome-shell stack trace]
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]:   ubuntu : TTY=pts/2 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
opened for user root(uid=0) by ubuntu(uid=1001)
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
closed for user root
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.

  This system is using OLED (3456x2160) panel, and I can't reproduce this issue 
on FHD panel.
  --- 
  ProblemType: Bug
  Apport

[Desktop-packages] [Bug 1959747] Re: [upstream] Very high CPU and slow responsiveness in Thunderbird 91

2022-06-06 Thread UlfZibis

I now discovered, that webrender is disabled by default in Firefox 101
on Ubuntu. So the question is, why it is enabled by default in
Thunderbird.

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

Title:
  [upstream] Very high CPU and slow responsiveness in Thunderbird 91

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

Bug description:
  Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just
  moving the mouse cursor over a message list results in 365% CPU for
  me.

  I had to set this in the config editor to fix it:

    gfx.webrender.force-disabled = TRUE

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423

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


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

[Desktop-packages] [Bug 1973816] Update Released

The verification of the Stable Release Update for deja-dup has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Deja Dup's Google support will break in September 2022 for versions <
  43.3

Status in deja-dup package in Ubuntu:
  Fix Committed
Status in deja-dup source package in Jammy:
  Fix Released
Status in deja-dup package in Debian:
  New

Bug description:
  * Impact

  The method Deja-Dup is using to authentificate to google account will
  stop working in september.

  * Test case

  Configure deja-dup to do backups on a google drive account. After
  confirming the authorization through the web browser it should be
  possible to start the backup.

  Check on the webview that the files are correctly added.

  Restore some data and unsure that's working.

  * Regression potential

  The codepath is used for oauth authentification and integration with
  the system mimetype. Check that the webbrowser auth workflow works as
  expected, testing deb and snap based browsers

  --

  Hello! I'm the maintainer of Deja Dup. I was recently made aware that
  Google is removing an oauth workflow that Deja Dup uses, in September.

  Here's their blog post about it:
  https://developers.googleblog.com/2022/02/making-oauth-flows-
  safer.html

  Here's the upstream bug about switching to a new oauth flow:
  https://gitlab.gnome.org/World/deja-dup/-/issues/222

  I've released version 43.3 with a new oauth workflow. This basically
  switches us from redirecting the oauth page to a local
  http://localhost:/ page being served by deja-dup and instead has
  the browser launch a custom URI like
  'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches
  deja-dup and gives it the correct oauth token.

  The key differences for packagers is just to note that now deja-dup
  will register itself as a handler for those weird URI schemes (they
  are specific to deja-dup, as they include its client ids for the
  service).

  I think this deserves a backport to all supported releases. I can whip
  up a patch for you in a bit, just wanted to get this registered as an
  issue.

  To be a bit more specific about what will break:
  - Existing users that have already granted deja-dup access to Google will 
continue to work without any issue.
  - In August, users will see a warning on the oauth screen.
  - And then in September, any new attempt to connect deja-dup to Google will 
not work.

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


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

[Desktop-packages] [Bug 1970411] Update Released

The verification of the Stable Release Update for gnome-remote-desktop
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gnome-remote-desktop-daemon crashes on fuse_thread_func →
  g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
  missing fusermount3)

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in gnome-remote-desktop source package in Jammy:
  Fix Released
Status in gnome-remote-desktop package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  GNOME Remote desktop crashes if fuse3 package is not installed as it provides 
fusermount3, that fuse_session_mount() implicitly requires.

  Test Case
  =
  Verify that gnome-remote-desktop has a dependency on fuse3

  What Could Go Wrong
  ==
  This just adds a dependency.

  This bug should be very uncommon because a system without fuse3 also
  wouldn't have xdg-desktop-portal installed meaning Snaps don't work
  and wouldn't have ubuntu-desktop-minimal installed.

  Other Info
  =
  libfuse3 is currently suggesting fusermount3, I'm wondering if we should 
instead recommending it, given that one of the library function relies on that. 
It's possible for things to use the library without that function so that's why 
it's proposed to be only a Recommends and not a Depends.

  For Ubuntu 22.10, we should see if the kernel can support this
  natively without needing fusermount3 as suggested in comment 1.

  
  Stack trace:

  #0  g_log_structured_array (log_level=, fields=0x7f7859fefdd0, 
n_fields=3) at ../../../glib/gmessages.c:557
  writer_func = 
  writer_user_data = 
  recursion = 
  depth = 
  __func__ = "g_log_structured_array"
  _g_boolean_var_ = 
  #1  0x7f79092e2f99 in g_log_default_handler 
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, 
message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem", unused_data=unused_data@entry=0x0) at 
../../../glib/gmessages.c:3295
  fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 
0x7f790939a109, length = -1}, {key = 0x7f790932a09f  
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 
140157821898257}}
  n_fields = 
  #2  0x7f79092e43fa in g_logv (log_domain=0x0, 
log_level=G_LOG_LEVEL_ERROR, format=, args=) at 
../../../glib/gmessages.c:1387
  domain = 0x0
  data = 0x0
  depth = 
  log_func = 0x7f79092e2ee0 
  domain_fatal_mask = 
  masquerade_fatal = 0
  test_level = 6
  was_fatal = 
  was_recursion = 
  buffer = 
  msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  i = 2
  size = 
  #3  0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, 
log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 
"[FUSE Clipboard] Failed to mount FUSE filesystem") at 
../../../glib/gmessages.c:1456
  args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
  #4  0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at 
../src/grd-rdp-fuse-clipboard.c:1321
  rdp_fuse_clipboard = 0x5605ed301820
  args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
  argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
  result = 

  Further details:
   - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f

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


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

[Desktop-packages] [Bug 1970662] Re: Update gnome-remote-desktop to 42.1.1

This bug was fixed in the package gnome-remote-desktop - 42.1.1-0ubuntu1

---
gnome-remote-desktop (42.1.1-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1970662)
- Fixes black screen with virtio on qemu (LP: #1971195)
  * Drop all patches: applied in new release
  * Depend on libmutter instead of gnome-shell | budgie-desktop
- This is a more accurate dependency
  * Require libmutter 42.1 for Nvidia fixes
  * Depend on fuse3 (Closes: #998846) (LP: #1970411)
  * Don't automatically enable the systemd user service (LP: #1973028)
  * Add postinst to remove the automatic enabling of the user service

 -- Jeremy Bicha   Tue, 17 May 2022 14:27:16 -0400

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-remote-desktop to 42.1.1

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Jammy:
  Fix Released

Bug description:
  NOTE
  
  This adds a dependency on mutter 42.1 so mutter 42.1 needs to reach 
jammy-updates (and I assume fully phased) before we let this update in to 
jammy-updates. The dependency was added to not regress support for Nvidia users.

  Impact
  --
  This is a new stable release in the GNOME 42 series

  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/42.1.1/NEWS

  
  Test Case #1
  
  Install all updates. Log out and log back in.
  Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote 
Desktop Sharing.
  Turn it off then on because there may be a gnome-control-center bug with 
initial enabling.

  From a second computer, connect to the first computer using Remmina.

  The Remote Desktop page on the first computer provides the username
  and password to use. I wasn't able to get the "Remote Desktop Address"
  to work (maybe avahi doesn't work well?) so just use the first
  computer's IP address.

  So something like:
  RDP jeremy@192.168.1.1

  Ensure that the connection works.

  Test Case #2
  
  Do test case #1 but this time also enable the Legacy VNC option on the Remote 
Desktop Sharing page.
  Connect using VNC instead and ensure that the connection works.

  What Could Go Wrong
  ---
  RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)

  RDP Sharing can be used for providing remote support so it's important
  that this feature works well because it may be difficult for the
  remote admin to fix issues in person.

  gnome-remote-desktop is part of GNOME Core and falls under the GNOME
  Stable Release Update microrelease exception

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

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


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

[Desktop-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)

This bug was fixed in the package gnome-remote-desktop - 42.1.1-0ubuntu1

---
gnome-remote-desktop (42.1.1-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1970662)
- Fixes black screen with virtio on qemu (LP: #1971195)
  * Drop all patches: applied in new release
  * Depend on libmutter instead of gnome-shell | budgie-desktop
- This is a more accurate dependency
  * Require libmutter 42.1 for Nvidia fixes
  * Depend on fuse3 (Closes: #998846) (LP: #1970411)
  * Don't automatically enable the systemd user service (LP: #1973028)
  * Add postinst to remove the automatic enabling of the user service

 -- Jeremy Bicha   Tue, 17 May 2022 14:27:16 -0400

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-remote-desktop-daemon crashes on fuse_thread_func →
  g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
  missing fusermount3)

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in gnome-remote-desktop source package in Jammy:
  Fix Released
Status in gnome-remote-desktop package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  GNOME Remote desktop crashes if fuse3 package is not installed as it provides 
fusermount3, that fuse_session_mount() implicitly requires.

  Test Case
  =
  Verify that gnome-remote-desktop has a dependency on fuse3

  What Could Go Wrong
  ==
  This just adds a dependency.

  This bug should be very uncommon because a system without fuse3 also
  wouldn't have xdg-desktop-portal installed meaning Snaps don't work
  and wouldn't have ubuntu-desktop-minimal installed.

  Other Info
  =
  libfuse3 is currently suggesting fusermount3, I'm wondering if we should 
instead recommending it, given that one of the library function relies on that. 
It's possible for things to use the library without that function so that's why 
it's proposed to be only a Recommends and not a Depends.

  For Ubuntu 22.10, we should see if the kernel can support this
  natively without needing fusermount3 as suggested in comment 1.

  
  Stack trace:

  #0  g_log_structured_array (log_level=, fields=0x7f7859fefdd0, 
n_fields=3) at ../../../glib/gmessages.c:557
  writer_func = 
  writer_user_data = 
  recursion = 
  depth = 
  __func__ = "g_log_structured_array"
  _g_boolean_var_ = 
  #1  0x7f79092e2f99 in g_log_default_handler 
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, 
message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem", unused_data=unused_data@entry=0x0) at 
../../../glib/gmessages.c:3295
  fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 
0x7f790939a109, length = -1}, {key = 0x7f790932a09f  
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 
140157821898257}}
  n_fields = 
  #2  0x7f79092e43fa in g_logv (log_domain=0x0, 
log_level=G_LOG_LEVEL_ERROR, format=, args=) at 
../../../glib/gmessages.c:1387
  domain = 0x0
  data = 0x0
  depth = 
  log_func = 0x7f79092e2ee0 
  domain_fatal_mask = 
  masquerade_fatal = 0
  test_level = 6
  was_fatal = 
  was_recursion = 
  buffer = 
  msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  i = 2
  size = 
  #3  0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, 
log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 
"[FUSE Clipboard] Failed to mount FUSE filesystem") at 
../../../glib/gmessages.c:1456
  args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
  #4  0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at 
../src/grd-rdp-fuse-clipboard.c:1321
  rdp_fuse_clipboard = 0x5605ed301820
  args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
  argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
  result = 

  Further details:
   - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f

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


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

[Desktop-packages] [Bug 1971195] Update Released

The verification of the Stable Release Update for gnome-remote-desktop
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gnome-remote-desktop leads to a session crash inside qemu with virtio-
  vga

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Jammy:
  Fix Released

Bug description:
  Impact
  ==
  A minimal QEMU image of Ubuntu Desktop will fail to start after installing. 
This is because of a gnome-remote-desktop crash made worse because the 
gnome-remote-desktop service was always running. This update fixes the crash 
and stops gnome-remote-desktop from running when it's not in use.

  We worked around this bug before the Ubuntu 22.04 LTS release by
  updating osinfo-db so that installs using GNOME Boxes and Virt Manager
  would do the right thing by default. But that didn't help for this
  particular test case.

  Test Case
  =
  1. On a jammy host, create a jammy guest:
  $ qemu-img create -f qcow2 vm.qcow2 50G
  $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device 
virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO]

  2. Install Ubuntu in that VM (minimal install), no problems are
  expected yet.

  3. After the installation is concluded and the VM reboots, try to
  login using the Wayland session (it should be the default, no need to
  select anything). It will fail and bring you back to the login screen
  (apparently due to a gnome-shell crash; I don't think the details are
  relevant to the problem here).

  What is expected: that both the Wayland and X11 sessions work out-of-
  the-box.

  Workaround
  ===
  remove gnome-remote-desktop, and the Wayland session will work just fine in 
the conditions described above. This is why I'm reporting this issue in 
gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be 
wrong though...

  Extra information
  =
  1. gnome-shell starts as expected if the X11 session is selected instead.
  2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it 
work in both the X11 and Wayland sessions:
  $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device 
virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2

  What Could Go Wrong
  ===
  See the master update bug report at LP: #1970662

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


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

[Desktop-packages] [Bug 1971712] Update Released

The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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

[Desktop-packages] [Bug 1971195] Re: gnome-remote-desktop leads to a session crash inside qemu with virtio-vga

This bug was fixed in the package gnome-remote-desktop - 42.1.1-0ubuntu1

---
gnome-remote-desktop (42.1.1-0ubuntu1) jammy; urgency=medium

* New upstream release (LP: #1970662)
- Fixes black screen with virtio on qemu (LP: #1971195)
* Drop all patches: applied in new release
* Depend on libmutter instead of gnome-shell | budgie-desktop
- This is a more accurate dependency
* Require libmutter 42.1 for Nvidia fixes
* Depend on fuse3 (Closes: #998846) (LP: #1970411)
* Don't automatically enable the systemd user service (LP: #1973028)
* Add postinst to remove the automatic enabling of the user service

-- Jeremy Bicha Tue, 17 May 2022 14:27:16 -0400

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Status: Fix Committed => Fix Released

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

Title:
gnome-remote-desktop leads to a session crash inside qemu with virtio-
vga

Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in gnome-remote-desktop source package in Jammy:
Fix Released

Bug description:
Impact
==
A minimal QEMU image of Ubuntu Desktop will fail to start after installing.
This is because of a gnome-remote-desktop crash made worse because the
gnome-remote-desktop service was always running. This update fixes the crash
and stops gnome-remote-desktop from running when it's not in use.

We worked around this bug before the Ubuntu 22.04 LTS release by
updating osinfo-db so that installs using GNOME Boxes and Virt Manager
would do the right thing by default. But that didn't help for this
particular test case.

Test Case
=
1. On a jammy host, create a jammy guest:
$ qemu-img create -f qcow2 vm.qcow2 50G
$ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device
virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO]

2. Install Ubuntu in that VM (minimal install), no problems are
expected yet.

3. After the installation is concluded and the VM reboots, try to
login using the Wayland session (it should be the default, no need to
select anything). It will fail and bring you back to the login screen
(apparently due to a gnome-shell crash; I don't think the details are
relevant to the problem here).

What is expected: that both the Wayland and X11 sessions work out-of-
the-box.

Workaround
===
remove gnome-remote-desktop, and the Wayland session will work just fine in
the conditions described above. This is why I'm reporting this issue in
gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be
wrong though...

Extra information
=
1. gnome-shell starts as expected if the X11 session is selected instead.
2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it
work in both the X11 and Wayland sessions:
$ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device
virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2

What Could Go Wrong
===
See the master update bug report at LP: #1970662

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

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

[Desktop-packages] [Bug 1970662] Update Released

The verification of the Stable Release Update for gnome-remote-desktop
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update gnome-remote-desktop to 42.1.1

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Jammy:
  Fix Released

Bug description:
  NOTE
  
  This adds a dependency on mutter 42.1 so mutter 42.1 needs to reach 
jammy-updates (and I assume fully phased) before we let this update in to 
jammy-updates. The dependency was added to not regress support for Nvidia users.

  Impact
  --
  This is a new stable release in the GNOME 42 series

  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/42.1.1/NEWS

  
  Test Case #1
  
  Install all updates. Log out and log back in.
  Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote 
Desktop Sharing.
  Turn it off then on because there may be a gnome-control-center bug with 
initial enabling.

  From a second computer, connect to the first computer using Remmina.

  The Remote Desktop page on the first computer provides the username
  and password to use. I wasn't able to get the "Remote Desktop Address"
  to work (maybe avahi doesn't work well?) so just use the first
  computer's IP address.

  So something like:
  RDP jeremy@192.168.1.1

  Ensure that the connection works.

  Test Case #2
  
  Do test case #1 but this time also enable the Legacy VNC option on the Remote 
Desktop Sharing page.
  Connect using VNC instead and ensure that the connection works.

  What Could Go Wrong
  ---
  RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)

  RDP Sharing can be used for providing remote support so it's important
  that this feature works well because it may be difficult for the
  remote admin to fix issues in person.

  gnome-remote-desktop is part of GNOME Core and falls under the GNOME
  Stable Release Update microrelease exception

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

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


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

[Desktop-packages] [Bug 1936302] Re: To support elanmoc driver

This bug was fixed in the package libfprint -
1:1.90.2+tod1-0ubuntu1~20.04.8

---
libfprint (1:1.90.2+tod1-0ubuntu1~20.04.8) focal; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Refresh
  * debian/patches: Cherry-pick upstream elanmoc driver support for Elan's
Match on Chip devices (LP: #1936302).

  [ Andy Chi ]
  * d/p/elanmoc-Adjustments-to-protocol-change-passing-an-empty-u.patch:
Cherry-pick upstream fixes for elanmoc driver (LP: #1936302)

 -- Marco Trevisan (Treviño)   Fri, 20 May 2022
15:32:12 +0200

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

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

Title:
  To support elanmoc driver

Status in OEM Priority Project:
  Fix Committed
Status in libfprint package in Ubuntu:
  In Progress
Status in libfprint source package in Focal:
  Fix Released
Status in libfprint source package in Impish:
  Fix Released

Bug description:
  The upstream already accept the Elan fingerprint support.
  https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/278

  This ID is included in upstream.

  [Impact]

   * Devices have elanmoc [04f3:0c7e] fingerprint component will get
 supported.

  [Test Plan]

   * Find a machine with this fingerprint device

   * Launch `settings` and enable `Fingerprint Login`

   * Enroll finger and then logout

   * Login system with enrolled finger

  [Where problems could occur]

   * The only impact will be [04f3:0c7e] will be supported.

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


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

[Desktop-packages] [Bug 1971712] Re: Add support for Intel DG2

This bug was fixed in the package mesa - 22.0.1-1ubuntu2.1

---
mesa (22.0.1-1ubuntu2.1) jammy; urgency=medium

  * Add patches to support Intel DG2. (LP: #1971712)

 -- Timo Aaltonen   Mon, 09 May 2022 13:44:31 +0300

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

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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

[Desktop-packages] [Bug 1973028] Update Released

The verification of the Stable Release Update for gnome-remote-desktop
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gnome-remote-desktop user service is always running

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  The gnome-remote-desktop systemd user service is always running.

  This was a contributing factor for LP: #1971415

  Although it's "harmless" for the user service to be running if remote
  desktop sharing is not enabled, it's a waste of resources to run a
  service if it's not needed.

  Test Case
  -
  Install all Ubuntu updates and the gnome-remote-desktop update.
  From a clean install (or new user), run this command:
  systemctl --user status gnome-remote-desktop.service

  It should show the service as "Active: inactive"

  Open the Settings app to the Sharing page. Turn on Sharing and turn on
  Remote Desktop. Use the systemctl command to verify that the service
  is "Active: active (running). Log out and log back in and reverify.

  Now turn off Remote Desktop Sharing and verify that the service is
  inactive. Log out and log back in and reverify.

  More details
  ---
  This fix uses a dpkg postinst script to remove 
/etc/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service . 
(That file is a symlink to the actual service). We couldn't use 
https://manpages.debian.org/unstable/dpkg-maintscript-helper because the file 
is technically not a "conffile" as recognized by dpkg.

  It also modifies debian/rules so that that file is no longer
  automatically added.

  Instead of /etc/systemd/user/ , the user service is intended to be
  enabled with the symlink ~/.config/systemd/user/gnome-
  session.target.wants/gnome-remote-desktop.service . That is
  appropriate since the GNOME implementation is per-user, not system-
  wide and it is also disabled by default.

  Fixing this bug has been strongly urged by the GNOME Remote Desktop
  maintainers, and this brings us in line with how non-Debian distros
  have been packaging gnome-remote-desktop.

  What could go wrong
  ---
  The RDP and VNC sharing services in GNOME could start when they shouldn't or 
not start when they should.

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


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

[Desktop-packages] [Bug 1973028] Re: gnome-remote-desktop user service is always running

This bug was fixed in the package gnome-remote-desktop - 42.1.1-0ubuntu1

---
gnome-remote-desktop (42.1.1-0ubuntu1) jammy; urgency=medium

-- Jeremy Bicha Tue, 17 May 2022 14:27:16 -0400

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Status: Fix Committed => Fix Released

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

Title:
gnome-remote-desktop user service is always running

Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in gnome-remote-desktop source package in Jammy:
Fix Released

Bug description:
Impact
--
The gnome-remote-desktop systemd user service is always running.

This was a contributing factor for LP: #1971415

Although it's "harmless" for the user service to be running if remote
desktop sharing is not enabled, it's a waste of resources to run a
service if it's not needed.

Test Case
-
Install all Ubuntu updates and the gnome-remote-desktop update.
From a clean install (or new user), run this command:
systemctl --user status gnome-remote-desktop.service

It should show the service as "Active: inactive"

Open the Settings app to the Sharing page. Turn on Sharing and turn on
Remote Desktop. Use the systemctl command to verify that the service
is "Active: active (running). Log out and log back in and reverify.

Now turn off Remote Desktop Sharing and verify that the service is
inactive. Log out and log back in and reverify.

More details
---
This fix uses a dpkg postinst script to remove
/etc/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service .
(That file is a symlink to the actual service). We couldn't use
https://manpages.debian.org/unstable/dpkg-maintscript-helper because the file
is technically not a "conffile" as recognized by dpkg.

It also modifies debian/rules so that that file is no longer
automatically added.

Instead of /etc/systemd/user/ , the user service is intended to be
enabled with the symlink ~/.config/systemd/user/gnome-
session.target.wants/gnome-remote-desktop.service . That is
appropriate since the GNOME implementation is per-user, not system-
wide and it is also disabled by default.

Fixing this bug has been strongly urged by the GNOME Remote Desktop
maintainers, and this brings us in line with how non-Debian distros
have been packaging gnome-remote-desktop.

What could go wrong
---
The RDP and VNC sharing services in GNOME could start when they shouldn't or
not start when they should.

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

[Desktop-packages] [Bug 1936302] Re: To support elanmoc driver

This bug was fixed in the package libfprint -
1:1.90.7+git20210222+tod1-0ubuntu4~21.10.4

---
libfprint (1:1.90.7+git20210222+tod1-0ubuntu4~21.10.4) impish; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Refresh
  * debian/patches: Cherry-pick upstream elanmoc driver support for Elan's
Match on Chip devices (LP: #1936302).

  [ Andy Chi ]
  * d/p/elanmoc-Adjustments-to-protocol-change-passing-an-empty-u.patch:
Cherry-pick upstream fixes for elanmoc driver (LP: #1936302)

 -- Marco Trevisan (Treviño)   Mon, 23 May 2022
22:34:16 +0200

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

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

Title:
  To support elanmoc driver

Status in OEM Priority Project:
  Fix Committed
Status in libfprint package in Ubuntu:
  In Progress
Status in libfprint source package in Focal:
  Fix Committed
Status in libfprint source package in Impish:
  Fix Released

Bug description:
  The upstream already accept the Elan fingerprint support.
  https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/278

  This ID is included in upstream.

  [Impact]

   * Devices have elanmoc [04f3:0c7e] fingerprint component will get
 supported.

  [Test Plan]

   * Find a machine with this fingerprint device

   * Launch `settings` and enable `Fingerprint Login`

   * Enroll finger and then logout

   * Login system with enrolled finger

  [Where problems could occur]

   * The only impact will be [04f3:0c7e] will be supported.

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


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

[Desktop-packages] [Bug 1973564] Update Released

The verification of the Stable Release Update for xdg-desktop-portal-gtk
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Focal:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Focal:
  Fix Released

Bug description:
  * Impact
  The file dialog implementation doesn't return the current filter. It is in 
the spec and it is fixed in newer versions of the portals. But the 1.6.0 
version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

  * Test case

  $ snap install --candidate inkscape.

  In Inkscape if you just draw on the canvas and hit save a save dialog
  will appear. There is a selector at the bottom right that adjust which
  files you see, but also which format you want to save in. So if you
  make your file "test.pdf" and select "Portable Document Format
  (*.pdf)" in the selector you should get a PDF file. Before these
  patches you will get a file "test.pdf" which is actually an SVG file.
  After the patches you'll get a "test.pdf" that is actually a PDF.

  * Regression potential

  That's a change to the fileselector portal so check that opening and
  saving files in a few snaps and flatpaks still works as intended

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


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

[Desktop-packages] [Bug 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04

This bug was fixed in the package xdg-desktop-portal-gtk -
1.6.0-1ubuntu1

---
xdg-desktop-portal-gtk (1.6.0-1ubuntu1) focal; urgency=medium

  * Return the current filter selected from file dialogs
- d/patches/filechooser-current-filter.patch
  (lp: #1973564)

 -- Ted Gould   Wed, 18 May 2022 15:30:59 +0200

** Changed in: xdg-desktop-portal-gtk (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Focal:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Focal:
  Fix Released

Bug description:
  * Impact
  The file dialog implementation doesn't return the current filter. It is in 
the spec and it is fixed in newer versions of the portals. But the 1.6.0 
version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

  * Test case

  $ snap install --candidate inkscape.

  In Inkscape if you just draw on the canvas and hit save a save dialog
  will appear. There is a selector at the bottom right that adjust which
  files you see, but also which format you want to save in. So if you
  make your file "test.pdf" and select "Portable Document Format
  (*.pdf)" in the selector you should get a PDF file. Before these
  patches you will get a file "test.pdf" which is actually an SVG file.
  After the patches you'll get a "test.pdf" that is actually a PDF.

  * Regression potential

  That's a change to the fileselector portal so check that opening and
  saving files in a few snaps and flatpaks still works as intended

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


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

[Desktop-packages] [Bug 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04

This bug was fixed in the package xdg-desktop-portal - 1.6.0-1ubuntu1

---
xdg-desktop-portal (1.6.0-1ubuntu1) focal; urgency=medium

  * Pass the current_filter from XDG Portal save dialogs through
- d/patches/pass-current-filter-on-save.patch
  (lp: #1973564)

 -- Ted Gould   Mon, 16 May 2022 10:58:47 -0500

** Changed in: xdg-desktop-portal (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  File dialog doesn't return current filter in Ubuntu 20.04

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Focal:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Focal:
  Fix Released

Bug description:
  * Impact
  The file dialog implementation doesn't return the current filter. It is in 
the spec and it is fixed in newer versions of the portals. But the 1.6.0 
version doesn't return it.

  This is an issue for Inkscape which uses the filter to select which
  file format someone wishes to save as if they override the defaults.
  This works well on Ubuntu 22.04.

  * Test case

  $ snap install --candidate inkscape.

  In Inkscape if you just draw on the canvas and hit save a save dialog
  will appear. There is a selector at the bottom right that adjust which
  files you see, but also which format you want to save in. So if you
  make your file "test.pdf" and select "Portable Document Format
  (*.pdf)" in the selector you should get a PDF file. Before these
  patches you will get a file "test.pdf" which is actually an SVG file.
  After the patches you'll get a "test.pdf" that is actually a PDF.

  * Regression potential

  That's a change to the fileselector portal so check that opening and
  saving files in a few snaps and flatpaks still works as intended

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


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

[Desktop-packages] [Bug 1977748] [NEW] apport-bug thinks it's running on Xorg

You have been subscribed to a public bug:

Instructed by "ask a question" I tried to file a wayland-targeted bug,
but apport-bug thinks I'm running Xorg.  See
https://answers.launchpad.net/ubuntu/+question/702075

PRETTY_NAME="Ubuntu 22.04 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy

$ ps -ef | grep Xwayland
xx  24931685  0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 
-rootless -noreset -accessx -core -auth 
/run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 
-initfd 7

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
Uname: Linux 5.15.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun  6 06:40:48 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
   Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0991]
InstallationDate: Installed on 2021-10-02 (246 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. XPS 13 9310
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic 
root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/17/2022
dmi.bios.release: 3.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 3.6.0
dmi.board.name: 0MK6WC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
dmi.product.family: XPS
dmi.product.name: XPS 13 9310
dmi.product.sku: 0991
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
apport-bug thinks it's running on Xorg
https://bugs.launchpad.net/bugs/1977748
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1959747] Re: [upstream] Very high CPU and slow responsiveness in Thunderbird 91

2022-06-06 Thread UlfZibis

From another side I got the hint, that miss-configured (web)rendering could be 
the source of the problem and cause lots of time spent in error logging. See:
https://bugzilla.mozilla.org/show_bug.cgi?id=1772673#c11

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

Title:
  [upstream] Very high CPU and slow responsiveness in Thunderbird 91

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

Bug description:
  Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just
  moving the mouse cursor over a message list results in 365% CPU for
  me.

  I had to set this in the config editor to fix it:

    gfx.webrender.force-disabled = TRUE

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423

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


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

[Desktop-packages] [Bug 1976547] Re: Update gnome-remote-desktop to 42.2

** Also affects: gnome-remote-desktop (Ubuntu Jammy)
Importance: Undecided
Status: New

** Description changed:

Impact
--
This is a new stable release in the GNOME 42 series
-
- https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/42.2/NEWS

Test Case #1

Install all updates. Log out and log back in.
Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote
Desktop Sharing.
Turn it off then on because there may be a gnome-control-center bug with
initial enabling.

From a second computer, connect to the first computer using Remmina.

The Remote Desktop page on the first computer provides the username and
password to use. I wasn't able to get the "Remote Desktop Address" to
work (maybe avahi doesn't work well?) so just use the first computer's
IP address.

So something like:
RDP jeremy@192.168.1.1

Ensure that the connection works.

Test Case #2

Do test case #1 but this time also enable the Legacy VNC option on the Remote
Desktop Sharing page.
Connect using VNC instead and ensure that the connection works.

What Could Go Wrong
---
RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42.
(Previously only VNC Sharing was offered.)

RDP Sharing can be used for providing remote support so it's important
that this feature works well because it may be difficult for the remote
admin to fix issues in person.

gnome-remote-desktop is part of GNOME Core and falls under the GNOME
Stable Release Update microrelease exception

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

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

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

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Status: New => In Progress

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

Title:
Update gnome-remote-desktop to 42.2

Status in gnome-remote-desktop package in Ubuntu:
Fix Committed
Status in gnome-remote-desktop source package in Jammy:
In Progress

Bug description:
Impact
--
This is a new stable release in the GNOME 42 series

Test Case #1

From a second computer, connect to the first computer using Remmina.

The Remote Desktop page on the first computer provides the username
and password to use. I wasn't able to get the "Remote Desktop Address"
to work (maybe avahi doesn't work well?) so just use the first
computer's IP address.

So something like:
RDP jeremy@192.168.1.1

Ensure that the connection works.

Test Case #2

Do test case #1 but this time also enable the Legacy VNC option on the Remote
Desktop Sharing page.
Connect using VNC instead and ensure that the connection works.

What Could Go Wrong
---
RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42.
(Previously only VNC Sharing was offered.)

RDP Sharing can be used for providing remote support so it's important
that this feature works well because it may be difficult for the
remote admin to fix issues in person.

gnome-remote-desktop is part of GNOME Core and falls under the GNOME
Stable Release Update microrelease exception

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

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

[Desktop-packages] [Bug 1973816] Re: Deja Dup's Google support will break in September 2022 for versions < 43.3

This bug was fixed in the package deja-dup - 42.9-1ubuntu3

---
deja-dup (42.9-1ubuntu3) jammy; urgency=medium

  * debian/patches/git-goauth-deprecation.patch:
- update the oauth workflow, the local redirection currently used by
  deja-dup is being deprcated by Google and will stop working.
  Thanks Michael Terry providing us backports of the fix!
  (lp: #1973816)

 -- Sebastien Bacher   Fri, 20 May 2022 16:20:58
+0200

** Changed in: deja-dup (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Deja Dup's Google support will break in September 2022 for versions <
  43.3

Status in deja-dup package in Ubuntu:
  Fix Committed
Status in deja-dup source package in Jammy:
  Fix Released
Status in deja-dup package in Debian:
  New

Bug description:
  * Impact

  The method Deja-Dup is using to authentificate to google account will
  stop working in september.

  * Test case

  Configure deja-dup to do backups on a google drive account. After
  confirming the authorization through the web browser it should be
  possible to start the backup.

  Check on the webview that the files are correctly added.

  Restore some data and unsure that's working.

  * Regression potential

  The codepath is used for oauth authentification and integration with
  the system mimetype. Check that the webbrowser auth workflow works as
  expected, testing deb and snap based browsers

  --

  Hello! I'm the maintainer of Deja Dup. I was recently made aware that
  Google is removing an oauth workflow that Deja Dup uses, in September.

  Here's their blog post about it:
  https://developers.googleblog.com/2022/02/making-oauth-flows-
  safer.html

  Here's the upstream bug about switching to a new oauth flow:
  https://gitlab.gnome.org/World/deja-dup/-/issues/222

  I've released version 43.3 with a new oauth workflow. This basically
  switches us from redirecting the oauth page to a local
  http://localhost:/ page being served by deja-dup and instead has
  the browser launch a custom URI like
  'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches
  deja-dup and gives it the correct oauth token.

  The key differences for packagers is just to note that now deja-dup
  will register itself as a handler for those weird URI schemes (they
  are specific to deja-dup, as they include its client ids for the
  service).

  I think this deserves a backport to all supported releases. I can whip
  up a patch for you in a bit, just wanted to get this registered as an
  issue.

  To be a bit more specific about what will break:
  - Existing users that have already granted deja-dup access to Google will 
continue to work without any issue.
  - In August, users will see a warning on the oauth screen.
  - And then in September, any new attempt to connect deja-dup to Google will 
not work.

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


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

[Desktop-packages] [Bug 1977748] Re: apport-bug thinks it's running on Xorg

2022-06-06 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  apport-bug thinks it's running on Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Instructed by "ask a question" I tried to file a wayland-targeted bug,
  but apport-bug thinks I'm running Xorg.  See
  https://answers.launchpad.net/ubuntu/+question/702075

  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy

  $ ps -ef | grep Xwayland
  xx  24931685  0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 
-rootless -noreset -accessx -core -auth 
/run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 
-initfd 7

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  Uname: Linux 5.15.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  6 06:40:48 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0991]
  InstallationDate: Installed on 2021-10-02 (246 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic 
root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2022
  dmi.bios.release: 3.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.6.0
  dmi.board.name: 0MK6WC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

2022-06-06 Thread Paride Legovini

aptly is Fix Release in Kinetic in:

aptly (1.4.0+ds1-7) unstable; urgency=medium

  * Team upload.
  * Add support for zstd compression (Closes: #1010465)


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

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  Fix Released
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  Invalid
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz=1=1
  https://codesearch.debian.net/search?q=control.tar.xz=1=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed already
  ceph- not affected in Ubuntu's version
  circlator   - not affected, just test data
  cowdancer   - not

[Desktop-packages] [Bug 1977757] [NEW] tracker-extract: needs to rebuild shared objects with SHSTK support enabled

2022-06-06 Thread Juro Bystricky

Public bug reported:

When using a kernel compiled with enabled CET shadow stack on CPU
supporting CET, we fail to load various shared libraries. We see the
following journal messages:

Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-jpeg.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-jpeg.so:
 rebuild shared object with SHSTK support enabled
Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-pdf.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-pdf.so: 
rebuild shared object with SHSTK support enabled
Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-tiff.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-tiff.so:
 rebuild shared object with SHSTK support enabled
Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-xps.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-xps.so: 
rebuild shared object with SHSTK support enabled
Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so:
 rebuild shared object with SHSTK support enabled
Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so:
 rebuild shared object with SHSTK support enabled
Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so:
 rebuild shared object with SHSTK support enabled

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: tracker-extract 3.3.0-1
Uname: Linux 5.15.0-mvp3v8-5-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Jun  6 08:31:15 2022
InstallationDate: Installed on 2022-06-03 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: tracker-miners
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tracker-miners (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  tracker-extract: needs to rebuild shared objects with SHSTK support
  enabled

Status in tracker-miners package in Ubuntu:
  New

Bug description:
  When using a kernel compiled with enabled CET shadow stack on CPU
  supporting CET, we fail to load various shared libraries. We see the
  following journal messages:

  Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-jpeg.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-jpeg.so:
 rebuild shared object with SHSTK support enabled
  Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-pdf.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-pdf.so: 
rebuild shared object with SHSTK support enabled
  Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-tiff.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-tiff.so:
 rebuild shared object with SHSTK support enabled
  Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-xps.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-xps.so: 
rebuild shared object with SHSTK support enabled
  Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module 
'/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so':
 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so:
 rebuild shared object with SHSTK support enabled
  Jun 04 11:08:35 juro-ArcherCity

[Desktop-packages] [Bug 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

2022-06-06 Thread Brian Murray

** Tags added: rls-jj-incoming

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

Title:
  NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Situation:

  My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a
  privacy perspective, for readability reasons and for network
  management policies, DHCPv6 should *always* be preferred over SLAAC
  addresses when available. And according to RFC 6724, the smaller /128
  scope of the DHCPv6 address should be chosen over the larger /64 scope
  of the SLAAC address.

  NetworkManager has always been able to adhere to that by simply
  setting ip6.privacy=0 for the connection (in nm-connection-editor
  *not* selecting "Prefer temporary address" for IPv6 privacy
  extensions). Then it would use the DHCPv6 address as the source for
  all outgoing traffic.

  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.

  Regression:

  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection.

  Constantly removing the SLAAC addresses with `ip addr del` or
  disabling SLAAC RA's on the router are now the only ways to stop
  NetworkManager from preferring SLAAC over DHCPv6. None of the local
  options in NetworkManager 1.36.6 are able to restore the previous,
  desired and correct way of working: the SLAAC address should never be
  used as the preferred address if a DHCPv6 lease is given.

  Looking at the changelog of NetworkManager 1.36.6, multiple things
  regarding IP address order and temporary addresses have been changed
  in that release, any of them (or a combination) introducing this bug:

  * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
  * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
  * Ensure temporary IPv6 addresses are removed on disconnect and reapply.

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  Steps to reproduce:

  1. Connect to a network where the router sends "A" and "M" bits in the
  RA's and has a DHCPv6 server running (e.g. any OpenWrt router).

  2. When running `ip -6 a`, the list now sorts SLAAC addresses above
  DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not
  the case. (The Linux kernel uses the address highest in the list as
  preferred.)

  3. When running something like `curl ifconfig.co`, the SLAAC address
  is being returned, which makes sense as that is now preferred by the
  kernel. (But it shouldn't be.)

  Desired behaviour:

  NetworkManager should always sort DHCPv6 addresses above SLAAC
  addresses, as is the case for all versions prior to 1.36.6 and also
  corrected again in 1.38.0. In case static addresses are manually set,
  those should take first priority, with DHCPv6 second and
  SLAAC/autoconf last.

  Implications:

  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in
  all kinds of firewalls to allow me to access servers for my work. Now
  that the "wrong" address is being preferred for outgoing traffic (a
  SLAAC address that I have no influence on and cannot centrally
  configure), I am being locked out of the servers in question unless I
  forcefully remove the addresses or disable SLAAC on my router, so my
  outgoing traffic is being routed through the DHCPv6 address again.

  Note that "just disabling SLAAC RA's on the router" is not something
  everybody can do, as it requires root access to the device. Moreover,
  it would break IPv6 connectivity entirely for devices that don't
  support DHCPv6 (read: Android).

  Conclusion:

  So this update introduces a very breaking change in IPv6 source
  address selection to an LTS release, while LTS releases should be
  stable.

  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should. As that version is also used in Ubuntu kinetic, most likely
  this bug is not present there.

  Looking at the changelog of 1.38.0:

  * Fix bug setting priority for IP addresses.
  * Static IPv6 addresses from "ipv6.addresses" are now preferred over 
addresses from DHCPv6, which are preferred over addresses from autoconf. This 
affects IPv6 source address selection, if the rules from RFC 6724, section 5 
don't give a exhaustive match.

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS

  It looks like Ubuntu just introduced that bug by upgrading to 1.36.6,
  while a proper fix has only

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

2022-06-06 Thread Paul Stejskal

I can confirm this is not resolved. Please prioritize a fix as I cannot
log into Zoom (SSO based login).

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

[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

2022-06-06 Thread Paul Stejskal

Is this scheduled to be fixed soon? My apologies if this may not be the
right bug but I use Firefox and cannot log into the Zoom app behind a
SSO login (as it must go to zoom.us). Firefox already has safeguards
about "are you sure you want to open this" and asks twice. It worked
fine in KUbuntu 21.10 but 22.04 is broken and I cannot log in. This is a
workflow stopper.

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in Mozilla Firefox:
  In Progress
Status in KeePassXC Snap Builds:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  In Progress
Status in goopg package in Ubuntu:
  Confirmed
Status in kdeconnect package in Ubuntu:
  Confirmed
Status in plasma-browser-integration package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

  [Workaround]
  If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with 
this app.

  sudo apt install gnome-shell-extension-manager

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


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

[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

2022-06-06 Thread David D Lowe

@paulstejskal I don't think the issue you are describing is caused by
the bug described in this bug report. You might need to file a separate
bug report or ask for help elsewhere.

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in Mozilla Firefox:
  In Progress
Status in KeePassXC Snap Builds:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  In Progress
Status in goopg package in Ubuntu:
  Confirmed
Status in kdeconnect package in Ubuntu:
  Confirmed
Status in plasma-browser-integration package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

  [Workaround]
  If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with 
this app.

  sudo apt install gnome-shell-extension-manager

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


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

[Desktop-packages] [Bug 1977772] [NEW] Update gnome-desktop to 42.2

Public bug reported:

Impact
--
This updates the GNOME version number shown in the GNOME Settings > About 
dialog from 42.1 to 42.2

And it skips the bubblewrap sandbox for the thumbnailer for Snap apps
(this had been done previously for Flatpak). This is useful for the
Cheese snap.

Test Case
-
Install the updated packages
Open the Settings app.
Scroll down in the left sidebar and click About
The GNOME Version should be 42.2

What Could Go Wrong
---
Because this is part of core GNOME, it falls under the
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

** Affects: gnome-desktop (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: gnome-desktop (Ubuntu Jammy)
 Importance: Medium
 Status: In Progress


** Tags: jammy upgrade-software-version

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

** Changed in: gnome-desktop (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: gnome-desktop (Ubuntu Jammy)
   Status: New => In Progress

** Description changed:

  Impact
  --
  This updates the GNOME version number shown in the GNOME Settings > About 
dialog from 42.1 to 42.2
  
- And it skips the bubblewrap sandbox for Snap apps (this had been done
- previously for Flatpak). This is useful for the Cheese snap.
+ And it skips the bubblewrap sandbox for the thumbnailer for Snap apps
+ (this had been done previously for Flatpak). This is useful for the
+ Cheese snap.
  
  Test Case
  -
  Install the updated packages
  Open the Settings app.
  Scroll down in the left sidebar and click About
  The GNOME Version should be 42.2
  
  What Could Go Wrong
  ---
  Because this is part of core GNOME, it falls under the
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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

Title:
  Update gnome-desktop to 42.2

Status in gnome-desktop package in Ubuntu:
  Fix Released
Status in gnome-desktop source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  This updates the GNOME version number shown in the GNOME Settings > About 
dialog from 42.1 to 42.2

  And it skips the bubblewrap sandbox for the thumbnailer for Snap apps
  (this had been done previously for Flatpak). This is useful for the
  Cheese snap.

  Test Case
  -
  Install the updated packages
  Open the Settings app.
  Scroll down in the left sidebar and click About
  The GNOME Version should be 42.2

  What Could Go Wrong
  ---
  Because this is part of core GNOME, it falls under the
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


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

[Desktop-packages] [Bug 1976256] Re: fprintd ftbfs in the jammy release pocket

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

** Also affects: fprintd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009395
   Importance: Unknown
   Status: Unknown

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

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

Title:
  fprintd ftbfs in the jammy release pocket

Status in fprintd package in Ubuntu:
  Fix Committed
Status in fprintd source package in Jammy:
  Triaged
Status in fprintd package in Debian:
  Unknown

Bug description:
  as seen in a test rebuild, this package fails to build in the jammy
  release pocket (note the log behind the link might go away):

  https://launchpadlibrarian.net/604216188/buildlog_ubuntu-jammy-
  amd64.fprintd_1.94.2-1_BUILDING.txt.gz

  [...]

  ==
  ERROR: test_pam_timeout (__main__.TestPamFprintd)
  --
  Traceback (most recent call last):
File "/<>/tests/pam/test_pam_fprintd.py", line 327, in 
test_pam_timeout
  self.setup_device()
File "/<>/tests/pam/test_pam_fprintd.py", line 85, in 
setup_device
  device_path = self.obj_fprintd_mock.AddDevice('FDO Trigger Finger Laser 
Reader', 3, 'swipe')
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
  return self._connection.call_blocking(self._named_service,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in 
call_blocking
  reply_message = self.send_message_with_reply_and_block(
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.InvalidArgs: 
Invalid arguments: More items found in D-Bus signature than in Python arguments

  --
  Ran 1 test in 0.251s

  FAILED (errors=1)
  stderr:
  PWRAP_DEBUG[ (19455)] - pwrap_init: Initialize pam_wrapper
  PWRAP_DEBUG[ (19455)] - copy_confdir: Copy config files from 
/<>/obj-x86_64-linux-gnu/tests/pam/services to /tmp/pam.q
  PWRAP_DEBUG[ (19455)] - pwrap_init: Successfully initialized 
pam_wrapper
  PWRAP_DEBUG[ (19457)] - pwrap_init: Initialize pam_wrapper
  PWRAP_DEBUG[ (19457)] - copy_confdir: Copy config files from 
/<>/obj-x86_64-linux-gnu/tests/pam/services to /tmp/pam.s
  PWRAP_DEBUG[ (19457)] - pwrap_init: Successfully initialized 
pam_wrapper
  PWRAP_DEBUG[ (19460)] - pwrap_init: Initialize pam_wrapper
  PWRAP_DEBUG[ (19460)] - copy_confdir: Copy config files from 
/<>/obj-x86_64-linux-gnu/tests/pam/services to /tmp/pam.0
  PWRAP_DEBUG[ (19460)] - pwrap_init: Successfully initialized 
pam_wrapper
  --

  531/531 fprintd:dist / check-translations 

 OK   0.17s
  08:35:21 G_SLICE=always-malloc MALLOC_CHECK_=2 MALLOC_PERTURB_=96 
/<>/po/check-translations.sh
  --- output ---
  --

  
  Summary of Failures:

  496/531 fprintd:+test_fprintd_utils+TestFprintdUtils / 
TestFprintdUtils.test_fprintd_delete
FAIL 0.33s  
 exit status 1
  498/531 fprintd:+test_fprintd_utils+TestFprintdUtils / 
TestFprintdUtils.test_fprintd_enroll
FAIL 0.33s  
 exit status 1
  499/531 fprintd:+test_fprintd_utils+TestFprintdUtils / 
TestFprintdUtils.test_fprintd_list  
FAIL 0.31s  
 exit status 1
  504/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify / 
TestFprintdUtilsVerify.test_fprintd_list_all_fingers
  FAIL 0.31s   exit 
status 1
  505/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify / 
TestFprintdUtilsVerify.test_fprintd_multiple_verify_fails   
  FAIL 0.32s   exit 
status 1
  506/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify / 
TestFprintdUtilsVerify.test_fprintd_verify  
  FAIL 0.31s   exit 
status 1
  507/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify / 
TestFprintdUtilsVerify.test_fprintd_verify_any_finger_identification

[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS

2022-06-06 Thread fprietog

Just updated to these packages:

- gnome-remote-desktop (42.1.1-0ubuntu1)
- libfreerdp2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1)
- libfreerdp-server2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1)
- libfreerdp-client2-2:arm64 (2.6.1+dfsg1-3ubuntu2.1)

And VNC and RPD sharing are working now in arm64 (Raspberry Pi 4B). So
bug seems to be fixed.

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

Title:
  VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu
  22.04 LTS

Status in gnome-remote-desktop package in Ubuntu:
  In Progress

Bug description:
  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  # apt-cache policy gnome-remote-desktop
  gnome-remote-desktop:
Instalados: 42.0-4ubuntu1
Candidato:  42.0-4ubuntu1
Tabla de versión:
   *** 42.0-4ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
  100 /var/lib/dpkg/status

  # uname -a
  Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  
  Summary of the bug:
  ---
  When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 
Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect 
(connection is refused). The connection passes the Password check validation 
but don't connect (sometimes shows screen garbage before disconnecting).

  I've used several VNC clients (Remmina in Ubuntu and Real VNC in
  Android) getting the same problem failing either in X11 or Wayland.

  Notes: 
  - VNC connection does work in in previous Ubuntu 21.10 version with the same 
architecture (arm64) and same Raspberry Pi.
  - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and 
gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that 
doesn't work on arm64 (Raspberry Pi).

  There is no apport info at all. Also there is almost no info in the
  journal regarding this problem. When I try to connect to VNC server it
  show this:

  On Wayland:
  ---
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
1884160 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
4169728 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
8130560 bytes), total 32768 (slots), used 83 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
8294400 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
8294400 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
8294400 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 
8294400 bytes), total 32768 (slots), used 3 (slots)
  abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main 
process exited, code=killed, status=11/SEGV
  abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed 
with result 'signal'.
  abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions 
vanished
  abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 1.
  abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop.
  abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop...
  abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop.
  abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load 
libcuda.so.1
  abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load 
libnvidia-encode.so.1
  abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started
  abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started

  
  On X11:
  ---
  abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main 
process exited, code=killed, status=11/SEGV
  abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions 
vanished
  abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed 
with result 'signal'.
  abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 19.
  abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop.
  abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop...
  abr 25 00:12:18 fpgrpi systemd[2859]: Started GNOME Remote Desktop.
  abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load 
libcuda.so.1
  abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load 
libnvidia-encode.so.1
  abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: RDP server started
  abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: VNC server

[Desktop-packages] [Bug 1969509]

2022-06-06 Thread Emilio

Created attachment 9279754
Bug 1772693 - Don't transition from fullscreen -> maximized on double-click. 
r=stransky


It's probably unexpected (even though after the patch above it behaves
properly).

Depends on D148340

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

Title:
  [snap] Unmaximized but not unfullscreened

Status in Mozilla Firefox:
  In Progress
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 21.10
  Firefox 99.0.1-1 from snap

  With title bar hidden:
   maximize Firefox window
   set it full-screen
   move cursor to the upper edge of the screen
   double-click the bar

  The window ends up in unexpected state

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


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

[Desktop-packages] [Bug 1969509]

2022-06-06 Thread Emilio

Created attachment 9279753
Bug 1772693 - Fix transition from fullscreen to maximized. r=stransky


We don't call MakeFullScreen(false), causing weirdness. This is needed even
with the next patch because otherwise other things like grabbing the tabbar
cause the same kind of weirdness.

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

Title:
  [snap] Unmaximized but not unfullscreened

Status in Mozilla Firefox:
  In Progress
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 21.10
  Firefox 99.0.1-1 from snap

  With title bar hidden:
   maximize Firefox window
   set it full-screen
   move cursor to the upper edge of the screen
   double-click the bar

  The window ends up in unexpected state

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


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

[Desktop-packages] [Bug 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental

Marc, the current Debian experimental version supports both PKLA and JS
policy files. Are you saying that you only want one style to be
supported in an Ubuntu release?

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

Title:
  [security review] Sync policykit-1 0.120-6 (main) from Debian
  experimental

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 0.120-6 (main) from Debian experimental

  Changelog entries since current kinetic version 0.105-33:
  https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

  It appears the Debian maintainer is considering switching Debian to the
  updated version in time for the next Debian Stable release (so uploading
  to unstable later this year).

  My requested deadline is August 25, Ubuntu 22.10 Feature Freeze.

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


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

[Desktop-packages] [Bug 1969509] Re: [snap] Unmaximized but not unfullscreened

2022-06-06 Thread Bug Watch Updater

** Changed in: firefox
   Status: New => In Progress

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

Title:
  [snap] Unmaximized but not unfullscreened

Status in Mozilla Firefox:
  In Progress
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 21.10
  Firefox 99.0.1-1 from snap

  With title bar hidden:
   maximize Firefox window
   set it full-screen
   move cursor to the upper edge of the screen
   double-click the bar

  The window ends up in unexpected state

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


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

[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS